Applies To
SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

Consider the following scenario:

  • You enable AlwaysOn for a database in Microsoft SQL Server 2012 Service Pack 1 (SP1).

  • You enable FILESTREAM for Transact-SQL access, I/O access, and remote access on the database.

  • You use Filetable on the database.

  • You upgrade the SQL Server to SQL Server 2014.

In this scenario, the Filetable data is inaccessible through the clustered share, and the cluster resource share does not work after you upgrade the SQL Server.

Cause

The issue occurs because related driver changes after you upgrade from SQL Server 2012 SP1 to SQL Server 2014.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Workaround

To work around this issue, change manually the path property of the resource <AvailabilityGroupName>_FSShare to point to the correct driver: From'\\?\GLOBALROOT\Device\RsFx0201\<localmachine>\{AvailabilityGroupID}' to '\\?\GLOBALROOT\Device\RsFx0300\<localmachine>\{AvailabilityGroupID}'

Status

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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.