Author: ezeltje
Subject: ProcessMonitor stops after reaching history depth
Posted: 28 September 2016 at 1:47pm
I am troubleshooting a client-server application where the clients become unresponsive after several weeks of continuous operation. When the problem occurs, either the server side of the application is restarted or the server is rebooted.
Since I strongly suspect that the root cause of the problem is on the server, I want to run ProcessMonitor until the application gets restarted or the server rebooted. I have configured it to use backing files for storing the event data so I can analyze it offline. To avoid using to much disk space for the logging I have restricted the history depth to 125M events.
I expected ProcessMonitor to continue to run but it stops, seemingly when it reaches the history depth limit. I didn't find anything in the Windows event log about ProcessMonitor stopping unexpectedly, so this appears to be designed behaviour. The manual suggests otherwise "that you can leave Process Monitor running for long periods and ensure that it always keeps the most recent events". Therefore I consider this a bug.
I have to add that I script running ProcessMonitor and that I run that script through the task scheduler to allow ProcessMonitor to run unattended while I'm not logged in.
Subject: ProcessMonitor stops after reaching history depth
Posted: 28 September 2016 at 1:47pm
I am troubleshooting a client-server application where the clients become unresponsive after several weeks of continuous operation. When the problem occurs, either the server side of the application is restarted or the server is rebooted.
Since I strongly suspect that the root cause of the problem is on the server, I want to run ProcessMonitor until the application gets restarted or the server rebooted. I have configured it to use backing files for storing the event data so I can analyze it offline. To avoid using to much disk space for the logging I have restricted the history depth to 125M events.
I expected ProcessMonitor to continue to run but it stops, seemingly when it reaches the history depth limit. I didn't find anything in the Windows event log about ProcessMonitor stopping unexpectedly, so this appears to be designed behaviour. The manual suggests otherwise "that you can leave Process Monitor running for long periods and ensure that it always keeps the most recent events". Therefore I consider this a bug.
I have to add that I script running ProcessMonitor and that I run that script through the task scheduler to allow ProcessMonitor to run unattended while I'm not logged in.