A Recovery Pending state means SQL Server could not finish opening a database, most often because it could not open a file. I reproduced two file errors on SQL Server 2025, show what each leaves in the error log, and explain how AUTO_CLOSE and antivirus scanning caused one client case.
SQL SERVER – FIX: Msg 22004 – The Log File is Not Using Unicode Format
The SQL Server Agent log would not open in SSMS and showed Msg 22004, the log file is not using Unicode format. Here is the setting that fixed it.
SQL SERVER – DPM Backup Failure – E_COORD_LOG_CHAIN_BROKEN – The Backup Failed Because of a Gap in The LSN the Log Files
SQL SERVER – DPM Backup Failure – E_COORD_LOG_CHAIN_BROKEN – The Backup Failed Because of a Gap in The LSN the Log Files
SQL SERVER – Error: Could not Load File or Assembly Microsoft. SqlServer. management. sdk. sfc Version 12.0.0.0
Could not load file or assembly errors come in many flavors. Here is how to read the assembly name and version in the message and fix the missing file.
SQL SERVER – Fix Error: Invalid object name STRING_SPLIT
A reader on SQL Server 2016 got Invalid object name STRING_SPLIT when trying the new function. Here is why the error shows up and how to fix it.
SQL SERVER – Installation Error – Unable to Open Windows Installer File – 2147286960
Installing SQL Server 2016 failed with “Unable to open Windows Installer file” and error -2147286960. Here is what caused it and how I fixed the setup.
SQL SERVER – Service Pack Failure: MissingRegistryKeyException. The Registry Key is Missing
A reader hit MissingRegistryKeyException during a service pack, but my earlier fix did not help. Here is another cause of the missing registry key and the fix.