Event Log

<< Click to Display Table of Contents >>

Navigation:  Monitoring with EventSentry > System Health Monitoring > Application Scheduler >

Event Log

Event Log 32 n t

The following events are logged by this feature with the Application Scheduler event category.

 

Event ID

Event Description

Example

10200

An application was executed successfully.

superdel.exe was run for 15 seconds with the result shown below. Return Code was 0.

 

10201

A process could not be created.

The process superdel.exe could not be created due to the following error: The file could not be found.

 

10202

A process exceeded the maximum configured time interval, but the process could not be terminated.

The process superdel.exe exceeded the maximum allowed time interval of 15 minute(s). EventSentry was unable to terminate the process due to the following error: Acess Denied.

 

10203

A process exceeded the maximum configured time interval and was terminated.

The process superdel.exe exceeded the maximum allowed time interval of 15 minute(s). The process was terminated. Please increase the timeout interval for this drive in the management application (System Health -> 3rd Party Applications).

10204

A process was executed successfully.

dosomething.exe was executed successfully.

10205

A process exceeded the maximum configured time interval but could not be terminated. 0 or more child processes were terminated.

The process dosomething.exe exceeded the maximum allowed time interval of 2 minute(s). EventSentry was unable to terminate the process due to the following error:

 

Access Denied

 

1 child process(es) were successfully terminated.

10206

A process exceeded the maximum configured time interval and was terminated.

The process adlist.exe exceeded the maximum allowed time interval of 5 minute(s). The process and 0 child process(es) was terminated. Please increase the timeout interval for this process in the management console (System Health -> Application Scheduler).

10210

A process was not started because the isolation level of the schedule is set to local and another instance of the same process is already running.

The process adlist.exe was not started because the script is configured for local isolation and another instance of the same script is already running.

10211

A process wasn't started because it is configured for global isolation, and another process also configured for global isolation is already running.

The process adslist was not started because a script which is configured for global isolation (avscan.exe) is already running.