Consider the following scenario:

  • You use AlwaysOn Availability Groups together with FileTables in an instance of Microsoft SQL Server 2014, 2012, or 2016.

  • You enable the "FILESTREAM for file I/O access" option on both the primary replica and the secondary replica, and you provide different Windows share names for the FILESTREAM on each replica.

  • The instance name of the SQL Server on each replica is different.

In this scenario when a failover occurs, the file path of the FileTables becomes incorrect.

For example, if you try to retrieve the path locator ID value for the specified file or directory in the FileTable by using the GetPathLocator function, you may receive the following error message:

Msg 33425, Level 16, State 1, Line 10
Invalid share name in the FileTable path.


This problem was first fixed in the following cumulative updates for SQL Server:

Cumulative Update 6 for SQL Server 2014 Service Pack 1

Cumulative Update 1 for SQL Server 2016

Cumulative Update 3 for SQL Server 2012 SP3

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:

Latest cumulative update for SQL Server 2014

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2012 SP3


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


Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!