When did you last time patch your SQL Server? I often discuss this question with my clients, I get many different kinds of answers.
Setup Error 1603: Patch Fails With Not Enough Disk Space on the Volume
Setup error 1603 appeared for three features in a SQL Server patch, all pointing to one component log. That log said Disk full: there is not enough disk space on the volume D. Freeing space on the drive was the corrective action.
WMI Invalid Class: Patch Rule Fails on Cluster Service Check
A WMI invalid class error can sit behind a patch rule failure that looks like a cluster problem. The rule was Not clustered or the cluster service is up and online. Recompiling the WMI MOF files with mofcomp fixed it for my client.
SQL SERVER – Patch Failure – Unable to Retrieve the Cluster Service
Patching SQL Server 2008 R2 on a Windows Server 2012 cluster failed: unable to retrieve the Cluster Service. Here is what Detail.txt showed and the fix.
How Old Version of SQL Server Running on Server? – Interview Question of the Week #183
Is your server on an old version of SQL Server? Run SELECT @@VERSION to see the build and the date the patch was created, a check I often run during a Health Check.
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 – Patch Rule Failure: Not Clustered or the Cluster Service is Up and Online
A SQL Server 2016 service pack failed the rule “Not clustered or the cluster service is up and online”. Here is what Detail.txt showed and how we fixed it.