There's Something about SQL!

...SQL Server, BI and other Cool Technology... var sc_project=1839145; var sc_invisible=1; var sc_partition=17; var sc_security="180bc290";

SQL Server 2005 Service Pack 2 is not successfully updated when you try to install or to uninstall a security update

SQL Server 2005 Service Pack 2 is not successfully updated when you try to install or to uninstall a security update

  • Comments 1
  • Likes

If you recently found yourself in installing latest SQL Server 2005 Security Update (you did installed it right?):

 

Microsoft Security Bulletin MS09-004 – Important

http://www.microsoft.com/technet/security/bulletin/MS09-004.mspx

 

..and had a look to the known issues page...

You might have had a heart attack (as I did at first) in seeing the following:

 

SQL Server 2005 Service Pack 2 is not successfully updated when you try to install or to uninstall a security update

http://support.microsoft.com/kb/957008

"When you try to install a security update for Microsoft SQL Server 2005 Service Pack 2, Microsoft SQL Server 2005 is not successfully updated. This issue occurs because the rollback process for the security updates incorrectly removes the SQL Server 2005 service accounts from the respective local SQL Server service groups. "

 

You can guess my reaction when immediately I thought: "oh my, so not just this but all previous SQL Server 2005 SP2 Security Updates which I've applied were not successful" :-S!!!

 

Ok now, did I scare you off? :-)

You can just relax as the title and the description are a bit misleading. Nothing too bad out there (and in fact, title and description are in the process of being updated...)

 

This issue triggers if and only if for any reason the rollback process is started.

If the build was installed successfully without a rollback (which you can check by verifying the build number), then the security update was installed correctly.

If you check at the end of the process your instance build number (anyway, it is best practice to do so :)) and it matches the Security Update build number - then you are safe.

 

- Beatrice Nicolini -

Comments
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment