faloheroes.blogg.se - Procmon logs

Disable registry, network and process trace by pressing these buttons: In most trouble shooting scenarios, file tracing is enough. When started, MPM will automatically start showing all processes currently running, with registry, file, network and process activity. On first run, you will have to confirm to a license agreement. The tool does not have to be installed, just run it from the new location. Just copy the contents of the archive file to a new folder on the PC or server where you want to trace the problem, for example to C:\Program Files (x86)\Microsoft Process Monitor. Please note that MPM is not an Exact tool and not supported as such.

If you would like to save the logs, you can by going to File -> Save.Microsoft Process Monitor (MPM) can be used to trace problems related to file or registry access, or to show which process may be the last to execute before an error occurred.

Once you find the errors, determine if they are relevant to your issue.

Please take notes of any warnings or errors.

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. Go to the page in your web application before your error occurs.