Re: Error 9582 on Exch2000SP3 and W2KSP4 w/2.5 G RAM
From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 11/10/04
- Next message: Greg Draz: "Tool to perform MDB to PST conversion"
- Previous message: Blake: "Amount of email passing through Exchange 2003"
- In reply to: Chris: "Error 9582 on Exch2000SP3 and W2KSP4 w/2.5 G RAM"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Nov 2004 13:51:54 -0600
Are you running Windows 2000 Advanced Server? Even though Windows 2000
Standard can handle up to 4gb of ram, Exchange 2000 cannot take advantage of
it unless you are running Windows 2000 Advanced (where you can set the /3gb
switch). I typically don't recommend putting any more than 2gb in an
Exchange server that is running on Windows 2000 Standard. Following are
some troubleshooting tips from a technet article. The last point mentions
Storage Groups. How many do you have? How many databases? Although you
will never hear PSS tell you to do this, you may end up wanting to pull out
either 512mb or 1gb of RAM.
To troubleshoot virtual memory problems
1.
Determine if your server is running Windows 2000 Server or Windows 2000
Advanced Server. If your server is running Windows 2000 Server, ensure that
the /3GB switch is not in the boot.ini file. If your server is running
Windows 2000 Advanced Server and there is more than 1GB of physical RAM
installed, ensure that the /3GB switch does appear in the boot.ini file.
Note Because Windows 2000 Server (Standard) does not support the /3GB
tuning switch, do not attempt to scale individual servers to host multiple
thousands of users.
2.
Check the Application log for 9582 warnings (less than 32MB virtual
memory blocks available) or 9582 errors (less than 16MB virtual memory
blocks available). On some large systems, it is usual to drop below the 32MB
threshold during peak activity; however the available virtual memory should
rise significantly during non peak activity.
3.
Check the application log for other errors that indicate that you are
out of memory (such as 12800 MIME processing errors) in addition to 9582
warnings. If the warnings are accompanied by other errors indicating that
you are out of memory, users may be unable to access mail. If no other
processing errors occur, and users are able to access their mail, it
indicates that the 9582 warnings may be relatively harmless. However, 9582
warnings should still be investigated for possible action.
4.
Monitor the MSExchangeIS\VM Largest Block Size counter. This counter is
the best way to investigate virtual memory issues. You can monitor this
counter in real time, or monitor 1-minute intervals. Collecting 18-24 hours
of data to determine if a trend indicates that memory is being released.
Monitor the minimum value to see what the drop is. It can be normal on large
servers if this minimum value is around 55MB.
5.
Be aware that other store-related processes, such as virus scanning,
can tip the threshold. However, as long as user performance is not affected,
and the virtual memory block grows again during non-peak activity,
corrective action may not be necessary. However, if you expect user load to
increase, you may want to reduce overall virtual memory consumption so that
the server can accommodate a greater load.
6.
To reduce virtual memory consumption, first ensure that the Exchange
server is running Exchange 2000 Server Service Pack 3 (SP3); Exchange SP3
has specific virtual memory optimizations.
7.
If 9582 warnings are still being logged, then you must perform a
registry change. This registry change is acceptable as long as there is an
adequate amount of RAM available on the server. Monitor the Memory\Available
Bytes counter. Make sure the counter indicates more than 200MB.
Change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\HeapDeCommitFreeBlockThreshold to equal 262144.
8.
At this point, if you are still experiencing virtual memory issues,
then you either have a heavily loaded system or memory leaks. If you suspect
a memory leak, monitor the Process(Store)\Private Bytes counter to determine
if it is growing over time. If you suspect the system is overloaded, you
will likely also encounter other indications, such as high CPU utilization.
9.
If the 9582 warnings have not stopped, then look at your Physical
Disk\Disk Queue Length counter for the database and transaction log drives
(run the diskperf -y command at the command prompt to view these counters).
The disk queue length should never be consistently above the number of
spindles in the array. You will see peaks, and ranges into the low hundreds
are acceptable. If the disk queue lengths are up into 300 and beyond
consistently, then you may have a disk bottleneck.
10.
If you reach this point and are still encountering virtual memory
issues, you must further reduce virtual memory consumption. For example,
find out what the storage group and database configuration is. You can
reduce this to 3 storage groups-to try to further reduce virtual memory
consumption.
-- Ben Winzenz Exchange MVP "Chris" <jack_mioff@YO_MAMMYexcite.com> wrote in message news:fpp4p059jtqu6avg6nljiphsealjh9j359@4ax.com... > HELP!!!! > > I have a single Exchange server with 2.5G RAM. > Exchange 2000 SP3 > Windows 2000 Server SP4 > > I am getting a 9582 *warning* message: > 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 gone to EventID.net and followed along with all the Qxxxxx > articles. I have: > > 1. Installed the last Post-SP3 patch (Store.exe shows version > 6.0.6603.0) > 2. I have added the HeapDecommit reg entry detailed in Q315407 > 3. I have set up counters in Performance Monitor as per Q325044, but I > don't know what they mean...here are the results: > > MSExchangeIS > VMLargestBlockSize 21876736.000 > VMTotalFreeBlocks 333.000 > VMTotalLargeFreeBlocks 21876736.000 > > Process Store > Virtual Bytes 1774796800 > > Any ideas? > Thanks! > _____________________________________________ > Remove "YoMammy" from the address to send mail.
- Next message: Greg Draz: "Tool to perform MDB to PST conversion"
- Previous message: Blake: "Amount of email passing through Exchange 2003"
- In reply to: Chris: "Error 9582 on Exch2000SP3 and W2KSP4 w/2.5 G RAM"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
