hopkins1003
asked on
Exchange Server Freezing With 100% CPU For 30 Minutes At Same Time Each Day
Our Exchange 2003 server every day at the same time freezes with 100% CPU. The server freezes for about 30 minutes. The process that is maxing it out is svchost which has many services. We started restarting each service and once we restarted the server service that had dependent Exchange services (MS Exchange MTA Stacks, MS Exchange Information Store and MS Exchange System Attendant) the CPU usage went down. Any Idea whey this is occurring?
This server is a virtual server in a VMware environment.
This server is a virtual server in a VMware environment.
It's a while since I played with E2003, but if it's happening at the same time each day, I'd be looking for something like the scheduled maintenance settings, or a scheduled virus scan. Or even someone doing a large mailshot at the same time each day.
ASKER
Thanks for you help. I was able to identify the issue. Our RMM tool was the culprit. Once I uninstalled it, the problem went away. I am working with the developer to determine the reason. We had a similar issue with another server in the environment and the common denominators are Server 2003 and being a VMware guest. I will let you know if I find out more, but thanks for helping me narrow it down.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We were able to resolve the issue
That said, you should be able to get a better idea of exactly what is going on by using Perfmon to get a trace log of more performance counters, like hard drive usage, memory usage, etc. You should also check to see what time your database maintenance is set to occur. With this being in a virtualized environment, also check to see which servers are also running on the VM host and see if there are functions on those servers that are over-utilizing resources. Because Exchange 2003 was never optimized to work in a virtual environment, there's a strong likelihood that this is a symptom of that. If you can move the VM to an empty VM Host, then see if the problem persists, you will have a better idea of whether it's virtualization issues or the server software itself causing problems.