Re: Exch2K - Virtual Memory Fragmentation

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Jaclynn Hiranaka [MSFT] (jaclynnh_at_online.microsoft.com)
Date: 05/03/04 

Date: Mon, 3 May 2004 11:59:36 -0400

Check out Michael Palermiti's blogs on the topic:
http://blogs.msdn.com/mfp2/archive/2004/02/21/77492.aspx
http://blogs.msdn.com/mfp2/archive/2004/02/23/78542.aspx
http://blogs.msdn.com/mfp2/archive/2004/02/25/79955.aspx 

-- 
Hope that helps.
-------------------------
Jaclynn Hiranaka
Enterprise Messaging Support
This posting is provided "AS IS" with no warranties, and confers no rights.
© 2004 Microsoft Corporation. All rights reserved.
"Dvord Direwood" <dvord@Hotmail.com> wrote in message
news:eHq52BSMEHA.3712@TK2MSFTNGP11.phx.gbl...
> Small Business Server 2000
> Dell PE2650
> Xeon 2.4
> 4GB RAM
>
> What follows is a loose log of what I've been experiencing and what I've
> done.  What I find interesting is that it's ALWAYS Xhours to the minute
> when the exchange service starts generating errors.
>
> I did try the /3gb switch even though it's not Adv. Server, but it did
> not help nor worsen the situation.  I have long since shut it off.
>
> Before /3gb
>
> Event Type:    Error
> Event Source:  MSExchangeIS
> Event Category:        Performance
> Event ID:      9582
> Date:          4/19/2004
> Time:          4:39:35 AM
> User:          N/A
> Computer:      BLRB01
> Description:
> The virtual memory necessary to run your Exchange server is fragmented
> in such a way that normal operation may begin to fail. It is highly
> recommended  that you restart all Exchange services to correct this
> issue.
>
> For more information, click
> http://www.microsoft.com/contentredirect.asp.
>
> after /3gb
>
> Event Type:    Warning
> Event Source:  MSExchangeIS
> Event Category:        Performance
> Event ID:      9582
> Date:          4/20/2004
> Time:          4:30:22 AM
> User:          N/A
> Computer:      BLRB01
> Description:
> The virtual memory necessary to run your Exchange server is fragmented
> in such a way that performance may be affected. It is highly recommended
> that you restart all Exchange services to correct this issue.
>
> For more information, click
> http://www.microsoft.com/contentredirect.asp.
>
>
> Error - IS Restart Log
>
> Start 4/20     6:40
> 1st Err 4/20   13:40
> Start 4/20     17:14
> 1st Err 4/20   22:14
> Start 4/21     7:02
> change 4/21    8:44    changed all Antivirus mail filtering to SMTP
> inbound only, no store scanning
>
> Changed reg entry to use larger blocks of virtual memory to reduce
> fragmentation
>
> http://support.microsoft.com/default.aspx?kbid=315407
>
> needs reboot
>
> also removed /3gb switch, not valid for this server.
>
> rebooted 4/22 7:42 am
> 1st Error 4/23 1:42 am  - Error not warning
>
> I am still getting this error from 5-12 hours after restarting exchange
> is service.

Relevant Pages

  • RE: Front End Server hold all incoming email
    ... possible directions flow fine ... -When you restart Exchange Services are you including the SMTP service (not ... the virtual server)? ...
    (microsoft.public.exchange2000.transport)
  • Re: Exch2K - Virtual Memory Fragmentation
    ... Enterprise Messaging Support ... Server, but it did> not help nor worsen the situation. ... It is highly> recommended that you restart all Exchange services to correct this> issue. ...
    (microsoft.public.exchange2000.information.store)
  • Exch2K - Virtual Memory Fragmentation
    ... Small Business Server 2000 ... What follows is a loose log of what I've been experiencing and what I've ... that you restart all Exchange services to correct this issue. ...
    (microsoft.public.exchange2000.information.store)
  • Re: Last step
    ... The best test is to either power down the Exchange 5.5 server or at least ... stop all of the Exchange services and ensure that everything continues to ... Enterprise Messaging Support ...
    (microsoft.public.exchange.setup)
  • RE: SBS 2008 unresponsive
    ... What's happening is the exchange services are stuck ... server should be super quick. ... Here is what you can do, reboot in safe mode, go into msconfig, startup tab, ... In my case it was the Trend Micro Worry Free 6.0 Advanced that was ...
    (microsoft.public.windows.server.sbs)