Messages when installing SP1 for Sql Server 2005

Service Pack 1 for Sql Server 2005 was released in April. I have installed it on quite a few systems: 32-bit, 64-bit, and 64-bit cluster. SP1 is cluster-aware, meaning that if you want to upgrade a cluster, the installation package can detect that and will apply the changes to all nodes.

Of my installs, all were successful except one. In that instance, I was partially successful: Integration Service was not upgraded successfully, the rest of the system such as Sql Server Service and Native Client were all successful. There appears to be some SSIS related issues with SP1. I will talk about that in a future post.

Anyway, during the upgrade process, there are 2 messages you need to be aware of. They are all related to the fact that the upgrade touches many components and services.

The first message you will see is this:

—————————
Pending Reboot Files Found
—————————
A previous program installation caused unrelated pending file operations. The patch installation will succeed even if your computer is not rebooted.

Do you want to proceed?
—————————
Yes No
—————————
Click Yes to this one.

The second message looks like this:
—————————
Locked Files Found
—————————
The following files are currently locked.

In order to prevent a necessary reboot at the end of the patch install process, close down all other applications before proceeding.

Write locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftesql.exe (msftesql.exe)
Write locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftepxy.dll (msftesql.exe)
Write locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msfte.dll (msftesql.exe)

—————————
Cancel Try Again Continue
—————————
For this one, click Continue.

3 thoughts on “Messages when installing SP1 for Sql Server 2005”

  1. Found the same thing SSIS in some instances. Technically (and hopefully), I don’t count SP1 as an actual service pack. Yes, there are a number of fixes thrown in, but it is there for a primary reason – enabling database mirroring. Let’s hope SP2 has a little bit more polish. I do like that you can update multiple instances in one sweep (especially nice on my dev server that has 7 instance and I actually wanted to keep on at RTM).

  2. Thanks James. Great point!

    I will blog about some upgrade issues with SSIS in a future post.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.