Here's the environment I have:
- 2 Exchange 2003 (SP2) servers
- Both running on Windows 2003, SP2
- All in a Windows 2003 AD
- One Exch server has no mailboxes, runs OWA 2003 and is designated as a fornt-end server
- The second Exch server hosts approximately 650 mailboxes
This environment has existed since January but on/around May 15st (8 days ago) the front-end OWA server will have the w3wp.exe process run away with 100% of the CPU usage (or close to it) OWA stops responding for clients.
None of the following get OWA working again:
- Manually killing the w3wp.exe process(es)
- Stopping the OWA web site in IIS Manager
- Restarting the front-end (OWA) server
In order to get OWA working again (even after the OWA server is restarted) the Information Store must be restarted on the mailbox server (back-end server). Just dismount and mount the store and then OWA connects no problem. Lasts about 2 hours and the same thing happens - this has gotten much worse the last couple of days - 4-5 times a day where last week it was only once a day or so.
Servers are restarted early each morning and memory is never fully utilized - never more than 1.2 GB or so.
OWA box is dual processor P3 (yeah, yeah) with 2GB of RAM, 4GB will be put in later this week
Back-end server is a Dual-core Dell 2950 (dual processor) with 4GB of RAM.
Any ideas? Where to start troubleshooting?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
With the Symantec product installed that is always my first suspect. Disabled? No -remove it. In most cases it is the cause of the problem.
If the best practises tool found an out of date storage driver and that was all, then there is nothing much to worry about. Many servers have that issue and there are no newer drivers available.
Simon.
Please apply the following patch from MS:
http://www.microsoft.com/d
It should take care of your problem.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup Zone:
PAQ - refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
meverest: Experts Exchange Cleanup Volunteer
spector9000 - this is an old question. Unlike a forum it is not possible to "bump" questions back up the list. The only people who will see your post are those that have already participated. Instead you should post your question as a new question in the Exchange Server Zone which will allow other experts the chance to see the question and respond.
Simon
Business Accounts
Answer for Membership
by: SembeePosted on 2007-05-22 at 15:15:23ID: 19138002
What else is on the box?
Any Symantec products for example?
Are the servers fully patched to the same level?
Have you run the Exchange best practises tool on the server?
Simon.