"1635" or "1603" error code when you install update rollups or service packs for Exchange Server 2007 or Exchange Server 2010


When you try to install an update rollup or service pack for Microsoft Exchange Server 2007 or for Microsoft Exchange Server 2010, you receive a "1603" or "1635" error code.


This problem occurs because an .msp file from an earlier update rollup is missing.

When you install a rollup update or service pack, Exchange Server 2007 and Exchange Server 2010 check the "%systemdrive%\WINDOWS\Installer" folder for .msp files from earlier update rollups. If an .msp file is missing, the installation process fails with a "1603" or "1635" error code.


To resolve this issue, follow these steps:
  1. Make sure that all antivirus, anti-spam, and monitoring services are disabled.
  2. Clear the data in the "%SystemDrive%\Windows\TEMP"folder.
  3. Try to install the update rollup or service pack.
  4. If the installation fails, open the Exchangesetup.msilog installation log in the "%SystemDrive%\ExchangeSetupLogs" folder.

    Note If there is no Exchangesetup.msilog installation log, create it by using the /lxv setup switch. For example, the following command installs Update Rollup 8 for Exchange Server 2007 Service Pack 1 and creates an installation log on the local drive:
    Exchange2007-KB968012-x64-EN.msp /lxv c:\Rollup.log
    The following log is an example of the installation log:
    MSI (s) (80:B8) [22:57:41:526]: Opening existing patch 'C:\WINDOWS\Installer\9dd4195.msp'.
    MSI (s) (80:B8) [22:57:41:526]: Opening existing patch 'C:\WINDOWS\Installer\33502bc.msp'.
    MSI (s) (80:B8) [22:57:41:526]: Note: 1: 2203 2: C:\WINDOWS\Installer\33502bc.msp 3: -2147287038
    MSI (s) (80:B8) [22:57:41:526]: Couldn't find local patch 'C:\WINDOWS\Installer\33502bc.msp'.

    Looking for it at its source.
    MSI (s) (80:B8) [22:57:41:526]: Resolving Patch source.
    MSI (s) (80:B8) [22:57:41:526]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Looking for sourcelist for
    product {FAD5369A-D8A9-4783-97E1-3DDB12DCBBAC}
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Adding {FAD5369A-D8A9-4783-97E1-3DDB12DCBBAC};
    to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Now checking product {FAD5369A-D8A9-4783-97E1-3DDB12DCBBAC}
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (80:B8) [22:57:41:526]: SOURCEMGMT: Processing net source list.
    MSI (s) (80:B8) [22:57:41:526]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
    MSI (s)(80:B8) [22:57:41:526]: Note: 1: 1706 2: -2147483647 3: Exchange2007-KB949870-x64-EN.MSP Snippet: Exchangesetup.msilog file or Exchangesetuplog.txt log file
    This example log file indicates that 33502bc.msp file in the "C:\windows\installer" folder was not found during the installation process. Additionally, the log file indicates that this .msp file is related to Exchange2007-KB949870-x64-EN.MSP. To resolve this issue, follow these steps:
    1. Download update 949870 from the Microsoft Download Center.
    2. Copy the update file that you downloaded to the "C:\windows\installer" folder.
    3. Rename the update file as "33502bc.msp."
    4. Run the installation process again.
  5. If no other .msp files are missing, the installation process succeeds. However, if the installation process fails, you must repeat step 4 for each missing .msp file. 

Article ID: 2784788 - Last Review: Nov 23, 2012 - Revision: 1

Microsoft Exchange Server 2007 Enterprise Edition, Microsoft Exchange Server 2007 Standard Edition, Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2010 Standard