Tag Info

New answers tagged

0

I found a solution. Here is example where filetable name is 'physical_files', target path is 'folder1', target file have stream_id = 'FF9CF452-B522-E411-A464-00259060BBB9' declare @path varchar(MAX); set @path = '\folder'; declare @parent hierarchyid; set @parent = GetPathLocator(CONCAT(FileTableRootPath('dbo.physical_files'), @path)); select @parent ...


0

I believe the mystery is cleared up. The documentation only says that the SQL Server account needs full access to the filestream folder, but when I checked who had access to the main DATA folder, I saw that the SYSTEM account also had access. I gave full rights to the FS folder to the SYSTEM user, and now I don't get this error anymore.


0

Turned out to be an HBSS issue. Typically, I would have had this turned off during install but the environment I'm working with is particularly secured where you can't have HBSS set to "learning mode." it turns out that filestream creates a registry key for each directory created and these exceptions have to be in place before creating the filestream ...



Top 50 recent answers are included