KBWe just published this one today so if you’re seeing empty Service Level Tracking Summary Reports in System Center Operations Manager 2007 then you’ll want to check this one out:



If you run a Service Level Tracking Summary Report in System Center Operations Manager 2007 and select a different TO Date then "Today" it may come up empty depending on the chosen Service Level Objective (SLO) and/or selected date.


The SLOs defined in the SCOM 2007 console are stored into a specified Management Pack (MP). Whenever we modified that MP it will create a new edition of the MP and insert a new record into the DW database to mark the timestamp when this MP was installed. When we run the Service Level Tracking Report it will check to see if there is a corresponding MP record within the specified time period. This validation is used to ensure that all SLOs were defined in the respective Management Group during the reporting period. That means that even if the MP was created a long time ago, if we make any modification on the objects contained in this MP it will change the MP installation DateTime. If the MP installation DateTime is outside of the specified time period in the Service Level Summary Report then the report will be empty.


This has to do with how the Management Packs are preserved in the DW. By default sealed MPs are stored for 400 days after their deletion and unsealed MPs up to 400 days but we also only keeping the last 3 versions of each unsealed MP. If your unsealed MP contains many objects (in this case SLOs) and you change them rather frequently, it is likely you can get into these situations. You can consider doing one or all of the following things:

1) Seal MPs where you store SLOs
2) Store SLOs separately (in separate MPs)
3) Increase the number of versions of the sealed MP DW will preserve. To do this, run the following SQL Query on the SCOM Data Warehouse Database (default: OperationsManagerDW):

UPDATE [MaintenanceSetting] SET [NonSealedManagementPackMaxVersionCount] = 8

NOTE: 8 is just an example number. DO NOT set the number too high. We advise against setting this to a larger number than 10. You should try a smaller number until it fits for your environment.

More Information

This article applies to System Center Operations Manager 2007 RTM, SP1 and R2.

Query Words

OpsMgr 2007, MOM


For the most current information please see the following Knowledge Base article:

KB2567404 - The Service Level Tracking Summary Report in System Center Operations Manager 2007 may be empty if TODAY is not selected for the TO date

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