FIX: "Element not found" error occurs when you browse to the FileTable database directory in SQL Server

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:

About cumulative updates for SQL Server
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:
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.

Article ID: 3189229 - Last Review: 10/18/2016 03:01:00 - Revision: 3.0

Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Enterprise Core, Microsoft SQL Server 2016 Standard, Microsoft SQL Server 2012 Service Pack 3, Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Enterprise Core, Microsoft SQL Server 2012 Standard, Microsoft SQL Server 2014 Service Pack 1, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Enterprise Core, Microsoft SQL Server 2014 Standard

  • kbqfe kbfix kbexpertiseadvanced kbsurveynew KB3189229