Troubleshooting jobs issues

The following table identifies issues related to BMC Server Automation jobs that are one of the following:

  • Known product behavior, with steps to resolve the issue
  • Product behavior that is working as designed
  • Common problem, with steps to resolve the issue

Job type


Workflow Job

Canceling a Workflow Job that executes a child job while in progress does not cancel its child job. The child job runs independently of the Workflow Job with no indication of its association with the Workflow Job.

Deploy Job

Deploy Jobs failed at the commit stage with the Unable to run the Shavlik packager for generating deployment batch files error when the Microsoft XML Core Services (MSXML) version is earlier than 6.0 SP2 on the target.

This failure is due to an earlier version of MSXML installed on the target computer than is required by BMC BladeLogic Server Automation. Ensure that the targets for Windows Deploy Jobs have MSXML 6.0 SP2 or later.

Network Shell Script Job

After running a Network Shell Script Job on Windows with an NSH script that contains BLCLI commands, the job run log contains a message that points you to the location of further logs. The path in this message is incorrect, due to redirection by the WOW64 emulator (a Microsoft feature). The incorrect path that appears in the message is C:\Windows\system32\config\systemprofile\Application Data/BladeLogic.

To find the correct location of the log files, browse the relevant directory (including its subdirectories, as the exact full path depends on your Windows environment):

  • (32-bit systems) C:\Windows\System32\config\systemprofile\AppData
  • (64-bit systems) C:\Windows\SysWOW64\config\systemprofile\AppData
Snapshot Job (Windows hotfixes)

You might experience performance degradation with windows hotfixes, when multiple job servers are running a single snapshot job on several hundred targets at the same time.

Workaround: You can try leaving the Check for updates option in the Global Configuration parameter list unchecked, and manually check for updates by clicking Download.

All types

If the operating system of an application server is not configured to use the same time zone as the database server, abnormal job execution behavior can result.  Typically, jobs are seen to kick off, but then they either disappear from the Tasks in Progress view or stay in waiting to execute state until the job queue timeout is reached (a default of 1 hour) and then fail.

Workaround: Ensure that the application server and database are running in the same time zone.

Was this page helpful? Yes No Submitting... Thank you