Export (0) Print
Expand All

Troubleshooting Operations Manager, PRO, and Reporting Issues in VMM

Updated: August 14, 2009

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

This topic provides guidance for troubleshooting issues with Performance and Resource Optimization (PRO), reporting, and the integration of System Center Operations Manager 2007 with System Center Virtual Machine Manager (VMM) 2008 and Virtual Machine Manager 2008 R2.

Possible causes

  • The root management server for Operations Manager is in a different Active Directory domain than the VMM server. If the two servers are in different domains, manual configuration of Operations Manager is required.

  • The VMM server is in a disjointed namespace, and the server was not identified by its fully qualified domain name (FQDN).

  • The Configure Operations Manager option of the VMM Setup Wizard is run on the root management server too soon after you install the VMM server. The Setup Wizard attempts to add the VMM service account to the local Administrators group on the root management server. That operation will fail unless you allow time for the service connection point (SCP) to replicate to your Active Directory Domain Services (AD DS) domain controllers.

  • A VMM Administrator Console is already installed on the root management server when you run the Configure Operations Manager option of the VMM Setup Wizard.

Solutions

  • If your root management server is in a different domain from the VMM server, do not use the Configure Operations Manager option of the VMM Setup Wizard. Instead, follow the instructions in How to Manually Configure Operations Manager for VMM 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=162962).

    ImportantImportant
    This procedure explains how to perform one task in the integration process. To ensure a successful integration, do not perform this procedure without first performing the integration tasks that precede this one, as described in How to Integrate Operations Manager with VMM 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=162959).

  • If the VMM server is in a disjointed namespace, run the Configure Operations Manager option of the VMM Setup Wizard again, and identify the VMM server by its FQDN.

  • If you run the Configure Operations Manager option of the VMM Setup Wizard immediately after you install the VMM server, the service connection point (SCP) might not replicate to your AD DS domain controllers before the wizard runs. Run the Setup Wizard again after allowing time for AD DS replication. AD DS replication time varies, depending on your network configuration, locations of your domain controllers, and the size and complexity of your AD DS environment.

  • If a VMM Administrator Console is installed on the root management server when you run the Configure Operations Manager option of the VMM Setup Wizard, a message appears that states that the Setup Wizard will remove the console. Finish the wizard to allow it to remove the console. Then, run the wizard again.

Possible causes

  • The OpsMgr SDK Service in Operations Manager 2007 (known as the System Center Data Access service in Operations Manager 2007 R2) is unable to register Service Principle Names (SPNs) for itself in AD DS. This is the most common cause of an Access Denied error message when you attempt to specify the Operations Manager server in VMM. This error message is associated with error event 26371 (0x80006703) in the Operations Manager event log, but it is manifested in VMM as an Access Denied error. Every time the OpsMgr SDK Service starts on your Operations Manager root management server, the service must be able to register SPNs for itself in AD DS. If the SDK service runs as Local System, the account has the necessary permissions to read and write the SPNs and you do not have to update any configurations. However, if you are using an Active Directory domain account as the service account, you must either manually register the SPNs for the root management server or you must grant the SDK service account the permissions that it requires to read and write the SPNs when the service starts.

  • The service account for the VMM server was not added to the Administrator role in Operations Manager.

Solution

Use the following procedure to troubleshoot these issues.

To troubleshoot Access Denied issues when specifying the Operations Manager server in VMM

  1. To verify that SPNs are registered correctly, log on to a computer that is in an Active Directory domain by using an account that has Read SPN permission, and then run the following command, where <computername> identifies the root management server:

    SetSPN.exe –L <computername>
    
  2. If the command does not return SPNs for the root management server, use the procedures in task 1 in How to Integrate Operations Manager with VMM 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=162959) either to manually register the SPNs for the root management server or to grant the SDK service account the permissions that it requires to read and write the SPNs when the service starts. Task 1 provides steps to verify that an Operations Manager deployment meets the requirements of VMM.

  3. Ensure that the VMM service account is a member of the Administrator role in Operations Manager. To add the account to the Administrator role, follow the instructions in How to Add Members to the Administrator Role in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkID=162900).

  4. On the root management server, restart the SDK service. (In Operations Manager 2007 SP1, the service name is OpsMgr SDK Service; in Operations Manager 2007 R2, the service name is System Center Data Access service.)

  5. Restart the root management server.

  6. Specify the Operations Manager server in VMM by following the steps in How to Specify the Operations Manager Server for VMM (http://go.microsoft.com/fwlink/?LinkID=162980).

  7. If you still receive an Access Denied error message, contact Customer Support Services (CSS) for VMM. For more information about VMM support options, see System Center Virtual Machine Manager 2008 Support (http://go.microsoft.com/fwlink/?LinkID=68951).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft