Thanks for the feedback and the helpful links. I've read all of Heath's blogs a few times, as well as all the other blogs and any Wix or MSI documentation I could find. I hadn't come across the white paper yet though so I'll be reading through that soon. Thanks for the link.
Unfortunately as Tony mentions the information, if even out there, is scattered and seemingly incomplete. Most examples show you how to make a simple first patch that updates one file, but there don't seem to be any examples of more complex patching (with custom actions for example) or examples of creating subsequent patches and the different ways of doing it. Tony - In essence I was doing what you suggested. I had full installers that I was targeting for each patch: RTM - Patch1 TargetImage RTMPostBuild1 (removed launch condition) - Patch1 UpgradeImage and Patch2 TargetImage RTMPostBuild2 (updated file1 and adds directory2/file2) - Patch2 UpgradeImage and Patch3 TargetImage RTMPostBuild3 (updated file1 and adds directory3/file3) - Patch3 UpgradeImage After getting your feedback I decided to go back and just have each of the patches target the RTM just for fun. Patch2 built as expected but Patch3 still didn't build! Comparing Patch2.wxs and Patch3.wxs I changed one property at at time, until the only thing left that was different was the PatchCreation Id and the Id of the TargetImage element. I reread the MsiIntel.SDK\Patching\Readme.doc and sure enough this field is limited to 13 characters, and I had 15. I picked a shorter name and everything builds and installs/uninstalls now as expected. So for anyone else running into this issue, apparently one of the causes could be too many characters in the Id field of the TargetImage element, which has a max length of 13 characters. The same for the UpgradeImage element. For future reference is there a good way to debug PatchWiz errors? Or at least a list of the error codes and what the mean? Thanks again, Shawn On Mon, Aug 18, 2008 at 10:22 PM, John Nannenga <[EMAIL PROTECTED] > wrote: > If folks are looking for some good information regarding patching, you > might try the following: > > The Windows Installer 3.0 Patching white paper (an excellent resource): > > http://www.microsoft.com/downloads/details.aspx?FamilyID=ad7ac91e-2493-4549-ae6f-bf5e007c12a3&DisplayLang=en > > Heath Stewart's blog, perhaps starting here: > http://blogs.msdn.com/heaths/archive/2005/09/12/464047.aspx > (but he has lots more advice therein regarding patches) Example: > http://blogs.msdn.com/heaths/archive/2006/06/14/cumulative-service-packs-with-minorupdatetargetrtm.aspx > > > > ________________________________________ > From: [EMAIL PROTECTED] [ > [EMAIL PROTECTED] On Behalf Of Tony Juricic > [EMAIL PROTECTED] > Sent: Monday, August 18, 2008 8:19 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Patching fails with 1627 > > 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 > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
