ErrorCode Class

Separator used to separate the insertion strings for the error message text. See Params.

The child job has finished running.

The user canceled the job while it was running.

The job was preempted by a higher priority job. For details, see the CanPreempt and the PreemptionType cluster parameter in the Remarks section of SetClusterParameter(String, String).

The job exceeded its run-time limit. See Runtime and Runtime.

An error occurred on the node.

The job or task was scheduled to run on a node that is no longer reachable.

The parent job of this child job has been canceled.

The process has exited.

The job failed to start on one or more nodes or the nodes were not reachable.

The job failed to start on node {0}.

The scheduler was not able to execute the command specified in the task.

The task failed.

The task exceeded its run-time limit. See Runtime.

The job to which the task belongs was canceled.

The task was canceled while it was running because a job with higher priority preempted the task. If the task can be rerun, the HPC Job Scheduler service will attempt to automatically queue it again.

An unknown error occurred.

The value is outside the allowable range of values.

Authenticate failure.

The user canceled the job or task.

You cannot remove item {0} from the default job template.

You cannot change the name of the default job template.

You cannot submit child job, instead you must submit the parent job.

Not able to register with the server.

Cryptography error.

A database exception occurred while processing the request.

The scheduler was unable to create a new job because the database is full.

Duplicate application found in the software license item.

The environment variable name was too long. The size must be smaller than {0} characters.

The environment variable value was too long. The size must be smaller than {0} characters.

The job template property {0} is not a legal job template property.

You cannot cancel the job in its current state.

You cannot cancel the task in its current state.

The provided environment variable name is not valid.

The provided environment variable value is not valid.

You cannot filter on property '{0}' for this type of object.

The job identifier does not identify an existing job in the scheduler.

Invalid specification for '{0}'.

The node identifier does not identify and existing node in the cluster.

The requested operation is not valid.

The job template identifier is not valid.

The row enumeration identifier is not valid.

The task identifier does not identify and existing task in the scheduler.

The job already exists on the server.

Job modification failed: {0}.

The job was not found on the server.

Unable to revert the job changes.

You must specify a job template name.

The user does not have permission to use the job template.

No storage is currently defined for the property.

You do not have permission to change this job template.

The user is not allowed to create job templates.

The default job template cannot be deleted.

The user is not allowed to delete job templates.

Cannot perform the operation because you are not connected to the server.

The job must be in the configuration state in order to submit the job.

You can submit the task only if the task is in the Configuring state.

You can reconfigure only canceled or failed jobs.

The user does not have permission to perform the operation.

You cannot change HPC-defined environment variables.

The job template item that you are trying to set already exists.

The default value for the job template item is not within the allowed value range for the item.

The default values specified for the job template item {0} must include all of the required values for that item. Ensure that the default values include all the values in the Required Values list, and then try again.

The job template item that you are trying to set does not exist.

The minimum constraint for the job template item is greater than its maximum constraint.

You must provide a default value for the job template item.

Invalid template: The template item {0}'s default value, {1}, is larger than the default value of the related template item, {2} (default value: {3}). Correct this inconsistency and try again.

Invalid template: The template item {0}'s maximum value, {1}, is larger than the maximum value of the related template item, {2} (maximum value: {3}). Correct this inconsistency and try again.

Invalid template: The template item {0}'s minimum value, {1}, is larger than the minimum value of the related template item, {2} (minimum value: {3}). Correct this inconsistency and try again.

The value of the job template item cannot be less than zero.

The data type used to set or access the job template item does not match the data type of the item.

A job template with the specified name already exists.

The job template does not exist in the scheduler.

The property is read-only and cannot be set.

The property name already exists.

The value is too large.

You cannot change the property when the job is in the current state.

Failed to modify the task.

You cannot change the property when the node is in the current state.

You cannot modify the job property when the job is in its current state.

You cannot modify the job property when the job is in its current state.

The task cannot be modified in its current state.

If the job is a backfill job, you cannot modify the job's runtime value when the job is running.

The exception was not expected.

The specified node group does not exist.

The software license format is not valid. The valid format is application: numberoflicenses{,application:numberoflicenses.

The cluster does not contain a node that is capable of running a broker job.

Failed to run the activation filter specified in the ActivationFilterProgram cluster parameter.

There are no nodes available to run the task.

The BackendBinding value specified in the service broker's configuration file is not valid. Correct the binding and start a new session.

The configuration file for the service broker was not valid.

The broker could not find the HPC environment information.

The service name or assembly name was not specified.

The broker failed to open the service broker web service.

The broker failed to open the service registration web service.

An unexpected exception occurred. Please see the broker execution log for details.

Not able to find the service assembly file name in the service registration file. Please ensure that the service registration file has the correct format.

Failed to find the service assembly file. Please ensure that the assembly has been deployed and registered on the node.

Failed to load the service assembly. Please ensure that the security settings for the assembly are correct and that the service assembly information at HKLM\Microsoft\Hpc\ServiceRegistry<ServiceName>\AssemblyPath) is correct.

The service registration file is not in the correct format. Please use the service registration XML schema to ensure that the service registration file is in the correct format.

Failed to find the service contract interface from the service assembly. Please ensure that the contract information provided in the service registration is valid (see HKLM\Microsoft\Hpc\ServiceRegistry<ServiceName>\AssemblyPath and Contract type).

The service registry is corrupt.

Failed to register to the broker service.

Failed to find the contract implemented by the service type.

Failed to open the service host. Please ensure that the NetTcp port sharing service is running and that the user has permission to use port sharing service, and that the firewall settings are correct.

The service name is not specified.

Cannot locate the service registration file in both %CCP_HOME%ServiceRegistration folder and user specified central registration folder (if any). Please ensure that the service has been successfully deployed.

Failed to find the service type from the service assembly. Please ensure that the type information in the service registration is valid (see HKLM\Microsoft\Hpc\ServiceRegistry<ServiceName>\AssemblyPath and ServiceType).

Failed to load the service type from the service assembly.

An unexpected exception occurred. Please see the service host execution log for details.

The operation was a success.

An unknown error occurred.

A batch job cannot be a child job.

Failed to compute the maximum resource requirement for the job.

Failed to compute the minimum resource requirement for the job.

A child job cannot contain another child job.

The parent identifier included in the child job is different than its parent’s actual identifier.

The child job must be a router job.

The child job is not valid.

The cluster does not contain the required minimum number of resources.

The credentials specified for this job are not able to log onto the cluster.

Failed to calculate task group level.

The contents of the DependsOn property is not valid.

Job submission failed because the job submission filter application is not valid. Your cluster administrator should check that the submission filter is an executable binary file (".exe" file) or Windows command script (".cmd" file).

A node that the job requests does not support the job’s job type.

The job is missing the user name or password.

The list of requested nodes does not contain a valid node.

The job requires a node that is not available.

The list of nodes that the task requires must be included in the list of the nodes that the job requested.

The maximum number of resource units must be greater than zero.

The maximum number of resource units cannot be less than zero.

You must specify the maximum number of resource units that the job requires if the AutoCalculateMax property is false.

You must specify a maximum resource value for the task.

The minimum value must be less than the maximum value.

The minimum number of resource units must be greater than zero.

The minimum number of resource units cannot be less than zero.

You must specify the minimum number of resource units that the job requires if the AutoCalculateMin property is false.

You must specify a minimum resource value for the task.

The task must specify a command to run.

The computed resources for the job is less than the required number of resources.

The node does not exist in the cluster.

The cluster does not contain a node that supports the specified resource requirements for the job (for example, memory or core requirements). Please adjust your requirements and submit the job again.

The parent job must be a service job.

The parent job is not valid.

The job template does not exist.

The property value is not within the allowed range of values as specified by the job template.

A property that requires a value as specified by the job template has not been set.

A router job cannot be a child job.

To reserve resources for a job (when the job does not contain tasks and has requested that it run until canceled), you must specify the maximum and minimum resource values for the job – you cannot request that the scheduler compute the maximum and minimum resource values.

To reserve resources for a job (when the job does not contain tasks and has requested that it run until canceled), you must specify the maximum and minimum resource values for the job.

A service job cannot be a child job.

Job submission failed because the job submission filter application could not be found. Your cluster administrator should check that the submission filter is accessible from the head node of the cluster and the path to the submission filter is a fully-qualified (not relative) path name.

The job failed to pass the job submission filter specified in the SubmissionFilterProgram cluster parameter.

The task must specify the same resource unit as the job.

The dependency list for multiple tasks creates a circular dependency.

The minimum and maximum resource requirements cannot be computed for a job with exclusive access to the nodes. You must specify the minimum and maximum resource values and resubmit the job.

The task can run exclusively on a node only if the job specifies that it must run exclusively on the node.

The task failed because the scheduler could not validate its parent job. Correct the validation error on the parent job and resubmit the job.

The task specifies a list of dependent tasks but the task does not specify a name value for itself; each dependent task and the task specifying the dependency must include a name value.

The task cannot specify required nodes when the job has requested that the scheduler compute the required resources.

The increment value for a parametric task must be greater than or equal to 1.

The start value for a parametric task cannot be greater than end value.

The maximum resource value for the task must be less than that of the job.

The minimum resource value for the task must be less than that of the job.

The minimum resource value for the task must be less than its maximum The minimum resource value for the task must be less than that of the job value.

You have exceeded the number of times that a task can be queued again. The TaskRetryCount cluster parameter specifies the maximum number of times that a task can be queued again.

The job requires a node that is not available.

The list of nodes that the task requires must be included in the list of the nodes that the job requested.

The task specifies more required nodes than the job's specified maximum resource usage.

The run-time value for the task is greater than the length of time that the job is scheduled to remain running.

The task failed validation.

You cannot queue the task again because the task is marked to run only one time.

The depends on list is ambiguous because multiple tasks specify the same name.

An unexpected exception occurred while validating the job.

Gets the error category to which the specified error code belongs.

Creates the message text for the error using the specified insertion strings.

Retrieves a formatted string that represents the message string for the specified error code.