4

We had difficulty setting up a FileTable share on a SQL 2014 instance and after giving up on trying to name it after our instance name, we left the name of the share as mssqlserver, but it finally came online, online meaning if you right click in SSMS on the FileTable table you can "Explore FileTable Directory", however it seems to randomly go offline again after some time and you receive the usual canned error message:

So, after magically disabling/enabling FILESTREAM at the server level, database level via t-sql/ssms/configuration manager it some how comes back, but I have to mess with the setting at all of those spots for it to come back! and there seems to be no magical sequence of steps that makes it come back.

Has anyone out there experienced this? Will a restart of the service/server help this? If not, will a repair of sql server help?

Paul White
  • 67,511
  • 25
  • 368
  • 572
Eric Swiggum
  • 739
  • 1
  • 6
  • 26
  • So you're using FileTables? Or classic Filestream..? Can you access the filestream share using the UNC path when the GUI is throwing this error msg? – Molenpad Mar 03 '17 at 16:39
  • Yes, sorry, FileTables! No I cannot reach the UNC path when the GUI is throwing the error, however I CAN reach it when I am local to the box via SSMS or UNC. I am one restart away from calling microsoft css support team. – Eric Swiggum Mar 03 '17 at 17:35
  • I'm trying to replicate your error... Just checking that non-transaction access is enabled for filestream in your setup? Also that your filestream config is set to allow remote connections in sql server configuration manager? – Molenpad Mar 03 '17 at 19:54
  • yes and yes, and after we rebooted the entire server, the filetable broke and we had to perform the magic to get it back, so we will be getting in touch with MS – Eric Swiggum Mar 07 '17 at 17:56
  • the server restart broke the filetable share as expected... phoning MS now. – Eric Swiggum Mar 09 '17 at 17:51
  • This just happened to us. Did MS provide a fix? In order to make it work on our server, I had to renamed the share on the service properties from mssqlserver to mssqlserver1. – Rhyous Mar 31 '17 at 23:01
  • @EricSwiggum This is currently happening to me as well. Any fix? – AperioOculus Jul 28 '17 at 20:02
  • I never phone MS, and basically if i turn off FS completely in SSMS on the server properties and re-enable it, that would "fix" the issue... not sure if any of use want to eat $500 or more to find out why. I guess I could submit something to MS connect. However, i will add that it hasn't acted up in some time... – Eric Swiggum Aug 01 '17 at 18:17

1 Answers1

2

It appears that after setting it via configuration manager the issue went away.

Mr. Mclaren
  • 36
  • 4
  • 2
    I'll consider this issue ... "resolved" as it appears to no longer be happening although I never really got any real explanation as to why. – Eric Swiggum Oct 31 '18 at 15:55