Orchestrator Runbooks, Folders and/or Statistics are not displayed or updated in the Orchestration Console

Gilt für: Microsoft System Center 2012 Orchestrator

Symptoms


You may experience one of the following problems while using the System Center Orchestrator Orchestration Console or when accessing System Center Orchestrator data using the Web Service:

1. New Runbooks and/or Folders that have been created using the Runbook Designer are not displayed even though the user has the appropriate permissions to see them.

2. Summary pages have incorrect results for all statistics.

Cause


System Center Orchestrator uses a series of scheduled tasks executed by Microsoft SQL Server Service Broker timer conversations. One or more of these conversations is being ended without a new conversation being established.

Resolution


This problem is resolved in System Center 2012 Service Pack 1. The following workarounds are available to mitigate the problem reactively prior to application of System Center 2012 Service Pack 1:

Workaround for Symptom 1

Execute the following T-SQL query using SQL Server Management Studio to provide immediate symptom relief:

TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache
Then execute the following T-SQL query to reestablish the task execution:
EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].EnqueueRecurrentTask 'ClearAuthorizationCache'

Workaround for Symptom 2


Execute the following T-SQL query using SQL Server Management Studio to reestablish the task execution:
EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].EnqueueRecurrentTask 'Statistics'

More Information


The contents above make the assumption that SQL Server Service Broker is functioning as expected. If the workaround steps above do not mitigate the problem, further diagnostics of the SQL Server Service Broker are warranted such as whether or not the Service Broker is enabled on the Orchestrator database and whether the service and endpoints are configured correctly.

To check if Service Broker is enabled on the Orchestrator database, execute the following T-SQL query using SQL Server Management Studio:

SELECT is_broker_enabled FROM sys.databases WHERE name = '<database>'

"<database>" should be replaced with the name of your Orchestrator database. The result of this query should be "1" to reflect that the Service Broker is enabled on that database.

If the result of the query above is "0", then execute the following T-SQL query using SQL Server Management Studio to enable Service Broker:

ALTER DATABASE <database> SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE <database> SET ENABLE_BROKER
GO
ALTER DATABASE <database> SET MULTI_USER
GO

"<database>" should be replaced with the name of your Orchestrator database.

To check the configuration of the SQL Server Service Broker, the SSBDIAGNOSE utility can be used as outlined below.

If you are using Windows Authentication to your SQL Server, follow the instructions below:

Please open a Command Prompt using the "Run as administrator" functionality and execute the following command (all one line):

ssbdiagnose -LEVEL INFO -E -d <database> CONFIGURATION FROM SERVICE http://schemas.microsoft.com/SystemCenter/Orchestrator/Maintenance/MaintenanceService TO SERVICE http://schemas.microsoft.com/SystemCenter/Orchestrator/Maintenance/MaintenanceService ON CONTRACT DEFAULT

NOTE Change "<database>" to the name of your System Center Orchestrator database.

If you are using SQL Authentication to your SQL Server, follow the instructions below:

Please open a Command Prompt using the "Run as administrator" functionality and execute the following command (all one line):

ssbdiagnose -LEVEL INFO -U <user> -P <password> -d <database> CONFIGURATION FROM SERVICE http://schemas.microsoft.com/SystemCenter/Orchestrator/Maintenance/MaintenanceService TO SERVICE http://schemas.microsoft.com/SystemCenter/Orchestrator/Maintenance/MaintenanceService ON CONTRACT DEFAULT

NOTE Change "<user>" to the SQL Username, "<password>" to the password for the SQL user and "<database>" to the name of your System Center Orchestrator database.