Consider the following scenario:
- Assume that you have a FileTable in Microsoft SQL Server.
- You try to open a FileTable directory by using SSMS, File Explorer or Windows API.
- When an application performs directory enumeration for the FileTable directory, the request call can be intercepted by a file system filter driver present in the client machine. The FileInformationClass request parameter can be changed to use FILE_ID_EXTD_DIR_INFORMATION instead. In this case, the client may receive an ERROR_FILE_NOT_FOUND (0x2) as a response from SQL Server.
In this situation, you may receive an error message that resembles the following on Windows:
"The File location cannot be opened. Either access is not enabled or you do not have permissions for the same."
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is 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: