July 1, 2014 at 3:25 pm
I have a database which is stuck in Recovery pending state. I tried bringing it online by running alter database 'dbname' set online command and got the following error:
Msg 5591, Level 16, State 5, Line 1
FILESTREAM feature is disabled.
Msg 5105, Level 16, State 14, Line 1
A file activation error occurred. The physical file name 'i:\Vid\FSDATA' may be incorrect. Diagnose and correct additional errors, and retry the operation.
Msg 945, Level 14, State 2, Line 1
Database 'VidDB' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed
I checked for Filestream settings in configuration manager and it was disabled. I enabled it (without restarting SQL services) and tried to re-run the query, but no luck.
On top, seems like backups are no-good as I'm unable to restore it from old backups.
Anyone have faced a similar issue like this? and what steps were taking to resolve it?
Thanks
July 1, 2014 at 3:38 pm
sqlguru939 (7/1/2014)
A file activation error occurred. The physical file name 'i:\Vid\FSDATA' may be incorrect. Diagnose and correct additional errors, and retry the operation.
Does that directory exist?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2014 at 4:07 pm
After enabling FileStream (check all 3 options) in SQL Server configuration Manager, run the following command & restart SQL service (mandatory)
EXEC sp_configure filestream_access_level, 2
RECONFIGURE
GO
*This should get you past the Filestream error.
July 2, 2014 at 6:13 am
Does that directory exist?[/quote]
yes that directory exists
July 2, 2014 at 6:15 am
priyeshn (7/1/2014)
After enabling FileStream (check all 3 options) in SQL Server configuration Manager, run the following command & restart SQL service (mandatory)EXEC sp_configure filestream_access_level, 2
RECONFIGURE
GO
*This should get you past the Filestream error.
I checked all 3 options but didn't restart SQL services as that will requires opening a change ticket and getting all the approvals. I'm hoping to avoid that.
I also enabled filestream by running the above command. Still no luck.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply