When you run a report in Operations Manager 2007, data may not be displayed. You can check for the following conditions to determine the cause. This article provides different conditions when a report might return no data and recommendations for correcting the problem.

Incorrect object selected

The data that you are looking for may be associated with a different object than the one you have selected. For example, you might be looking for alerts related to disk drives on a particular computer and select the computer as the object for the report. Monitors and rules measuring such information as disk utilization and transfer time are targeted at disk classes such as Windows Server 2008 Logical Disk and Windows Server 2008 Physical Disk. Any performance data or alerts are going to be associated with these objects as opposed to the computer that the disks are installed on.

• Check the details of the report for any information about particular classes that the report was designed for.
• In the Authoring workspace, check for rules and monitors targeted at the chosen class. If there are no rules or monitors collecting the information that you're interested in, then you may need to select an object of a different class for the report.
• Try selecting the target object using Add Group instead of Add Object to include any objects contained by the current object instead of the object itself. If you locate the data that you are interested in, it should include the name and class of the object that the data is associated with.

No data available for the selected date range

While there may be data available for the selected objects, there may be no data available for the time period selected.  There are multiple reasons why this may be the case.

Data warehouse not yet updated

Data written to the data warehouse is only available to reports after it has been aggregated. Data aggregation typically occurs within a few minutes so that data appears to be available almost immediately. If your data warehouse is under excessive load, it may take longer for the data to be aggregated. If you are running a report for data from a recent time period such as the current day, it may not be available yet.

• Try setting a start date several days back and the current date as the end date. In addition to showing if older data is available, the date that the data ends will identify how far behind the aggregation is currently running.
• Check the collected database statistics for the data warehouse database to determine if it is experiencing excessive load.

Data not collected for the specified time period

While data might be available for some time periods, it may not have been collected for the time period selected. This could have been due to the target object being in maintenance mode, the agent on the target computer not functioning, or some problem with the Operations Manager 2007 environment during that time period.

• Run the Availability report for the target object to determine if it was being monitored during the time period.
• Extend the date range to determine if data was available outside of the selected range.

Expected data not being collected

Event and performance data is collected to the data warehouse through collection rules. If a rule does not exist to collect a particular event or a particular performance counter, then it will not be collected into the data warehouse.

• Check if the data is available in views in the Monitoring workspace. If the data is available in a view, then it will typically be available in a report. By right clicking on the event or performance counter, you can view the properties of the collection rule. Check the Configuration tab of the rule to determine if it has a response to publish to the data warehouse.
• In the Authoring workspace, check the rules for the class to determine if any exist to collect the desired data. If a rule does exist, view its properties and check the Configuration tab to determine if it has a response to publish to the data warehouse.