Consider the following scenario:

  • You use FileTables in an instance of Microsoft SQL Server 2012 , 2014, or 2016.

  • You enable the non_transacted_access for a database, and set it to FULL access.

  • You remove the first Filestream container from the database.

  • You restart the instance of SQL Server.

  • You browse to the FileTable database directory in Windows Explorer.

In this scenario, you receive an error message that resembles the following:

<FileTable directory> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Element Not Found.


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

Cumulative Update 2 for SQL Server 2016

Cumulative update 9 for SQL Server 2014 SP1

Cumulative update 2 for SQL Server 2014 SP2

Cumulative Update 5 for SQL Server 2012 Service Pack 3 (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 2016

Latest cumulative update for SQL Server 2014 SP1/SP2 

Latest cumulative update for SQL Server 2012 SP3


To work around this issue, create a new Filestream container for the database.


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


Learn about the terminology that 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!