Orchestrator does not reconnect when the SQL server is restarted

Article ID: 2768366 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Runbooks stop executing and the Orchestrator Runbook Service and Management Server do not function as expected when the SQL Server instance that hosts the Orchestrator database is restarted. Errors are expected to occur during the downtime of the SQL Server, however proper connectivity and behavior does not restore once the SQL Server instance has restarted.

When the problem is occurring, the following events are logged to Orchestrator's Event window:

The Orchestrator Runbook Service on <server name> is no longer running. Verify the status of the Runbook Server and try to restart Orchestrator Runbook Service. If the problem persists, contact Technical Support.

and

The Runbook Server is suspended because the product license expired.

Cause

The Orchestrator services must be restarted in order for normal behavior to be restored. Microsoft has determined this is an issue in System Center 2012 Orchestrator.

Resolution

This issue has been fixed in System Center 2012 Orchestrator Service Pack 1.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2768366 - Last Review: February 11, 2013 - Revision: 1.2
Applies to
  • Microsoft System Center 2012 Orchestrator
Keywords: 
KB2768366

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com