#WINDOWS 2008 PROCESS MONITOR SERIES#I am starting a series tagged with “ Tools Tips and Tricks” which will document the various tweaks that I use for data collection for the various data collection/analysis tools that I use on a day-to-day basic. Note that this option considerably increases the export time due to symbol resolution time involved. The symbol path is needed when /SaveAs2 option is used for converting the. This will help you resolve the function calls using the symbol path and if a source path is present, open a text viewer dialog with the source line highlighted which is being referenced. Additionally, you can specify the path to the source files for the application in the same dialog. You can point to the symbol path (local symbol cache or Microsoft Symbol Server: ) using Options –> Configure Symbols. Process Monitor can use symbol information, if available, to show functions referenced on event stacks. I normally point the backing file to a local drive on the machine which has sufficient amount of disk space. This prevents using the page file as the backing store for trace capture and avoid running in unresponsive server issues while you are still capturing your trace and the paging file fills up. One of the most useful options that I suggest using when capturing a Process Monitor trace is to use the backing file option ( /BackingFile command line parameter or CTRL B when using the GUI). I had used /OpenLog and /SaveAs1 option to generate the XML file from the saved. The command line options specified are immensely helpful if you are scripting the capture of a trace using a batch file or if you are generating an automation routine to load the captured data into another data source. More information about the above is available in the Process Monitor help file. In the toolbar show on the left in the screenshot, you can enable/disable the following captures: The capture tracks three classes of operations: File System, Registry and Process. The first tip is to disable any activity that you don’t want to capture or are not required for the issue that you are troubleshooting. This prompted me to think about capturing data with Process Monitor and some things I learnt along way while using this tool working at CSS. I recently wrote about importing a Process Monitor trace into SQL Server database table and crunch up the data to extract the events and call stacks. Use the options mentioned in Tools Tips and Tricks #1: Process Monitor so that the filters are correctly set and the page file doesn’t get overwhelmed if you are capturing data for long periods or on servers where there is high amount of activity. Or you could alternatively create a configuration file and use the /LoadConfig command line switch for Process Monitor.Īgain the possibilities are endless and you can extend this by using the command line options for PsExec and Process Monitor. After that Exit Process Monitor and run the above command from Command Line. If you need to set filters for Process Monitor, then run the Process Monitor tool in GUI mode and set the Filters and save it. This utility takes a parameter for milli-seconds to wait. #WINDOWS 2008 PROCESS MONITOR WINDOWS#If you do not prefer the ping method to simulate waits, you can use the SLEEP utility available with Windows 2003 Resource Kit. The command that I used to execute the commands present in the. The reason why we would have to run Process Monitor from command line is because while running setup, it’s recommended that you do not log into the passive nodes using Terminal Services or Console Mode. cmd file to spawn Process Monitor on a different server and capture a trace using a local file as the backing file. Start %PM% /quiet /minimized /AcceptEULA /backingfile D:\ProcMon\notepad.pml cmd file that I am using in this case has the following commands: This is quite useful if you need to collect a Process Monitor trace from one of the passive nodes while running SQL Server 2005 setup. The scenario that I will discuss today is collection of a Process Monitor trace on a server without logging onto the machine. #WINDOWS 2008 PROCESS MONITOR INSTALL#PsExec lets you execute processes on other systems without having to manually install client software. Today I shall talk about using PsExec (part of the PsTools package) to collect data from a remote box through PsExec. A new week begins and the Tools, Tips and Tricks series continues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |