Re: Store.EXE 50% CPU Time?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Minvt (Minvt.1eqdi7_at_mail.mcse.ms)
Date: 10/26/04


Date: Tue, 26 Oct 2004 04:04:07 -0500


Hi Andy,

I am enountered a similar problem. I am running Exchange 2003 on xeon
Piii 700 (single processor) hosting only 20 users at the moment. I have
problem matches your post, the Store.exe seems to use very high memory
and processor. As I checked the Task manager, the memory usage is
increasing and never goes back down, eventually the service freezes,
but the server still running at a reasnable speed. can anyone confirm
that is this because exchange 2003 cannot run on Xeon Piii 700 (single
processor with 1500 RAM)? or is it something is still not configured
properly.

Thanks

Regards
Minh

--
Minvt
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1124588.html
 


Relevant Pages

  • Re: Open Server 5.0.5 Hardware Upgrade
    ... I have used HP/Compaq Proliant in the past. ... Why stop at PIII. ... years and have never had a problem (even on the Xeon chip). ... Xeon is supposed to have problems with any release prior to 5.0.6, ...
    (comp.unix.sco.misc)
  • Re: [SLE] SuSE Pro 9.3 on a Intel Xeon server freezing
    ... How come the default kernel is Pentium-II ... >instead of P4 Xeon. ... Because there are still enough PII, PIII and older VIA EPIA machines ...
    (SuSE)
  • Re: Memory and Exchange 2003 with SBS 2003
    ... Only single processor but yes, its a Xeon. ... >> gets for a network this size. ... >> I am consistently recieving alerts that allocated memory is too high and the ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory and Exchange 2003 with SBS 2003
    ... hmmm still not sure but if your server has been online for 45 days you ... aren't patching are you? ... I'm still checking on the Xeon thing. ... > Only single processor but yes, ...
    (microsoft.public.windows.server.sbs)