Installing or upgrading to BES 4.0 causes Mobile Data Service to fail

[BESadmin]

Installing or upgrading to BES 4.0 causes Mobile Data Service to fail

Environment

• BlackBerry® Enterprise Server software version 3.6 to 4.1 Service Pack 2 for Microsoft® Exchange
• BlackBerry Mobile Data Service
• SDR43228
• SDR45626

Problem

Warning: The external version of this article does not include a resolution for Cause 1. Instead, customers are instructed to contact their service providers.

If you install or upgrade to any version between BlackBerry Enterprise Server software version 4.0 and 4.1 Service Pack 2, the BlackBerry Mobile Data Service repeatedly terminates. The Microsoft Windows® Event Log displays the following:

The BlackBerry Mobile Data Service service terminated unexpectedly. It has done this <X> time(s). The following corrective action will be taken in 0 milliseconds: No Action.

Note: To determine the cause, refer to the initialization.log file located in C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Current Date\.

Cause

Summary of Causes
This problem may be caused by one of the following:

1. MDSConfig table is not updated correctly.
2. Multiple BlackBerry Enterprise Server installations.
3. BlackBerry Mobile Data Service file system migration failure.

Resolution

Cause 1

If you upgrade from BlackBerry Enterprise Server 3.6 Service Pack 3 or later, the MDSConfig table located within the Microsoft SQL database is not updated correctly. The Initialization log displays the following:

net.rim.shared.service.ServiceException:
net.rim.bmds.shared.service.authorization.JDBCAuthorizationDatastore
at net.rim.shared.service.vxww.startServices(Unknown Source)
at net.rim.application.ipproxyservice.IPProxyServiceApplication.initialize(Unknown Source)
at net.rim.application.ipproxyservice.IPProxyServiceApplication.<init>(Unknown Source)
at net.rim.application.ipproxyservice.IPProxyServiceApplication.main(Unknown Source)

Resolution 1

Contact your technical support representative. Please have the following information ready:

• BlackBerry Enterprise Server debug logs
• A copy of the BlackBerry Enterprise Server Management database for both version 4.0 and the previous version.

Cause 2

There are multiple BlackBerry Enterprise Server software installations where the BlackBerry Enterprise Server is renamed. You see the following in the initialization.log file:

rimmir.mirrim.mir.zvzy: MDS is not running from MDS home!
at net.rim.application.ipproxyservice.IPProxyServiceApplication.initialize(Unknown Source)
at net.rim.application.ipproxyservice.IPProxyServiceApplication.<init>(Unknown Source)
at net.rim.application.ipproxyservice.IPProxyServiceApplication.main(Unknown Source)

You may also see multiple instances of the BlackBerry Enterprise Server listed in BlackBerry Manager, with different Service Routing Protocol (SRP) connectivity states, or multiple instances of BlackBerry Enterprise Server listed in the following path:

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\Servers

The original BlackBerry Enterprise Server folder contains this full set of directories:

1. Conf
2. Config
3. Logs
4. Work

Resolution 2

After you determine which instance of the BlackBerry Enterprise Server software is the original, uninstall the new instances, then reinstall the BlackBerry Enterprise Server with the original BlackBerry Enterprise Server name.

Cause 3

During the upgrade from BlackBerry Enterprise Server software version 3.6, some BlackBerry Mobile Data Service files do not migrate correctly. In this case, no BlackBerry Mobile Data Service logs are created. When you start the BlackBerry Mobile Data Service, the BlackBerry Application Log reports errors similar to the following:

Event Type:  Error
Event Source: MDS_BES40
Event Category:    None
Event ID:    15000
Description:
The description for Event ID ( 15000 ) in Source ( MDS_BES40 ) cannot be found. The local computer may not
 have the necessary registry information or message DLL files to display messages from a remote computer. 
You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. 
The following information is part of the event: <2005-01-25 10:41:59 EST>:[10]:<MDS_BES40>:<ERROR>:
<LAYER = MDS, Invalid zipfile Could not initialize for verifying with the given key.>

Resolution 3

To verify and correct the BlackBerry Mobile Data Service file system migration, complete the following steps:

1. Locate the mdsweb.jar file in C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\Servers\<servername>\conf. Note: The mdsweb.jar file size should be 238.751 bytes, and it should be dated 01.11.2004 (for BlackBerry Enterprise Server software version 4.0).
2. If the values in the mdsweb.jar file are different than in the Note above, use a file extractor to extract a copy of the mdsweb.jar file from data.cab on the installation CD. The extracted file has a different prefix, so you must rename it and copy it to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\Servers\<servername>\conf. For example, when the mdsweb.jar file is extracted from data.cab, it is named F130_mdsweb.jar. You must delete the F130_ portion of the file name before you copy the file.
3. Check the entire contents of C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\ClassPath against a BlackBerry Enterprise Server software version 4.0 with a functioning BlackBerry Mobile Data Service.
4. If any of the files are older than 01.11.2004, or are missing when compared to BlackBerry Enterprise Server 4.0 with a functioning BlackBerry Mobile Data Service, extract the missing files from data.cab on the installation CD, remove the prefixes so they are correctly named, and copy them to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\ClassPath.