asked on

Microsoft exchange 2003 SP2- The Microsoft Exchange Information Store service uses 100 percent of processor.

Particular users keep experiencing delay when accessing their outlook. They get messages like, outlook is retrieving data from the exchange server or AD server. I ran Exmon and noticed that the store CPU usage is intermittently at 100%. I know we have users with mail sychronization software running, desktop search apps running, shared calenders, archived folders saved remotely on shared drives, plus any other harmful app you can think of. My question is- is there anyway I can fix this problem short of informing some of my users that they need to get rid of some of these processor intensive apps and settings?

ASKER CERTIFIED SOLUTION

Michael Worsham

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Michael Worsham

You also might want to check this article:

Exchange Memory Allocation
http://www.msexchange.org/articles/Exchange-Memory-Allocation.html

west33637

ASKER

Hello all, after much research and tweaking. What worked for me in this situation was rebooting the exchange server to the most basic video driver, by modifying the boot.ini. This freed up some cpu/memory for exchange. Also, using Performance monitoring on the windows 2003 server, I was able to monitor msexchangeIS- RPC processes and user count. When the RPC count was very high I was able to simultaneously look at Exmon and determine which user was responsible for the extremely high RPC processes count. When I was able to find the users that were consistently running very high counts I found that they were running google desktop search, amonst other 3rd party apps and it was synchronizing with outlook and running up the RPC count and using up the Exchange store.exe processor. For most users I was able to uncheck google desktop search in Outlook add-in manager. Some other users were running redirector.exe or other 3rd party apps. Once I stopped those processes from sychronizing with Outlook the problem became very minimal. Microsoft exchange troubleshooting assistant was very helpful in discovering the problems and pointing me in the right direction for solutions.

west33637

ASKER

also mwecomputers links were useful. particularly the hotfix and adjustment to the msExchESEParamCacheSizeMax size were very useful.

west33637

ASKER

thanks a lot.

Michael Worsham

Glad I could help!

-- Michael