First published on TECHNET on Nov 12, 2012
Here’s a new Knowledge Base article we published. This one talks about an issue with System Center 2012 Orchestrator that happens when the SQL Server instance it’s using 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.
A fix is scheduled to be available in an upcoming update for System Center. Please contact Microsoft Technical Support for more details.
- Orchestrator does not reconnect when the SQL server is restarted (
| Knowledge Engineer | Management and Security Division
Get the latest System Center news on
App-V Team blog:
ConfigMgr Support Team blog:
DPM Team blog:
MED-V Team blog:
Orchestrator Support Team blog:
Operations Manager Team blog:
SCVMM Team blog:
Server App-V Team blog:
Service Manager Team blog:
System Center Essentials Team blog:
WSUS Support Team blog:
The Forefront Server Protection blog:
The Forefront Endpoint Security blog :
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog: