My Blackberry Media Manager kept exiting on me when trying to access the Media stored on my Blackberry Storm.  The specific error was:

Microsoft Visual C++ Runtime Library X Runtime Error!

Program: C:\program Files\Roxio\Media Manager 9\Mediamanager9.exe

R6025 – pure virtual function call

The problem ended up being that the RoxMediaDB9 service was disabled.

I changed the service from disabled to manual (could have been set to automatic if I wanted it to start following each reboot), started the RoxMediaDB9 service, which allowed Media Manager to start without issue.

I was troubleshooting a Blackberry Manager problem today that required the BES MDS credentials.  The admin thought he knew what the credentials were, but wasn’t sure.  So I wrote the following SQL query and ran it against the Blackberry Enterprise Server’s BesMgmt database to get the user name and password:  

A user was recently having issues with his Groupwise email on his Blackberry, so our BES admin planned on removing him from BES, then re-adding him.  Removing the user was no problem, but the admin was quite suprised to find out he could not re-add the user.  When searching for the user to add, the user was not found. 

Blackberry KB15941 exlains that starting with BES 4.1, additional warnings are logged to the Blackberry Messaging and Windows Application log.  These warnings are informational in nature, and do not indicate a problem.

If you’d like to reduce or eliminate these messages, KB04342 says to edit the EventLogLevel DWORD value  of the appropriate BES service located at : 

After our recent upgrade of our Blackberry Enterprise Server from version 4.0.7 to 4.1.14, I  noticed the total pending message counts shown in the BES MAGT log file never droppped below 275.  I was concerned about this, thinking that the server was busy and could never get all messages processed, even during times of light usage, like in the middle of the night.  

KB 13718 explains the correct order to stop and start Blackberry Enterprise Server (BES) services for Microsoft Exchange:

1. BlackBerry Router.
2. BlackBerry Dispatcher.
3. BlackBerry Controller.
4. All remaining BlackBerry services.

The BlackBerry Enterprise Server for Microsoft Exchange Disaster Recovery Guide explains the correct order is:

1. BlackBerry Controller
2. BlackBerry Router
3. BlackBerry Dispatcher
4. all remaining BlackBerry services

KB04293 explains the correct order for BES 4.0 or later with Exchange is:

1. BlackBerry Router
2. BlackBerry Dispatcher
3. BlackBerry Controller
4. all other BlackBerry Enterprise Server services

The BlackBerry Enterprise Server for IBM Lotus Domino Version 4.1.3 Upgrade Guide explains the correct order is:

1. BlackBerry Controller
2. BlackBerry Router
3. BlackBerry Dispatcher
4. all remaining services

I was unable to find any official Blackberry documentation regarding the proper order to stop and start the BES services for Groupwise, but this document on the Vodaphone support web site suggests the following order:

Start the Blackberry services in the following order:

1. Blackberry Dispatcher
2. Blackberry Router
3. Blackberry Controller
4. Blackberry Alert
5. Blackberry Attachment Service
6. Blackberry Mobile Data Service
7. Blackberry Policy Service
8. Blackberry Synchronization Service

Reverse the order of the services when you stop the services.

As you can see, the documentation does not consistently explain the order the BES services should be stopped and started.

I have a client who wanted to integrate Blackberry Enterprise Server (BES) version 4.1.3 with his Groupwise 7.0.1 system. He already had a Windows 2003 SP2 server ready for me to install BES onto, so I figured it would be a quick job. I was wrong.

The first hurdle appeared when I started to run the BES setup program on the Windows 2003 server. The installer refused to run because the server was running in Terminal Services Application mode, which is not a supported configuration.

We changed our plan and started running the BES installer on a different Windows 2003 SP2 server, but this time the installer quit because we did not have at least SQL 2000 SP3a on the server. Determining which version of SQL 2000 is installed is not the easiest thing to do, so we just went ahead and downloaded and installed SQL 2000 SP4.

After installing SQL 2000 SP4 we were able to install BES without problems, but BES was unable to communicate with Groupwise. We determined the problem was the version of the Groupwise client installed on the BES server was 7.0.1 IR1, which is not a supported configuration – we’d later learn we needed to be on versions 7.0.2 or 6.5.6 FTF4. Utilizing client 7.0.2 would have required upgrading the entire Groupwise system, so we decided to backrev to client 6.5.6.

I uninstalled the 7.0.1 IR1 client, rebooted the server, then installed GroupWise 6.5
Support Pack 6, Update 1 dated June 27, 2006. After rebooting the server again, BES and Groupwise could not communicate.

We uninstalled the GroupWise 6.5 Support Pack 6, Update 1 client, rebooted, then tried GroupWise 6.5 Post SP6 Client Rev 4 dated November 10, 2006. We found this to be the required client version according to KB04164, but it didn’t work for us despite following the special installation instructions listed in TID 2974707. We kept receiving the following error message in gwenv1.dll when executing the client:

Entry point not found. WpfCheckAncestryAnd Read

I figured the problem had to lie with gwenv1.dll, so I checked the file’s date. C:\windows\system32\gwenv1.dll was dated 6/16/2006, while the gwenv1.dll found in GroupWise 6.5 Post SP6 Client Rev 4 was dated 11/6/2006.

I suspected the problem was that files from previous Groupwise client installations were not being overwritten by the new client installations. I uninstalled the GroupWise 6.5 Post SP6 Client Rev 4 client , rebooted, ran Messaging Architects’ GW CleanIT, rebooted, then reinstalled GroupWise 6.5 Post SP6 Client Rev 4 client per the TID’s instructions.

We were finally able to communicate with Groupwise through the BES server!

In hindsight, I wish I would have found Blackberry’s KB KB12662, “Perform basic troubleshooting steps for Novell GroupWise”, prior to beginning the BES installation. It probably would have saved us a few hours worth of work.

Yesterday I installed Blackberry Enterprise Server (BES) on a Windows 2003 SP2 server that would synchronize with Groupwise 7.0.1. Installing BES was fairly straightforward, but getting the Groupwise client to synchronize the users and address books was another story.

Once we had the entire system functioning properly, it was time to synchronize the first Blackberry with the server. From the Blackberry Manager we selected the option to Generate and Email Activation Password, but the user never received the activation message – neither in her email nor on her Blackberry. We finally tracked down the result of the failure, which was we were sending the activation email from an alias address, not from a user with an actual mailbox.

This morning we changed the address the activation message was sent from to a user with an actual mailbox. When we tried to resend the activation email to the Blackberry device we received the following error from Blackberry Manager:

A password was not generated. The user still has a non-expired activation password for which the number of attempts has not exceeded the maximum of 5.

I couldn’t find anywhere to cancel the pending activation request, and was not about to wait the 48 hours for the message to expire. Nor was I going to enter the incorrect password 5 times to nullify the activation request.

Finally, I found the following solution:

1) In Blackberry Manager, right click the user and select Set Activation Password

2) In the Password box, leave both fields blank

3) In the Password Expires in _ hours box, enter a 0 (zero) and click OK

This will expire the existing activation email and password and will allow you to resend the activation email to the Blackberry device.

To resend the Activation email from Blackberry Manager, right click the user and select Generate and Email Activation Password.