Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering when the virtual machine uses a storage device that is managed by a third-party clustered file system or a third-party replication solution

You cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering when the virtual machine uses a storage device that is managed by a third-party clustered file system or a third-party replication solution

View products that this article applies to.

Symptoms

When a virtual machine uses a storage device that is managed by a third-party clustered file system or by a third-party replication solution, you cannot configure a Hyper-V virtual machine by using Windows Server 2008 Failover Clustering. You receive the following error message:
There was an error while validating the storage configuration for virtual machine ‘name’. Disk path ‘path’ is not a path to storage in the cluster or to storage that can be added to the cluster.
This issue prevents high availability deployment of Hyper-V under the following circumstances:
  • You use a clustered file system that has a Storage Area Network (SAN).
  • You use a solution that uses replication to keep VHD data consistent between the nodes in the cluster.

↑ Back to the top

Cause

This issue occurs because the Windows Server 2008 Failover Cluster virtual machine High Availability Role Wizard cannot determine whether the storage is located on a shared clustered disk that will be available after a failover. Therefore, the High Availability Role Wizard reports the error message that is mentioned in the "Symptoms" section.

The VHD and all configuration data are required to be shared across all nodes in a cluster. If the VHD and configuration data reside on a local disk, you may have to configure a shared clustered physical disk.

There may be a valid configuration for the High Availability Role Wizard if you are using one of the following to keep virtual machine data synchronized on all nodes:
  • A third-party clustered file system
  • A third-party storage resource
  • A third-party replication solution
However, the High Availability Role Wizard rejects the valid configuration because the High Availability Role Wizard cannot verify configuration.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have the following software updates and features installed or enabled:
  • Failover clustering feature is installed
  • Cluster not using cluster-managed shared storage
  • Hyper-V update for Windows Server 2008 (KB950050) is installed
  • Windows Server 2008

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Failoverclusters.objectmodel.resources.dll6.0.6001.2229761,44029-Oct-200807:08x86
Failoverclusters.objectmodel.dll6.0.6001.22297509,44029-Oct-200806:56x64
Failoverclusters.snapin.resources.dll6.0.6001.22297974,84829-Oct-200807:08x86
Failoverclusters.snapin.dll6.0.6001.222971,679,36029-Oct-200806:56x86
Cprepsrv.exe6.0.6001.22297672,25629-Oct-200806:53x64
Failoverclusters.common.resources.dll6.0.6001.22297172,03229-Oct-200807:08x86
Clusres.dll6.0.6001.222971,154,04829-Oct-200806:54x64
Failoverclusters.wizards.dll6.0.6001.22297577,53629-Oct-200806:56x86
Failoverclusters.wizards.resources.dll6.0.6001.22297249,85629-Oct-200807:08x86
Clnetcfg.dll6.0.6001.22297659,45629-Oct-200806:54x64
Failoverclusters.common.dll6.0.6001.222973,268,60829-Oct-200806:56x86

↑ Back to the top

This hotfix updates the Failover Cluster Management "Configure a Service or Application" business logic that is related to the virtual machine role.

Before you install this hotfix, the High Availability Role Wizard return an error message that states that the configuration cannot be clustered and that the virtual machine will not be added to the cluster. This occurs if a virtual machine is stored on a disk that is not verified by the cluster.

This hotfix changes this error message to a warning message. Additionally, the details of the warning message are provided in the report that is at the end of the wizard. The warning states that the configuration is not located on a storage disk that can verified by the cluster. It does allow for the virtual machine to be added to the cluster or to be made highly available.

You must contact your vendor to make sure that your storage is configured correctly and that virtual machine data is available to all nodes.

Note This hotfix applies only to the Windows Server 2008 x64-based platform.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Amd64_failoverclusters.objectmodel.resources_31bf3856ad364e35_6.0.6001.22297_en-us_7c91e082e20c37c0.manifestNot Applicable3,55529-Oct-200807:17Not Applicable
Amd64_failoverclusters.objectmodel_31bf3856ad364e35_6.0.6001.22297_none_dff40fe8a4bc72e9.manifestNot Applicable8,00529-Oct-200807:23Not Applicable
Amd64_failoverclusters.snapin.resources_31bf3856ad364e35_6.0.6001.22297_en-us_766aed8e56d3605f.manifestNot Applicable3,54829-Oct-200807:17Not Applicable
Amd64_failoverclusters.snapin_31bf3856ad364e35_6.0.6001.22297_none_5ef5aa5c19ce34de.manifestNot Applicable4,10029-Oct-200807:22Not Applicable
Amd64_microsoft-windows-f..cluster-agentserver_31bf3856ad364e35_6.0.6001.22297_none_9462859a2f8a1ad6.manifestNot Applicable31,31229-Oct-200807:23Not Applicable
Amd64_microsoft-windows-f..ed-common.resources_31bf3856ad364e35_6.0.6001.22297_en-us_35dc3abdfaaa9f8c.manifestNot Applicable3,60429-Oct-200807:17Not Applicable
Amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.0.6001.22297_none_1d288c1a6eb90409.manifestNot Applicable11,04729-Oct-200807:21Not Applicable
Amd64_microsoft-windows-f..overcluster-wizards_31bf3856ad364e35_6.0.6001.22297_none_9ca0d374d46351ea.manifestNot Applicable3,09129-Oct-200807:28Not Applicable
Amd64_microsoft-windows-f..r-wizards.resources_31bf3856ad364e35_6.0.6001.22297_en-us_231b949134c8e69d.manifestNot Applicable3,56929-Oct-200807:17Not Applicable
Amd64_microsoft-windows-f..ster-managed-common_31bf3856ad364e35_6.0.6001.22297_none_b821835f68243b81.manifestNot Applicable6,25129-Oct-200807:27Not Applicable
Package_for_kb958065_client_1~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable9,65829-Oct-200820:02Not Applicable
Package_for_kb958065_client~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,44029-Oct-200820:02Not Applicable
Package_for_kb958065_sc_0~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable21,78829-Oct-200820:02Not Applicable
Package_for_kb958065_sc~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,43229-Oct-200820:02Not Applicable
Package_for_kb958065_server_0~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable22,29129-Oct-200820:02Not Applicable
Package_for_kb958065_server~31bf3856ad364e35~amd64~~6.0.2.0.mumNot Applicable1,44029-Oct-200820:02Not Applicable

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbexpertiseinter, kbhyperv, kbautohotfix, kbclustering, kb, kbfix

↑ Back to the top

Article Info
Article ID : 958065
Revision : 1
Created on : 1/7/2017
Published on : 11/22/2010
Exists online : False
Views : 135