That means that the perfRun.exe for the monitor crashed. Not too helpful by itself
Inspect the Windows event log on the Execution Server for any crash events around the same time.
Verify that you've not run out of disk space or other basic resources on that system.
Thank you for the response. I should have added that we get a clean run and then this error and then another clean run. We are upgrading from 3.9 / 2003 servers to 4.2.2 / 2008 servers. Most of our scripts are running with no issues, but two seem to have this error.
My advice above still applies. Are there any events logged in Windows Event Log at the time of the crash?
In a TM ART ES, the perfRun.exe process starts when the monitor is activated or updated and doesn't end unless the monitor has a finite schedule or the system is shutdown. So in the two problem cases, when the perfRun wakes up for another iteration, something is causing it to crash.
Is there anything unusual about the two monitors that are having problems? Are they longer scripts than the others? More complex (like looping or anything)? Different monitor type (Citrix vs Web, etc)?
Did you do any config file tweaks to your 3.9 systems that you have not brought forward to your 4.2 system?
Also, if you have not done so, I'd recommend a support case be opened.
South Coast Software Consulting