Tuesday, January 20, 2009

Poolmon Logging Instructions

Use PoolMon3VBS.zip which allows you to capture what is consuming Paged and NonPaged pool memory.

If the SRV/2019 or SRV/2020 is occurring now or we are very close to the next occurrence we should examine the handle count in Task Manager Processes tab for each process. To add the Handle column to the Processes tab click "View" then "Select Columns...".

A high handle count (larger than 5,000) may indicate the offending process without any further troubleshooting. Stop the process or service if it is not necessary and observe Kernel Page and Nonpaged memory usage under Task Manager Performance tab. Else, complete the remaining steps to start data gathering. Sometimes a memory dump is required in addition to the output files generated by running _LogPool-as-a-service.CMD or LogPool.cmd

1) Collecting the Poolmondata:
- Rename PoolMon3VBS.ZIx to PoolMon3VBS.ZIP and extract its contents C:\POOLMON3
- Double click _LogPool-as-a-service.CMD to have Poolmon running as a service so that you do not have to restart LogPool.CMD each time you reboot or close the command window running LogPool.cmd.
- To be notified of a 2019, 2020, 2021, 2022 event in the system event log double click the corresponding 2019Mon.CMD, 2020Mon.CMD, 2021Mon.CMD or 2022Mon.CMD (requires another CMD instance)

When the issue reoccurs zip up the "C:\POOLMON3\Poolmon-Output" folder and save the zip file for review. For the next few days zip up the TXT files, the .CSV file and save the zip files at the start of each day even if the issue has not occurred. Often times you can determine abnormal consumption of pool memory resources before the issue occurs.

Starting with WinXP you can right click a folder and select "Send To" then "Compressed (zipped) Folder". After the issue is resolved you can remove the Poolmon service by double clicking on RemovePoolmon3service.cmd

No comments: