ActiveBatch Messages

A Job has been marked as ‘aborted’.

This is an internal error usually indicating that insufficient hardware or software resources are available to satisfy a memory request.

The Execution Agent was unable to find the Job file’s extension to program association. The Job was not run.

This DBPurge message can appear in the Application Event Log and indicates that DBPurge was unable to remove old audit messages from a specific Job.

This is a general error indicating that a bad parameter was specified. Depending on the context you should specify a legal value or property and try again.

A Job completed and had a Batch Start (Success or Failure) action associated with it. That action could not be performed. Additional information accompanies this message indicating more specifically what the problem was.

This is a general non-specific error indicating that the client was unable to connect to a server machine. Please check the machine name or IP address and try again.

This message can occur if the “Copy File” feature is enabled for a Main, Pre or Post file. As the message indicates an error occurred while attempting to copy the file to the Job Scheduler.

The Execution Agent was unable to create the batch Job’s log file. Typically, the log file specification is not valid or proper OR the main Job script file specification is also not valid. Please check the log/script file specification and ensure it can be created from the Execution machine.

Self-explanatory. This error message concerns the running of the DBPurge facility to prune unneeded Jobs from the ActiveBatch system.

The Batch Job failed because a Job dependency could not be satisfied.

An error occurred disconnecting from a Job Scheduler machine. This is typically not something to be overly concerned about since the error occurs on the disconnect itself.

This error is returned when an attempt has been made to create an object with a duplicate key (2 objects with the same name).

This serious error usually indicates some level of license tampering. Please run the ABATLIC program to obtain more information.

An Active Directory published name was provided by a user and could not be translated. Please check the AD name given and try again.

The Job Scheduler was unable to connect to the Execution Agent machine. Please check the machine name or IP address and try again; the machine may not be on the network; the machine may not be running RPC or DCE services.

Self-explanatory. Depending on network conditions this problem may resolve itself as the machine is rediscovered.

The Execution Agent has set this Job’s exit status code because of an overrun for CPU time and has aborted the Job.

This Job was terminated because it tried to execute after its established dispatch time.

The Execution Agent has set this Job’s exit status code because of an overrun for elapsed run time and has aborted the Job.

A Job was aborted when an Execution Agent/machine failed. The Job was not marked as being restartable.

A non-specific error occurred. The error is typically either internal or transient. Please try the operation again.

The ActiveBatch Administrator has prevented your file from being copied to the Execution Machine through the System policy CopyScriptMax

A Force Run command was issued and was unable to execute. The JSS log (found in the LOG sub-directory provides additional information).

ActiveBatch is unable to retrieve the owner of the object. This error may appear if the domain of the owner’s account is not available.

The object you want to delete is referred to by other objects. You must either disassociate these object references or enable the forceddelete flag to forcibly dereference these associations.

This error can be returned if you attempt to connect to a Job Scheduler while the Scheduler is still in the process of starting. Please wait a moment and try again.

The ActiveBatch base product license you’ve previously entered does not allow operation on this Operating system type (for example, Enterprise or Datacenter Server).

The operation to initialize a Queue failed. The Queue was not created. A more specific error usually accompanies this error.

This is an internal error indicating a failure to create a security descriptor the object. This error may be logged to the product’s trace file.

This audit message indicates that a Job instance could not be executed because the template’s property did not allow multiple concurrent copies of the Job to run simultaneously.

This audit message indicates that a Job instance could not be executed because the “If Job Active… Wait” property was enabled and the timeout period expired.

You attempted to perform a Queue or Job operation for which you lack sufficient access permissions.

You have attempted to create a Job and Schedule combination in which the Job will never run. For example, scheduling a Job on December 25th and then assigning a Calendar with Christmas as a holiday.

Self-explanatory.

The operation attempted is illegal when used against a Job’s template. Please verify operation and then issue against Job instance.

Either: an invalid context was specified on an enumeration, or an invalid operation was specified based on a Job current state. For example, attempting to release a Job which isn’t held.

The time you entered was not in 24-hour time format. 00:00 through 23:59 is the legal range.

An illegal O/S priority value has been specified as part of a Job.

You specified an illegal O/S priority value as the Job default with a Queue.

Data associated with a Registry Key is of an incompatible type. For example, the datatype should be REG_DWORD and the value was found to be REG_SZ; the value itself is not legal.

The time you entered was not in 24-hour time format. 00:00 through 23:59 is the legal range.

This general error indicates that you are attempting to add an object to a collection and the object already exists. For example, trying to add the same account and access to a security collection.

This is the exit status code of a Job that has been aborted.

You attempted to trigger a Job that is held for execution. Release the Job first and then retry.

This is an internal error indicating that the Job’s History information could not be retrieved.

You tried to Force Run a Job that is not in a wait state

This is the exit status code of a Job Scheduler Service which could not be started. Check the trace file or NT Application Event Log for more information.

An attempt to delete a Queue failed due to Jobs currently on Queue. You can indicate that a ‘flush’ operation first be performed prior to the actual Queue delete.

A Job with monitoring enabled completed execution in much less time than was unexpected. The Job is marked as having failed.

The client was unable to connect to the Job Scheduler machine. Please check the machine name or IP address and try again; the machine may not be on the network.

The Job Scheduler service cannot be started. Please check the AbatJSS.log file (in the LOG sub-directory) for more information.

This error/warning code indicates that a search for a specific object failed to be found in the database.

The evaluation serial number has expired. Please contact ASCI or your distributor for an extension.

When using the Personal Edition license you are restricted to a Workstation/Professional NT system and all connections are local to that system.

This error indicates that the user’s username and/or password was not proper for logging the user onto the Execution Machine. Check the username and password (may be case sensitive) for the target system. More specific details may be found in the Execution Agent log file.

This licensing error indicates that the maximum number of Execution Agent licenses has been reached. Count each Execution Machine you are attempting to connect to (regardless of whether the machine is active or the Queue is started) and then compare against the value reported by the ABATLIC program.

You are attempting to connect to a non-Microsoft Execution Agent and your license only permits you to connect to Microsoft Execution Agents.

This is an error indicating that a protocol sequence established in the Registry is not available on this machine. The RPC protocol sequence Registry key should be examined since it contains erroneous transports.

A machine name needs to be specified. This error most typically occurs as a requirement for an Execution Queue or when connecting to a Job Scheduler machine.

This message code, typically returned as part of a context search, indicates that no more objects are available.

Attempting an advanced connection requires a password; attempting to execute a batch Job requires a password (unless Blank Password is enabled). Specify the password and try again. Note: You can let Activebatch remember the password for you.

No Queue Name was specified and one was required. Specify a valid Queue Name and try again.

Self-explanatory.

You have attempted to perform an operation that requires a current connection to a Job Scheduler machine. Please make the connection and try again.

Self-explanatory. Check Queue properties.

You attempted to insert an object with a name that conflicts with an already existing object. The object you insert requires a unique name.

The Execution Agent was unable to open the batch Job’s script file. Please check the main Job’s file specification and ensure it can be opened from the Execution machine.

Self-explanatory.

An attempt to create a Queue of the same name failed since Queue names must be unique.

The Queue name you specified does not exist. Please check the spelling and try again.

ActiveBatch was unable to open a Registry Key value in HKEY_LOCAL_MACHINE. While you should check Registry security permissions this error typically means that the ActiveBatch Registry keys have been corrupted or otherwise tampered with. You should try executing a product REPAIR through the ADD/REMOVE Control Panel applet.

ActiveBatch was unable to obtain the specified Registry value-name. Typically this means the ActiveBatch Registry keys and/or value names have been corrupted or otherwise tampered with. You should try executing a product REPAIR through the ADD/REMOVE Control Panel applet.

Self-explanatory.

An error occurred while attempting to run this Job interactively. The error is most likely due to a lack of desktop permissions.

The client interface encountered an error while communicating with the Job Scheduler.

Your attempt to take ownership of this object failed. Verify that you have “Executive” level permission.

Self-explanatory.

Self-explanatory.

The batch user has been automatically granted the “Logon as a Batch User” right.

This audit message indicates that all Job dependencies were met.

An event occurred which triggered execution of a Job.

Self-explanatory. This message is displayed by the command-line client.

Self-explanatory. Typically found in the JSS Trace file or NT Application Event Log indicating the Job Scheduler Service has been started.

Typically a template Job is marked for deletion when one or more active instances are still executing.

Microsoft’s WMI Services are either not available or have not been started.

Operation completed normally. No action to be taken.

ActiveBatch was unable to lookup the specified accounts SID and validate the account. Check any domain and account name spelling.

The Execution Agent could not create a Windows 2000 Job Object within which to encapsulate the batch Job.

The Job Scheduler was unable to open the Job step(s) script/program file. An additional error code provides more information.

An error occurred creating the batch Job process. More specific details may be found in the Job’s log file.

The Job could not be restarted as it has reached its maximum restart count.

ActiveBatch was unable to find the object’s Security Descriptor.

This audit message appears if a Job was scheduled for execution but could not be executed due to an Exclusion List or Calendar conflict.

You cannot restart a Job that is not currently executing.

Self-explanatory. Check that the machine’s name or IP address is correct; verify that the machine is up and connected to the proper network; verify the RPCSS or DCE services have been started.

For Windows 2000 machines, the Execution Agent attempts to load a special DLL which associates Windows Job Objects with ActiveBatch Jobs. This warning indicates that Windows 2000 Job Objects will not be used.

Self-explanatory. Please check the Job step(s) file specifications. They must be accessible from the client machine.

This error can occur when a Generic Queue with Round Robin scheduling determines that no active Execution Queues are available to dispatch a Job.

The specified alert could not be found for update or deletion purposes.

Self-explanatory.

The machine or user characteristic you specified could not be found.

The specified user/machine contact information could not be found for update or deletion purposes.

Self-explanatory. The Job’s ID did not match any present Jobs in the system.

The specified policy does not exist. Check the policy name spelling.

The Job Scheduler and Execution Agent services cannot be run on non-Windows 2000/NT systems.

The specified Job is not a template. Certain operations can only be performed on a template Job, for example, you cannot submit or move a non-template Job to the OnDemand Queue.

A processor mask was specified for this Job. However, the mask affinity operation could not be performed. The Job will still execute. This can be caused if the number of actual processors is less than that specified or an O/S specific restriction on assigning processors to Jobs is violated.

An attempt to modify a property failed because the property was locked and cannot be changed by an ActiveBatch non-Administrator.

You didn’t specify a Schedule ID or the query event string for a Job.

This message, if displayed, would be found in a product trace file.

You cannot delete this Schedule since Jobs are currently associated. You can disassociate the Jobs from this Schedule and then delete the Schedule.

The Execution Agent could not terminate the Windows 2000 Job Object.  More information typically follows this error.

A Job was triggered was unable to be cloned. An additional message provides more information concerning this condition.

Unable to issue TRIGGER command as ActiveBatch Triggers are not enabled.

An unexpected exception occurred. Typically this message code is not delivered to user code and is found in the product’s trace file depending on the trace level specified.

The Execution Agent was unable to reconnect back to the Job Scheduler machine.

The WMI software has either not been installed or started.

ActiveBatch encountered an error issuing the Event Query string to WMI

Operation completed normally. No action to be taken.

Self-explanatory. Typically found in the JSS Trace file or NT Application Event Log indicating the Job Scheduler Service has been started.

Self-explanatory. This message is displayed by the command-line client.

An event occurred which triggered execution of a Job.

Microsoft’s WMI Services are either not available or have not been started.

This audit message indicates that all Job dependencies were met.

Typically a template Job is marked for deletion when one or more active instances are still executing.

The batch user has been automatically granted the “Logon as a Batch User” right.

An unexpected exception occurred. Typically this message code is not delivered to user code and is found in the product’s trace file depending on the trace level specified.

The Job Scheduler and Execution Agent services cannot be run on non-Windows 2000/NT systems.

An error occurred creating the batch Job process. More specific details may be found in the Job’s log file.

Self-explanatory. Check that the machine’s name or IP address is correct; verify that the machine is up and connected to the proper network; verify the RPCSS or DCE services have been started.

Self-explanatory. The Job’s ID did not match any present Jobs in the system.

You cannot delete this Schedule since Jobs are currently associated. You can disassociate the Jobs from this Schedule and then delete the Schedule.

You cannot restart a Job that is not currently executing.

The machine or user characteristic you specified could not be found.

This message code, typically returned as part of a context search, indicates that no more objects are available.

The specified user/machine contact information could not be found for update or deletion purposes.

The specified alert could not be found for update or deletion purposes.

You didn’t specify a Schedule ID or the query event string for a Job.

This error can occur when a Generic Queue with Round Robin scheduling determines that no active Execution Queues are available to dispatch a Job.

Self-explanatory. Please check the Job step(s) file specifications. They must be accessible from the client machine.

The Job Scheduler was unable to open the Job step(s) script/program file. An additional error code provides more information.

An attempt to modify a property failed because the property was locked and cannot be changed by an ActiveBatch non-Administrator.

A Job was triggered was unable to be cloned. An additional message provides more information concerning this condition.

The specified policy does not exist. Check the policy name spelling.

The specified Job is not a template. Certain operations can only be performed on a template Job, for example, you cannot submit or move a non-template Job to the OnDemand Queue.

ActiveBatch was unable to lookup the specified accounts SID and validate the account. Check any domain and account name spelling.

The Execution Agent was unable to reconnect back to the Job Scheduler machine.

The Execution Agent could not create a Windows 2000 Job Object within which to encapsulate the batch Job.

The Execution Agent could not terminate the Windows 2000 Job Object.  More information typically follows this error.

For Windows 2000 machines, the Execution Agent attempts to load a special DLL which associates Windows Job Objects with ActiveBatch Jobs. This warning indicates that Windows 2000 Job Objects will not be used.

This message, if displayed, would be found in a product trace file.

ActiveBatch was unable to find the object’s Security Descriptor.

A processor mask was specified for this Job. However, the mask affinity operation could not be performed. The Job will still execute. This can be caused if the number of actual processors is less than that specified or an O/S specific restriction on assigning processors to Jobs is violated.

The WMI software has either not been installed or started.

ActiveBatch encountered an error issuing the Event Query string to WMI

Unable to issue TRIGGER command as ActiveBatch Triggers are not enabled.

The Job could not be restarted as it has reached its maximum restart count.

Self-explanatory.

This audit message appears if a Job was scheduled for execution but could not be executed due to an Exclusion List or Calendar conflict.

A non-specific error occurred. The error is typically either internal or transient. Please try the operation again.

A machine name needs to be specified. This error most typically occurs as a requirement for an Execution Queue or when connecting to a Job Scheduler machine.

This is a general non-specific error indicating that the client was unable to connect to a server machine. Please check the machine name or IP address and try again.

The client was unable to connect to the Job Scheduler machine. Please check the machine name or IP address and try again; the machine may not be on the network.

The Job Scheduler was unable to connect to the Execution Agent machine. Please check the machine name or IP address and try again; the machine may not be on the network; the machine may not be running RPC or DCE services.

This is an internal error usually indicating that insufficient hardware or software resources are available to satisfy a memory request.

Data associated with a Registry Key is of an incompatible type. For example, the datatype should be REG_DWORD and the value was found to be REG_SZ; the value itself is not legal.

This is an error indicating that a protocol sequence established in the Registry is not available on this machine. The RPC protocol sequence Registry key should be examined since it contains erroneous transports.

This is a general error indicating that a bad parameter was specified. Depending on the context you should specify a legal value or property and try again.

The operation to initialize a Queue failed. The Queue was not created. A more specific error usually accompanies this error.

An error occurred disconnecting from a Job Scheduler machine. This is typically not something to be overly concerned about since the error occurs on the disconnect itself.

No Queue name was specified and one was required. Specify a valid Queue name and try again.

Attempting an advanced connection requires a password; attempting to execute a batch Job requires a password (unless Blank Password is enabled). Specify the password and try again. Note: You can let Activebatch remember the password for you.

ActiveBatch was unable to open a Registry Key value in HKEY_LOCAL_MACHINE. While you should check Registry security permissions this error typically means that the ActiveBatch Registry keys have been corrupted or otherwise tampered with. You should try executing a product REPAIR through the ADD/REMOVE Control Panel applet.

ActiveBatch was unable to obtain the specified Registry value-name. Typically this means the ActiveBatch Registry keys and/or value names have been corrupted or otherwise tampered with. You should try executing a product REPAIR through the ADD/REMOVE Control Panel applet.

You specified an illegal O/S priority value as the Job default with a Queue.

The time you entered was not in 24-hour time format. 00:00 through 23:59 is the legal range.

The time you entered was not in 24-hour time format. 00:00 through 23:59 is the legal range.

The Queue Name you specified does not exist. Please check the spelling and try again.

Self-explanatory. Depending on network conditions this problem may resolve itself as the machine is rediscovered.

An attempt to create a Queue of the same name failed since Queue names must be unique.

An illegal O/S priority value has been specified as part of a Job.

This error/warning code indicates that a search for a specific object failed to be found in the database.

This error is returned when an attempt has been made to create an object with a duplicate key (2 objects with the same name).

This is an initialization error and indicates that the

Database server has not been started. Verify that W32MKDE.EXE exists within the ActiveBatch installation directory.

Self-explanatory.

This error indicates that the user’s username and/or password was not proper for logging the user onto the Execution Machine. Check the username and password (may be case sensitive) for the target system. More specific details may be found in the Job’s log file.

An attempt to delete a Queue failed due to Jobs currently on Queue. You can indicate that a ‘flush’ operation first be performed prior to the actual Queue delete.

A Job has been marked as ‘aborted’.

This is the exit status code of a Job that has been aborted.

This error can be returned if you attempt to connect to a Job Scheduler while the Scheduler is still in the process of starting. Please wait a moment and try again.

Either: an invalid context was specified on an enumeration, or an invalid operation was specified based on a Job current state. For example, attempting to release a Job which isn’t held.

This error usually indicates that insufficient resources have been allocated for the Database server.

Self-explanatory. Check Queue properties.

You attempted to perform a queue or Job operation for which you lack sufficient access permissions.

This is an internal error indicating a failure to create a security descriptor the object. This error may be logged to the product’s trace file.

The Execution Agent was unable to find the Job file’s extension to program association. The Job was not run.

The Execution Agent was unable to create the batch Job’s log file. Typically, the log file specification is not valid or proper OR the main Job script file specification is also not valid. Please check the log/script file specification and ensure it can be created from the Execution machine.

The Execution Agent was unable to open the batch Job’s script file. Please check the main Job’s file specification and ensure it can be opened from the Execution machine.

The evaluation serial number has expired. Please contact ASCI or your distributor for an extension.

This is the exit status code of a Job Scheduler Service which could not be started. Check the trace file or NT Application Event Log for more information.

You have attempted to perform an operation that requires a current connection to a Job Scheduler machine. Please make the connection and try again.

This general error indicates that you are attempting to add an object to a collection and the object already exists. For example, trying to add the same account and access to a security collection.

The client interface encountered an error while communicating with the Job Scheduler.

Self-explanatory.

This message can occur if the “Copy File” feature is enabled for a Main, Pre or Post file. As the message indicates an error occurred while attempting to copy the file to the Job Scheduler.

The ActiveBatch Administrator has prevented your file from being copied to the Execution Machine through the System policy CopyScriptMax.

This is an internal error indicating that the Job’s History information could not be retrieved.

The Batch Job failed because a Job dependency could not be satisfied.

Self-explanatory.

The Execution Agent has set this Job’s exit status code because of an overrun for elapsed run time and has aborted the Job.

The Execution Agent has set this Job’s exit status code because of an overrun for CPU time and has aborted the Job.

Self-explanatory.

A Job completed and had a Batch Start (Success or Failure) action associated with it. That action could not be performed. Additional information accompanies this message indicating more specifically what the problem was.

A Job was aborted when an Execution Agent/machine failed. The Job was not marked as being restartable.

This licensing error indicates that the maximum number of Execution Agent licenses has been reached. Count each Execution Machine you are attempting to connect to (regardless of whether the machine is active or the Queue is started) and then compare against the value reported by the ABATLIC program.

You are attempting to connect to a non-Microsoft Execution Agent and your license only permits you to connect to Microsoft Execution Agents.

This serious error usually indicates some level of license tampering. Please run the ABATLIC program to obtain more information.

When using the Personal Edition license you are restricted to a Workstation/Professional NT system and all connections are local to that system.

Self-explanatory.

Your attempt to take ownership of this object failed. Verify that you have “Executive” level permission.

ActiveBatch is unable to retrieve the owner of the object. This error may appear if the domain of the owner’s account is not available.

Self-explanatory. This error message concerns the running of the DBPurge facility to prune unneeded Jobs from the ActiveBatch system.

This DBPurge message can appear in the NT

Application Event Log and indicates that DBPurge was unable to remove old audit messages from a specific Job.

This audit message indicates that a Job instance could not be executed because the template’s property did not allow multiple concurrent copies of the Job to run simultaneously.

This audit message indicates that a Job instance could not be executed because the “If Job Active… Wait” property was enabled and the timeout period expired.

Self-explanatory.

An error occurred while attempting to run this Job interactively. The error is most likely due to a lack of desktop permissions.