One BES user did not initialize
Posted on 2009-07-01
We are deploying a "new" Exchange 2000 server in our organization (yes, I know, an upgrade is on the table...) We have moved one BES user to the "new" E2K system. He was working fine for 2 weeks and then we had a 2 minute WAN outage and the BES server took nearly a day to "recover" and send him mail to his BB again. Here is what happened:
WAN connection dropped approx 1am between office with BES (4.0.1) and office with ExchangeNew (2000 SP3 on VM) and ExchangeOld (2000 SP3). BES started showing hung threads/processes, and restarted itself after some time as expected. WAN connection came back up (not sure if before or after BES restart). Users on ExchangeOld all started working fine. The 1 Blackberry user on ExchangeNew would not initialize (alert from BES 1 user did not initialize). Tried restart of all BES services approx 10:30am. No change. Approx 4pm, set user to use Static Agent (which created and started new Agent process 200). No change, same log errors. Set back to automatic agent, which set user back to original agent. Started working shortly after.
- Checked pings between BES / Exchange, both directions.
- Checked mailbox stores were mounted and ok
- Checked that user could send/receive email fine using outlook
- Restarted ALL BES services
Related log message in agent log:
MAPI call failed. Error 'Network problems are preventing connection to the Microsoft Exchange Server computer.', LowLevelError 1726, Component 'Microsoft Exchange Server Information Store', Context 1300
What could cause the BES connectivity problem on the new BES server?