SD job status 'The timeout period for this activation has elapsed.'
Article ID: 407597
Updated On:
Products
Issue/Introduction
When rolling out a Software Package on all the Systems, some of them fail with:
Job execution error status message, The timeout period for this activation has elapsed.
Environment
Client Automation - All versions
Cause
This means the error of this software distribution is not caused by the Agent, but at Scalability
Server level, during the container building still in progress before actually sending it to the Agent.
Resolution
The long time on container progressing might due to the great number of Agents. So, as to try
solve this issue follow the steps below:
When you deploy that software package via DSM Explorer, select the package to deploy, then on the Jobs tab
and in the Job tab below you'll see the fields 'Deliver at: and 'Activate at'. Try to set a delay in hours
to the activate time from the deliver (perhaps greater than the current value).
On the Job Option tab, confirm if the Store packages in the Scalability Server's Staging Library is marked on.
Additional Information
Additionally to that, check previously the SD tables for inconsistencies as in the ref. article (make sure
to have a backup of the database):
How to clean SD tables from lost rows or data inconsistency ?
Feedback
