Blackberry Exchange Server Problem when server is rebooted.
MS Exchange 2000 running on Server A, Blackberry Exchange Server (BES) and SQL Server running on Server B. Everything is fine .. except: when Server B is rebooted, one or more of the BES services do not start, typically remaining forever in the "starting" status. This frequently happens with the Blackberry Dispatcher service. when this happens, it's not possible to stop or start the service, so BES does not start either.
The only solution I've come up with is to keep rebooting the server until all the Blackberry services start properly. usually this takes about 8-15 reboots.
One other symptom is that if one of the Blackberry services is not going to start properly, logging in to the server takes much longer than if all the services do start.
The only solution I've come up with is to keep rebooting the server until all the Blackberry services start properly. usually this takes about 8-15 reboots.
One other symptom is that if one of the Blackberry services is not going to start properly, logging in to the server takes much longer than if all the services do start.
ASKER
BES Version 4.0.0.97, we do not subscribe to maintenance (we're a broke startup, Blackberry is our one luxury) so never get updates from RIM.
Don't know what you mean about DNS servers - I do not find any setting for this in BES configuration. As for this server, it is only running SQL Server, BES and GP. DNS, WINS, DHCP, RAS, etc. are on another server, which is the domain controller. IPCONFIG on this server shows the DNS server as the primary domain controller and not an external IP.
Don't know what you mean about DNS servers - I do not find any setting for this in BES configuration. As for this server, it is only running SQL Server, BES and GP. DNS, WINS, DHCP, RAS, etc. are on another server, which is the domain controller. IPCONFIG on this server shows the DNS server as the primary domain controller and not an external IP.
You should still be able to get major fixes and updates from the public site of the Blackberry web site. I have done so in the past. I can't remember if that is the latest version of 4.0 or not - I know there are some service packs.
Anything in the event logs?
Simon.
Anything in the event logs?
Simon.
ASKER
lots of SQL-related errors in the event log all the time, but users never report any problems. here is an example:
[SYNC-DSession] DevMgmt connector responded RESTORE_FAILED_BECAUSE_OF_
when the reboot problem is happening, no unusual errors appear in the event log.
[SYNC-DSession] DevMgmt connector responded RESTORE_FAILED_BECAUSE_OF_
when the reboot problem is happening, no unusual errors appear in the event log.
I would ignore the SQL errors if the server appears to be working correctly - it is error messages at startup that you are more interested in.
In my experience a BES either works or it doesn't.
My only other thought was the NIC or something else connected to the network connection. It might be bad or suspect and only works some of the time.
Simon.
In my experience a BES either works or it doesn't.
My only other thought was the NIC or something else connected to the network connection. It might be bad or suspect and only works some of the time.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The Blackberry Dispatcher service is the one that regularly fails to start. I have made the registry change recommended in the KB article, and will test as soon as possible. SQL authentication is correctly configured. BES was purchased directly from RIM.
Is the network configuration correct? You should have DNS servers pointed at the domain controllers ONLY for DNS. No external domain controllers should be listed.
Simon.