All of a sudden today we started to have a major issue on our Exchange 2003 Enterprise SP2 server running on a Windows 2003 box. It is behind a firewall with HTTP/HTTPS, POP3, and SMTP open. Our MX records point to our Anti-spam service off site and they send us the mail after. SMTP on Exhange and the firewall only allow mail from Anti-spam server IPs so I don't think we are being spammed to death. Firewall logs don't show anything.
Our user of BB, Droid, and Iphone connect to the exhange server via sync on devices. This server has been up and running for years and no recent changes. It has not been rebooted (until today) for months. The only thing I tried to do today is configure someone's BlackBerry to connect to the Exchange Server via OWA. Shortly after all heck broke loose.
It started out with users looking like they are connected to the Exchange Server with Outlook 2003, but no one was getting new emails. We checked the queue and discovered a bunch of the mail sitting in the "Local Delivery - SMTP" queue with System Manager.
If we reboot, the mail starts flowing, but shortly after it hangs up again. We notice in the Application Event Log a bunch of Error 3007 and 3014 entries:
Event 3007
Source ServerActiveSync
User: domain\user with a phone
Description: Exhange Mailbox server response timeout:Server:[my server fqdn] User:myusersname: Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded.
The server looks like it is slow to respone here and there, but TaskManager shows very little CPU use as does ProcessExplorer.
Event 3014
Source ServerActiveSync
User: domain\user with a phone
Description: The Exchange mailbox Server: [my server fqdn] has reached its timeout threshold. The mailbox server will be protected from new requests for [60] seconds.
Usually after several of these, the queue starts filling up. Rebooting or restarting the exhange services will start the mail flowing again.
The last thing I noticed was when I though that it might be the user with the BB phone I just tried to configure. I went to to block their phone and I notice that this no longer works for any user. I get to the page and when I search for any mailbox I get the error:
"Failed to access user's Mailbox, verify that the mailbox and user account are enabled and functional. "
I just used this a couple of weeks ago when a user lost their phone so I know it was working then.
Our user of BB, Droid, and Iphone connect to the exhange server via sync on devices. This server has been up and running for years and no recent changes. It has not been rebooted (until today) for months. The only thing I tried to do today is configure someone's BlackBerry to connect to the Exchange Server via OWA. Shortly after all heck broke loose.
It started out with users looking like they are connected to the Exchange Server with Outlook 2003, but no one was getting new emails. We checked the queue and discovered a bunch of the mail sitting in the "Local Delivery - SMTP" queue with System Manager.
If we reboot, the mail starts flowing, but shortly after it hangs up again. We notice in the Application Event Log a bunch of Error 3007 and 3014 entries:
Event 3007
Source ServerActiveSync
User: domain\user with a phone
Description: Exhange Mailbox server response timeout:Server:[my server fqdn] User:myusersname: Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded.
The server looks like it is slow to respone here and there, but TaskManager shows very little CPU use as does ProcessExplorer.
Event 3014
Source ServerActiveSync
User: domain\user with a phone
Description: The Exchange mailbox Server: [my server fqdn] has reached its timeout threshold. The mailbox server will be protected from new requests for [60] seconds.
Usually after several of these, the queue starts filling up. Rebooting or restarting the exhange services will start the mail flowing again.
The last thing I noticed was when I though that it might be the user with the BB phone I just tried to configure. I went to to block their phone and I notice that this no longer works for any user. I get to the page and when I search for any mailbox I get the error:
"Failed to access user's Mailbox, verify that the mailbox and user account are enabled and functional. "
I just used this a couple of weeks ago when a user lost their phone so I know it was working then.
