Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Chap
Starting Member
30 Posts |
 Posted - 2009-10-15 : 15:20:04
|
| We are unable to get the filestream online. All settings in the Configuration Manager are correct. The Event Viewer gives the following error:Cluster File Share 'SQL Server FILESTREAM share (MSSQLSERVER)' cannot be brought online because the share could not be created.Any help is appreciatedGeorge |
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-10-15 : 15:37:35
|
| What does this return: EXEC sp_configure 'filestream access level'Can you post the complete error message?Can you confirm that the SQL Service account has access to the file share? |
 |
|
|
Chap
Starting Member
30 Posts |
Posted - 2009-10-15 : 15:43:45
|
| It returns a 2 as expected. We have several different errors in the Event viewer, the previous is the first, others are:Cluster file share resource SQL Server FILESTREAM share (MSSQLSERVER) failed to start with error 2116.Cluster resource 'SQL Server FILESTREAM share (MSSQLSERVER)' in Resource Group 'SQL Server (MSSQLSERVER)' failed.George |
|
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-10-16 : 09:44:41
|
| Look at the cluster resources in Cluster Administrator for your SQL group - it should show you which of the resources has not started. Your database engine is running, but one of the other resources might have failed to start.If you find the failed resource, try and restart it and then look in the application logs for any errors. |
|
|
|
Chap
Starting Member
30 Posts |
Posted - 2009-10-16 : 10:40:51
|
| Thanks yellowBug for all your help. The problem has been solved by first creating a document folder on the F: drive then we had to sync both clusters. We did this by going to the Sql Server Configuration manager, MSSQLSERVER service. Disabled the Filestream and made sure the windows share name was correct. After re-enabling Filestream, all is working. I think the trick was making sure Filestream had a folder and it was named the same on both clustersGeorge |
|
|
|
|
|
|
cluster filestream