SQL Server Developer Center >
SQL Server Forums
>
SQL Server Express
>
KB970892 Sql server will not insall
KB970892 Sql server will not insall
- SQL update will not install KB970892 error code 0x663. Now I can not open any of my programs that need sql. I have been on hold with microsoft on and off for two hours now. ANY HELP
Answers
- I was having the same problem so I did some digging and found out that if you have any SQL Server related services disabled then it will prevent the update from completing. That being said, I had SQL Server (EXPRESS) disabled since I also have the full-blown version of SQL Server 2005 installed and it was eating up my memory/resources ... so I disabled it awhile back. To get this update to go thru without failing I basically pulled up the Services console (ie: goto Start-Run ... and type in services.msc) and changed the status from "Disabled" to "Manual" and I started the service just to be sure. Then I reran the update and it went all the way through without any problems. Afterwards I stopped the services and I'm hoping that by leaving the Status at "Manual" that I want have to stop it and disable it for future updates that could be impacted by this. If not, I'll just continue to disable it manually because it is a resource hog.Hope this helps.
- Marked As Answer byXiao-Min Tan – MSFTMSFT, ModeratorFriday, October 23, 2009 9:28 AM
All Replies
- there are no error messages on my screen, but the yellow update icon always there. "Security Update for SQL 2005 service pack 3(KB970892) " check box is selected and it is gray. you can install it again and again and again...
- Same thing here. Running XP x64. SQL Server (Developer Edition) still works, though.
- Proposed As Answer byXiao-Min Tan – MSFTMSFT, ModeratorMonday, October 19, 2009 2:38 AM
- Unproposed As Answer byXiao-Min Tan – MSFTMSFT, ModeratorMonday, October 19, 2009 2:41 AM
- Same problem here for last 2 days on Vista Business Edition, SP2.
Tried the obvious - clearing cache, tried with the service running and with it stopped, tried mix of related stuff stopped (e.g. SQL server active directory helper, Server browser etc) but all to no avail.
We do use a lot of SQL server requests here... but on separate servers anyway (and they're running Linux with MySQL since we outgrew MSSQL on Server 2008) so I suppose the answer is to just disable the service and ignore the update, as most people don't need the server running locally anyway?
- I was having the same problem so I did some digging and found out that if you have any SQL Server related services disabled then it will prevent the update from completing. That being said, I had SQL Server (EXPRESS) disabled since I also have the full-blown version of SQL Server 2005 installed and it was eating up my memory/resources ... so I disabled it awhile back. To get this update to go thru without failing I basically pulled up the Services console (ie: goto Start-Run ... and type in services.msc) and changed the status from "Disabled" to "Manual" and I started the service just to be sure. Then I reran the update and it went all the way through without any problems. Afterwards I stopped the services and I'm hoping that by leaving the Status at "Manual" that I want have to stop it and disable it for future updates that could be impacted by this. If not, I'll just continue to disable it manually because it is a resource hog.Hope this helps.
- Marked As Answer byXiao-Min Tan – MSFTMSFT, ModeratorFriday, October 23, 2009 9:28 AM
SQL update will not install KB970892 error code 0x663. Now I can not open any of my programs that need sql. I have been on hold with microsoft on and off for two hours now. ANY HELP
Just by chance I mentioned this problem in my local pub and was overheard by a silver surfer, who asked me the obvious... "Why don't you just uninstall SQL Server then?".
I didn't know if it would stop the rest of the system from working (It is Vista Business Edition, and Server 2005 was pre-installed when it came from Dell) or whether the Anti-Virus or Anti-Spyware would be affected... but was so fed up with the KB970892 glitch I thought I'd try... and it worked. Yes, everything works fine after removing SQL Server 2005, and the Microsoft update now go through without problem because it knows not to try to download the fix for server 2005 as I'm not using it.
Now this isn't the fix for everyone I'm sure, as some people *do* use MSSQL locally... But it's worth a try, and it certainly didn't break my machine!- Proposed As Answer byTheLinuxGuru Monday, October 19, 2009 7:34 AM
- Thanks. I had the same problem as I occasionally need SQL locally but generally don't start the service to save memory.
Starting the two services that I have specified as Manual: "SQL Server" and "SQL Server Agent" enabled kb921896 to install.
It was not neccessary to change the Startup method, simply starting those two key services was adequate. normally I see this quite a bit with SBS 2003, but this is what worked for me
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL\Server\MSSQL.1\Setup\Resume, if set to 1, change to 0. Once changed to 0
This has worked for SQL 2005 SP2 and SQL 2005 SP3 installs....- Proposed As Answer byPaul Leclerc Tuesday, November 10, 2009 3:44 PM
- Where normally you can find the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL\Server\MSSQL.1\Setup\Resume
As previous recommednations did not work, now I have to go with your recommendation! - The solution proposed by JiuJtsuMike worked for me.
You can find what he's talking about in the registery: Start>run> then type: regedit
Then navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server\MSSQL.1\Setup\Resume - The solution proposed by JiuJtsuMike also worked for me (registry fix). I tried the other methods (starting other SQL server services, enabling disable SQL Server services) and it did not work.
BTW: I got this update after installing Visual Studio 2008 SP1 and running Windows Update again. So, if you're puzzled why you'd get this update when you're not even "using" SQL Server, it's because VS 2008 and VS 2005 installs SQL Server 2005 Express. - This also worked for me. It is amazing how much pain people have to go through with M$ just to get the basic security flaws covered.
I was banging my head for days on this one.
Thank you for the research and the posting. - JiuJitsuMike's solution works
Reinstalling SQL Server also works but reg edit is easier. normally I see this quite a bit with SBS 2003, but this is what worked for me
Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL\Server\MSSQL.1\Setup\Resume, if set to 1, change to 0. Once changed to 0
This has worked for SQL 2005 SP2 and SQL 2005 SP3 installs....
Yes, this works. I have never, ever, trusted myself to do anything with the registry-- the warnings about doom and gloom from a mistake scare the ____ out of a total novice like myself-- who just wants the stupid machine to work, doesn't mess around with settings, etc.
Having failed to find any other trick that works, tried this one with some trepidation, and the problem is now resolved. Changed a 1 to a 0. For the life of me I have no idea how a person would ever get to the point that they look at a failed update and think.."humm, ya know I bet that value buried 5 levels down in the registry is probably set to 1 and thats causing the issue". Its amazing to me. But it worked. JiuJyutsu Mike, your kung fu is the best!Try downloading the update and running the install manually. I found for me that the problem came from trying to update x86 based versions or SQL server running on an x64 box. The auto update attempted to update using the x64 version of the update software. I did a manual update with the x86 version of the update software and it went fine.
- This registry entry does not exist on my PC, and I continue to get this ANNOYING error from MS (going on for 6+ weeks now). I don't use SQL (at least ot my knowledge) - so next step will probably be to try and REMOVE it and see if that cures the problem...
Geez, MS - don't understand why you can't fix stuff like this... - thanks, of all the options listed, for over a month, this is the only one that worked. thank you.
