Topic Last Modified: 2010-06-29

Beginning the release of Microsoft Exchange Server 2007, Microsoft changed the servicing strategy for Exchange software updates. Updates (also known as update rollup packages) are now released as major rollups of cumulative fixes. For more information about this servicing strategy, see Microsoft Knowledge Base article 937194, The product service strategy for Exchange Server 2007.

Typically, you do not experience any issues when you install Exchange update rollup packages. However, if you do experience an issue, you may not be able to easily troubleshoot the cause of the failure. This topic discusses some of the common causes of update rollup installation failures. This topic also provides information about how to troubleshoot installation failures.

Common Update Rollup Installation Issues

The following sections describe some of the common issues that cause update rollup installation failures.

An Incorrect Update Rollup Version is Used

Because the Exchange Management Console may be run on a 32-bit operating system, and because a 32-bit version of Microsoft Exchange may be used for testing purposes, it is possible to install an incorrect version of an update rollup package. In this scenario, you receive the following warning message when you try to install the particular update rollup:

The version of this file is not compatible with the version of Exchange Server 2007 that you're running. Check your computer to see whether you need an x64 (64-bit) or x86 (32-bit) version of this file.

To resolve this issue, obtain the appropriate version of the update rollup package.

An Interim Update is Installed

Microsoft releases critical interim updates for Microsoft Exchange outside of the release schedule for update rollups. If you install an interim update, the interim update must be removed before you install the update rollup package that contains the same fix as the interim update. If an interim update is installed, you receive the following warning message when you install the particular update rollup package:

Unable to install because a previous Interim Update for Microsoft Exchange has been installed. Please use Add/Remove Programs to uninstall the Interim Update before running this setup again.

Remove any existing IUs from Add/Remove programs (Windows 2003) or Programs and Features (Windows Vista, 2008) and attempt to install the Rollup once more.

This issue may also occur during the removal of an update rollup. If an interim update is installed, you must remove the interim update before you remove an update rollup. In this scenario, if you try to remove the update rollup before you remove the interim update, you receive the following warning message:

Uninstall cannot continue. The <Wizard Name> has determined that an Interim Update has been installed. This Update Rollup cannot be uninstalled until the Interim Update has been uninstalled.

You may experience a similar issue if you try to install an update rollup that is an earlier version than the update rollup version that is currently installed. In this scenario, you receive the following warning message when you try to install the earlier update rollup:

Installation cannot continue. The <Wizard Name> has determined that this Update Rollup has been superseded by the currently installed Update Rollup. Installation of this Update Rollup is unnecessary.

To resolve these issues, remove the interim update, and then install the latest update rollup for the version of Microsoft Exchange that you are running.

No Internet Connectivity is Available

When you try to install an update rollup, the installation may stop responding (hang) when the .NET Framework tries to perform the certificate revocation operation. To resolve this issue, temporarily disable certificate revocation. To do this, use one of the following methods.

Method 1: Set the State entry in the registry

To disable certificate revocation checks in the registry, follow these steps:

  1. In Registry Editor, locate the following registry subkey:

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Wintrust\Trust Providers\Software Publishing\State

  2. Set the following registry value:Value name: StateValue type: REG_DWORDValue data: 0x00023e00

  3. Exit Registry Editor, and then try to install the update rollup.

  4. After the update rollup is installed successfully, set the State registry value to 0x00023c00.

Method 2: Configure Internet Explorer

To disable certificate revocation checks in Internet Explorer, follow these steps:

  1. Start Internet Explorer.

  2. On the Tools menu, click Internet Options.

  3. In the Internet Options dialog box, click the Advanced tab.

  4. Under Security, click to clear the following check boxes:

    • Check for publisher’s certificate revocation

    • Check for server certificate revocation

  5. Exit Internet Explorer, and then try to install the update rollup.

  6. After the update rollup is installed successfully, modify the Internet Explorer properties to re-enable certificate revocation.

For more information about certificate revocation in Microsoft Exchange, see the Exchange Server Team Blog article Exchange 2007 managed services might time out during certificate revocation checks.

Exchange Services Do Not Restart Automatically

If Microsoft Exchange-related services do not restart after an update rollup installation, see Microsoft Knowledge Base article 944752, Exchange Server 2007 managed code services do not start after you install an update rollup for Exchange Server 2007.

Other Issues

You may also experience the following issues when you install an update rollup:

  • After you install an update rollup by using Windows Update, certain services are disabled.

  • Outlook Web Access does not work.

This issue may occur if the %SYSTEMDRIVE%\ExchangeSetupLogs folder has been removed or renamed. For more information, see Microsoft Knowledge Base article 930809, Description of Update Rollup 1 for Exchange Server 2007.

Troubleshooting Installation Issues

You may experience an update rollup installation issue that is not addressed in the previous sections in this topic. This section contains information that you can use to help troubleshoot other causes of an update rollup installation failure.

Examine the Application Event Log

In some cases, Microsoft Exchange Update Rollup Setup may exit unexpectedly. Or, Setup may report that it ended prematurely. In this case, you receive the following error message:

Setup Wizard for Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467) ended prematurely because of an error. Your system has not been modified. To install this program at a later time, please run the installation again.

To troubleshoot this issue, examine the Application log on the affected server. Windows Installer logs installation errors in the Application log. For example, Windows Installer logs the following entry for error code 1603:

Event type: Error

Event source: MsiInstaller

Event category: None

Event ID: 1024

Description: Product: Microsoft Exchange Server-Update 'Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580) 8.1.311.3' could not be installed. Error code 1603.

Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support:

http://go.microsoft.com/fwlink/?LinkId=23127

To troubleshoot a Windows Installer error, enable verbose MSI Logging.

Enable Verbose MSI Logging

Because Microsoft Exchange uses the Windows Installer for updating, you must increase MSI Logging for the affected update rollup. To generate a verbose log file for an MSI or MSP package, Use one of the following methods.

Method 1: Use Command-Line Options

You can run the update rollup package together with the logging option to generate an installation log file for the particular installation attempt. For example, run the following command to create a log file during the update rollup installation:

Copy Code 
Exchange2007-KB<RollupPackageNumber>-x64-EN.msp /lxv* c:\<path>\<filename>.log

Method 2: Set a Registry Value

You can set a registry entry to generate verbose logging for all MSI updates. To do this, follow these steps:

  1. At a command prompt, enter the following command:

    net stop msiserver

  2. Start Registry Editor (regedit.exe), and then locate the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

  3. Create the following registry entries in the Installer subkey:

    Value name: loggingValue type: REG_SZ

    Value data: voicewarmup!



    Value name: debug

    Value type: REG_DWORD

    Value data: 7

  4. Exit Registry Editor, and then start the Windows Installer service. To do this, run the following command at a command prompt:

    net start msiserver

After you enable verbose logging, a new Msi*.log file is created every time that you use Add or Remove Programs.

Note:
We recommend that you do not leave verbose logging enabled. Verbose logging may affect system performance and may use a lot of disk space.

For more information about how to enable Windows Installer logging, see Microsoft Knowledge Base article 223300, How to enable Windows Installer logging.

Search the MSI Log File for Return Value 3

After you configure Windows Installer verbose logging, search the MSI log file for the following string:

Return value 3

Generally, the first instance of Return value 3 identifies the cause of the installation issue. To troubleshoot the installation issue, examine the entries that immediately precede the return value 3 entry. For more information about this procedure, see the Microsoft Exchange Server Team Blog article How to locate the cause of error code 1603 in a verbose MSI log file.

The following sections describe issues that may be logged by Windows Installer verbose logging. The information in these sections is taken from real-world issues that have been handled by Microsoft Enterprise Communications Support technicians.

Case 1: An incorrect ExecutionPolicy is Set

An Microsoft Exchange update rollup package installation may fail on Windows Server 2008 if an incorrect ExecutionPolicy is set.

The following is an excerpt from log file entries that immediately precede the first instance of Return value 3.

MSI (s) (DC!BC) [06:51:04:902]: PROPERTY CHANGE: Deleting QtExecCmdLine property.

Its current value is '"C:\Program Files\Microsoft\Exchange

Server\\bin\QuietExe.exe"

"C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe" " -command .

'C:\Program Files\Microsoft\Exchange Server\\bin\servicecontrol.ps1'

BeforePatch"'.

MSI (s) (DC!BC) [06:51:06:355]: Creating MSIHANDLE (4) of type 790531 for thread 4540

CAQuietExec: Error 0x80070001: Command line returned an error.

MSI (s) (DC!BC) [06:51:06:355]: Closing MSIHANDLE (4) of type 790531 for thread 4540

MSI (s) (DC!BC) [06:51:06:355]: Creating MSIHANDLE (5) of type 790531 for thread 4540

CAQuietExec: Error 0x80070001: CAQuietExec Failed

MSI (s) (DC!BC) [06:51:06:355]: Closing MSIHANDLE (5) of type 790531 for thread 4540

MSI (s) (DC!BC) [06:51:06:355]: Closing MSIHANDLE (2) of type 790541 for thread 4540

MSI (s) (DC:C8) [06:51:06:355]: Closing MSIHANDLE (1) of type 790542 for thread 6776

Action ended 6:51:06: CA_SAVEDATA_STOP_SERVICES. Return value 3.

In this log file excerpt, Return value 3 appears next to CA_SAVEDATA_STOP_SERVICES.

Microsoft Exchange uses Custom Actions (CAs) when it installs update rollup packages by using the Windows Installer engine. In the CA_SAVEDATA_STOP_SERVICES custom action, Microsoft Exchange tries to run the PowerShell script that is named servicecontrol.ps1 together with the BeforePatch option.

In this case, the script did not run because of an incorrect ExecutionPolicy setting in PowerShell. To determine the current PowerShell execution policy, run the Get-ExecutionPolicy cmdlet. By default, the PowerShell execution policy is set to RemoteSigned.

To resolve this issue, set the ExecutionPolicy to RemoteSigned or to Unrestricted. Then, try to install the update rollup again. After the update rollup has been installed, set the ExecutionPolicy to RemoteSigned.

For more information about this issue, see the following topics:

Case 2: Update Rollup Cannot Delete a Temporary File

A 1603 error may occur if the update rollup installation cannot delete or modify a temporary .msp file during the installation process. The following is an excerpt from the MSI log file for this error.

MSI (c) (E8:F0) [08:54:18:744]: Windows Installer installed an update. Product

Name: Microsoft Exchange Server. Product Version: 8.1.240.6. Product Language:

1033. Update Name: Update Rollup 4 for Exchange Server 2007 Service Pack 1

(KB952580) 8.1.311.3. Installation success or error status: 1603.

MSI (c) (E8:F0) [08:54:18:744]: Note: 1: 1729

MSI (c) (E8:F0) [08:54:18:745]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (E8:F0) [08:54:18:756]: Transforming table Error.

MSI (c) (E8:F0) [08:54:18:758]: Transforming table Error.

MSI (c) (E8:F0) [08:54:18:758]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (E8:F0) [08:54:18:758]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (E8:F0) [08:54:18:769]: Transforming table Error.

MSI (c) (E8:F0) [08:54:18:772]: Transforming table Error.

MSI (c) (E8:F0) [08:54:18:772]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (E8:F0) [08:54:18:772]: Product: Microsoft Exchange Server -- Configuration failed.

MSI (c) (E8:F0) [08:54:18:773]: Windows Installer reconfigured the product. Product

Name: Microsoft Exchange Server. Product Version: 8.1.240.6. Product Language:

1033. Reconfiguration success or error status: 1603.

MSI (c) (E8:F0) [08:54:18:775]: Attempting to delete file

C:\Users\<user alias>\AppData\Local\Temp\2\3b396.msp

MSI (c) (E8:F0) [08:54:18:775]: Unable to delete the file. LastError = 32

MSI (c) (E8:F0) [08:54:18:781]: Grabbed execution mutex.

MSI (c) (E8:F0) [08:54:18:781]: Cleaning up uninstalled install packages, if any exist

MSI (c) (E8:F0) [08:54:18:781]: Attempting to delete file

C:\Users\<user alias>\AppData\Local\Temp\2\3b396.msp

MSI (c) (E8:F0) [08:54:18:784]: MainEngineThread is returning 1603

This error may occur when User Account Control is running on Windows Server 2008. To resolve this issue, verify that the update rollup installation is running from an elevated command prompt. To do this, right-click the cmd.exe shortcut, and then click Run as Administrator. Then, try to install the update rollup again.

Case 3: The Windows Installer Directory Does Not Contain .msp or .msi files from Previous Installations

When an update rollup installation fails, you may receive an error message that resembles the following message:

This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

When this error occurs, an entry is logged in the MSI log file that resembles the following entry.

=== Verbose logging started: 8/27/2007 13:12:59 Build type: SHIP UNICODE

3.01.4000.4042 Calling process: C:\WINDOWS\System32\msiexec.exe ===

MSI (c) (58:50) [13:12:59:838]: Resetting cached policy values

MSI (c) (58:50) [13:12:59:838]: Machine policy value 'Debug' is 0

MSI (c) (58:50) [13:12:59:838]: ******* RunEngine:

******* Product: {24B2C164-DE66-44FE-B468-A46D9D5E6B31}

******* Action:

******* CommandLine: **********

MSI (c) (58:50) [13:12:59:838]: Machine policy value 'DisableUserInstalls' is 0

MSI (c) (58:50) [13:12:59:838]: Warning: Local cached package

'C:\WINDOWS\Installer\380f45.msi' is missing.

MSI (c) (58:50) [13:12:59:838]: User policy value 'SearchOrder' is 'nmu'

MSI (c) (58:50) [13:12:59:838]: User policy value 'DisableMedia' is 0

MSI (c) (58:50) [13:12:59:838]: Machine policy value 'AllowLockdownMedia' is 0

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Media enabled only if package is

safe.

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Looking for sourcelist for product {24B2C164-DE66-44FE-B468-A46D9D5E6B31}

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Adding

{24B2C164-DE66-44FE-B468-A46D9D5E6B31}; to potential sourcelist list (pcode;disk;relpath).

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Now checking product

{24B2C164-DE66-44FE-B468-A46D9D5E6B31}

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Media is enabled for product.

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (c) (58:50) [13:12:59:838]: SOURCEMGMT: Trying source C:\Documents and

Settings\Administrator\Desktop\.

MSI (c) (58:50) [13:12:59:853]: Cloaking enabled.

MSI (c) (58:50) [13:12:59:853]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (58:50) [13:12:59:853]: SOURCEMGMT: Resolved source to: 'C:\Documents and Settings\Administrator\Desktop\'

MSI (c) (58:50) [13:12:59:885]: SOFTWARE RESTRICTION POLICY: Verifying package -->

'C:\Documents and Settings\Administrator\Desktop\EXCHANGESERVER.msi' against

software restriction policy

MSI (c) (58:50) [13:12:59:885]: SOFTWARE RESTRICTION POLICY: C:\Documents and

Settings\Administrator\Desktop\EXCHANGESERVER.msi has a digital signature

MSI (c) (58:50) [13:13:00:010]: SOFTWARE RESTRICTION POLICY: C:\Documents and

Settings\Administrator\Desktop\EXCHANGESERVER.msi is permitted to run at the

'unrestricted' authorization level.

MSI (c) (58:50) [13:13:00:010]: Cloaking enabled.

MSI (c) (58:50) [13:13:00:010]: Attempting to enable all disabled privileges before calling Install on Server

MSI (c) (58:50) [13:13:00:010]: End dialog not enabled

MSI (c) (58:50) [13:13:00:010]: Original package ==> C:\Documents and

Settings\Administrator\Desktop\EXCHANGESERVER.msi

MSI (c) (58:50) [13:13:00:010]: Package we're running from ==>

C:\DOCUME~1\ADMINI~1 \LOCALS~1\Temp\2\1d700e29.msi

MSI (c) (58:50) [13:13:00:041]: APPCOMPAT: looking for appcompat database entry with ProductCode '{24B2C164-DE66-44FE-B468-A46D9D5E6B31}'.

MSI (c) (58:50) [13:13:00:041]: APPCOMPAT: no matching ProductCode found in

database.

MSI (c) (58:50) [13:13:00:041]: MSCOREE not loaded loading copy from system32

MSI (c) (58:50) [13:13:00:041]: Opening existing patch

'C:\WINDOWS\Installer\5c321.msp'.

MSI (c) (58:50) [13:13:00:041]: Note: 1: 2203 2: C:\WINDOWS\Installer\5c321.msp 3: -2147287038

MSI (c) (58:50) [13:13:00:041]: Couldn't find local patch

'C:\WINDOWS\Installer\5c321.msp'. Looking for it at its source.

MSI (c) (58:50) [13:13:00:041]: Resolving Patch source.

MSI (c) (58:50) [13:13:00:041]: User policy value 'SearchOrder' is 'nmu'

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Media enabled only if package is

safe.

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Looking for sourcelist for product {09679EB4-B32D-4F10-88C9-34299B366C5B}

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Adding

{09679EB4-B32D-4F10-88C9-34299B366C5B}; to potential sourcelist list

(pcode;disk;relpath).

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Now checking product

{09679EB4-B32D-4F10-88C9-34299B366C5B}

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Media is enabled for product.

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Processing net source list.

MSI (c) (58:50) [13:13:00:041]: Note: 1: 1402 2: UNKNOWN\Net 3: 2

MSI (c) (58:50) [13:13:00:041]: Note: 1: 1706 2: -2147483647 3:

Exchange2007-KB935490-x64-EN.MSP

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Processing media source list.

MSI (c) (58:50) [13:13:00:056]: SOURCEMGMT: Resolved source to:

'Exchange2007-KB935490-x64-EN.MSP'

MSI (c) (58:50) [13:13:00:056]: Note: 1: 1314 2: Exchange2007-KB935490-x64-EN.MSP

MSI (c) (58:50) [13:13:00:056]: Unable to create a temp copy of patch

'Exchange2007-KB935490-x64-EN.MSP'.

This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

C:\Documents and Settings\Administrator\Desktop\EXCHANGESERVER.msi

MSI (c) (58:50) [13:13:00:056]: Note: 1: 1708

MSI (c) (58:50) [13:13:00:056]: Note: 1: 2729

MSI (c) (58:50) [13:13:00:056]: Product: Microsoft Exchange Server -- Installation failed.

In this case, Update Rollup 4 for Exchange 2007 SP1 failed to install because of a missing .msp file from a previous update rollup installation. Specifically, the .msp file from Update Rollup 2 for Exchange 2007 SP1 is missing.

This issue was determined by examining the log file entries, such as the following entries.

MSI (c) (58:50) [13:13:00:041]: Couldn't find local patch 'C:\WINDOWS\Installer\5c321.msp'. Looking for it at its source.

This entry indicates that Windows Installer tried to locate 5c321.msp. Because Windows Installer could not locate the file, Windows Installer tried to locate it by its source entry.

MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Looking for sourcelist for product {09679EB4-B32D-4F10-88C9-34299B366C5B}

This entry indicates that the source for the missing .msp file is GUID {09679EB4-B32D-4F10-88C9-34299B366C5B}. Subsequent entries in the log file resolve the product GUID to the particular package name.

MSI (c) (58:50) [13:13:00:041]: Note: 1: 1706 2: -2147483647 3: Exchange2007-KB935490-x64-EN.MSP MSI (c) (58:50) [13:13:00:041]: SOURCEMGMT: Processing media source list.MSI (c) (58:50) [13:13:00:056]: SOURCEMGMT: Resolved source to: 'Exchange2007-KB935490-x64-EN.MSP'MSI (c) (58:50) [13:13:00:056]: Note: 1: 1314 2: Exchange2007-KB935490-x64-EN.MSP

This entry indicates that the affected package is Exchange2007-KB935490-x64-EN.MSP. The following entry shows that Windows Installer is unable to create a temporary copy of the patch.

MSI (c) (58:50) [13:13:00:056]: Unable to create a temp copy of patch 'Exchange2007-KB935490-x64-EN.MSP'.This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

B935490 represents Update Rollup 2 for Exchange 2007 SP1. In this scenario, Windows Installer tries to locate the previous update rollup even though you are installing Update Rollup 4 for Exchange 2007 SP1.

This issue occurs because Windows Installer performs the following actions even though update rollup packages contain cumulative updates to the Microsoft Exchange code:

  • Checks for previously installed update rollup packages

  • Locates the .msi file for any previously installed update rollup packages

Windows Installer uses the previously installed files to create a full installation set to use for the current update rollup. If Windows Installer determines that a previous update rollup is installed but cannot locate the appropriate .msp file, the current update rollup installation fails.

To resolve this issue, make a copy of the update rollup file that is specified in the log file, and then rename the file to the same name that is referenced in the log file. In this example, make a copy of the Update Rollup 2 for Exchange 2007 SP1 file, and then rename it to 5c321.msp. Then, copy the renamed file to the C:\Windows\Installer directory.

From this error, note the following information about Windows Installer files:

  • You should not modify or remove the contents of the C:\Windows\Installer directory.

  • Windows Installer tracks all patches by product name and by GUID. Also, Windows Installer keeps a copy of the installer files in the C:\Windows\Installer directory. These files are renamed by using a random hexadecimal file name. The file names are unique and are referenced in the registry. Therefore, you cannot copy the contents of the C:\Windows\Installer directory among servers.

    The registry contains information about the patches that have been installed over the base Microsoft Exchange product. These registry entries point to the .msp and .msi files in the C:\Windows\Installer directory together with the original locations of the Setup source files. For example, the Microsoft Exchange base product has the following registry subkey: HKEY_CLASSES_ROOT\Installer\Products\ 461C2B4266EDEF444B864AD6D9E5B613The Patches subkey that appears under this subkey contains references to all update rollups that are installed. These update rollups are also referenced under the following subkeys:HKEY_CLASSES_ROOT\Installer\Patches

    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Patches

Note:
These registry entries are provided for reference purposes. We recommend that you do not modify or delete these registry entries.

Case 4: Registry or File System Corruption

Registry or file system corruption, especially that of the Windows Installer components, may make it difficult to troubleshoot an update rollup installation issue. Although this occurs infrequently, a registry or file system corruption issue requires you to rebuild the server. In this scenario, you must reinstall the operating system, perform a new Microsoft Exchange installation together by using the /recoverserver option, and then install the appropriate update rollup.

Case 5: False Positives

Although Windows Installer verbose logging may help you to troubleshoot an installation error that you experience, some error messages that are logged do not indicate that a problem exists with the installation.

The following error is commonly logged by Windows Installer verbose logging. However, this error does not indicate that a problem exists in the update rollup installation. Instead, this error is generated only because verbose logging is enabled.

SI (c) (E8:E4) [13:22:15:847]: Note: 1: 2262 2: Error 3: -2147287038

DEBUG: Error 2826: Control BottomLine on dialog ErrorDlg extends beyond the boundaries of the dialog to the right by 5 pixels

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ErrorDlg, BottomLine, to the right

Common error condition strings that are generated by the verbose logging feature are another kind of false positive errors that may appear in an MSI log file. These error conditions appear near the end of the log file in the Property section. For example, the following entries may appear in the MSI log file.

Property(C): msgRequiresProc = The version of this file is not compatible with the version of Exchange Server 2007 that you're running. Check your computer to see whether you need an x64 (64-bit) or x86 (32-bit) version of this file.

Property(C): msgINTERIMUPDATEDETECTED = Unable to install because a previous Interim Update for Exchange Server 2007 has been installed. Please use Add/Remove Programs to uninstall the Interim Update before running this setup again.

Property(C): msgInterimIncorrectRollup = Installation cannot continue. The [Wizard] has determined that this Interim Update is incompatible with the current Exchange Server 2007 configuration.

Property(C): msgUninstallTargetRollupBeforeInterim = Uninstall cannot continue. The [Wizard] has determined that an Interim Update has been installed. This Update Rollup cannot be uninstalled until the Interim Update has been uninstalled.

Property(C): msgOlderInstallOnNewerRollupIncorrectRollup = Installation cannot continue. The [Wizard] has determined that this Update Rollup has been superseded by the currently installed Update Rollup. Installation of this Update Rollup is unnecessary.

These error conditions represent properties that are exposed in the .msp packages and that can be used by the Windows Installer engine, Msiexec.exe. These errors do not indicate installation issues. We recommend that you focus on Return value 3 strings in the log files to troubleshoot an installation issue that you experience. For more help to troubleshoot an installation issue, contact Microsoft Customer Support Services (CSS).