Exchange crashes 9582 w/ error
I have an Exchange Server that crashes with intermittent problems. The only event I have is MSSExchangeIS reporting 9582, every hour after starting Exchange services.
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.
I have read several others with the error, but not a conclusive fix. I do not run IMAP, don't have a cluster and I use W2k Standard, so can't use the /3 switch.
I did note that a couple of people suggested stop using anti-virus. I current have McAfee VS7.0 installed with GroupShield 5.2. I do have MS/McAfee recommended exclusions for the file system scanner. I hate to think the answer is stop using a/v. Has anyone else resolved this error.
Steve
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.
I have read several others with the error, but not a conclusive fix. I do not run IMAP, don't have a cluster and I use W2k Standard, so can't use the /3 switch.
I did note that a couple of people suggested stop using anti-virus. I current have McAfee VS7.0 installed with GroupShield 5.2. I do have MS/McAfee recommended exclusions for the file system scanner. I hate to think the answer is stop using a/v. Has anyone else resolved this error.
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ben, how are you?? Good to see a fellow MVP out here :)
David
David
Doing good :-) Looks like you've been around here for a while.
Ben
Ben
Yea, started doing this after I left Microsoft, just to keep up with the world, and it turned into fun :). It's a good place to help a lot of people, just don't get caught up in the emotions out here. Some of the experts can be upsetting at times, it's best just to ignore it and move on. But you're a really calm guy, shouldn't be a problem for you :)
David
David
I've tried everything to fix this problem as everyone suggested but the 9582 warning still comes up which ended at restarting the Information Store. I know there's a solution to this problem somehow. This may be a good place to get it.
My Server Config:
Dell Poweredge 6500
3 Processors (700Mhz)
Memory = 2 GB
OS = Win2K Standard (SP4)
Exchange = 2000 (SP3) with August 31 2004 SP3 Rollup Patch
Antivirus = Antigen
Backup = BackupExec 9.0 Remote agent
Actions taken to fix the problem.
1. I can't use the 3/GB because I'm running Win2KStandard
2. Modified msExchESEParamCacheSizeMax
3. Changed HeapDeCommitFreeBlockThres
The last option I haven't done yet is to remove a memory chip, which I'm so hesitant of doing. Any other suggestions?
My Server Config:
Dell Poweredge 6500
3 Processors (700Mhz)
Memory = 2 GB
OS = Win2K Standard (SP4)
Exchange = 2000 (SP3) with August 31 2004 SP3 Rollup Patch
Antivirus = Antigen
Backup = BackupExec 9.0 Remote agent
Actions taken to fix the problem.
1. I can't use the 3/GB because I'm running Win2KStandard
2. Modified msExchESEParamCacheSizeMax
3. Changed HeapDeCommitFreeBlockThres
The last option I haven't done yet is to remove a memory chip, which I'm so hesitant of doing. Any other suggestions?
Don't bother removing the memory, not worth your time. Did you restart the store after the ADSI changes?
Yes I restarted the server. Would the 3 processors affect HeapDeCommitFreeBlockThres
ASKER
Steve