Automatic Update on Sql Server 2005 Server Failed for Visual Studio 2005 SP1

  • We have two database servers with OS MS 2003 Server and SQL Server 2005 SP2 installed. When we logged into the servers it indicates that there are updates ready for the computer to click to apply. We have this servers on our network MS Automatic Updates list. The problem we are experiencing is that we proceed and click for the update to be installed but instead after a few seconds it displays a message indicating that "some updates could not be installed" :hehe: The updates is Visual Studio 2005 Service Pack 1.

    We proceed to go to Control Panel, Add/Remove programs we found a MS Visual Studio 2005 PRemier Partner Edition - ENU installed on the server. Seems that the patch can't be applied to this version.

    Has anyone else experience this situation? If so, what we can do to apply the update successfully.

  • You need the appropriate edition of the SP1. AFAIK you have to download it manually from Microsoft Downloads - there are different editions.

    OTOH, Microsoft Update is not perfect, and it just might be that there's nothing wrong with the patch, only with Microsoft Update. 😉

    ML

    ---
    Matija Lah, SQL Server MVP
    http://milambda.blogspot.com

  • I don't think this is a problem with editions.

    I suspect this may be a problem with disk space.

    This update is HUGE, on the order of 400+ MB.

    The update file is an exe file, but it is just a wrapper around a 400+ MB .MSI file (Microsoft installer file).

    So, to install it, you need the 400+ MB for the source file plus 400+MB for the .MSI plus the space to actually install it.

    If you attempt to apply this update via Automatic Updates, it tries to put the original copy of the file on C: and puts the .MSI file on C: as well.

    If your C: drive is tight on space (probably anything less than 1.5GB is tight in this situation)

    What you can do is to download the install from MS, then extract the .MSI file (there is a command line to do this) and run the .MSI from some other drive letter.

    Also, you may have to kill the one that Automatic Updates has downloaded. I'm not sure of the exact location of the file, but once you have a copy of it to know the size, you can search for files of similar size on C:

  • Oh, I completely forgot about that one! And to think this was one of the reasons why I moved my temp folder off C:... :hehe:

    ML

    ---
    Matija Lah, SQL Server MVP
    http://milambda.blogspot.com

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply