Hello All,

You may be already experimented this issue with System Center Orchestrator 2012 RC, the statistics available in the web console are never updated and always stay at zero. The two print screens below represent the problem that I had in my lab environment :

This problem is due to a SQL Store procedure that doesn’t start and doesn’t update the statistics in the web console.

To solve that, the very first step is to ensure that the SQL Broker in enable on your SQL Server. Go to you SQL Server and run the following Query :

select is_broker_enabled from sys.databases where name= 'Orchestrator’

If it is not (you get a return value of 0) then you need to enable it by doing the following:

alter database Orchestrator set enable_broker WITH ROLLBACK IMMEDIATE

Now, we’ll check the last execution time of the procedure that is taking care of the statistic update. Execute the follow query :

SELECT
      [m].[Name],
      [m].[IsEnabled],
      [m].[IntervalInSeconds],
      [m].[LastExecutionTime]
FROM [Orchestrator].[Microsoft.SystemCenter.Orchestrator.Maintenance].[MaintenanceTasks] [m]

This will return the following table :

We could see that the LastExcutionTime of the Statistics store procedure is MARCH 15, or this normally procedure has to run every 10 minutes (600 seconds). It’s clear that something is going wrong there.

To start manually this procedure, we have to run the follow query :

EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].[EnqueueRecurrentTask] @taskName = 'Statistics'

After a few seconds, we must find some data in the following table :

SELECT *
FROM [Orchestrator].[Microsoft.SystemCenter.Orchestrator.Statistics.Internal].[Statistics] 

Running manually the procedure must solve the issue in the majority of the case, but if you still have any statistic  data after running all the SQL queries above, it’s certainly due to your SQL Server that is not working properly.

In fact, it was my case, still no updated statistics. if like me, you are running  your lab SQL server in  a VM on your laptop, VM that you never shutdown /reboot, but always use the PAUSE feature. This could cause some problem with the SQL Store procedures.

How to solve that ? Simply reboot your SQL Server. After the reboot, my statistic updated automatically.

I hope this help you

Thanks to Travis Wright and Chris Sanders for their help on this topic.

Christopher KEYAERT

database · FROM · MaintenanceTasks · Orchestrator · Store

• Thoughts on OpsMgr – SCOM R2 Agent Installation Error: HRESULT: 0x80070BC9 http://bit.ly/djHPcy #
• Thoughts on OpsMgr – EventID 10: Active Directory Helper Objects Installation unsuccessful. MSI was not found http://bit.ly/dboRS1 #
• I love MobileRSS on my iPhone, Check it out – http://bit.ly/9xkO5W #
• SCUG.be – SCDPM 2010 Management Pack has been released http://bit.ly/95KLMb #
• Nexus SC: The System Center Team Blog – Looking for VHDs? http://bit.ly/9W37qP #
• Jonathan Almquist on Operations Manager – Rebuild a management group (disaster recovery) http://bit.ly/dA8Cua #
• Ex2010 MP issue: new-testcasconnectivityuser.ps1 script generates errors like ‘Mailbox could not be http://bit.ly/anzHP5 #
• Nexus SC: The System Center Team Blog – TechEd EMEA – Opalis Sessions http://bit.ly/9NlDWE #
• Thoughts on OpsMgr – Exchange 2010 SP1: a known issue, a canary and flip flopping… http://bit.ly/b4QXef #
• Thoughts on OpsMgr – CU#3 for SCOM R2: PRO Tip Issue / 23619 SDK Service Related http://bit.ly/bYUnJg #
• Kevin Holman's OpsMgr Blog – After moving your OperationsManager Database–you might find event 18054 errors http://bit.ly/9L5cOs #
• Nexus SC: The System Center Team Blog – Windows Azure Monitoring Management Pack Release Candidate (RC) http://bit.ly/bkikku #
• Operations Manager Team Blog – Trouble with setup due to SQL not being detected? http://bit.ly/95TDCs #

database · disaster · nexus · Thoughts · twitter