Hi All,

I had an interesting issue with a BES 5 install yesterday and thought I would share it.

Yesterday I installed BES 5 for Exchange 2007 on a Windows 2008 server for a customer and most of the BES services would not start with the error - The dependency service does not exist or has been marked for deletion.

This was the 5th time I have installed this configuration of BES for customers and had not had this issue before and there were no errors during the BES install or that I could find in the logs. After a bit a head scratching and swearing, I looked at an another customers BES on 2008 to check the service dependencies and they were different to the server I had just installed.

On the server I had just installed, the effected services had these dependencies from the windows services applet - Workstation, EventLog.

The working server 2008 BES had these dependencies - Workstation, EventLog, tcpip.

I then checked the service dependencies in the registry at - Local Machine\System\CurrentControlSet\Services\Blackberry Controller on the 2008 BES with Service issues.
The DependOnService value showed these - NtLmSsp, EventLog, LanmanWorkstation

NtLmSsp service doesn’t exist on Server 2008 but does on 2003.

The same registry key on the working server 2008 BES had these dependencies – EventLog, LanmanWorkstation, tcpip

So armed with this information, I changed the DependOnService value to show EventLog, LanmanWorkstation, tcpip for each BES service that had the incorrect dependencies. These were Controller, Dispatcher, MailStore, Policy, Router, SyncServer.

The server was then rebooted and all services started and BES services ran without issue, users activated, mail sent, received, all good.

Has anyone else seen this issue or have an idea why this would happen ? Apart from, It’s a Windows thing.

Thanks
Dave

Thank you ,, you hit it right on the nose. I had the same exact problem you discribed and I tried everything and seached all over but your solution is the one that worked for me. Thanks again