Link to home
Start Free TrialLog in
Avatar of MJespersen
MJespersen

asked on

Microsoft.Exchange.Search.ExSearch service high CPU usage

Hi

I have 2 Exchange 2010 Mailbox servers with very high CPU usage on the "Microsoft.Exchange.Search.ExSearch.exe" service. The two server are set up within the same DAG. They have been running for about a year, with no problems, but sudently this problem has occured. I haven't change any configuration settings resently, so I don't understand why the problem appears now. In all fairness, the problem may have been there for some time, since we rarely open the console on the servers. I have searched for solutions to this problem on the web, but can't seem to find any that solve the problem for me. Someone wrote about the C++ Redistribution package causing this problem and recommended reinstalling this, but that didn't help. Another wrote about a lack of memory causing this, but have 16 GB of memory, and only about 50 users. And as far as I can tell, there is plenty of memory avaible. Another thing about the server is that if I reboot it, the Information Store service fails to start, bacause of a timeout. I can simply start it manually and everything works. I don't know ff this is related to the problem or not.

Have anyone seen this problem before?

Any help will be greatly appreaciated!

Regards / Mark
ASKER CERTIFIED SOLUTION
Avatar of Chris
Chris
Flag of United Kingdom of Great Britain and Northern Ireland image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Sushil Sonawane
Sushil Sonawane
Flag of India image
Make sure exchange server updated with latest service pack and rollup and exchange installation folder excluded in antivirus scan.
Avatar of MJespersen
MJespersen

ASKER

Deleting the index folder solved the problem - Thanks!
Avatar of Rob
Rob
Hi all,

I'm experiencing a similar problem. Just a quick question though. I've followed the steps above, moving the CatalogData folder and restarting the indexing search. That said, the CPU is running close to 100% immediately. My questions are two fold. Firstly, would you expect this behavior when the service is started after the folder delete / move? Secondly, if yes, is there a way to monitor how much the service has indexed? I may have to run this after business hours if the high load continues.

Many thanks for any feedback.

Rob