Software

Ask something
Discussion Locked

Store.exe process puts Processor @ 100%

0 helpful
5 replies

by dark force 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two Winsows NT 4.0 sp6 servers running Exchange 5.5 sp4. The problem I am having is this: about every 45 seconds, the processor jumps to 100% for about 10 seconds, then drops back to 0% for the next 45 seconds. I have determined that the store.exe process is causing the jumps. After the jump, the System Idle Process goes to around 100%.

One is a PIII-333MHz with 1024MB RAM, the other is a PIII-450MHZ with 512MB RAM.

The p3-450's store.exe is using about 210,560K.
The p3-333's store.exe is using about 69,456K.

After I have rebooted the servers, Store.exe memory usage drops to about 9,000-10,000K. They work fine for about 1-1 1/2 weeks, then start doing it again.

The problem appears to be invisible to the end-users.

I have searched through Technet and have come up empty. I have rebuilt the Information Store database, and it still does this.

This has got me puzzled, so I am throwing it out to you guys. Hopefully there is something that I haven't tried.

Thanks,

JW

5 replies

by xena it warrior

Hi,
Have you run all the updates on the server as well as reapplied Exchange service packs? Is there an Exchange virus scan utility running? If so, disable the virus scan services and see if that makes the difference. Also, download the SecurityHotfix Checker (HFNetChk) Tool from Microsoft and apply all the hotfixes listed.

by nettek

Believe it or not, this is the way NT was designed to work. It will allow a single process to utilize 90-100% of the cpu, until another process requests CPU time. As quoted in MSKB article Q172813, "It should be noted... that it is normal for CPU utilization by the Store.exe process to randomly rise..." If Store.exe continually used 90-100%, or if Exchange appeared to stop responding, then I would be concerned. Otherwise, if this is happening to both servers, and you are not experience performance problems, I would not be too concerned. Also see MSKB article Q157044 for confirmation.

by dark force

I have read these articles, but I do not feel they are applicable to my situation. This is happening on only 2 of my 3 Exchange Servers. These servers are connected to each other via fiber and then to the third server via a T1 trunk. The third server has not had this problem, while being less powerful and having more users.

This discussion is closed to new replies.