KB970892 Will Not Install.
When I booted my XP SP3 machine Tuesday night (10/13), the many MS updates loaded.
I then let them all install.All updates installed except for one.
I am getting the following message, for KB970892:The following updates were not installed. Security Update for SQL Server 2005 Service Pack 3 (KB970892)
I am running SQL Server Express 2005:
Microsoft SQL Server Management Studio Express 9.00.4035.00 Microsoft Data Access Components (MDAC) 2000.085.1132.00 (xpsp.080413-0852) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.3603 Operating System 5.1.2600
Answers
- I had this problem and tried a number of things including disabling automatic updates, deleting the install files re-enabling automatic updates, and running the update again. This didn't work.
Starting the SQL service also didn't work.
What ended up working for me was using the Microsoft Installer cleanup utility to remove ALL SQL installation files and then running the update again. Description of the Microsoft Installer cleanup utility: http://support.microsoft.com/kb/290301
-MM- Proposed As Answer byDaren Lahey Tuesday, October 20, 2009 3:57 PM
- Marked As Answer byFOCUSGuy Wednesday, October 21, 2009 2:08 AM
All Replies
- Hi,
The service you are trying to updat is switched off.
run - services.msc
Look for SQL Server
Properties - Startup - Set to Automatic
run the update again.
After complete set properties back to switched - off.- Proposed As Answer byarly15 Monday, October 19, 2009 4:03 PM
- My machine showed seven entries for “SQL Server” of:
SQL Active Directory Helper Service
SQL Server (MSSMLBIZ)
SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Agent (SQLEXPRESS)
SQL Server Browser
SQL Server VSS Writer
- I set the properties for every one of them to “Automatic”.
- I reran the install.
- The “Security Update for SQL Server 2005 Service Pack 3 (KB970892)” still did NOT install.
- Any thoughts?- The Start Up Type is set to 'Automatic' for all of my SQL* services.
Still the update will not install. - Did you stop them all?
So none of them running and also non of them swiched-off.
It worked fine in my xp after stopping them all and change swiched off to automatic.
Maybe an other instance of SQL still running? (MSSQL maybey?)
Hi Ovlovv40,
I checked and I did see a service called MSSQL$MICROSOFTBCM.
I stopped this service and set the Start Up Type to Automatic.I then tried the update, and it again could not install.
Regards,
FOCUSGuyEssentially there is registry issue caused by one of the following:
· An operation has removed the local groups for the initial installation of
SQL Server 2005.
· An operation has changed the security identifiers (SID) for the local
groups.
This is fixed by:
Removing the following registry subkeys that store SID settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\SQLGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\AGTGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\FTSGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\ASGroup
If one of the keys is missing, dont worry about it just delete the keys if present. And as always, BACK UP YOUR REGISTRY BEFORE MAKING ANY CHANGES.
- Proposed As Answer bytwharte Monday, October 26, 2009 4:05 AM
- scary monsters changing the directory...did this actually work?
schroe - Greetings,
I have the "KB970892 Will Not Install" update problem also. I tried everything I could find on the web, which isn't much. Also tried the resgistry thing that d240z suggested and getting nowhere fast.
I'm running XPSP3 with SQL Express 2005 SP3.
Anybody know how to fix this yet? - Hello,
I too am not able to install kb97o892 on my SBS2003. I have 3 sql services started; my sql 2005, Microsoft##SSEE which is for Sharepoint and SqlExpress 2005. - NO IT DID NOT WORK.
I've tried everything.
Leave it to Microsoft to put something out there that will not work with no solution how to make it work.
Just like Vista!
No wonder Apple is cleaning Microsoft's clock.
I'm tired of wasting hours of my time. My next machine is going to be a Mac, and I have been a loyal Microsoft user for 20 years.- Edited byIBuyDayton.com Monday, October 19, 2009 12:46 PMTired of t
- Edited byIBuyDayton.com Monday, October 19, 2009 12:47 PMTired of it!
- I currently have several machines that will not install this update. I have tried the above suggestion of switching the service off and setting it automatic on start-up but that didnt work either. Is there something wrong with this update or does anyone know of another way to get it installed? I do not see why I would have to make any registry changes to get the update to install so I have not tried that proposed solution.
- I had this problem and tried a number of things including disabling automatic updates, deleting the install files re-enabling automatic updates, and running the update again. This didn't work.
Starting the SQL service also didn't work.
What ended up working for me was using the Microsoft Installer cleanup utility to remove ALL SQL installation files and then running the update again. Description of the Microsoft Installer cleanup utility: http://support.microsoft.com/kb/290301
-MM- Proposed As Answer byDaren Lahey Tuesday, October 20, 2009 3:57 PM
- Marked As Answer byFOCUSGuy Wednesday, October 21, 2009 2:08 AM
- I want to to confirm that this solution has worked for me. meaning, it installed the update. The problem is that afterwards I kept getting the update back again from windows update.... and it's not installing it anymore... same KB number.
- Thank you MentatMike!
Indeed, when I used the Windows Install Cleanup utility, and removed all Microsoft SQL 2005 * files, the update, KB970892 did indeed install.
Like Daren, the update continued to download from Windows Update, and kept on wanting to be reinstalled, upon the successful install.
So, to fix this new issue, I went to the Windows Update web page, and selected the option to 'hide' this particular update.
Whew! - This worked for me on the first try -- thanks Ovlovv40.
I had this problem and tried a number of things including disabling automatic updates, deleting the install files re-enabling automatic updates, and running the update again. This didn't work.
Starting the SQL service also didn't work.
What ended up working for me was using the Microsoft Installer cleanup utility to remove ALL SQL installation files and then running the update again. Description of the Microsoft Installer cleanup utility: http://support.microsoft.com/kb/290301
-MMThank you for solving this issue, I tried it and it works from the first time.
Aladinz- I tried removing the install files using the Microsoft Installer Cleanup Utility and not only did it NOT work, it completely and utterly broke MS-Office!!! I popped in my MS-Office CD to try and repair and the Repair fails!!
If you have SQL Server 2005 installed as part of MS-Office 2007 Small Business edition I would STRONGLY recommend that you do NOT follow these directions!! - Salutations,
I have had this same issue for a more than a week now and it's still screwed up. The update appears to install because it is listed in "Add/Remove" in control panel.
Every time I try to reinstall the update it just persistently keeps giving me the "failed update installation" error. And then it downloads the update again.
What gives with this update? Would somebody from Microsoft please chime in and lay down something official about this issue?
Thanks - Just wanted to let everyone know that the solution MentatMike had worked for me on a couple of machines but on others it still doesnt want to install.
I have done every proposed solution except the registry change, like i stated in my previous post. Does anyone know how critical this security update is? I know that security updates are all critical but does it make me more vulnerable to an injection or exploit of some sort??
Thanks everyone for all the replies and suggestions cause this is my first time posting on this forum!
-KB-
www.tekbasesolutions.com Essentially there is registry issue caused by one of the following:
· An operation has removed the local groups for the initial installation of
SQL Server 2005.
· An operation has changed the security identifiers (SID) for the local
groups.
This is fixed by:
Removing the following registry subkeys that store SID settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\SQLGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\AGTGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\FTSGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.X\Setup\ASGroup
If one of the keys is missing, dont worry about it just delete the keys if present. And as always, BACK UP YOUR REGISTRY BEFORE MAKING ANY CHANGES.
This fixed it for me on a Winxp SP3.
I had FTSgroup (blank) and SQLgroup (SID) and removing them allowed me to install.- This worked for me on SBS 2003:
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\Resume, if set to 1, change to 0
or
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup\Resume, if set to 1, change to 0
- Proposed As Answer byChris Keeble Monday, November 02, 2009 11:32 AM
- Solution from KenMark work on my SBS 2003 as well. Thanks!
- This solution (KenMark's) worked like a charm for me just like it did for Ratslab. I tried some (did not tested the one about deleting the registry keys) of the previous recommendations but all of them failed. This one really works... Now I will have to wait to see if the update keeps coming... I clicked on Check for Updates and it wasn't there...
- I tried a couple things and finally got it to work by using KenMarks instructions first and then running the cleanup utility... then it worked.
1. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\Resume, if set to 1, change to 0
2. Run the cleanup utility.
3. Install Update
I tried both seperatley at different times and it did not work until I did them in that order. - Thanks, this worked great for me! And simple fix for a frustrating update.
This worked for me on SBS 2003:
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\Resume, if set to 1, change to 0
or
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup\Resume, if set to 1, change to 0
Did just this on Win XP, did not run clean up utility, and installed update without incident. Thanks!- Proposed As Answer bybigcabguy Saturday, November 07, 2009 4:39 PM
- In my case, the issue was that the server had been renamed, which was messing up stored SID. Deleting the SQLGroup key (actually, I renamed it to xSQLGroup) caused the installer to recreate it. It installed fine after that.
- Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup\Resume, if set to 1, change to 0
This worked for me! In my case, the issue was that the server had been renamed, which was messing up stored SID. Deleting the SQLGroup key (actually, I renamed it to xSQLGroup) caused the installer to recreate it. It installed fine after that.
Thanks Bill, I used the following as suggested by MG07 above, in addition to running the MS Installer Clean-up to get a clean install of KB970892. I had my suspciousions because I am on Vista SP 1 and I wasn't real sure that this same issue existed across platforms.
1. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\Resume, if set to 1, change to 0
2. Run the cleanup utility.
3. Installed KB970892
It is kind of disappointing to have soo many quick fixes given to you in order to fix one problem and it raises other problems in their wake. I am trying to start a business, but it seems that I spend more time trying to keep my system functional than developing my products. It would mean so much if someone at MS could take the time to set up a complete regressive testing environment that would be able to possibly stave-off some of these issues that so many users run into every day
Thomas Johnson
Tom JohnsonI was able to complete the install of this update on a Vista host after following the directions in the posts above and changing the entry
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\Resume, if set to 1, change to 0"
The registry entry works. I did not have to make any changes with the cleanup utility.
I also had problems with this update not installing in the past on XP hosts. To resolve that I had to remove MSXML6 SP2 using the cleanup utility then run the update again and when successful reinstall MSXML6 SP2
Thank you all for sharing the info


