The System Center Orchestrator Management Service is not running. This service is used by the Runbook Designer to connect to the Orchestrator database. If this service is not running it means runbook authors will not be able to connect to Orchestrator using the Runbook Designer.
The Orchestrator Management Service also supports certain maintenance functions including the Purging of the Orchestrator logs. The Log Purge job is configured in the Runbook Designer. If the Orchestrator Management Service is not running and a Log Purge job has been configured then this job will be run. This can result in unwanted data accumulating in the Orchestrator database.
A service can stop for many reasons, including:
The service was stopped by an Administrator.
The service encountered an exception that stopped the service.
The service was improperly configured, which prevented it from starting.
The service was prevented from starting because the user account assigned to the service could not be authenticated.
Once the service has been restarted consider suspending the Log Purge job in the Runbook Designer and running the job manually. An extended outage of this service can result in accumulation of log data that can cause the Log Purge job to take longer to complete and impact database performance.
The service can be restarted using the Services snap-in which can be accessed through the Computer Management console task:
