Troubleshoot Your Orchestrator Installation
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
The latest troubleshooting information for System Center 2012 - Orchestrator is available in the release notes at Release Notes for System Center 2012 - Orchestrator. The following information provides additional instructions and caveats that you can use during installation to resolve problems you might experience.
If you experience problems during installation, installation log files are located in the folder C:\Users\%USERNAME%\AppData\Local\SCO\LOGS.
If you experience problems when you are running Orchestrator, the product log files are located in the folder C:\ProgramData\Microsoft System Center 2012\Orchestrator\.
When you deploy additional Runbook Designer applications to your environment, you might see a failed installation message. To correctly install the Runbook Designer, enable the following firewall rules as they apply to your operating system and deployment configuration.
By default, Windows Firewall with Advanced Security is enabled on all Windows Server 2008 R2 computers, and blocks all incoming traffic unless it is a response to a request by the host, or it is specifically allowed. You can explicitly allow traffic by specifying a port number, application name, service name, or other criteria by configuring Windows Firewall with Advanced Security settings.
If you are running Windows Server 2012 R2, enable the following rules to allow all Monitor Event activities to function correctly:
Windows Management Instrumentation (Async-In)
Windows Management Instrumentation (DCOM-In)
Windows Management Instrumentation (WMI-In)
When a runbook server or Runbook Designer is installed behind a firewall, specific firewall rules are required between the remote computers that are used to deploy the runbook server and Runbook Designer. An additional rule is required for the remote connection between the Runbook Designer and the runbook server to allow the Orchestrator management service to accept remote connections. If you are using the Monitor WMI task, the runbook server requires a special firewall rule on the computer that uses PolicyModule.exe.
Enable the following firewall rules on your computer:
|Operating system||Firewall rule|
|64-bit||%ProgramFiles (x86)%\Microsoft System Center 2012 R2\Orchestrator\Management Server\OrchestratorManagementService.exe|
|32-bit||%ProgramFiles%Microsoft System Center 2012 R2\Orchestrator\Management Server\OrchestratorManagementService.exe|
|Operating system||Firewall rules|
|Windows Server 2008 R2|
|Operating system||Firewall rule|
|64-bit||%ProgramFiles (x86)%\Microsoft System Center 2012 R2\Orchestrator\Runbook Server\PolicyModule.exe|
|32-bit||%ProgramFiles\Microsoft System Center 2012 R2\Orchestrator\Runbook Server\PolicyModule.exe|
For more information about adding firewall rules, see Add or Edit a Firewall Rule.
When you reboot your runbook server, the RunbookService attempts to connect to the orchestration database. If the database is not available, the RunbookService fails. The event log message is This computer was unable to communicate with the computer providing the server.. Typically, this can occur when the SQL server and the runbook server are installed on the same computer.
To solve this problem. you can manually start the RunbookService, or configure the RunbookService to make multiple attempts during startup to connect to database before failing.
If you attempt to uninstall Orchestrator while logged in with an account that is a member of OrchestratorSystemGroup but is not an administrator, uninstall removes all accounts from OrchestratorSystemGroup. If you stop the runbook service and attempt to restart the service, the services fails because the user account does not have the correct permissions to retrieve the orchestration database connection. An account that is an administrator or a member of the OrchestratorSystemGroup is required to retrieve the orchestration database connection.
To solve this problem, an administrator can add the user back to OrchestratorSystemGroup.
If you get HTTP errors when starting the Orchestration console, try the following mitigations:
HTTP error 404.3 – Not Found: Ensure that both .NET Framework 4.5 and Windows Communication Foundation (WCF) HTTP Activation are installed. You can find the instructions in Single-Computer Requirements for System Center 2012 R2 Orchestrator.
HTTP error 404.17 – Not Found: Ensure that Windows Communication Foundation (WCF) HTTP Activation is installed. You can find the instructions in Single-Computer Requirements for System Center 2012 R2 Orchestrator.