Can't access VNN FILESTREAM share when you use the FILESTREAM and FileTable features on a Windows Server 2012-based failover cluster


Consider the following scenario:
  • You have a Microsoft SQL Server 2012 database that contains FILESTREAM data and FileTables.
  • The database is in an AlwaysOn Availability Group that is hosted on a Windows Server 2012-based failover cluster.
  • You create an availability group listener for the Availability Group.
  • You check whether you can access a VNN FILESTREAM share that has the primary replica of the availability group by using Virtual Network Name in the following format:
In this scenario, you cannot access the share because the VNN FILESTREAM share creation fails.

Note When you access the share by using the name of the node that has the primary replica of the Availability Group, all files are visible in the share.
This issue occurs because the FILESTREAM driver is not recognized as a cluster disk when located on a cluster.
This hotfix is also available at Microsoft Update Catalog

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 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.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not 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 global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
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

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_microsoft-windows-smbserver_31bf3856ad364e35_6.2.9200.20686_none_524a31888dbb804e.manifest
File versionNot applicable
File size51,285
Date (UTC)12-Apr-2013
Time (UTC)22:55
PlatformNot applicable
File nameWow64_microsoft-windows-smbserver_31bf3856ad364e35_6.2.9200.20686_none_5c9edbdac21c4249.manifest
File versionNot applicable
File size46,279
Date (UTC)12-Apr-2013
Time (UTC)22:55
PlatformNot applicable

For more information about using the FILESTREAM and FileTable features together with AlwaysOn Availability Groups, go to the following MSDN website:


Article ID: 2835620 - Last Review: 06/12/2013 23:48:00 - Revision: 1.0

Windows Server 2012 Essentials, Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Foundation

  • kbautohotfix kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced kbqfe KB2835620