Troubleshooting the Server Virtualization Management Pack

  • Article

This section provides assistance with troubleshooting your installation of the Server Virtualization Management Pack.

Problem

Report data is not available immediately after installing Reporting.

Possible Cause

Operations Manager Reporting needs at least one hour to collect data and populate the Reporting data warehouse.

Solution

After both Reporting and the Server Virtualization Management Pack are deployed on Operations Manager 2007, you must wait at least one hour to generate reports.

Problem

The Reporting Settings dialog box in the MM Administrator Console will not accept the URL entered for the Reporting server (Error 3407).

Possible Cause

The resource name portion of the URL (beyond the scheme name, "http(s)://") provided for the Reporting server is too short.

Solution

Enter a valid name for the Reporting server, including a resource name that is at least three characters long.

Problem

The SQL Server Management Pack for Operations Manager 2007 fails to discover the Operations Manager database when the designated database is running Microsoft SQL Server Express.

Possible Cause

The Server Virtualization Management Pack discovery script runs before the SQL Server Management Pack has discovered the VMM database.

Solution

Restart the Operations Manager Health service. This will cause the SQL Server Management Pack to runs its discovery scripts. After the SQL Server Management Pack discovers the database, Operations Manager will populate the relevant database entries. The amount of time that takes depends on the interval of the discovery cycle. The default setting for this interval is four hours.

Problem

When running the Host Utilization or Host Utilization Growth report against a host listed in the Virtual Machine Utilization report, the results are empty.

Possible Cause

This happens when Operations Manager is aware of the host's association with Virtual Server but not with Virtual Machine Manager. The Host Utilization report and the Host Utilization Growth report collect data from both Virtual Server and Virtual Machine Manager. If either data source is unavailable, the report cannot be generated.

Possible causes include:

  • The host is not managed by Virtual Machine Manager. In that case, Operations Manager can collect the needed data from Virtual Server but not from Virtual Machine Manager. To be able to get these reports for the host, add the host to Virtual Machine Manager. For more information, see "About Adding Hosts" (https://go.microsoft.com/fwlink/?LinkId=98840) in VMM Help.

  • The host was added to Virtual Machine Manager since the last discovery cycle, and therefore no data is available yet. Run the report again after the next discovery.

  • The VMM server that manages the host is not available, and therefore no data can be collected for the host. Use the Engine Health monitor in the Server Virtualization Management Pack to diagnose and troubleshoot issues with the VMM server.

Solution

Ensure that the host is being managed by Virtual Machine Manager and that it appears in both the list of Virtual Servers and the list of Managed Hosts managed by Virtual Machine Manager in Operations Manager.

If you have recently added the host to Virtual Machine Manager, you might have to wait as long as four hours for the discovery cycle to complete.

Problem

MonitoringHost.exe causes CPU usage on the Virtual Machine Manager server to reach 100 percent on a 30–60 second cycle.

Possible Cause

The Operations Manager Agent service is exceeding thresholds in the Agent Health monitor. This forces a restart of the service, which then causes Operation Manager to run its agent discovery scripts, placing a high load on the CPU.

Solution

Increase the value for the following thresholds in the Agent Health monitor in Operations Manager:

  • Health Service Handle Count Threshold

  • Health Service Private Bytes Threshold

Note

It is best practice to save customizations, such as new threshold settings, in a new Management Pack. For more information, see Getting Started.

To apply an override to these thresholds:

  1. In the Search box in the Operations Console, enter Health Service Handle Count Threshold, and then click Search.

  2. In the Search results window, right-click Health Service Handle Count Threshold, point to View, and then click Monitors.

  3. In the Monitors window, drill down to the Health Service Handle Count Threshold as follows: Health Service > Entity Health > Performance > Health Service Performance> Health Service Handle Count Threshold.

  4. Right-click Health Service Handle Count Threshold, point to Overrides, point to Override the Monitor, and then click For a group.

  5. In the Select Object dialog box, select VMM 2007 Server Group, and then click OK.

  6. In the Override Properties dialog box, select the Agent Performance Monitor Type - Threshold check box.

  7. In the Override Setting column, enter 10000, and then click OK.

  8. In the Monitors window, right-click Health Service Private Bytes Threshold, point to Overrides, point to Override the Monitor, and then click For a group.

  9. In the Select Object dialog box, select VMM 2007 Server Group, and then click OK.

  10. In the Override Properties dialog box, select the Agent Performance Monitor Type - Threshold check box.

  11. In the Override Setting column, enter 1610612736, and then click OK.