KB970892 Will Not Install.

Question

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

Answer 1

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.

Answer 2

- 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?

 

Answer 3

The Start Up Type is set to 'Automatic' for all of my SQL* services. 

Still the update will not install. 

Answer 4

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?)

Answer 5

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,
FOCUSGuy

 

 

Answer 6

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.

Answer 7

scary monsters changing the directory...did this actually work?

schroe

Answer 8

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?

Answer 9

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.

Answer 10

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.

Answer 11

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.

Answer 12

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

Answer 13

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.

Answer 14

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!

Answer 15

This worked for me on the first try -- thanks Ovlovv40.

Answer 16

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

Thank you for solving this issue, I tried it and it works from the first time.  

---

Aladinz

Answer 17

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!!

Answer 18

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

Answer 19

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

Answer 20

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.

Answer 21

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

Answer 22

Solution from KenMark work on my SBS 2003 as well. Thanks!

Answer 23

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...

Answer 24

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.

Answer 25

Thanks, this worked great for me! And simple fix for a frustrating update.

Answer 26

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!

Answer 27

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.

Answer 28

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\Setup\Resume, if set to 1, change to 0

This worked for me!

Answer 29

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 Johnson

Answer 30

I 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

Answer 31

No problem Coles, glad I could contribute in some small way. If you are satisfied with this answer, plz take the time to mark this response with 'Proposed as answer' so this can help others in the future.

Tom Johnson

 

---

Tom Johnson

Answer 32

I personally found "jaspain's" solution at the Symantec forums to work and so far, no one there is complaining about it.  He was the original poster AND the solution finder, though others contributed to his solution:

http://www.symantec.com/connect/forums/security-update-sql-server-2005-service-pack-3-kb970892-fails-install

Here's the solution in case that link ever goes dead (quoting jaspain...extra emphasis on the last step, restarting the services)
NOTE:  This applied to users with BackUp Exec, but it would seem other installs of SQL Express may be incomplete so this could apply.

jaspain said:

In this case Microsoft made the following recommendation, which did successfully resolve the issue. To summarize the problem, the security update KB970892 failed to install because the original installation of SQL Express 2005 SP3 did not run to a final completion, even though there was no indication of any problem during the original installation process.

The fix is as follows:

• Open the Programs and Features (Add/Remove Programs) control panel.
• Select Microsoft SQL Server 2005, and click Change.
• Select the database engine component.
• Allow the system configuration check to complete.
• Then choose Complete the suspended installation.
• You may get the error message "The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package "SqlRun_SQL.msi" in the box below." This means that the installer needs access to the original installation files.
  • In this case download SQL Express 2005 SP3 from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6.
  • Execute SQLEXPR.EXE /x and extract the installation files to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Baseline Cache\Express\SP3. This is the location recommended by the article http://support.microsoft.com/kb/955250/, but the location may not really matter.
  • Provide the Setup subdirectory of this path in response to the error dialog above.
• Installation will continue, but you may encounter an additional error "[(Microsoft] [SQL Native Client [SQL Server] Password Validation failed. The password does not meet the Windows policy requirements because it is too short.. To continue, correct the problem, and then run SQL Server Setup again."
  • To correct this problem, open the Registry Editor.
  • Locate the key HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters. Note that it may be MSSQL.2 or some other instance number instead of 1. For x86 operating systems, omit Wow6432Node from the registry path.
  • Create a string (REG_SZ) value named SQLArg3 and set the data to "-T4606" (no quotes).
  • In response to the error message, cancel the installation and allow it to roll back. Then try the installation again.
• Once the suspended installation of SQL Express 2005 SP3 runs to a successful completion, the KB970892 security patch should install successfully.
• You will need to start up the Backup Exec services after the patch installation.

Answer 33

Hi FOCUSGuy

I had the same problem for some time. Today I was able to solve it in a very simple way.

I had SQL Server Express (SQLEXPRESS service) stopped and set to "Disabled". After I changed this to "Automatic" (even without starting the service, just altering the properties) the update installed successfully. After this I changed SQLEXPRESS back to "Disabled". No further problem so far - windows update does not complain about missing KB970892.


Rgds
scherand

Answer 34

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

Just tried this on our Windows Server 2003 SP2 Standard Edition server and it worked perfectly.  I'm glad I read through this entire forum before attempting the first possible solution.  No cleaning required, just a simple registry edit from 1 to 0 solved all my headaches.

Answer 35

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

Just tried this on our Windows Server 2003 SP2 Standard Edition server and it worked perfectly.  I'm glad I read through this entire forum before attempting the first possible solution.  No cleaning required, just a simple registry edit from 1 to 0 solved all my headaches.

Worked for me on WinXP SP3 as well. Just asking me, what this does. Is that a way to pretend that the installation of SQL Express 2005 SP3 did run to a final completion ?

Answer 36

OMG. I have been looking at this for weeks and it turns out that such a simple registry change solves the problem. Shame MS could not have told us this months ago.
Now a happy chappy. Windows XP SP3.

Answer 37

In my case, a two-node clustered environment on Win2k3 servers where WSUS is handling patch management, the patch seemed to install without issue on the ACTIVE node but failed on the Passive node.  As I have numerous clustered servers at various locations, the failure was on the passive node in every case.

From what I have gathered, the SQL patch KB970892 is failing to recognize a Clustered SQL instance ... in my case, for Backup Exec.  Proof is in the patch’s logs which can be found at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary*.txt where (within the first 12 lines) it reads “Cluster Installation: No ”.  Specifically, the patch attempts to stop the Service “SQL Server (BKUPEXEC)” which is “MSSQL$BKUPEXEC”.   
  
The following (manual) procedure provided the remedy:
 
1.       Using Cluster Administrator, made Node 2 the owner of the cluster.
2.       Using Cluster Admin, located “MSSQL$BKUPEXEC”.
3.       Right-click “MSSQL$BKUPEXEC” and chose “Take Offline”.

• Be sure not to take offline the Disk resource where the SQL DB is located, if that applies to your situation.

4.       Alter registry value to undo a RESUME flag, considering the patch failed previously:

• HKLM > Software > Microsoft > Microsoft SQL Server > MSSQL.1 > Setup >> Resume to have DWORD value of 0.

5.       Retrieve the KB970892 patch manually and run it:

• http://www.microsoft.com/downloads/details.aspx?familyid=0d878f4b-71e8-4170-9a14-1bce684811ce&displaylang=en
• File is named: SQLServer2005-KB970892-x86-ENU.exe

6.       After successful patch installation, right-click “MSSQL$BKUPEXEC” and choose “Bring Online”.

Pull from this example what you need for your specific scenario.

Answer 38

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

Great solution!.. solved my 5 x failed updates of trying and trying!

Answer 39

I am running Windows 7 64-bit Ultimate, and do not use SQL at all.  After I installed MS Visual Studio 2008 (after a fresh install of Windows 7 as I was migrating to Win7 from Vista) - I ran into this KB970892 error, and am really stuck now.  No matter what I do, I cannot get past the error.  Many of the regedit hints (layout) above are not even present on my machine, so I am not sure what to try next...

The error code I get is an FF which simply says "Windows Update encountered an unknown error".  Not much help MS...

I tried downloading the actual SP3 .exe upgrade from MS and ran it successfully.  However, Windows Update still comes up with this patch after that manual install, and this darn patch still won't install. 

Microsoft - what now?

Answer 40

So why can't someone remove all that trash above that doesn't do squat and just post these nice easy and correct might I add solutions on pages like this.  Woot woot.  thank you!!!  love registry tweaks.

Answer 41

raf

Thanks for sharing.

Answer 42

Hi All,

After going through and trying EVERY single posting here, with nothing but fail after fail, I uninstalled SQL server through control panel - uninstall programs. I then went to the Microsoft site and downloaded SQL server AGAIN. The update finally worked.

However, my computer (Windows 7) is still slow to start and lacks colour in the tray icons still.

Dont know if this is any help, but I would try this before changing your registry and all the other solutions given here. Its a lot faster and solves the update issues, ATLEAST.

Anyone know how to get back to quick booting and get those colours back?