The System Center Operations Manager Support Team Blog

This is the OpsMgr 2007 blog for the Microsoft support team. If you were looking for the SCOM 2007 or MOM 2005 blog then you are in the right place.

Troubleshooting Blank Reports in System Center Operations Manager

Troubleshooting Blank Reports in System Center Operations Manager

  • Comments 2
  • Likes

ToolsI just wanted to let you know  that we just published a great KB article on how to troubleshoot some common reasons for blank reports in System Center Operations Manager 2007 (OpsMgr 2007) and System Center 2012 Operations Manager (OpsMgr 2012).  If you ever have any trouble with OpsMgr reports then this is a great place to start:

=====

Blank reports can be a common issue with System Center Operations Manager. These are caused by many different reasons, and for the focus of this article we will discuss the following:

1. The wrong type of entity was selected as the report target.
2. The corresponding performance collection rule or the script that generates the performance data is not enabled for the report target.
3. There is a functional problem with the Health Service on the agent.
4. Management servers are unable to insert data into the OperationsManagerDW database.
5. Data is stuck in the staging tables in the OperationsManagerDW database.

There are other reasons why reports may return blank but….

=====

For the complete article please see the following:

KB2573329: Troubleshooting Blank Reports in System Center Operations Manager (http://support.microsoft.com/kb/2573329)

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager
The AVIcode Team blog: http: http://blogs.technet.com/b/avicode
The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv

clip_image001 clip_image002

Comments
  • When I run:

    Declare @DataSet uniqueidentifier

    Set @DataSet = (Select DataSetId From StandardDataset Where SchemaName = 'Perf')

    Exec StandardDataSetMaintenance @DataSet

    I get back:

    Caution: Changing any part of an object name could break scripts and stored procedures.

    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

    Is this normal?  The account I'm using has all rights on this db.

    If I run the same against "State" it works OK, but the number of rows is not decreasing, around 700.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment