Remotely installed BlackBerry MDS Connection Services fail to start after applying MR7

Article ID: KB36027

Type: Support Content

Last Modified: 06-10-2014


Product(s) Affected:

  • BlackBerry Enterprise Server for Novell GroupWise
  • BlackBerry Enterprise Server for Novell GroupWise v5.0 SP4 MR7
  • JI 701036

The remotely installed BlackBerry MDS Connection Service failed to start after applying MR7 to BlackBerry Enterprise Server for GroupWise 5.0 SP4.


While starting the service, it was seen that bmds.exe was unable to load MSVCR100.dll and aborted initialization as the file was not found.

The following event will be logged in the Windows Event Viewer:

Service could start up the JVM C:\Program Files (x86)\Java\jre1.7.0_51\bin\client\jvm.dll

[EN= 126] [EMSG= 桔⁥灳捥晩敩⁤潭畤敬挠畯摬渠瑯戠⁥潦湵(error code = 126)] [SRC=尮潳牵散橜癡獡牥敶⹲c][LINE=444]

During installation, the installer did not copy MSVCR100.dll to the required location and prevents the BlackBerry MDS Connection Service from starting if an appropriate version's location is not in the PATH statement for the server. This issue is not seen on a server that hosts multiple components that also require the library file MSVCR100.dll, it has only been seen on servers hosting a standalone remote component install of BlackBerry MDS Connection Service.

This is a previously reported issue that is being investigated by our development team. A resolution is currently unavailable.

Copy the MSVCR100.dll file from this location:

C:\Program Files (x86)\Java\jre1.7.0_51\bin

To the following two locations:

C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\MDS\Bin\

C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\BAS\external\bin\


By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.

Visit the BlackBerry Technical Solution Center at