[latitude1]

My setup is Exchange and Windows 2003. BESX 5.0.2 installed on its own Windows 2003 server. This install is about 2 weeks old. All works great except... maybe 2 or 3 times a week the devices are unable to send (and can't do an address lookup from our address book). I haven't delved into any depths of checking whats what (e.g. what elase is affected) yet but a quick fix to get it going and works every time is to stop the BB Controller, Dispatcher and Router services in that order and then starting them again in this order BB Router, Dispatcher and Controller. Any thoughts as to why this happens / what to check etc would be appreciated. Thanks

[penguin3107]

Are your domain controller(s) and/or Exchange server being rebooted at some point?
Sounds like BES is losing connectivity to one, or both.

BES doesn't particularly like when either of those things happen and typically needs to have its services restarted as a result.

[lprmcnit]

We saw similar issues, as Penguin3107 suggested, when there was a loss of connectivity to the domain controllers/global catalog server. There is a settting in a RIM kb article that configures the registry on BES to attempt connection to a secondary and possibly tertiary catalogue server if connection to the first one fails. As I recall the default setting is just 1 GCS. We found BES requires a connection to the GCS to be able to do address book lookups.