“Unexpected error occurred” during SQL Server 2005 SP1 install.

  • Article

When you are trying to install SP1 you may see “Unexpected error” message. This error message will appear right after package has been extracted in a temporary folder.

Popup window will have a title “Unexpected error occurred”

Window text: “The following unexpected error occurred”.

Confirm Behavior

In order to confirm this behavior please switch to temporary folder where files have been extracted. By default, SP1 setup will create a temporary folder on disk with most of the available space. You should look for a folder like:

I:b90f2a07b3b452e0b87d

Where I drive indicates one of the drives on your computer.

Next, run hotfix.exe and you should see the same error message.

This error message usually means something wrong with \computernamedrive$ administrative shared resource.

What Next?

Run following command in command prompt:

net share

You will see output similar to following

C:Documents and SettingsAdministrator.DOMAIN>net share

Share name Resource Remark

----------------------------------------------------------

H$ H: Default share

F$ F: Default share

IPC$ Remote IPC

G$ G: Default share

ADMIN$ C:WINDOWS Remote Admin

E$ E: Default share

C$ C: Default share

The command completed successfully.

Locate the drive to which SP1 was extracted to – in our case, I drive. If you’re experiencing issue described above, you will not see this drive in the output.

In order to fix this issue you have two options:

  1. Use /EXTRACT parameter with SP1 setup to extract files to specific folder on drive where administrative share resource is available.

    C:>SQLServer2005SP1-KB913090-x86-ENU.exe /extract:E:Hotfix

    Then run hotfix.exe.

    More details about update packages and their startup options can be found here.

  2. Enable administrative share resource on drive with most available space.

    For example in case if you will need to fix drive I: run following command from command prompt:

    net share I$=I:

Hope this helps.

Need More Help?

Please use the technical support link on this blog to contact us, in case the resolution above didn’t solve your problem.

 

 

Posted By : Sergey Pustovit