A client was having some backup issues which related to backing up some of the SQL databases, this turned out to be a permissions error which has supposedly been fixed in the latest patch, so off I go to download it from Microsoft and installed it.  However this resulted in an error on one of the databases SBSMONITORING. Fine I thought, this is just because I knew that SQL service wasn’t running as it tends to put the disk usage in meltdown.

So I started the service and re-tried the update but received this error:

“A failure was detected for a previous installation, patch, or repair for instance ‘SBSMONITORING’ during configuration for fearures
[SQL_Replication_Core_Inst,SQL_Engine_Core_Inst,MPT_AGENT_CORE_CNI,SQL_FullText_Adv,]. In order to apply this patch package (KB2703280), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
Error code 0x84B20001”

YAY, that sounds like a fun one!
As it turns out after the first failure, setup changes a registry key so these get detected if setup is ran again, what we need to do is find them and change the value from 4 to 1:

First, open Regedit (here’s how) and find the Registry key, I found it at

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SBSMONITORING\ConfigurationState


You’ll see on the right side that all the Values are set to 4, double click each one and change the Value to 1

Now you can re-run the SQL Update. (You may need a reboot).

Hope this gets you out of a sticky Quibble.