"Upgrade could not open the MSI file" error message when you run Spsupgrade.exe from the command line to upgrade a server in your server farm to SharePoint Portal Server 2003 Beta 2 Technical Refresh

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When you run Spsupgrade.exe from the command-line to upgrade a server in your server farm to Microsoft Office SharePoint Portal Server 2003 Beta 2 Technical Refresh, you may receive the following error message:
Upgrade could not open the MSI file
Cause
This problem may occur if the following conditions are true:
  • You run Spsupgrade.exe from the command line.

    To do this, copy the Sps\Upgrade folder from the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD to a folder on the local hard disk, and then specify the location of the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files by using a UNC path.
  • You use a backslash character (\) at the end of the UNC path when you specify the location of the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files.

    For example, use the following command-line syntax, where FileServer is the name of the server, and directory for CD files is the name of the shared folder:
    Spsupgrade.exe \\FileServer\directory for CD files\
The "Upgrade SharePoint Portal Server" section of the Readme.htm text file, located on the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD, contains an error in Step 1. It incorrectly states that "the command line syntax is \\fileserver\directory for CD files\", as follows:
1. Insert the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD into your CD drive.

Note Running upgrade from a network share is not supported. Upgrade must be run from the CD or copied to the local computer and run from there.

If only the \SPS\Upgrade directory is copied to the local computer, you must specify the path of the copies of the CD files when running SPSUpgrade.exe from the command line. The command line syntax is SPSUpgrade \\fileserver\directory for CD files\. If all of the files on the CD are copied to the local computer, simply run SPSUpgrade.exe from the local computer.
The following text contains the correct command-line syntax to use when you run SPSUpgrade.exe from the command-line:
SPSUpgrade \\fileserver\directory for CD files
Resolution
When you run Spsupgrade.exe from the command line, do not use a backslash character (\) at the end of the UNC path when you specify the location of the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files. Use the following command-line syntax when you run Spsupgrade.exe from the command-line, where FileServer is the name of the server, and directory for CD files is the name of the shared folder:
Spsupgrade.exe \\FileServer\directory for CD files
Workaround
To recover a server where an upgrade operation using Spsupgrade.exe was not completed successfully, follow these steps:
  1. Log on to the server as a member of the local Administrators group.
  2. Click Start, click Run, type cmd in the Open box, and then click OK.
  3. Switch to the folder that contains the SPS\Upgrade files that you copied from the SharePoint Portal Server Beta 2 2003 Technical Refresh CD. For example, type the following lines at the command prompt, where Drive is the drive that contains the folder where you copied the files to, Path is the path of the folder that contains the files, and FolderName is the name of the folder that contains the files, pressing ENTER after each line:
    Drive:
    cd Drive:\Path\FolderName
  4. Type the following line, where CDimage is the path of the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files, and then press ENTER:
    msiexec /qb /i CDimage\WSS\Sts.msi /l*v STS_Install.log LAUNCHEDFROMSETUPSTS=1
  5. Switch to the drive where Microsoft Windows is installed.
  6. Type the following line, and then press ENTER:
    cd %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\60\Config
  7. Type the following line, and then press ENTER:
    copy Web.config Web.config.bak
  8. Type the following line, where CDimage is the path of the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files, and then press ENTER:
    msiexec /qb /I CDimage\SPS\Sps.msi /l*v SPS_Binary_Upgrade.log REBOOT=ReallySuppress
  9. Type the following line, where CDimage is the path of the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files, and then press ENTER:
    msiexec /qb /famsv CDimage\SPS\Sps.msi /l*v SPS_Repair.log REBOOT=ReallySuppress DONTSTARTSERVICE=1
  10. When the Setup program is completed and you are prompted to restart the server, click No.
  11. Run Spsupgrade.exe.

    Make sure that you do not use a backslash character (\) at the end of the UNC path when you specify the shared folder that contains the SharePoint Portal Server 2003 Beta 2 Technical Refresh CD files. Use the following command-line syntax, where FileServer is the name of the server, and directory for CD files is the name of the shared folder:
    Spsupgrade.exe \\FileServer\directory for CD files
More information
For more information about how to deploy, configure, and administer SharePoint Portal Server, see the Microsoft Office SharePoint Portal Server 2003 Administration Guide. The Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm) is located in the Docs folder in the root folder of the SharePoint Portal Server 2003 Beta 2 Tech Refresh CD.

For more information about SharePoint Portal Server, visit the following Microsoft Web site:
Properties

Article ID: 871176 - Last Review: 01/17/2015 17:43:41 - Revision: 2.0

  • Microsoft Office SharePoint Portal Server 2003
  • kbnosurvey kbarchive kberrmsg kbfix kbbug KB871176
Feedback