Re: [WiX-users] Patching fails with 1627
I opened an incident with MSFT, here's what they said (after a very round-about conversation): The documentation on it is correct - it needs to be at least one more than the highest number in the DiskID column of the Media table. This field can be null only if you are using version 2.0 of Patchwiz.dll and if the MinimumRequiredMsiVersion in the Properties table (Patchwiz.dll) http://msdn2.microsoft.com/en-us/library/aa370890.aspx is set to 200. The nullable field was only allowed with older versions of Patchwiz.dll. I was positive the spirit of the msdn doc was saying it would work with PatchWiz 2.0 or greater, but apparently not. They said they'd improve the error message (long term) and write up a kb (short term). -jh From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, March 31, 2007 2:44 PM To: Huck, Jacob Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patching fails with 1627 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. Yes. That's interesting -- I'm specifying the number but based on the doc, I'm wondering whether patchwiz 4.0 needs it... -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multiple cultures and codepage error
So to be clear, it is only useful to pass in multiple cultures in at the same time when all of those cultures share the same codepage? Is there a common codepage that works with most languages and Windows Installer? Such as utf-8 (65001)? I seem to recall reading that while it may work, string may not work correctly (explicitly here: http://www.nabble.com/Multi-language-msi-tf2057536.html#a5669170, but then somewhat contractdicted here: http://blogs.msdn.com/heaths/archive/2005/10/05/477577.aspx). And more importantly, if I switch to using a common codepage like utf-8, will my localization strategy (based on including additional transform streams, http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm) work? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, March 31, 2007 3:48 PM To: Huck, Jacob Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] multiple cultures and codepage error Huck, Jacob wrote: When I go to light an msi using the above wixlib and numerous other wixlibs that are not localized, I find that when I pass in -cultures:en-us the msi compiles without any issues, but as soon as I pass in -cultures:ja;en-us, I get the following error: light.exe : error LGHT0101 : The codepage '1252' has been specified in multiple localization files. Please resolve the conflict. Any insight into this error? When I compiled it with just en-us, it clearly was using codepage 1252 in multiple loc files. My understanding was that the multiple entries passed into the -culture arg were to indicate an order of use ja strings first if found, and en-us strings if not. Your understanding is correct but runs into the limitations of MSI: You can't mix codepages in the MSI. The error isn't very good (please file a bug -- it should be more descriptive) but basically it's saying that once a codepage has been set, you can't set a different one. The end result would be two codepages, and MSI doesn't support that. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patching fails with 1627
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. Thanks -jh From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Huck, Jacob Sent: Sunday, February 25, 2007 11:03 PM To: Bob Arnson; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patching fails with 1627 Sounded promising, but unless I did it incorrectly, it didn't work--I'm still getting the same error. How were you able to determine it was a schema issue (and then specifically that column)? I'd love to think I could apply the same logic to my issue. Thanks -jh From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Sunday, February 25, 2007 1:38 PM To: Huck, Jacob Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patching fails with 1627 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: 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. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] multiple cultures and codepage error
We've broken our build into numerous WiX fragments which in turn compile into numerous wix libs. All wixlibs contain english strings at a minimum and a few (namely the Dialog wixlibs) contain muliple languages under different cultures and codepages. For example, our common_dialogs.wixlib might contain the following One .wxl file contains: WixLocalization Culture=ja Codepage=932 xmlns=http://schemas.microsoft.com/wix/2003/11/localization http://schemas.microsoft.com/wix/2003/11/localization ... Another WixLocalization Culture=en-us Codepage=1252 xmlns=http://schemas.microsoft.com/wix/2003/11/localization http://schemas.microsoft.com/wix/2003/11/localization ... and so on. All are passed into lit.exe at the same time, which compiles with an issue. When I go to light an msi using the above wixlib and numerous other wixlibs that are not localized, I find that when I pass in -cultures:en-us the msi compiles without any issues, but as soon as I pass in -cultures:ja;en-us, I get the following error: light.exe : error LGHT0101 : The codepage '1252' has been specified in multiple localization files. Please resolve the conflict. Any insight into this error? When I compiled it with just en-us, it clearly was using codepage 1252 in multiple loc files. My understanding was that the multiple entries passed into the -culture arg were to indicate an order of use ja strings first if found, and en-us strings if not. Thanks -jh - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patching fails with 1627
Sounded promising, but unless I did it incorrectly, it didn't work--I'm still getting the same error. How were you able to determine it was a schema issue (and then specifically that column)? I'd love to think I could apply the same logic to my issue. Thanks -jh From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Sunday, February 25, 2007 1:38 PM To: Huck, Jacob Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patching fails with 1627 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: 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. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Patching fails with 1627
I'm currently building two varieties of my install, release and debug, using WiX 3.0. Right now I'm able to successfully create an MSP using msimsp 4.0 for the release msi's only; when I try to generate a debug MSP, I get the following error: 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: Any suggestions on how I can determine what is causing the problem? The only differences between the release MSI and debug MSI should be additional files per component (and additional internal cab files). I've tried about every combination of WiX entries/different pcp values but always receive this error. Thanks -jh - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
