OWA stops responding on Exchange 2003
- Hello,
Over the past two months periodically OWA stops responding on my Exchange 2003 server. All services are still running and you can connect via Outlook without any problems. Stopping and restarting the IIS services do not resolve the problem but a reboot will. There are no indications of problems in the event viewer. Today however the system did a bug check so now I am really concerned that there is a larger underlying problem.
System is Windows 2003, Exchange 2003, Trend Anti-virus, Symantec Backup Exec 12, the server is fully patched.
No new hardware has been intruduced and no major software installs or changes in months.
System is a HP Proliant DL 380, I believe has all hardware updates applied.
Thanks
Julie Lienemann
All Replies
- When the OWA stops responding , are you getting any error on IIS logs? Any event IDs that you get ? Instead of restarting the IIS service , have you tried stopping and restarting the default web site in IIS?
Run Exbpa and check for any error or any non default setting.
Raj - On Fri, 6-Nov-09 21:01:06 GMT, jlienema wrote:
ver is fully patched. No new hardware has been intruduced and no major software installs or changes in months.System is a HP Proliant DL 380, I believe has all hardware updates applied.Thanks
BSODs can only happen from software that runs in kernal mode. Those
are the bae O/S, drivers, filters (like AV software), etc. Exchange
runs in user mode and, while it might crash Exchange, it can't cause a
BSOD.
Find out what casued the BSOD and fix that.
OWA not accepting connections can be casued by the depletion of paged
and no-page system memory pools (which can also lead to BSODs). Check
the HTTPERR log files to see if that's what's happening.
If you are depeting one of the memory pools you might want to run
poolmon to see what's eating the memory.
How much physical memory is installed on the Exchange server? Are you
using the /3GB switch in boot.ini? What's the /USERVA value set to in
boot.ini?
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP - I would also try running EXBPA and make sure everything looks Good
http://www.microsoft.com/downloads/details.aspx?FamilyID=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en
Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3| - Nothing in the event viewer and restarting the web site didn't work.
Julie Lienemann - This is what is in the boot.ini
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /USERVA=3030 /PAE
The server has 12 gb, I did reboot this morning and saw an event that the memory setting are not optimal for Exchange so I will check that out.
Julie Lienemann - Hi,
Besides that,please post the error information when you try to browse OWA?You may get error code like 401,503,etc.
Regards,
Xiu - Just to update,
I ran the best practices analyzers, and did have some memory issue's which I corrected according to Microsoft tech note's essentially changing my boot.ini to have the following
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /USERVA=3030 /BURNMEMORY=8192 /PAE
Adding the burnmemory switch. OWA stayed up for almost 6 days, just went away again this morning. Unfortunately I wasn't at my computer so I couldn't try any restarting of services, the server was rebooted by a co-worker.
So I am back to sqare one, again nothing in the event viewer etc
Julie
Julie Lienemann - As i said in my first post, did you checked the IIS logs. Getting any errors and failed request? Paste it here. i am sure this has nothing to do with memory. Check the amount of free space on C drive.
Raj - Sorry, I cannot find any error's in the IIS logs. I have 49 GB free on the C drive.
Julie Lienemann - On Tue, 10-Nov-09 13:58:03 GMT, jlienema wrote:
>This is what is in the boot.inimulti(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /USERVA=3030 /PAEThe server has 12 gb, I did reboot this morning and saw an event that the memory setting are not optimal for Exchange so I will check that out.
And what about the HTTPERR log? And poolmon?
You might also want to install process monitor on the machine and the
the paged
and non-paged memory pools.
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
