priyaexch
asked on
Activesync and OWA stopped working
We have an issue in our front end server which redirects OWA and activesync requests. The server has only 700MB memory. Notice high memory utilization for w3wp.exe process and the page file utlization is also quite high. OWA and activesync stops working at a particular time daily. The only fix is to restart the server.
Getting event 3007
Exchange mailbox Server response timeout: Server: [server name] User: [user email address]. 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.
Also getting the below event: 3014
The Exchange mailbox Server[Server name] has reached its timeout threshold. The mailbox server will be protected from new requests for [60] seconds.
Any suggestions.
We have tried installing the below patch:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;941439
Getting event 3007
Exchange mailbox Server response timeout: Server: [server name] User: [user email address]. 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.
Also getting the below event: 3014
The Exchange mailbox Server[Server name] has reached its timeout threshold. The mailbox server will be protected from new requests for [60] seconds.
Any suggestions.
We have tried installing the below patch:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;941439
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
but I agree with busbar that 700Mb is very low for a FE, how many users are connecting to it?
ASKER
Nearly 1000 users are connecting to it.
Please try to increase the phusical memory atleast by 2 GB , so that it can withstand 1000 users concurrently .
if you are doing any kind of work around , it will be a temp solution for this , untill and unless u do the memory upgradation , this issue cannot be solved .
Cheers ,
Ganesh
if you are doing any kind of work around , it will be a temp solution for this , untill and unless u do the memory upgradation , this issue cannot be solved .
Cheers ,
Ganesh
ASKER
Hi MegaNuk
In the HTTpErr logs we see
Connection_Abandoned_By_Ap pPool ExchangeApplicationPool
whenever end users face the problem.
In the HTTpErr logs we see
Connection_Abandoned_By_Ap
whenever end users face the problem.
ASKER
We also get set of these
Connection_Dropped ExchangeApplicationPool
Connection_Dropped ExchangeApplicationPool
Are you seeing any 2019 or 2020 events in the event log?
Can you run ExBPA on there to see if it picks up any issues?
Run the Exchange Best Practice Analyser (Exchange 2003 version):
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3
It does sound like a memory shortage though cause you are only allowing for 0.7Mb per user (even less when you factor in the OS needs memory too)
Can you run ExBPA on there to see if it picks up any issues?
Run the Exchange Best Practice Analyser (Exchange 2003 version):
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3
It does sound like a memory shortage though cause you are only allowing for 0.7Mb per user (even less when you factor in the OS needs memory too)
If you try and log onto OWA during the issue do you get: "The page cannot be displayed"?
and "Connections_refused" entries in the HttpErr log file?
If so, have a look at this article:
http://support.microsoft.com/kb/934878
and "Connections_refused" entries in the HttpErr log file?
If so, have a look at this article:
http://support.microsoft.com/kb/934878
ASKER
We tried running EXBPA on the 1st day when the problem arised, it never returned any issues. We are planning to upgrade the memory soon and upgrade NIC drivers if feasible. Did not get any issue past 2days.
We are also checking the process explorer utility to see if there are any other dll apart from webmail/activesync related within w3wp.exe consuming high process during the issue.
Thanks for all your posts.
We are also checking the process explorer utility to see if there are any other dll apart from webmail/activesync related within w3wp.exe consuming high process during the issue.
Thanks for all your posts.
ASKER
Hi All,
We have increased the memory of the server now.
Thanks for all your time and valuable comments.
We have increased the memory of the server now.
Thanks for all your time and valuable comments.
Thanks for the update
2.) Has it ever worked properly?
3.) Have you checked the events logs to see if there are any particular events recorded at the same time as when it fails?
4.) Have a look in the IIS logs:
Have a look in the IIS logs and see what it is saying is happening around the failure time, it may be a specific user causing the issue. Maybe have a look in the HTTPErr#.log first to see if that is recording any errors for you. The HttpErr.log files can be found under C:\windows\system32\logfil
IIS logs should be under C:\Windows\system32\logfil
ActiveSync adds some custom fields that can be read to see what is actually happening during the synch:
http://msexchangeteam.com/archive/2005/03/28/403047.aspx