Kb948109 failed to install

Error code Any ideas anyone? The error is: Fatal error during installation. Still do not know if it is ok to change the service back to a Network Service log on but will find out.

As of now everthing is working with out errors. The update was failing originally saying access denied on starting the SQL service. If this is not the case for you the fix above may not resolve your issue. X is a placeholder for the corresponding value on a specific system. SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete.

Error when installing KB Reply to author. Report message as abuse. Show original message. Once ownership was taken I was able to propigate the permissions. It was different files in the data directory from the one the patch complained about on the systems which had this problem. Once the perms were pushed, the SQL Server manager was able to stop the DB's which I recomend doing prior to installing the patch unless you like rebooting.

If the SQL insntance is located on a network share, you should stop them because the share wont be up when the service starts during reboot and patch application otherwise.

This did the trick, I a ppreciate you spend time looking though these formuns to reslove our issues. We had exactly the same error with this patch, although I think the cause was different.

Box was Windows and SQL 64 bit. Ours turned out to be having a mount point directories below the Data directory for 3 large databases. Had to unmount the data directories for Data and Logs, which obviously made those 3 databases fail, then re-applied the patch successfully then reattached the mount points and restarted SQL. I think we had a similar problem with SP2 as well from memory and I have seen others with the same.

Not sure if this has any negative effect on those 3 databases, but without doing this SQL will not start as the patch failing stopped SQL restarting and the only way we could fix that was to get the fix successfully applied. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. SQL Server Setup. Sign in to vote.

Sunday, July 13, PM. Thursday, August 7, PM. Provide the permissions and try installing again.. Thanks much. Monday, July 14, PM.

Nice Fix Deepak. Tuesday, July 15, PM. Atlast found solution!!! Friday, July 18, PM. Morning, All I am having similar issues with the above update mine is pointing. Thanks Regards. Monday, July 28, AM. Tuesday, August 5, PM. I give Peter the gold star! This put the last nail in the coffin on this problem for me. At least on one system. Getting the programmer off his system long enough to bang my head on it was the other hard part. Now I get to do this to the rest of the computers it failed on.

Two of the files in the Data directory had mangled permissions - not the one the error is on. When I took ownership to the same owner on the other files an account that was disabled on the domain popped into the basic security window as the only user with rights. I took screen shots but there is no place to put them here easilly.

Once I propagated the file permissions onto the files in question and stopped the data base in the managment console only need to do this if you want to avoid a reboot the patch took about half an hour to install.

One note, once I knew what to look for, I found AccessEnum from the SysInternals useful in finding my files with managled permissions. I only wish it showed file owner in addition to Rights on files. I had the same problem. Any idea on how permissions got "manageled"? For me, no, I would probably chock it up to the entropy that occurs on systems that are heavily used and not reloaded between users. I can guess that the person whose account appeared did the initial install a few years ago.

I took over Network support in the last month.