August 16, 2010 at 2:23 pm
Hello,
We have a new sharepoint 2010 farm setup and we were playing with fliestream. We decided not to use it and I disabled filestream. After restarting the sql service, the database went off-line and I got the following message:
Database '<db_name>' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
I looked at the log file and saw the following:
FILESTREAM feature is disabled.
Error: 5105, Severity: 16, State: 14.
A file activation error occurred. The physical file name '<path>be incorrect. Diagnose and correct additional errors, and retry the operation.
How do I get around this issue? How do I disable filestream without making the database inaccessible?
Thanks in advance for any input.
August 16, 2010 at 4:23 pm
Enable filestream, remove the filestream file from the database files, remove the filestream filegroup, and disable filestream again. That should solve your issue.
August 16, 2010 at 9:21 pm
I tried deleting the files but I got a message the files cannot be dropped because its not empty. So, I did DBCC SHRINKFILE (RBSFilestreamFile, EMPTYFILE) and I got the following error message:
Msg 5509, Level 15, State 3, Line 1
The properties SIZE, MAXSIZE, or FILEGROWTH cannot be specified for the FILESTREAM data file 'RBSFilestreamFile'.
Do I have to manually go to the share and delete the files from there and then drop the file and filegroup?
August 17, 2010 at 12:27 pm
also, you may want to post in the correct forum section in future 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 9, 2014 at 12:18 am
Hi
I am also facing the same issue.
A file activation error occurred. The physical file name 'E: may be incorrect. Diagnose and correct additional errors, and retry the operation.
Error: 5105, Severity: 16, State: 14.
FILESTREAM feature is disabled.
Error: 5591, Severity: 16, State: 5.
Please let me know, how to resolve this issue.
suppoose if i enable the FILESTREAM feature and then restart the sql instance, the issue will resolved or not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply