White Papers
26 Update 1803 for Cloud Platform System (CPS) Standard
5.1 Troubleshooting the P&U process
Issue 1
Symptoms:
The P&U install process fails with an SMA MAX Timeout Error:
Exception calling "InvokeRunbook" with "2" argument(s): "Max Timeout reached for
SMA runbook 'Import-OmManagementPack'.
P&U fails after a two-hour timeout waiting for the Runbook to complete.
Description:
SMA Service is hanging when processing runbooks for P&U, specifically the “Import-OmManagementPack”
Runbook.
Detection:
Looking at running SMA jobs in the Windows Azure Pack management portal for administrators, under
Automation | Runbooks you see jobs stuck with the Job Status showing “Queued”.
Resolution:
There are two potential fixes for this issue, one temporary, and one more permanent.
The temporary fix resolves the problem immediately, but does not prevent it from happening again. This fix
involves rebooting the SMA VM (<P refix>APA01). This restarts any queued jobs in SMA.
The more permanent fix has performance impacts to SMA (<Prefix >APA01), but will prevent the issue from
happening again.
To apply the more permanent fix, do the following:
1. On the SMA VM (<Prefix>APA01), modify the following values in the Program Files\Microsoft
System Center 2012 R2\Service Management Automation\
Orchestrator.Settings.config file:
Old Values
New Values
<add key="MaxRunningJobs"
value="30"/>
<add key="MaxRunningJobs" value="1"/>
<add key="TotalAllowedJobs"
value="1000"/>
<add key="TotalAllowedJobs"
value="1"/>
2. After changing these two settings, reboot the SMA VM (xxxAPA01).