- You create a Windows Server 2012-based failover cluster and are using third-party dynamic disk resources.
- You configure a File Server service resource in the Failover Cluster Management snap-in.
- You try to add a cluster file share in the File Server service resource.
- You cannot create the cluster file share by using the Add File Share shortcut menu.
Note If the Add File Share shortcut menu does not start, install the hotfix that is described in Microsoft Knowledge Base (KB) article 2795993 to resolve this issue.
- When you try to create the cluster file share by using File Explorer, a Server Message Block (SMB) share is created instead of a cluster file share on the volume. For example, assume that you try to create a cluster file share that is named " ContosoShare" by using File Explorer on a drive named "ThirdPartyDisk" by using the following configuration:
Cluster Name: ContosoCluster
Cluster File server resource: \\ContosoFileShare
Thirdparty storage resource that \\ContosoFileShare depends on: ThirdPartyDisk
Server/Node Name: ContosoClusterNode1
Share Name: ContosoShare
In this situation, the file share is accessed through the "\\ContosoClusterNode1\ContosoShare" path instead of the "\\ContosoFileShare\ContosoShare" path.
- You cannot create the cluster file share by using the NetShare API or a Windows PowerShell command. Additionally, you receive an error message that resembles the following:System error 87 – The parameter is incorrect
Hotfix informationExamples of products that leverage third-party storage class resources which you should apply this hotfix if you are using these products include (but is not limited to):
- Symantec Storage Foundation for Windows
- Vision Solutions Double-Take Availability
- SIOS DataKeeper Cluster Edition
To resolve these issues, install the hotfix that is described in this article. Additionally, install the hotfixes that are described in KB 2795993 and KB 2795997 to resolve all the related issues. For more information about KB 2795993 and KB 2795997, click the following article numbers to view the articles in the Microsoft Knowledge Base:
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 this specific problem.
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, submit a request to 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 website: 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.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Additional file information
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
|File version||Not applicable|
|File version||Not applicable|
Id. de artículo: 2796000 - Última revisión: 29 mar. 2013 - Revisión: 1