Don't patch the patch! Always target: a) only RTM b) RTM + another (non-patched) full install built after RTM c) same as b plus you can add all full install MSI targets built after RTM and preceding your patch build)
I don't know why 'they' (i.e. secretive installer people who reveal pieces of a puzzle slowly and unwillingly, in a blog post or two, now and then, maybe never...) have never explained it well enough for everybody to understand, but the above works. -----Original Message----- From: Shawn Dwyer [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2008 1:52 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patching fails with 1627 Hi, I'm running into what seems to be a common error on the mailing list, but none of the solutions so far have worked for me. I have 3 basic test patches: RTM: installs file1 Patch1: targets rtm, updates launch condition of RTM Patch2: targets Patch1, updates file1 and installs directory2\file2 Patch3: targets Patch 2, updates file1 and installs directory3\file3 (doesn't touch file2) Using Wix 2.0.5325.0 and MsiMsp 4.0 I am able to successfully create Patch1.msp and Patch2.msp, but running MisMsp on Patch3.pcp gives the error: INFO: Phase V: Entering Generate MSP. INFO: Generating Patch Metadata. ERROR: Internal PatchWiz Error occurred. ERROR: The Last Error Received is: 1627 ERROR: The Last Error Received is: 1: 2213 2: I've ensured the MediaDiskId field is not blank (RTM Media Id=1, Patch1 Family DiskId=10, Patch2 Family DiskId=20, Patch3 Family DiskId=30) (all patches are in the same family) I've ensured the SequenceStart does not overlap (P1=1000, P2=2000, P3=3000) I've tried pointing MsiFileToUseToCreatePatchTables to the RTM.msi, and tried each of the other patch msi's just in case. Has anyone else run into this error that turned out to be a different problem/solution than below? Thanks, Shawn > Huck, Jacob wrote: > In case someone was looking at a similar issue: basically we > have multiple cab files in a debug install (to contain the pdbs, which > exceed 2GB in many cases). When generating the patch, I was leaving > MediaDiskId blank, but in needed to be set to a value greater than the > highest Media Id in the msi's. > >> Arnson, Bob wrote: >> I've gotten that before when I was use a File/Sequence column of I4; by >> default, Patchwiz supplies a Patch/Sequence column of I2 so you need to >> use the MsiFileToUseToCreatePatchTables option to specify an I4 column. >> >>> Huck, Jacob wrote: >>> ERROR: Failed to execute a view >>> ERROR: The Last Error Received is: 1627 >>> ERROR: The Last Error Received is: 1: 2259 2: >>> c:\temp\~pcw_tmp.tmp\3000.MSI 3: 4: ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
