BMDS errors galore – after removing old Java version from BES server

If you see a wild spike in your Application Log in the magnitude of thousands of critical errors from the source BMDS (error 0), then you likely just removed Java.

Actually you specifically removed an older version that your BES was pointing to in a registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BlackBerry MDS Connection Service

In the ImagePath String Value you’ll find what needs changed.  Here is an example of such a value :

“D:\Program Files\Research in Motion\BlackBerry Enterprise Server\MDS\bin\bmds.exe” -s jvmpath=”C:\Program Files\Java\jre1.6.0_07\bin\client\jvm.dll” -XX:+DisableExplicitGC -Xss64K -Xmx768M -Xms128M classpathdir=”D:\Program Files\Research in Motion\BlackBerry Enterprise Server\MDS\classpath\\” wrkdir=”D:\Program Files\Research in Motion\BlackBerry Enterprise Server\MDS\Servers\SERVER1\\” webserverdir=”D:\Program Files\Research in Motion\BlackBerry Enterprise Server\MDS\webserver\\” -rbes “SERVER1_MDS-CS_1″

That assumes that the BES server’s name is SERVER1.  Let’s say you just installed JAVA Runtime Engine version 1.6.07 on the server and removed all earlier versions.  Your path would need to reflect this version as it does above.

***this path has been updated as of Java 6.10:  http://duitwithsbs.wordpress.com/2008/11/29/blackberry-server-software-mds-java-update-mayhem/ ***

Kudos to Armando Diaz for his Event ID contribution:  http://eventid.net/display.asp?eventid=0&eventno=8647&source=BMDS&phase=1