Orchestrator does not reconnect when the SQL server is restarted
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.
The Runbook Server is suspended because the product license expired.
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.
This issue has been fixed in System Center 2012 Orchestrator Service Pack 1.
Article ID: 2768366 - Last Review: 02/11/2013 20:46:00 - Revision: 1.2
Microsoft System Center 2012 Orchestrator