FILESTREAM share configuration woes
-
Hi Everyone,
Have been wreaking my brain for the last couple of weeks with a new deployment of FILESTREAM to one of our SQL 2012 Servers. Not really sure where to turn with this one and I desperately need of some help figuring out what the heck the configuration is missing.
Problem: With FILESTREAM configured and the files visible via the \\SRV1\test\FileTableDB\FileTableTb_Dir\ dir locally on the server, for some reason the same UNC path is not accessible from any other server. Worked through most of the FILESTREAM configuration post out there and retried the whole configuration process from scratch a couple of times making sure to restart the instance after each configuration. Still came up empty handed though.
Question: Extensive Goggling has led me to believe that this might not be a SQL related issue and that it might be caused by permission one the service account of the instance. Am I heading down the right diagnostic path and if so where can I find a break down of which AD and OS permissions that are needed for SQL Server to present the FILESTREAM share to other servers?
Some configuration detail and changes I tried:
Server Names (Both part of the same domain):
SRV01 - Instance configured for filestream
SRV02 - External SQL server for testing access
FILESTREAM Configurations:
Engine level:
Instance level:
Database level:
Files visible in the share on SRV01:
User Permission of the test user:
sa on SRV01 and SRV02
Part of the administrator group on SRV01 and SRV02
SQL Service account identical for both servers, part of the administrator group and sa on the instances.
Server firewall:
Added rules for port 139 and 445, but decided to switch the firewall of all together at some point
Error from any other server:
When you try and open the share from another server this error is returned
Interesting replication of the error:
When accessing the UNC path locally from SRV01 the files with in the file table is accessible.
Using \\SRV01\Test\FileTableDB\FileTableTb_Dir:
But when you use the IP of SRV01 in the share path \\10.0.0.xxx\Test\FileTableDB\FileTableTb_Dir locally on SRV01 the same error that we get trying to access the UNC path for the share from SRV02 is returned:
Hopefully someone has experienced this before, will greatly appreciate any help or suggestions.
Have a good one
_________________________________________________________________
User "I need more space"
BOFH "Well, why not move to Texas?"The reason I love IT
-
I know this post is about a year old and you never had any replies, but I am also having the same issue, so I am wondering if you ever were able to work this out?
I have a client that is migrating to SQL2012.
They have SVR1 for SQL and SVR2 for a web app (which I don't know a lot about).
The app utilizes Filestream but they are getting the same "The device is not ready" error within the app.
I also get the same error when trying to access the Filestream share from the web server (same as you have noted).
I know that Filestream is configured correctly in SQL as I can upload a file directly using T-SQL.
There are inbound rules for ports 139 and 445, although I think they turned the firewall off during testing also.
The SQL Server service is using the NT Service\MSSQLSERVER service account.
I'd be very interested in hearing if you were able to determine the cause of the issue.
Thanks!
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply