Community Forums
Results 1 to 4 of 4

Thread: 1636 Error - This patch package could not be opened

  1. #1
    Join Date
    Mar 2007

    1636 Error - This patch package could not be opened

    Hi there

    We're having a problem with our latest patch build, and I thought I would see if anyone had encountered similar problems, or had some knowledge of the issues we are seeing.

    We have been updating our product using Minor upgrades as service packs and small updates as hotfixes. The minor upgrades are essentially a rollup of the small updates. We have recently released the 3rd minor update for our product. Then we released the first small update to this minor upgrade. Everything was well as it had been in the past. Unfortunately we are now testing the second small update and we are getting an error. The error occurs when applying the update on the client machine. We get a dialog box which tells us that "this patch package could not be opened".

    The relevant section of log is as follows:

    MSI (c) (FC:64) [15:23:13:759]: Note: 1: 2205 2: 3: Patch
    MSI (c) (FC:64) [15:23:13:759]: Note: 1: 2228 2: 3: Patch 4: CREATE TABLE `Patch` ( `File_` CHAR(72) NOT NULL, `Sequence` INTEGER NOT NULL, `PatchSize` LONG NOT NULL, `Attributes` INTEGER NOT NULL, `Header` OBJECT, `StreamRef_` CHAR(72) PRIMARY KEY `File_`, `Sequence` )
    MSI (c) (FC:64) [15:23:13:759]: Note: 1: 2262 2: Patch 3: -2147287038
    MSI (c) (FC:64) [15:23:14:212]: Note: 1: 2262 2: PatchPackage 3: -2147287038
    MSI (c) (FC:64) [15:23:14:212]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
    MSI (c) (FC:64) [15:23:14:212]: TRANSFORM: Applying regular transform to database.
    MSI (c) (FC:64) [15:23:14:275]: Note: 1: 2205 2: 3: MsiPatchOldAssemblyName 4:
    MSI (c) (FC:64) [15:23:14:275]: Note: 1: 2253 2: 3: MsiPatchOldAssemblyName
    MSI (c) (FC:64) [15:23:14:290]: Note: 1: 2729
    DEBUG: Error 2253: Database: Transform: Cannot delete table that doesn't exist. Table: MsiPatchOldAssemblyName
    1: 2253 2: 3: MsiPatchOldAssemblyName
    This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package.
    MSI (c) (FC:64) [15:23:14:337]: Product: AvantGard-Quantum Client - Update '{44B8F4AF-6EFE-4D09-B2A6-A2C6D962173A}' could not be installed. Error code 1636. Additional information is available in the log file c:\temp\\AGQ-BDTV3-04Apr07-Post-4.3.3-Hotfix-SiteClient.msp-install.log.

    MSI (c) (FC:64) [15:23:14:368]: Note: 1: 1708
    MSI (c) (FC:64) [15:23:14:368]: Note: 1: 2729
    MSI (c) (FC:64) [15:23:14:400]: Note: 1: 2729
    MSI (c) (FC:64) [15:23:14:400]: Product: AvantGard-Quantum Client -- Installation failed.

    MSI (c) (FC:64) [15:23:14:478]: Attempting to delete file c:\temp\517508.msp
    MSI (c) (FC:64) [15:23:14:509]: MainEngineThread is returning 1636
    === Verbose logging stopped: 5/04/2007 15:23:14 ===

    One point of interest is that we are updating an Administratively installed product if that helps.

    Any insight would be greatly appreciated!

    Thanks, Don.

  2. #2
    Join Date
    Apr 2007


    I just saw the same issue. Did you ever get this resolved??
    Last edited by Alexster; 04-27-2007 at 05:00 PM.

  3. #3
    Join Date
    Apr 2007
    Exact same problem here.

  4. #4
    Join Date
    Apr 2007

    One Solution I Found

    I found out that the two uncompressed images for the previous (error) product image and the new (fixed) product image hold the key.

    In both images are the uncompressed raw product files and MSI.

    I simply replaced the two MSI files with their COMPRESSED counterparts and ran the same msimsp.exe command again and then used msiexec.exe /p to apply the patch and it worked!!!

    However, using the Patch Design View of InstallShield to build the patch after the MSI files have been replaced with their compressed versions does not build successfully.
    It does build successfully with msimsp.exe and the resulting MSP files patches successfully.

    According to Windows Installer documentation, I believe the MSI files are supposed to be uncompressed. However, this does not seem to be the case and the compressed MSIs along with it's binary files seems to be the way to go!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts