KB: Reports are not populated in the System Center 2012 Operations Manager Reporting Pane

KB: Reports are not populated in the System Center 2012 Operations Manager Reporting Pane

  • Comments 4
  • Likes

imageHere’s a new Knowledge Base article we published. This one talks about an issue where reports do not populate in the OpsMgr 2012 Reporting Pane, or Report data does not update.



Reports do not populate in the System Center 2012 Operations Manager Reporting Pane, or Report data does not seem to be updating.


This can occur if the Data Warehouse Synchronization server entry is deleted.


To confirm this issue in the Operations Console, go to the Monitoring View and click on discovered inventory. Then change the Target type to Data Warehouse Synchronization server by completing the following:

1. Click Change Target Type on the right-hand task pane of the Operations Console
2. In the dialog that opens select View all targets
3. Locate and select Data Warehouse Synchronization Server in the list
4. Click OK

If this returns blank you are experiencing this issue.

To resolve the issue run the script below:

Note: You will have to edit the script and enter the Operations Manager Database server name, Data Warehouse servername and console path in the script . This is a PowerShell script which needs to copied to text and rename to .ps1 after entering the required information to run under PowerShell.


#Populate these fields with Operational Database and Data Warehouse Information
#Note: change these values appropriately
$OperationalDbSqlServerInstance = "<OpsMgrDB server instance. If its default instance, only server name is required>"
$OperationalDbDatabaseName = "OperationsManager"
$DataWarehouseSqlServerInstance = "<OpsMgrDW server instance. If its default instance, only server name is required>"
$DataWarehouseDatabaseName = "OperationsManagerDW"
$ConsoleDirectory = "<OpsMgr Console Location by default it will be C:\Program Files\System Center 2012\Operations Manager\Console"
$dataWarehouseClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouse
$seviewerClass = get-SCOMClass -name:Microsoft.SystemCenter.OpsMgrDB.AppMonitoring
$advisorClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouse.AppMonitoring
$dwInstance = $dataWarehouseClass | Get-SCOMClassInstance
$seviewerInstance = $seviewerClass | Get-SCOMClassInstance
$advisorInstance = $advisorClass | Get-SCOMClassInstance
#Update the singleton property values
$dwInstance.Item($dataWarehouseClass.Item("MainDatabaseServerName")).Value = $DataWarehouseSqlServerInstance
$dwInstance.Item($dataWarehouseClass.Item("MainDatabaseName")).Value = $DataWarehouseDatabaseName
$seviewerInstance.Item($seviewerClass.item("MainDatabaseServerName")).Value = $OperationalDbSqlServerInstance
$seviewerInstance.Item($seviewerClass.item("MainDatabaseName")).Value = $OperationalDbDatabaseName
$advisorInstance.Item($advisorClass.item("MainDatabaseServerName")).Value = $DataWarehouseSqlServerInstance
$advisorInstance.Item($advisorClass.item("MainDatabaseName")).Value = $DataWarehouseDatabaseName
$dataWarehouseSynchronizationServiceClass = get-SCOMClass -name:Microsoft.SystemCenter.DataWarehouseSynchronizationService
#$dataWarehouseSynchronizationServiceInstance = $dataWarehouseSynchronizationServiceClass | Get-SCOMClassInstance
$mg = New-Object Microsoft.EnterpriseManagement.ManagementGroup -ArgumentList localhost
$dataWarehouseSynchronizationServiceInstance = New-Object Microsoft.EnterpriseManagement.Common.CreatableEnterpriseManagementObject -ArgumentList $mg,$dataWarehouseSynchronizationServiceClass
$dataWarehouseSynchronizationServiceInstance.Item($dataWarehouseSynchronizationServiceClass.Item("Id")).Value = [guid]::NewGuid().ToString()
#Add the properties to discovery data
$discoveryData = new-object Microsoft.EnterpriseManagement.ConnectorFramework.IncrementalDiscoveryData
#$connector = Get-ScomConnector -name:"Operations Manager Internal Connector"
$momConnectorId = New-Object System.Guid("7431E155-3D9E-4724-895E-C03BA951A352")
$connector = $mg.ConnectorFramework.GetConnector($momConnectorId)
#Update Global Settings. Needs to be done with PS V1 cmdlets
Add-pssnapin microsoft.enterprisemanagement.operationsmanager.client
cd $ConsoleDirectory
Set-DefaultSetting ManagementGroup\DataWarehouse\DataWarehouseDatabaseName $DataWarehouseDatabaseName
Set-DefaultSetting ManagementGroup\DataWarehouse\DataWarehouseServerName $DataWarehouseSqlServerInstance


More Information

If the script completes successfully you should see a message like below:

PS C:\> .\AddDWInstance.ps1
Name : ManagementGroup\DataWarehouse\DataWarehouseDatabaseName
Value : OperationsManagerDW
Name : ManagementGroup\DataWarehouse\DataWarehouseServerName
Value : scsqlv


For the most current version of this article please see the following:

2771934 - Reports are not populated in the System Center 2012 Operations Manager Reporting Pane

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • any news on SQL2012 compatabilty for reporting? We're desperately waiting for SP1 otherwise..

  • Thank you for sharing

  • Thanks for this fix! Had this issue after upgrading from 2012 Cu3 to SP1, this did the trick :-)