I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
Security Update for SQL Server 2000 Service Pack 4 (KB960083) fails to install
Not many of you will see this, problem manifests if a SQL instance service is set to Disabled.
Client System EventLog:
Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2000 Service Pack 4 (KB960083).
Client WindowsUpdate log:
Handler :: START :: Handler: Command Line InstallHandler :::::::::Handler : Updates to install = 1Handler : WARNING: Command line install completed. Return code = 0x00002b33, Result = Failed, Reboot required = falseHandler : WARNING: Exit code = 0x8024200BHandler :::::::::Handler :: END :: Handler: Command Line Install.........COMAPI - WARNING: Exit code = 0x00000000; Call error code = 0x80240022REPORT EVENT: {B3B18A60-1D96-4D2B-A657-E4CDD945C7B0} <TRIMMED OUT THIS DATA} 101 80070643 CcmExec Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2000 Service Pack 4 (KB960083).
Lovely errors! Pass those 3D-Glasses over the error above, and you should see hidden text saying "You have a service that is disabled". If only!
Hop on to the target, find the patch in the ConfigMgr CACHE and manually run it. The Wizard will prompt you to select the instances to patch. Click on any Instances listed and it'll tell you what is wrong, that in this case, the service is disabled. Quit the patch when you've spotted the culprit.
To install it manually:
How much impact is this to us? Well that depends, as you know everything in life, even stuff as sublime as "Should you have Milk in your tea?" really depends on your tastes and preferences, and in this case you may have a taste for disabling SQL Instances. If you do, then those clients will play dumb when it comes to applying the patch.
The KB Article does indeed talk about Disabled Services:
Q. Will the updates be applied to disabled instances of SQL Server 2000, MSDE 2000, and SQL Server 2005? A. No. Only those instances of SQL Server 2000, MSDE 2000, and SQL Server 2005 that do not have a Startup type of disabled will be updated by the installer. For more information on disabled services, see Microsoft Knowledge Base Article 953740.
I just whipped this SQL Query up to identify ConfigMgr clients out there that meet the following:
SELECT v_GS_SERVICE.DisplayName0, v_GS_SERVICE.StartMode0, v_R_System.Name0 AS Expr1FROM v_GS_SERVICE INNER JOIN v_R_System ON v_GS_SERVICE.ResourceID = v_R_System.ResourceIDWHERE (v_GS_SERVICE.DisplayName0 LIKE 'MSSQL$%' and V_GS_SERVICE.StartMode0 = 'Disabled')