• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4681
  • Last Modified:

Blackberry Enterprise Server: Dispatcher service won't start - terminates with service-specific error 5009

 I Just did a fresh install of BES 5.0 on a Win 2003 R2 Box for use in an Exchange 2003 SP2 Environment.

The server is a physical box, not a VM - I also installed BES 5.0 on another server to use as a standby server for High Availability.


BESMgmt is on a remote SQL 2005 server.


When the services were started at the end of the installation process, the Dispatcher Service was reported to have started successfully but after a reboot of the server a message appeared at logon sayin that a service failed to start.


When I check the event viewer it is reports problems with starting the Dispatcher Service, I have also tried restarting the service manually in the Windows Services window without any luck.


Here is one of the error entries from the Event Viewer regardin the Dispatcher Service:


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7024
Date:            7/15/2009
Time:            2:22:20 PM
User:            N/A
Computer:      ******Description:
The BlackBerry Dispatcher service terminated with service-specific error 5009 (0x1391).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




The same thing happened with the Standby server, the service started successfully at the end of the install procedure but not after a reboot, and the entries in the event viewer of this server are identical to the one above.


I have searched around but I cannot find any articles or any other posts adressing the 5009 error message. There are several other posts regarding the dispatcher service on this and other forums but none of the other issues people are having seem to be related to the problem I am experiencing so I decided to post here hoping that someone might be able to help me.
1 Solution
1) I would check the BES logs for more info

2) You may need to contact RIM for support

I hope this helps !
lund99Author Commented:
The main issue seemed to be a mismatch between the cdo.dll and the mapi32.dll on the BES5 server and the Exchange server. Also the database on the BES5 server did not accept incoming connections on port 1433 for some reason, this had to be configured in the TCP/IP settings on the DB.

Because of all these different issues I chose to do a re-install of the server with a local database instead, after retrieving the right version numbers of the cdo.dll and mapi32.dll the dispatcher service seems to be working fine.
You can get away with installing BES and Exchange on the same box, the bigger problem is that you cnat have office installed - aka Outlook. That is where RIM will make you install on another box which is what they made me do when I upgraded to 5 for a client. The box had Exchange, TS and BES on it.
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

This issue turned out to be related to the SQL Server Browser service in my case. Once I enabled that service and started it up the BES services all fired up correctly.
The SQL Server Browser did the trick for me as well. Way to go ifiee!!!!!
The SQL Server Browser sorted this isse for me :-)  Now MAPI issue great!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now