VMs in Virtual Machine Manager report "Unsupported Cluster Configuration" and error 23772

Article ID: 2822797 - View products that this article applies to.
Expand all | Collapse all

Symptoms

In the Virtual Machine Manager admin console, VMs report Unsupported Cluster Configuration. The job view error is below:

Error 23772
One or more available cluster volumes associated with host %VMHostName; is not associated with a path in the default placement path list and will not be considered for placement. Refresh the cluster to ensure that all available cluster storage has an associated default placement path.

Cause

This can occur if there are duplicate Volume Serial Numbers (VSNs) on the host. Virtual Machine Manager uses VSNs to track which disk it is working with. 

Resolution

To identify if disks are using the same VSN, execute the single line below at an elevated PowerShell prompt:

Get-WmiObject Win32_volume | Format-table Name, @{Label = "SerialNumber";Expression = {"{0:X}" -f $_.SerialNumber}} –auto | out-file c:\temp\VSNs.txt
This will create an output file at c:\temp\VSNs.txt that will contain data similar to the following:

Name                                              SerialNumber
----                                              ------------
C:\                                               6A64D98D
D:\                                               529DC75F
\\?\Volume{2d4a81bf-5537-4ecb-b7fc-2008574726fb}\ 485CB3C7

If there are duplicate numbers in the SerialNumber column, you must change one of the VSNs. To do this, download VolumeID from Sysinternals. This tool allows you to change the VSN to another number, but it does require that the drive be assigned a letter. Once the VSNs have been changed you must reboot the server for Windows to recognize the new values.

If the disks are in a Failover Cluster CSV, they will not have drive letters. To correct these volumes using VolumeID, they must be taken out of the CSV long enough to be given a drive letter in Disk Management. Then you can change the VSN with VolumeID and place them back in the CSV. A reboot is required after changing VSNs.

More information

VSN’s are not commonly used or known about. To see the VSN of your C: drive, you can run the VOL command from a CMD prompt. An example of this is below:

C:\vol
Volume in drive C is OSDisk
Volume Serial Number is 6A64-D9Q7

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2822797 - Last Review: March 19, 2013 - Revision: 2.0
Applies to
  • Microsoft System Center 2012 Virtual Machine Manager
  • Microsoft System Center Virtual Machine Manager 2008
  • Microsoft System Center Virtual Machine Manager 2008 R2
  • Microsoft System Center Virtual Machine Manager 2008 R2 Service Pack 1
  • Microsoft System Center Virtual Machine Manager 2008 R2 Workgroup Edition
  • Microsoft System Center Virtual Machine Manager 2008 Workgroup Edition
Keywords: 
KB2822797

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com