RE: Virtual Memory error
Brian, Recently someone had the same issues as you and the following was posted here - Here is something from Marc Stanton (Microsoft) Here is a useful checklist for VM problems that should be able to help solve your problems 1. Check whether this is Win2K Server or Advanced Server. If it's Server, then make sure that the /3GB switch is not in the boot.ini. If this is Advanced Server and there is more than 1Gb of physical RAM installed, ensure that /3GB does appear in the boot.ini 2. Look at the app log.are you seeing 9582 warnings (i.e. 32Mb block available) or 9582 errors (i.e. 16Mb block available). 3. Are the 9582's being accompanied by other out of memory errors such as 12800 events. If so, then you probably have users calling up the support desk asking why their mail isn't working. If user experience is good, then the 9582 may be relatively benign, but should still be investigated for possible action. 4. Look at the MSExchangeIS | VM Largest Block Size perfmon counter .I find this is the best counter to try figure out if something is wrong. You can look at this in realtime to get some data, but if you want to spot trends and figure out if memory is being released, then log this counter for 1 min intervals and collect about 18-24 hours worth. Look at the 'Minimum' value to see what the dip is. Don't worry if this value appears to be low, our own E2K servers at Microsoft were running at 55Mb as the largest block size. 5. Be aware that other store-related processes like virus scanning can tip the threshold. For example, at one customer, by enabling MDB scanning, the VM block would dip below 32Mb and thus the 9582's were generated. However, we only dipped slightly under 32Mb and user perf was absolutely fine. Additionally, during the night, the VM block would grow and the 9582's would stop. This is a classic example of a benign 9582 .as long as user perf is good and the VM block grows again during quiet times. 6. Unfortunately, some scenarios will dictate that you need to do something to get rid of the 9582's .pulling the MDB scanner off (if running) will probably do the trick, but this is a band-aid, not the solution. First of all, you really need to make sure that the server is running Exchange SP3. At various customers, we saw massive VM improvements once SP3 was applied. If you're running on a cluster, also make sure that Q315771 is installed. You'll also want to get the latest scsiport.sys driver install. The version which comes with Win2K SP2 is known to fragment VM (see Q311901 for more details) 7. If you're still seeing 9582's then you need to perform a reg tweak. This tweak is okay as long as there is a decent amount of RAM available in the server. Look at Memory | Available Bytes .if you have more than a couple hundred megs, then you're fine. This is the parameter that ITG runs with: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\HeapDeCommitFreeBlockThreshold=262144 8. At this stage, things should be on the up. For example, by doing all the above, a customer was able to re-enable MDB scanning and still only dip to 348Mb as the VM Largest Block. If you're still seeing issues, then you're either dealing with a heavily loaded system, or a leaky application. If you suspect a leaky app, take a look at Process | Private Bytes | Store to see if this is growing over a period of time. If you suspect the system is overloaded, then there should be other giveaways (such as high CPU utilization). 9. If the 9582's have still not disappeared, then take a look at your Physical Disk | Disk Queue Lengths for database and log drives (you'll need diskperf -y to get these stats). The disk queue length should never be consistently above the number of spindles in the array. You will of course see peaks, and these can range into the low hundreds, but this is fine. If disk queue lengths are up into 300+ and beyond pretty consistently then you have a disk bottleneck somewhere. If you determine that the disk is good, then you can lower the ESE buffer from 850 to 800Mb and get some more VM to play with This is the msExchESEParamCacheSizeMax value that is outlined in the Quick Tuning Guide. Note: Many customers with large systems actually up this value from 0.85Gb to 1.2Gb to get additional perf, however if you're VM bound, then it's much better to lower the value. 10. If after all this, things are still looking bad, you need to find other ways of reducing VM consumption. For example, what is the SG / MDB configuration? A customer having massive VM problems had 4 Storage Groups hosting a total of 8 databases. We got that down to 3 storage groups and they went away .sometimes the fourth will tip the server over the edge. This is certainly true for Exchange 2000 SP2 and under. SP3 this is not as big of deal 11. If all else fails, you will need to get a VADUMP (E2K reskit) on the store and contact PSS
RE: Virtual Memory error
Thanks for the info on the q article I will start digging in more, Just seems odd that this popped up after 6 months of running smoothly. Brian _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Virtual Memory error
maybe your server has mutated into the Advanced form? :) any radiation sources nearby? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 7:34 AM To: Exchange Discussions Subject: RE: Virtual Memory error Thanks for the info on the q article I will start digging in more, Just seems odd that this popped up after 6 months of running smoothly. Brian _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Virtual Memory error
I interpret this: http://support.microsoft.com/default.aspx?scid=kb;en-us;266096 to mean that if you have more than 1GB of RAM in an exchange server, you must be run it on win2k advance and use the /3GB switch. In the past, other knowledgeable Exchange folk have argued against this interpretation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 1:06 PM To: Exchange Discussions Subject: Virtual Memory error My current setup is Windows 2000 (standard) with Exchange 2000 enterprise with 2 gig ram I am getting the following error message in the event log Source:MSExchangeIS, EventID:9582 The virtual memory 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 checked technet and they talk about a 3gb switch in the boot.ini if you are running Windows 2000 advanced server, but no other references. Is there any otehr places to look? Eventually it will degrade to the point I will have to restart the services and If I restart the services it will go away for a day but then it returns. Any help would be appreciated Thanks Brian McDonald _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Virtual Memory error
Ken, have you looked at other articles? Look at: http://support.microsoft.com/default.aspx?scid=kb;en-us;328882 It clearly states that the only reason that you don't use the /3gb switch on Standard is because you end up losing a GB of allocatable virtual memory. I have never seen a problem running Exchange 2000 on W2K Standard with more than 1gb of RAM. In fact, we had to upgrade ours from 1GB to 1.5GB - it is running even better now that we put more memory in it. Brian, Do not use the /3gb switch on W2K standard. Read the bottom part of that article for suggestions on what you might be able to do to help in your situation. Ben Winzenz Network Engineer Gardner White (317) 581-1580 ext 418 -Original Message- From: Ken Cornetet [mailto:[EMAIL PROTECTED] Posted At: Wednesday, July 02, 2003 2:50 PM Posted To: Exchange (Swynk) Conversation: Virtual Memory error Subject: RE: Virtual Memory error I interpret this: http://support.microsoft.com/default.aspx?scid=kb;en-us;266096 to mean that if you have more than 1GB of RAM in an exchange server, you must be run it on win2k advance and use the /3GB switch. In the past, other knowledgeable Exchange folk have argued against this interpretation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 1:06 PM To: Exchange Discussions Subject: Virtual Memory error My current setup is Windows 2000 (standard) with Exchange 2000 enterprise with 2 gig ram I am getting the following error message in the event log Source:MSExchangeIS, EventID:9582 The virtual memory 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 checked technet and they talk about a 3gb switch in the boot.ini if you are running Windows 2000 advanced server, but no other references. Is there any otehr places to look? Eventually it will degrade to the point I will have to restart the services and If I restart the services it will go away for a day but then it returns. Any help would be appreciated Thanks Brian McDonald _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
