We help IT Professionals succeed at work.

One BES user did not initialize

JohnDemerjian
on
Medium Priority
1,187 Views
Last Modified: 2012-05-07
EE

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.

Other troubleshooting:
-          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?
Comment
Watch Question

Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
the device had been working for 2 weeks.  when the wan link went down for two minutes, all the devices on the old exchange server became functional again.  on the new exchange server they did not.
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Rick

No I have not done that because the goal is to understand why the problem occurred, not just fix the symptom.  The idea is that before we move all users to the new exchange server, we want to make sure it is stable and working as expected.  with the delay in bes recovery, we got concerned and didn't want to migrate the rest of the users.  so the focus is understanding what could have gone wrong as opposed to correcting the one user account.
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.