Run process monitor and define any filters you require, once done goto File – Export Configuration and save it as ProcmonConfiguration.pmc in the same directory as the executable.Copy the process monitor executable into the exe directory in the logging folder structure.Extract the folder structure and files onto your server.First of all you need to download the logging.zip file that contains the batch files and folder structures from my drop box here.The rest of this blog will now cover the detailed steps to setup the rolling process monitor. Prevents the scheduled task that was running process monitor from running any more.įollowing this logic I now have a rolling process monitor solution that can run for months by running two simple batch files from scheduled tasks.Stops any running process monitor session.Create a schedule task that is fired on a windows event and does the following.Start a new instance of process monitor logging.Move the current log file to history folder and clean out any old logs.Stop any process monitor sessions already running.Run a scheduled task every x minutes that does the following.The solution I created for this is implemented using the following logic. How to ensure the capture stops once we have the data we are looking for.How to ensure we do not over write the data we are looking for.How to prevent the process monitor capture from consuming all available disk space.To identify the file lock I needed to run process monitor for as long as it takes to capture the problem even if it takes weeks or months for it to occur. Recently I needed to investigate why SSAS synchronisation commands were intermittently failing and the errors pointed to a file lock on a SSAS data file.
0 kommentar(er)
