Today I got a batch of updates via Windows Update. Most updates installed fine, but the “Security Update for SQL Server 2005 Service Pack 2 (KB948109)” failed with error code of 0×773F.
This computer runs Windows Vista and SQL Server 2005 Developer Edition.
There is also a named instance (MSSMLBIZ) for Outlook with Business Contact Manager (or whatever). I had disabled this instance for performance reasons as I never use the add-on. However, I had to enable and start the service through the SQL Server Configuration Manager to get the update to install.
Then I downloaded the stand-alone security update from the Microsoft Downloads. You can find it from here: Security Update for SQL Server 2005 Service Pack 2 (KB948109). This isn’t probably necessary, as long as all the instances are running, but if you still get errors, you can check the separate log file with more verbose information.
In short, all you need to do is:
- Make sure all the SQL Server 2005 instances are running able to start
- …or uninstall unnecessary instances, including hidden ones
- Download and run the manual update
This fixed it for me.
Update #1:
Make sure that you don’t have NTFS folder compression on for the folders where the database files (*.mdf, *.ldf) are located. This may prevent the instances from starting.
Update #2:
I just installed the patch through Windows Update on my home computer (Vista Ultimate, SQL Server Developer Edition) and it went fine (with services already stopped).
I’m now certain that my first problem was caused by the disabled service and starting the services has nothing to do with it (as commenters has pointed out).
One solution that I found was disabling the firewall (the error code was also different, though).
There are probably many causes for this issue, so if you succeed to fix it, please comment here what you did, thanks 
Update #3:
Updated SQL Server 2005 Standard Edition and Windows Server 2008 that hosts it. Through the Microsoft Update with no problems. Still recommend to proceed with caution on production servers before these symptoms are explained/fixed.
Update #4:
Found some good related discussions and solutions:
- http://www.technologyquestions.com/technology/windows-vista/241211-problems-installing-kb948109.html
- http://groups.google.com/group/microsoft.public.windowsupdate/msg/8c7a94f74f4dc12b
Especially this excerpt from the first link explains the 733F:
“Error: 733F– Services Failed to Start “From MS Support”
“Description: This error occurs when the installation program can’t start the SQL Server services. This can happen for several reasons including: expired account password, invalid user account, user account does not have permission to start the service, or there is something else wrong with the service.”
July 9, 2008 at 11:29 |
obviously you have to stop the process, otherwise the hotfix will not install, and complain the service is locking some files. but this doesn’t solve the problem, at least for me.
July 9, 2008 at 12:16 |
@Tsahi:
You are right that the started processes could cause locking issues, though they don’t prevent the patch from installing. It’ll just require rebooting.
Probably the error in my case was caused by the disabled instance (MSSMLBIZ) and enabling/starting it helped. Maybe just enabling would have been enough.
I hope you’ll find a way to install the patch!
July 9, 2008 at 17:53 |
Attempting to install the patch while SQL Server 2005 instance is running still resulted in a failed patch for me.
July 9, 2008 at 19:27 |
The manual update fails for me too — XP SP2, Firewall off, VirusScan disabled, one instance of SQL Express. However, my SQL Express installation is not on the C drive. One of the install attempts broke SQL Server, it wouldn’t start up (reporting error 17113). Ran System Restore using yesterday’s automatic restore point to get SQL Express up and running again.
To get rid of the Automatic Updates message, change to “Custom” install. Uncheck the box for KB948109, click Next, then check the box “Do not notify me of these updates again.” Continue and install other pending updates that won’t cause install errors. Come on Microsoft, I thought you guys were better than this…..
July 9, 2008 at 19:42 |
@Dan: Thanks for the report.
Just before I left from work my co-worker told me that his SQL Server (Developer Edition) was broken. I went to look and I think the symptoms you describe matches his. Event log claimed broken/corrupt Master -database file. He had also installed some updates.
Didn’t have the time to troubleshoot any longer, but something is clearly wrong with these updates.
For the record, after about 12 hours, there has been almost 500 hits to this post alone which tells that many people are experiencing the same problem. Waiting for Microsoft’s official statement about the issue…
July 10, 2008 at 04:03 |
Mine is due to unable to start the sqlexpress service. I change “log on as” from networkservice to local system, then manual update successfully. And then switch back to networkservice.
July 10, 2008 at 08:52 |
On my computer it was a completely different reason why it failed:
The Hotfix told me to take a look in a log-file.
This was not existing at all, because the path was not existing.
So I created that path and retried the Hotfix.
Then it runs well.
Greetings,
Axel
July 10, 2008 at 12:25 |
Changing the SQLExpress service to log on with a domain user account rather than NetworkService account worked for me. Once the user account had been changed I then installed the KB948109 update and it worked fine.
July 10, 2008 at 12:29 |
Thank you for your tips
I’m sure that at least some people will find a solution from your comments!
July 10, 2008 at 15:19 |
[...] 2005 Security Update (KB948109) failed to install. I did a search on Google and came up with a blog post that shows how to fix the [...]
July 10, 2008 at 22:35 |
Thanks jemm for helping me track down this problem on my computer. In my case, the error was caused by having my entire Program Files folder compressed. I decompressed the Microsoft SQL Server folder and its subfolders and then manually installed the update (may not have been necessary, but did give a LOT more information than the Windows Update). It installed successfully! Thanks again.
–Darren.
July 10, 2008 at 22:57 |
The following worked for me:
Delete the following values in the registry path [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup]
The registry values are:
AGTGroup
SQLGroup
FTSGroup
ASGroup
July 12, 2008 at 00:29 |
Hi,
I have Vista. I did everything but failed to do it. I downloaded the update and installed it and it says it fails to start the SQLExpress service but it is started alright (even though after I manually stoped it before installation). I gave up on the update but how do I get rid of the windows update message tells me to update everytime?
Milad
July 13, 2008 at 11:02 |
First do you need this SQL server 2005? I have a new Vista Sony laptop and I uninstall the damned \sql server. I will never use it
Even uninstalled, Vista WU will want to install the update so, when it fail, click the Show detail. You will see the update listed. Right click on it and select to ignore this update (forgot the right word listed). The update will be grayout. That it. Close the window
Alain
July 14, 2008 at 09:10 |
I think the log file at view the log at %programfiles%\Microsoft SQL
Server\90\Setup Bootstrap\Log\Hotfix\summary.txt is the best source of help. It gives the exact error. In my case, I have SQL Standard and SQL Express both installed on my laptop. I had disabled SQL Express service, since I don’t use it that much. The log told me that. Once I changed the service from disabled to manual, the update installed just fine.
July 14, 2008 at 17:12 |
Thank you for your helpful comments!
I’m sure each of them gives helpful tips to people still struggling with the issue.
July 14, 2008 at 21:45 |
Install failed.
Error code 6AA
When I look into SQL server Configuration Manager,
ACT! by Sage 2008 (10.0) Version 10.0.1.199,
is all that is running.
Could this be the problem?
Standing by
July 15, 2008 at 18:15 |
SQL Server VSS Writer service must be enabled and running for this update to succeed.
July 15, 2008 at 20:18 |
Dear BlueRage,
Would you be kind enough to narrate and detail that procedure.
With Great Appreciation,
George
July 15, 2008 at 20:44 |
@George:
1) Go to the Services snap-in (in Administrative Tools or Computer Management)
2) Locate SQL Server VSS Writer
3) Double click / right click for Properties
4) Make sure that the Startup type is not Disabled
5) Start the service if it is stopped
Hope this helps!
July 19, 2008 at 14:43 |
Had the same problem on my HP machine which is running Vista Home Premium and a developer edition of MS SQL Server 2005.
After reading your post I opened Administrative Tools > Services and set the permissions to all disabled instances of SQL Server to manual.
Then the update installed without a hitch.
/Johnny
July 19, 2008 at 19:49 |
Changing all SQL permissions to manual fixed it for me as well. Wonder why there is no reference to this problem yet on MicroSoft site?
Thanks for the tip!
July 22, 2008 at 21:58 |
Doing this fixed it for me:
http://support.microsoft.com/kb/916766
I basically just re-applied the default permissions to the entire sql folder through folder security. (ie, gave administrators full perms)
August 22, 2008 at 01:32 |
LOL
i was really worried until i read what the SQL Server did.
Welcome to uninstall. solved my problem straightaway
August 25, 2008 at 09:26 |
Thanks all for the help.
Just changed the logon on the “SQL Server” to “local” (under “administrative tools/services”) and then started the service. Then I could install it without any problems.
September 3, 2008 at 06:18 |
Hi, just wondering if anybody can assist me with this same problem on my computer. I have both full and express. So far I have:
- ensured that the Administrator group has complete access to all Data folders
- changed all Sql Server services to run under Local System account
Does anybody have any other suggestions?
I’m getting the following in the update Summary:
Product : SQL Server Database Services 2005 (SQLEXPRESS)
Product Version (Previous): 3054
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log
SQL Express Features :
Error Number : 29506
Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user David. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
The ‘David’ (thats me) is definitely a member of the Administrator group, and the Administrator definitely has Full Control over the listed Data directory.
Any advice would be appreciated,
September 3, 2008 at 06:46 |
Scratch that, I’ve just gotten to the bottom of it. As it turns out, there WAS a rogue datafile that was owned by former user account. In this case, blasting permissions down the heirarchy ignores these files, since Ownership had to be taken first (I gave the file to the Administrator group). After this I was finally able to run the update successfully
September 3, 2008 at 07:38 |
@dotnetdave:
Nice to hear you got it fixed
Thanks for your input – I’m sure it’ll help someone else
September 9, 2008 at 19:17 |
Nice. I had a damaged instance SQLEXPRESS (I think) that would not start when I went to the SQL server config util as suggested. Killed it alone – without removuig the rest of SQL Server using “Add and remove programs”. It hadn’t started anyway so whatever it was I doubt if I will miss it for the time being. Install is looking very good now for update. …Yep in fact it has just finished successfully. Thanks for puttig me on the right trail
September 9, 2008 at 19:22 |
@John: These kind of problems with computers can be really annoying sometimes
September 11, 2008 at 04:44 |
Hi dot net dave
can u explain me what u did ?
September 13, 2008 at 13:24 |
Security Update for SQL Server 2005 Service Pack 2 (KB948109)
Installation date: 9/13/2008 6:46 AM
Installation status: Failed
Error details: Code 733F
Update type: Important
October 1, 2008 at 15:51 |
I uninstalled SQL Server Express edition and re-installed it after which the update installed properly.
October 10, 2008 at 16:46 |
I have finally managed to get my computer to accept the hanging security update KB948109 – It needed SP1 AND SP2 – Incidentally I took this opportunity to update to SQL 2008 and the Upgrade Wizard tool – Excellent alongside the latest Visual Basic – very pleased.
November 21, 2008 at 20:44 |
I was able to complete KB948109 installation only after starting SQL Browser Service…
November 21, 2008 at 20:46 |
Sorry… I forgot details… Windows Server 2003 Standard Edition R2 with SP2 and SQL Server 2005 Express Edition
It was running on a virtual box driven by VMware Esx3i 3.5
March 9, 2009 at 18:22 |
Installing SQL Server Security Patches in line with Windows Updates can be disasterous..Probably should not install SQL Server Security update patches along with the install of Window updates on a home machine. SQL Server Security installs may require some service shut down or other hand holding; if the install goes in with windows updates…this corrupt your master databases as it turned out for me both SQL Server 2005/2005 services would not start up again after installation of this patch. [I had backups and with Microsoft help, I got both services rebuilt and restored but I won't be adding SQL Server patches to install in the same way as windows updates any more]
September 20, 2009 at 03:19 |
On my computer, the update installed by going to MMC (alt-click My computer –> Manage), going to services (at the bottom), SQL server config, and starting the services that were stopped/disabled. Basically, this is the same as what others were saying; I just wanted to say that it worked for me.
December 28, 2009 at 21:40 |
I was running into this same issue on our new HP workstations.
MSSMLBIZ was slated as manual start up (that would not start) and to use a network service account. I changed it to loacl system and it started fine and installed all updates without issue.