Free BlackBerry Support Incident
When you order BlackBerry Enterprise Server Express which is free, it comes with a complimentary support incident. This support incident is normally $249 and provides the same level of support that you would otherwise pay for. To take advantage of this offer log into the BlackBerry Expert Support Center with the username/password you were provided when you ordered the software. Once you are logged in click on "My Service Requests - Complimentary Support" which will have you fill out some contact information.
Once you have filled out the obligatory information you will be able to create your support incident and will receive a Service Request ID. Rather than waiting for Research In Motion to contact you, I would suggest calling (877) 255-2377 (toll free) or (519) 888-6181. Select option 2 for technical support, followed by option 4 so that you can speak with a technician. Remember, this is a one time deal so use it wisely.
BlackBerry Monitoring Console Service Wont Start With “service-specific error code 0″
At the time of this post the following BlackBerry KB is a draft and not available on their site. This problem occurs after applying service pack 1 which was the case with one of our clients.
Environment
BlackBerry Enterprise Server version 5.0
BlackBerry Monitoring Service version 5.0
Overview
After installing or upgrading to BlackBerry Monitoring Service 5.0, the BlackBerry Monitoring Console service will not start up. When attempting to start the service the following error is observed:
The Tomcat logs for the BlackBerry Monitoring Service record the following entries:
[2009-12-13 13:22:06] [info] Procrun (2.0.3.0) started
[2009-12-13 13:22:06] [info] Running Service...
[2009-12-13 13:22:06] [info] Starting service...
[2009-12-13 13:22:06] [174 javajni.c] [error] The specified module could not be found.
[2009-12-13 13:22:06] [986 prunsrv.c] [error] Failed creating java \jre\bin\client\jvm.dll
[2009-12-13 13:22:06] [1260 prunsrv.c] [error] ServiceStart returned 1
[2009-12-13 13:22:06] [info] Run service finished.
[2009-12-13 13:22:06] [info] Procrun finished.
Typically, the BlackBerry Monitoring Service Tomcat logs are located in the following directory:
<drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\Monitoring Service\external\tomcat\logs
Cause
The Apache Tomcat process, which is required to run the BlackBerry Monitoring Service web page, is unable to access jvm.dll due to the incorrect path recorded in the Apache registry keys.
Resolution
- Stop the all running BlackBerry Monitoring Services: Application Core, Data Collection Subsystem, and Polling Engine
- Verify and notate the correct path where the jvm.dll file exists, typically "<drive>:\Program Files\Java\jdk1.6.0_15\jre\bin\client\jvm.dll"
- Open the registry editor through Start > Run > regedit
- Go to the Java registry key located under the Apache Software Foundation registry key:
- Modify the Jvm value path of the jvm.dll file which was noted in step 2
- Start all the BlackBerry Monitoring Services up and verify each service remains started
- The BlackBerry Monitoring Console web page is now accessible
HKEY_LOCAL_MACHINE\Software\Apache Software Foundation\Procrun 2.0\BBMonitoringConsole\Parameters\JavaHKEY_LOCAL_MACHINE\Software\Wow6432Node\Apache Software Foundation\Procrun 2.0\BBMonitoringConsole\Parameters\Java
Could Not Start The BlackBerry MDS Connection Service on Local Computer
Props to my co-worker for figuring this out and sharing it with me. The following error will occur if you uninstall the JRE being used by the BlackBerry MDS Connection Service on a server running BlackBerry Enterprise Server or BlackBerry Professional Software Express.
To resolve the error go into the properties of the service and look at the executable path. The jvmpath= section referes to a version of JRE that has been unisntalled from the server. In this case jre1.6.0_07 is missing.
"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\<SERVER_NAME>\\" webserverdir="D:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\webserver\\" -rbes "<SERVER_NAME>_MDS-CS_1"
After installing the missing JRE the service will start.
Scheduled BlackBerry Professional Software Database Backups
BlackBerry Professional Software Express is installed on your Microsoft Exchange server rather than a seperate server like BlackBerry Enterprise Server requires. When you install BlackBerry Professional Software Express it gives you the option of installing Microsoft SQL Server Express 2005 for the database or using putting the database somewhere else, for example on a server running a full version of Microsoft SQL Server.
Microsoft SQL Server 2005 does not have the ability to setup a maintenance plan so to backup the BESMgmt database you will have do work around this. Install Microsoft SQL Server Management Studio Express on your Exchange server if it is not installed. Once installed open it up, expand databases, and right click BESMgmt and go to Taks then Back Up...
You should be able to leave most of the options at their default, make sure that the location of the SQL backup is in a directory that will be backed up and taken off site.
Click options on the left hand side and select "Overwrite all existing backup sets" and "Verify backup when finished".
Once you have done this click the script drop down arrow at the top and save it to a file. Use the file name BESMgmtBackup.sql, I saved mine to the default directory which is where the backup file will be written to as well.
Open a command prompt and run the command below. You will need to change <InstanceName> to the name of your SQL instance (probably the name of your server), you will also need to change the path to your .sql file if you changed it from the default.
"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLCMD.EXE" -S <InstanceName> -i "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\BESMgmtBackup.sql"
If the command runs successfully open scheduled tasks and create a new one, in the run field paste in the above command. Change the run as field to a domain user account that is setup as your serviceacct (a user that is locked down as a domain admin to run processes). Switch to the schedule tab and set it to run daily at 9AM, click OK and put in the password of the account you used.
Once the job has been created run the job to ensure that it runs successfully, if it runs successfully run it again to be sure that it overwrites correctly as it was setup to do.