Exchange 2000 performance error 1

[xmario2013]

Hi All:

We have a Dell Server running Dual Xeon 3GHz and with 4GB of RAM running Exchange 2000 Enterprise edition, ever since we migrate the Exchange 5.5 (on an old server and its offline now), we been getting this error on the new server:

we have rebooted the server several times and readjusted the virutal memory setting but it still pop up every hour


can anyone help ?

Thanks
XM



Event Type: Error
Event Source: MSExchangeIS
Event Category: Performance
Event ID: 9582
Date: 8/11/2004
Time: 11:11:40 AM
User: N/A
Computer: QPSVER-EX2K
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.

 

[xmsre]

First, which SP and post SP rollup?

Second, have you tried the very short list of tuning steps?

1. /3gb switch on advanced server
2. System Pages = 30000
3. Heapdecommitfreeblockthreshold = 0x40000

Third, have you tried any additional steps?

1. Trimming down the number of database buffers?
2. Altering heap parallelism?

 

[xmario2013]

Hi

I think its SP3 (or the latest one) how do I confirm all the SP and post SP patch ?

second I have tried those tuning parameter in boot.ini, but I think they only works for advance server, we have win2000 server standard edition

and
how do you
Trimming down the number of database buffers?
Altering heap parallelism?

Thanks
XM

 

[xmsre]

1. Do not use the /3gb switch with Windows 2000 server.

2. With 2000 server and no /3gb switch, altering system pages is not necessary.

3. Do set heapdecommitfreeblockthreshold to 0x40000

4. Check ther version number to determine which rollup you have. Don't use the March 2004 rollup, version 6556. Your best bet is the July 2004 version, build 6603.

5. One good approach would be to lower the value of msExchESEParamCacheSizeMax with ADSIEDIT. I'd start at around 768M and work down until the problem stops.

800M msExchESEParamCacheSizeMax=204800
768M msExchESEParamCacheSizeMax=196608
736M msExchESEParamCacheSizeMax=188416
704M msExchESEParamCacheSizeMax=180224
672M msExchESEParamCacheSizeMax=172032
640M msExchESEParamCacheSizeMax=163840
576M msExchESEParamCacheSizeMax=147456

http://support.microsoft.com/default.aspx?scid=kb;en-us;266768

6. On multi-processor servers, Exchange uses the formula # of processors * 4 to determine how many heaps, or pools, to divide available memory into. This can be skewed by hyperthreading CPUs which appear to be twice as many. Changing the MP Heap Parallelism Key to 0 changes the formula to # of processors + 3. Assuming hyperthreadng, on a dual CPU box, it would go from 16 to 7. This is close to what it should be without hyperthreading CPUs (8).

I think you'll get resolution by the time you get done with #5.

XMSRE

 

[xmario2013]

thanks !

 

[jbud]

4. Check ther version number to determine which rollup you have. Don't use the March 2004 rollup, version 6556. Your best bet is the July 2004 version, build 6603.

What's wrong with 6556? Is there a FAQ or kb article I've missed?

 

[Davetoo]

You know, I applied the July rollup, but my server is still saying Build 6249.4, which was the September '03 rollup if I'm not mistaken.

I don't recall any errors when I applied the July rollup, but now I wonder if I applied the wrong one!

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[xmsre]

jbud:

It's been recalled.