The correct order to stop and start BES services


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.

2 Responses to “The correct order to stop and start BES services”

  1. BES Device Activation Problems...and more. - Zimbra - Forums Says:

    […] in a particular order. So I went out and searched on the web and found the following link: The correct order to stop and start BES services the back room tech I stopped all of my BES services and went with the last order specified in the post. Then I […]

  2. Con Tz Says:

    Worked a treat.
    restarted the bes services in the order above (we have exchange 2003 and bes 4.1.6.22)

    we had a problem where by we couldn’t do enterprise activation. kept retrying and in the MAGT bes logs kept getting “LowLevelError 1209, Component ‘Microsoft Exchange Server Information Store’, Context 1281” errors

    we took the exchange server offline on the weekend for a defrag and of course severed the MAPI connection that the bes server has against the bes accounts and so the services needed to be restarted.

    –=Con


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: