Win32 application on a WSFC cluster cannot access a FILESTREAM share by using the VVN of a listener in SQL Server 2012

Applies to: SQL Server 2012 EnterpriseSQL Server 2012 StandardSQL Server 2012 Developer

Symptoms


Assume that a Microsoft SQL Server 2012 database is a member of an AlwaysOn availability group, and a listener name is configured for the availability group. You check whether a Win32 application on the Windows Server 2012 Windows Server Failover Clustering (WSFC) cluster can access a node that hosts a primary replica. To do this, you use the Virtual Network Name (VNN) of the listener. In this situation, the Win32 application cannot access a FILESTREAM share on the instance of SQL Server 2012.

Note The Win32 application tries to access the node by using the following path:
\\<VNN>\<filestream_share_name>

Cause


This issue occurs because local disks host the FILESTREAM data. However, in a Windows Server 2012 clustered environment, you can only add disks as cluster file shares on the cluster.

Status


Microsoft is currently working on a resolution for this issue. This Microsoft Knowledge Base (KB) article will be updated when the Windows fix becomes available. 

More Information


Win32 applications can access files that are associated with a FileTable in a SQL Server 2012 database by using a FILESTREAM share on an instance of SQL Server. Therefore, the Win32 applications can access the FILESTREAM share by using a Universal Naming Convention (UNC) name. 

Note The applications access the FILESTREAM share by using the following path:
\\<computer_name>\<filestream_share_name>