The first thing you should do when examining the logs is to see if anything in the “Result” column is not “SUCCESS”.Once the error occurs, go back to ProcMon and click the Capture Icon to stop capturing events.Go to your web application and trigger the error.There should NOT be a red “X” through it. Please make sure that the Capture icon (shaped like a magnifying class) is enabled.Click “Apply” and then “OK” to exit the Dialog.Create a rule that says “Process Name is w3wp.exe”.Add the w3wp.exe process to the filter by going to Filter -> Filter….
Reset the filter by clicking Filter -> Reset Filter.You need to be easily able to trigger the event that causes the error while ProcMon is running to avoid collecting too much information. So, with help of Process Monitor or similar system core level monitoring tools, users can thoroughly monitor and record the operations to any file/registry performed by any visible/invisible program in system at the same time, and finally through their reading/writing changes to get help for diagnosis of system failure or capture of malware, viruses or trojans, etc.Go to the page in your web application before your error occurs. It’s released in the excellent Windows Sysinternals, and offered by Microsoft TechNet, so its accuracy and reliability are needless to say.Īs a system process real-time monitoring tool, in general, Process Monitor not only combines all features of the two classic and powerful tools: Filemon + Regmon (of which Filemon is dedicated to monitoring any file operation process in system, and Regmon is used to monitor the reading/writing of registry), and also appends an extensive list of enhancements – please see the “Key Features” list for detail! Process Monitor is an advanced Windows OS and application monitoring tool (equivalent of Filemon + Regmon), specially designed for system troubleshooting and malware hunting for experienced users.
0 kommentar(er)
