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.
 
 
LVL 1
lund99Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SysExpertCommented:
1) I would check the BES logs for more info

2) You may need to contact RIM for support

I hope this helps !
0
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
daslzCommented:
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.
0
What were the top attacks of Q1 2018?

The Threat Lab team analyzes data from WatchGuard’s Firebox Feed, internal and partner threat intelligence, and a research honeynet, to provide insightful analysis about the top threats on the Internet. Check out our Q1 2018 report for smart, practical security advice today!

jfieeCommented:
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.
0
hindsightCommented:
The SQL Server Browser did the trick for me as well. Way to go ifiee!!!!!
0
B4ComputersCommented:
The SQL Server Browser sorted this isse for me :-)  Now MAPI issue great!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IT Administration

From novice to tech pro — start learning today.

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.