After a SQL Server cluster failover, SharePoint users could not open any page, though all SQL resources were online. Here is what we found and how we fixed it.
SQL SERVER – FIX – Error 1402 – Could not Open Key: UNKNOWN\Components – System Error 5 (Another Solution)
Installing KB3045311 failed with Error 1402, could not open key UNKNOWN\Components, system error 5. When my earlier fix did not help, this one worked.
SQL SERVER – FIX: Unable to Create Distribution Database on a UNC Share – Configure Distribution
With SQL Server on a UNC share, the Configure Distribution wizard refuses network paths for the distribution database. Here is how to create it anyway.
SQL SERVER – Unable to Start SQL After Patching – Database SSISDB is Enabled for Database Mirroring
After patching, SQL Server would not start. The SSIS hotfix script failed because database SSISDB is enabled for Database Mirroring. Here is the fix.
SQL SERVER – Steps to Deploy Distributed Availability Group – Windows Clusters in Different Domains
After a merger, a client had two Windows clusters in untrusted domains and no wish to use certificates. Here is how I deployed a Distributed Availability Group.
SQL SERVER – Event ID 1069 – Unable to Failover Clustered Instance to Another Node. Resource is not Loaded
My lab failover clustered instance would not move to the other node: Event ID 1069, resource is not loaded. Here is what the logs showed and the fix.
SQL SERVER – Unable to Add Node – Could not find subkey System \ CurrentControlSet \ Services \ MSSQLFDLauncher. Error code 0x851B0001
Running add node on Node2 failed with “Could not find subkey MSSQLFDLauncher”, error 0x851B0001. The cause was a missing Full-Text MSI in the setup media.