After patching, a client found every Maintenance Plan failing with 0x80131904, a network-related or instance-specific error. Here is the cause and the fix.
SQL SERVER – Event ID 26 – Your SQL Server Installation is Either Corrupt or has Been Tampered With (Error Getting Instance Name)
A named instance would not start, and Event ID 26 said the install was corrupt or tampered with (Error Getting Instance Name). Here is what I found.
SQL SERVER – Fix: Error: 1934, Level 16, INSERT or UPDATE Failed Because the Following SET Options have Incorrect Settings: ‘QUOTED_IDENTIFIER’.
A query ran fine in SSMS but failed in an Agent job with error 1934: SET options have incorrect settings: ‘QUOTED_IDENTIFIER’. Here is the simple fix.
Msg 17113: Error Opening master.mdf at Startup
Msg 17113 stops SQL Server at startup with an error opening master.mdf. I caused it myself by changing a startup parameter, and the file was still in place. The ERRORLOG showed the clue: the parameter name was wrong, and the fix was in Configuration Manager.
SQL SERVER – Fix: Error 946, Severity: 14 – Cannot open database ‘DB’ version 782. Upgrade the database to the latest version
Upgrading an AlwaysOn replica from SQL 2014 to 2016, databases got stuck and the ERRORLOG showed error 946, cannot open database version 782. Why and the fix.
Operating System Error 1326 in SQL Server: Cannot Open Backup Device
Operating system error 1326 means authentication failed while SQL Server tried to open its backup destination. In this 2017 case SQL Server ran on a workgroup computer and the share sat on a domain server. The tests here compare error 1326 with the path errors 3 and 67 and show how to read the service identity.
SQL SERVER – FIX: Msg 15281- SQL Server Blocked Access to Procedure ‘sys.xp_cmdshell’ of Component ‘xp_cmdshell’
Msg 15281: SQL Server blocked access to procedure ‘sys.xp_cmdshell’ because it is turned off. Here is how to turn xp_cmdshell on with sp_configure.