This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You connect a storage device to two computers that are running Windows Server 2008.
You install the Cluster service on these computers.
On the Action menu of the Failover Cluster Management Microsoft Management Console (MMC) snap-in window, you click Configure a Service or Application to create an application.
On the Action menu of the Share and Storage Management MMC snap-in window, you click Provision Storage to create a logical unit number (LUN) device that is greater than or equal to 2 terabytes.
You assign the LUN device to all servers in this cluster.
In this scenario, the Create and configure a cluster disk resource task displays the following warning message:
The cluster disk resource could not be created
In the Failover Cluster Management MMC snap-in window, the disk resource is created and is assigned to the "Cluster_Disk_Temporary_Group_LUN_Disk" temporary resource type, and the status of the disk resource is "Offline." Additionally, you cannot bring the disk resource online manually.
This problem occurs because the Share and Storage Management MMC snap-in window does not handle the disk GUID correctly. This behavior causes heap corruption.
To resolve this issue, install this hotfix on all cluster nodes and the servers that have the Share and Storage Management MMC snap-in window installed.
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:
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.
To apply this hotfix, your computer must be running one of the following operating systems:
Windows Vista Service Pack 1 (SP1)
Windows Vista Service Pack 2 (SP2)
Windows Server 2008
Windows Server 2008 Service Pack 2 (SP2)
If the Dfsobjectmodel.dll file is being used during the installation, you must restart the computer after you apply this hotfix.
You do not have to make any change to the registry.
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 Vista file information note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Vista and of Windows Server 2008
For all supported x64-based versions of Windows Vista and of Windows Server 2008
To work around the issue, you can use the Cluster.exe utility to assign the disk GUID manually. To do this, run the following command:
cluster.exe res <resource name> /priv DiskIdGuid=<guid>
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, 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 and for Windows Vista
Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista