In the recent few days, I have found many clients having various script upgrade failures while applying service packs or cumulative updates. Here are few of them. Let us learn about Script Upgrade Failure.
Here is one more ERRORLOG where SQL Server was not able to come online after failover.
2017-04-06 23:50:18.04 spid5s Configuration option ‘allow updates’ changed from 1 to 1. Run the RECONFIGURE statement to install.
<{81E6B8A0-60E9-4A9F-82E3-FD5326CC3663}>RsFxFt.Dll::RsFxMgmtInitialize failed: Error 0x80070002 (-2147024894)
<{C580416B-A13E-4ECD-B61B-AAFAE39E5E35}>Failed to initialize the CFsaShareFilter interface
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070002 (-2147024894)
2017-04-06 23:50:18.05 spid5s Error: 5597, Severity: 16, State: 1.
2017-04-06 23:50:18.05 spid5s FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration Manager before enabling through sp_configure.
2017-04-06 23:50:18.05 spid5s Error: 912, Severity: 21, State: 2.
2017-04-06 23:50:18.05 spid5s Script level upgrade for database ‘master’ failed because upgrade step ‘msdb110_upgrade.sql’ encountered error 5597, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2017-04-06 23:50:18.05 spid5s Error: 3417, Severity: 21, State: 3.
2017-04-06 23:50:18.05 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2017-04-06 23:50:18.05 spid5s SQL Server shutdown has been initiated
WORKAROUND/SOLUTION
The error message 0x80070002 means ERROR_FILE_NOT_FOUND. The system cannot find the file specified.
I am not sure, but it looks like something went wrong with file-stream related files/DLLs. Since my client as not using file-stream so I suggested them to disable it and try. They Disabled filestream from configuration manager and then SQL could come online.
Have you even seen such upgrade issues related to Script Upgrade Failure?
Reference: Pinal Dave (http://blog.SQLAuthority.com)
First appeared on SQL SERVER – Script Upgrade Failure – RsFxFt.Dll::RsFxMgmtInitialize failed: Error 0x80070002