After upgrading my server OS to Win2k, I reinstalled Exchange 5.5 and then went thru eseutil defrag and then the isinteg-fix and -patch routines. Got it working. A couple hours after it started up it went to 100% cpu on the store. The problem is when IMC is on, whether or not NAV exchange is running. The problem can be temporarily remedied by deleting IMC and then recreating it, usually requiring a server reboot. However, after an hour or so it's back up to 100%. The problem occurs for 10, 20, or 30 sec, then goes back down to zero for a similar amount of time, then back up. Actually the problem doesn't occur at all with IMC stopped, but then we don't get any email!
I've gone thru everything on this page:
http://support.microsoft.com/search/default.aspx?Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&Product=&KeywordType=ALL&Titles=false&numDays=&maxResults=25&Queryl=store.exe+cpu&Query=store.exe+cpu&QuerySource=gsfxSearch_Query&srchExtraQry=concerning the store.exe cpu problems.
Using all that applied, I settled on
http://support.microsoft.com/default.aspx?scid=kb;en-us;822006 as the only possible solution, and obtained the fix from MS. Yeay! The cpu usage was hardly existent afterwards. Then in the evening when I looked at it, it was already ramping back up. By morning, it was 100% again. So I guess the last great hope from MS didn't work.
The event logs don't appear to reveal anything. There's an occasional IMC error 2 about trying to remove a spool file but this is only a couple times / day. Doesn't appear related. Somebody please tell me something I don't know.
Start Free Trial
