SCVMM 2008 R2: VMM Service Crash with UnauthorizedAccessException while Gathering Information on the Source Machine

  • Article

Symptoms

When click clicking “SCAN SYSTEM” in the SCVMM P2V (Physical to Virtual) conversion wizard, the following error occurs:

“The connection to the Virtual Machine Manager server <SERVERNAME> was lost.”

 The job results will show the following error:

  “Error 1700”

“The Virtual Machine Manager service on the <HOSTNAME> server stopped while this job was running. This may have been caused by a system restart.”

Further analysis will reveal that there was not a system restart, but a VMM Service crash and restart.

Cause:

This can occur if there is a failure to access WMI on the source server or the source machine fails to initialize its WMI classes properly. You can verify specifics by browsing to some of the required WMI classes (Win32_processor, Win32_operating system, etc.) using a WMI browser (WMIC, WBEMTEST, etc.)

For example, you can test basic access by using the Computer management snap-in. Browse to Service and Applicatons – then to WMI control. Then right click and select properties and attempt to browse the common namespaces.

Resolution

If WMI returns error messages, be aware that they may not indicate problems in the WMI service or in WMI providers. Failures can originate in other parts of the operating system and emerge as errors through WMI. See the URL below with common error codes

https://msdn.microsoft.com/en-us/library/aa394559.aspx

  • 0x800410xx and 0x800440xx are WMI Operational Errors
  • 0x8007xxxx are Win32 errors, not WMI errors (Often DCOM security-related)
  • 0x80040xxx are DCOM errors, not WMI errors (Often DCOM configuration-related)
  • 0x80005xxx are ADSI errors (LDAP), not WMI errors

There is also a web site that contains these codes in detail:

https://msdn.microsoft.com/en-us/library/aa394559.aspx

If the entire WMI repository is corrupt, try salvaging and/or rebuilding the repository using the following method:

1.  Open an elevated command prompt.

2.    Verify the WMI repository is not corrupt by running the following command:

 winmgmt /verifyrepository

If the repository is not corrupted, a “WMI Repository is consistent” message will be returned. If you get something else, go to step 3. If the repository is consistent, perform a repair.

3. Run the following commands to repair WMI:

 winmgmt /salvagerepository

If the repository salvage fails to work, then run the following command to see if it resolves the issue:

winmgmt /resetrepository

After the last command, there should be a “WMI Repository has been reset” message returned that verifies the command was successful.