Previous Topic: VM Reservation Fails in a Clustered Environment

Next Topic: CA SDM Exception Error


Scheduled Jobs do not Run

Symptom:

Scheduled jobs do not run. When a scheduled job is run, the service controller and the initiation component must be active and accessible from the server that is running the job to ensure that the job runs. Symptoms of this issue include the following:

Solution:

Review the log file for the command line program that is running the job and look for the following entry: "Failed to get job id." Examples of log files are dpmpolicycli.log, dpmccmcli.log, and so on.

Note: For more information about log files, see the Reference Guide.