Re: Exchange 2000 Server Virtual Memory Fragmentation

From: Thirumeninathan Murugan [MSFT] (thirumen_at_online.microsoft.com)
Date: 07/26/04


Date: Mon, 26 Jul 2004 19:38:42 +0530

If you are running Windows 2000 standard edition, as you cannot use /3 GB
switch in the boot.ini, the initial memory
used by applications like exchange

http://support.microsoft.com/default.aspx?scid=%2fservicedesks%2fwebcasts%2fen%2fwc110502%2fwct110502.asp

Let's go on to the next slide (9), which is "What Can Contribute to the
Problem?" One of the big things that we have seen here in PSS that
contributes to this problem quite a bit is incorrect use of the /3GB switch
on Windows 2000 Servers. Windows 2000 can address 4 gigabyte (GB) of virtual
address space altogether. By default, user-mode applications, such as
Exchange or SQL ServerT or whatever you might have running on your server,
they get 2 GB to work in. Kernel mode or the system also gets 2 GB to work
in. So by default we can address 4 GB of virtual address space: user-mode
applications get 2 GB and the system gets 2 GB.

Now please note there is a Knowledge Base (KB) article, which is Q266096.
It's called "Exchange 2000 Requires /3GB Switch with More Than 1 Gigabyte of
Physical RAM" that actually tells you that we do require a /3GB switch in
the startup line of the Boot.ini file on the Exchange 2000 Server, if
Exchange has more than 1 GB of RAM. So that's usually the article that is
being followed when /3GB switch is being put into the Boot.ini file on the
Exchange servers. So let's continue on this incorrect use of the /3GB switch
(slide 10).

What happens? When the /3GB switch is used in Boot.ini, on the Windows 2000
Server what happens is user mode or all the applications gets 2 GB of
virtual address space and kernel mode gets 1 GB of virtual address space. On
the previous slide, you can see that, by default, they have 2 and 2, but if
you use a /3GB switch on Windows 2000 Standard Server, now we're going to
have 2 for user mode and 1 for the kernel mode, so we took away 1 GB from
the system.

On Windows 2000 Advanced Server, however, and Windows 2000 Datacenter
Server, what will happen if you are using that /3GB switch in a user-mode
application, such as in Exchange, is that you're going to have 3 GB of
virtual address space to work in and kernel mode will get 1 GB. What's going
to happen is that the /3GB switch is designed to take away 1 GB of virtual
address space from kernel mode, which is from systems, and give it to
user-mode application systems, which are your applications such as Exchange
or SQL Servers that are running on the server.

" However, it works only on Advanced Server and Windows 2000 Datacenter
Server. It's going to hurt you if it's being used on Windows 2000 Standard
Server. "

See whether the following changes have been made, these might be helpful.
HeapDecommitFreeBlockThreshold
XADM: The HeapDecommitFreeBlockThreshold Registry Key
http://support.microsoft.com/?id=315407
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value type: REG_DWORD
Value name: HeapDecommitFreeBlockThreshold
Value data: 262144 (0x00040000 in hex)

 msExchESEParamCacheSizeMax
XSTR: How to Modify the Store Database Maximum Cache Size
http://support.microsoft.com/?id=266768
OpenADSIEDIT. In the Configuration container navigate to CN=Services,
CN=Microsoft Exchange, CN=<Org_name>, CN=Administrative Groups,
CN=<AG_name>, CN=Servers, CN=<Server_Name>, CN=InformationStore
Right-click CN=InformationStore, and then click Properties
On the Select a property to view menu, click msExchESEParamCacheSizeMax.
In the Edit Attribute box, type 147456 and then click Set
(This will set the cache to 576MB - the default is 900)

msExchESEParamMaxOpenTables
XGEN: Exchange 2000 Server Memory Use and the /3GB Switch
http://support.microsoft.com/?id=328882
Open ADSIEDIT. In the Configuration container navigate to CN=Services,
CN=Microsoft Exchange, CN=<Org_name>, CN=Administrative Groups,
CN=<AG_name>, CN=Servers, CN=<Server_Name>, CN=InformationStore, CN=<Storage
group>
Right-click CN=<Storage Group>, and then click Properties
On the Select a property to view menu, click msExchESEParamMaxOpenTables
In the Edit Attribute box, type 13800, and then click Set
 (This value is for 4 processors - the limit of Windows 2000 Std.)

 msExchESEParamLogBuffers
XADM: ESE Log Buffers That Are Set Too Low Can Cause the Store to Stop
Responding
http://support.microsoft.com/?ID=328466
Open ADSIEDIT. In the Configuration container navigate to CN=Services,
CN=Microsoft Exchange, CN=<Org_name>, CN=Administrative Groups,
CN=<AG_name>, CN=Servers, CN=<Server_Name>, CN=InformationStore, CN=<Storage
group>
Right-click CN=<Storage Group>, and then click Properties
On the Select a property to view menu, click msExchESEParamLogBuffers
In the Edit Attribute box, type 512, and then click Set

Initial Memory Percentage
XADM: "Initial Memory Percentage" Registry Value Has No Effect
http://support.microsoft.com/?id=810883
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Value type: REG_DWORD
Value name: Initial Memory Percentage
Value data: 0xa

Nathan
Microsoft PSS
"This posting is provided "AS IS" with no warranties, and confers no rights"

"john" <johnboy1973@hotmail.com> wrote in message
news:85fc67bc.0407220230.3f8bc2fd@posting.google.com...
> Hi all
>
> I have the wondefull Event 9582 Error
>
>
> "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" ERROR
>
> Having viewd the webcast, tried the hotfixes, sp3, all KB's reg hacks,
> and even adsi edit fixes, I still have the error.
>
> I comes every hour, on the dot. Running 4GB ram, SP4 Win 2K, exk2 sp3.
>
> Anyone actually fixed this one ????
>
> Cheers in advance.
>
> John



Relevant Pages

  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... Majority of my users connect to Terminal Server and ... I also have users running on stand-alone PC's (Windows XP) ... run the Outlook Time Zone Data Update Tool or the Exchange calendar tool? ... 926666 Update for daylight saving time changes in 2007 for Exchange 2003 ...
    (microsoft.public.exchange.admin)
  • RE: Migrating from Win2k DCs to Win2k3 DCs; ADPrep question
    ... When you try to upgrade Windows 2000 DC to Windows 2003 while ... Exchange 2000 is installed. ... The reason is that Windows Server 2003 adprep ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ...
    (microsoft.public.windows.server.migration)
  • Re: upgrade from Win2k to win 2003 + exchange
    ... 842427 How to upgrade Exchange 2000 Server to Exchange Server 2003 in an ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ... > This is almost what I am looking for in order to upgrade our exchange 2000 ...
    (microsoft.public.exchange.setup)
  • Re: SBS 2000 DNS & Domain issues (connecting)
    ... Our network setup. ... Each computer and server are then connected to the switch. ... Windows cannot determine the user or computer name. ...
    (microsoft.public.backoffice.smallbiz2000)