[WiX-users] [WIX-users] Patch in Wix 3.6 is empty. warning PYRO1079: The cabinet '***.cab' does not contain any files
Hi all, Hope you can help me with this one. I have been google-ing but found no solution. What I have done is upgraded from Wix v3 to Wix v3.6 (because of VS2010 support). I have managed to get everything working just fine except for when building a patch. I get this warning from pyro.exe pyro.exe -nologo ..\Patch\obj\Deploy\Patch_7.17.8.3550.WixMsp -out ..\output\Deploy\Patch_7.17.8.3550.msp -t RTM ..\Patch\obj\Deploy\Diff.wixmst C:\Project\***\Setup\Patch\patch.wxs(10): warning PYRO1079: The cabinet 'RTM.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. So, the patch is empty even though I have modified a file which thereby should be included in the patch (and which worked before upgrading wix). Now the CAB-file is always empty in the patch for some reason. The best I could google was this link: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Applying-a-patch-msp-doesn-t-increase-the-product-version-td7173238.html He has almost the exact same problem and he says in hist first post that he got it working when going to v3.5, Is this bug confirmed in 3.6 or is there something other that is wrong? In Diff.wixmst I can see that the file I have altered is mentioned in there but I have no idea if that means it is considered modified or not. I can see some field tags there that have a modified=yes attribute, but the filed tags associated with the altered file do not seem to have that attribute. Like the guy in the link above I have tried changing the size and version of the file but to no avail in my case. In my patch.wxs it looks like this: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Patch AllowRemoval=no Manufacturer=*** DisplayName=Upgrade for *** - $(var.Version) Description=Upgrades *** components Classification=Update Media Id=5000 Cabinet=RTM.cab PatchBaseline Id=RTM/ /Media /Patch /Wix I read somewhere that the most common reason for this error is that the PatchBaseline is not matched up correctly with the first argument to pyro after the -t flag. But it seems in my case they are both called RTM... So, patch gets built without errors but does not include the files for the patch after upgrade to WIX v3.6. Anyone, any ideas? -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RegistrySearch fails, returns C: or Empty
Hello all, I am having some problems with an installation using Wix v3 During install of application I run Property Id=SETUPFOLDER RegistrySearch Id=SETUPFOLDER Root=HKCU Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder Type=raw / /Property SETUPFOLDER is later used for setting the target of a shortcut in the start menu. This works when I install or reinstall by running my bootstrapper setup.exe which then starts the MSI package. But when applying patches for instance or bypassig the setup.exe and running the MSI directly, then the registry search returns C: or is just empty. When I check that path in registry using regedit then I do find the correct value there but for some reason the RegistrySearch fails and I can't figure out why. Notable is that this error does not exist in Windows XP, but now as I have been porting it to Windows 7 I noticed this problem. So basically the code should work, but it doesn't do that in Win7 (only works if I go through the bootstrapper exe) Any suggestions? Thanks! Leo -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RegistrySearch fails, returns C: or Empty
Hi, thanks for fast reply! In the MSI log I can see that it actually finds the correct SETUPFOLDER path from registry, but then there are some rows saying: Ignoring disallowed property SETUPFOLDER But I can see that it finds the correct path because further down in the log I have something like AppSearch: Property: SETUPFOLDER, Signature: SETUPFOLDER MSI (c) (F0:80) [17:32:47:087]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c) (F0:80) [17:32:47:087]: PROPERTY CHANGE: Adding SETUPFOLDER property. Its value is '\\rrdb\xxx\xxx\Setup'. And then an .ini file is written and it now the log (almost at the very end) says: MSI (s) (3C:44) [17:34:07:697]: Executing op: IniWriteRemoveValue(Section=INSTANCE,Key=SetupFolder,,Mode=0) WriteIniValues: File: xxx.ini, Section: INSTANCE, Key: SetupFolder, Value: Note that the value: is empty. And then at the very very end of the log file it states the properties: Property(C): SETUPFOLDER = \\rrdb\xxx\xxx\Setup So again it has the correct value but it does not want to use it when specifying the target of the shortcut. Hope this gives you some idea... Thankful for help! 2011/10/25 Rob Mensching r...@robmensching.com What does the verbose log file show? On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi universalserial...@gmail.com wrote: Hello all, I am having some problems with an installation using Wix v3 During install of application I run Property Id=SETUPFOLDER RegistrySearch Id=SETUPFOLDER Root=HKCU Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder Type=raw / /Property SETUPFOLDER is later used for setting the target of a shortcut in the start menu. This works when I install or reinstall by running my bootstrapper setup.exe which then starts the MSI package. But when applying patches for instance or bypassig the setup.exe and running the MSI directly, then the registry search returns C: or is just empty. When I check that path in registry using regedit then I do find the correct value there but for some reason the RegistrySearch fails and I can't figure out why. Notable is that this error does not exist in Windows XP, but now as I have been porting it to Windows 7 I noticed this problem. So basically the code should work, but it doesn't do that in Win7 (only works if I go through the bootstrapper exe) Any suggestions? Thanks! Leo -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RegistrySearch fails, returns C: or Empty
Hi again, I believe I solved it (haven't done enough testing yet though!)! It seems that the property had to be set as Secure=yes since otherwise UAC will not allow it. Will get back to you if I find that it is not solved. But I just tried an installation that earlier did not work and now it did! Thanks for all help so far anyway! Leo 2011/10/25 Leo Koivuniemi universalserial...@gmail.com Hi, thanks for fast reply! In the MSI log I can see that it actually finds the correct SETUPFOLDER path from registry, but then there are some rows saying: Ignoring disallowed property SETUPFOLDER But I can see that it finds the correct path because further down in the log I have something like AppSearch: Property: SETUPFOLDER, Signature: SETUPFOLDER MSI (c) (F0:80) [17:32:47:087]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c) (F0:80) [17:32:47:087]: PROPERTY CHANGE: Adding SETUPFOLDER property. Its value is '\\rrdb\xxx\xxx\Setup'. And then an .ini file is written and it now the log (almost at the very end) says: MSI (s) (3C:44) [17:34:07:697]: Executing op: IniWriteRemoveValue(Section=INSTANCE,Key=SetupFolder,,Mode=0) WriteIniValues: File: xxx.ini, Section: INSTANCE, Key: SetupFolder, Value: Note that the value: is empty. And then at the very very end of the log file it states the properties: Property(C): SETUPFOLDER = \\rrdb\xxx\xxx\Setup So again it has the correct value but it does not want to use it when specifying the target of the shortcut. Hope this gives you some idea... Thankful for help! 2011/10/25 Rob Mensching r...@robmensching.com What does the verbose log file show? On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi universalserial...@gmail.com wrote: Hello all, I am having some problems with an installation using Wix v3 During install of application I run Property Id=SETUPFOLDER RegistrySearch Id=SETUPFOLDER Root=HKCU Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder Type=raw / /Property SETUPFOLDER is later used for setting the target of a shortcut in the start menu. This works when I install or reinstall by running my bootstrapper setup.exe which then starts the MSI package. But when applying patches for instance or bypassig the setup.exe and running the MSI directly, then the registry search returns C: or is just empty. When I check that path in registry using regedit then I do find the correct value there but for some reason the RegistrySearch fails and I can't figure out why. Notable is that this error does not exist in Windows XP, but now as I have been porting it to Windows 7 I noticed this problem. So basically the code should work, but it doesn't do that in Win7 (only works if I go through the bootstrapper exe) Any suggestions? Thanks! Leo -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error TRCH0228 : The codepages of the outputs donotmatch
Hi, Thanks for your answer! I have been trying long and hard, but this is what i get in the log: - Project C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Deploy.proj (Patch target(s)): Target Patch: Touching xxxPatch\xxxPatch.wixproj. Building patch cscript WiLangId.vbs C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\output\Deploy\xxxSetup.msi Codepage 0 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Package language = 1033, ProductLanguage = 1033, Database codepage = 0 torch.exe -nologo -v -p -xi Latestwixpdb\xxxSetup.wixpdb output\Deploy\xxxSetup.wixpdb -out xxxPatch\obj\Deploy\Diff.Wixmst C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Latestwixpdb\xxxSetup.wixpdb : error TRCH0228: The code pages of the outputs do not match. One output's code page is '0' while the other is '1252'. C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\output\Deploy\xxxSetup.wixpdb : error TRCH0229: The location of the mismatched code page related to the previous warning. C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Latestwixpdb\xxxSetup.wixpdb : error TRCH0279: The table definition of 'WixVariable' in the target database does not match the table definition in the updated database. A transform requires that the target database schema match the updated database schema. C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Deploy.proj(30,5): error MSB3073: The command torch.exe -nologo -v -p -xi Latestwixpdb\xxxSetup.wixpdb output\Deploy\xxxSetup.wixpdb -out xxxPatch\obj\Deploy\Diff.Wixmst exited with code 279. Done building target Patch in project Deploy.proj -- FAILED. - It seems to be exactly the same as before I ran the script, how can that be? Any suggestions? Thanks! Leo 2011/10/11 David Watson dwat...@sdl.com Hi, To support building patches against our old releases that were built with Wix 3.0. and now our release branches are being built on machines with Wix 3.5 installed. So we have RTM msis from wix 3.0 these have codepage 0. We now make an updated MSIs with wix 3.5 which now forces a codepage onto MSIs. There is a step in our patch creation msbuild project that updates the codepage of the new version of the MSI back to 0 from 1252 (or whatever it is by default). That step is using the microsoft vbscript utility WiLangId.vbs available in the windows installer SDK. How all this relates to your workflow I don't know specifically you will probably need to call the vbs somehow (post build step?) so you can build patches against an old wix 3.0 MSI. Note : there is a bug about this but it will not be addressed until Wix 4.0 http://sourceforge.net/tracker/?func=detailaid=3134424group_id=105970atid= 642714 Dave -Original Message- From: Leo Koivuniemi [mailto:universalserial...@gmail.com] Sent: 11 October 2011 14:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error TRCH0228 : The codepages of the outputs donotmatch Oh thanks, will try that, if I find out how (very new to this, really). So I put that in deploy.proj right? And what do I have to do in my C++ code to run it? Really appreciate any help, thanks! Rgds Leo 2011/10/11 David Watson dwat...@sdl.com We had this and had to run a step in our patch building scripts to set the codepage to 1251. Target Name=FixCodepage Message Text=Fixing codepage / Exec Command='cscript WiLangId.vbs $(UpdateMSIDir)\$(MSIName) Codepage 0' / /Target See http://msdn.microsoft.com/en-us/library/windows/desktop/aa369791(v=vs.85).asp x For the vbs file. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 11 October 2011 14:01 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error TRCH0228 : The codepages of the outputs donot match Trying to create a patch across WiX versions is not supported. Patching is very fragile and there are too many small changes in the tools that can break patching. That said, you may be able to get this to work by explicitly setting the code page on your Products. It's possible the default in WiX changed (due to some bug) and explicitly setting it might be able to get around it. On Tue, Oct 11, 2011 at 5:54 AM, Leo Koivuniemi universalserial...@gmail.com wrote: I am totally new to wix and have now a project in front of me using it. Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0 to 3.5 of the wix package. I have solved some errors resulting from that, but now I am stuck. When a patch is compiled I get the following error: error TRCH0228 : The codepages of the outputs do not match. One output's codepage is '0' while the other is '1251'. That is strange, because nothing else has changed in the project except from the wix version (still trying to make it run under VS2005
Re: [WiX-users] error TRCH0228 : The codepages of the outputs do not match
I am totally new to wix and have now a project in front of me using it. Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0 to 3.5 of the wix package. I have solved some errors resulting from that, but now I am stuck. When a patch is compiled I get the following error: error TRCH0228 : The codepages of the outputs do not match. One output's codepage is '0' while the other is '1251'. That is strange, because nothing else has changed in the project except from the wix version (still trying to make it run under VS2005 first). Googling I only really get one relevant hit, but the answers or comments don't tell me much. How do I deal with this easily? Anyone, please? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error TRCH0228 : The codepages of the outputs do not match
Thanks for your reply! Yes I read that but there are just too many Products in the package so in the time frame it is not feasible. Perhaps trying to upgrade to 3.6 beta may solve it? Will try. 2011/10/11 Rob Mensching r...@robmensching.com Trying to create a patch across WiX versions is not supported. Patching is very fragile and there are too many small changes in the tools that can break patching. That said, you may be able to get this to work by explicitly setting the code page on your Products. It's possible the default in WiX changed (due to some bug) and explicitly setting it might be able to get around it. On Tue, Oct 11, 2011 at 5:54 AM, Leo Koivuniemi universalserial...@gmail.com wrote: I am totally new to wix and have now a project in front of me using it. Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0 to 3.5 of the wix package. I have solved some errors resulting from that, but now I am stuck. When a patch is compiled I get the following error: error TRCH0228 : The codepages of the outputs do not match. One output's codepage is '0' while the other is '1251'. That is strange, because nothing else has changed in the project except from the wix version (still trying to make it run under VS2005 first). Googling I only really get one relevant hit, but the answers or comments don't tell me much. How do I deal with this easily? Anyone, please? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error TRCH0228 : The codepages of the outputs donot match
Oh thanks, will try that, if I find out how (very new to this, really). So I put that in deploy.proj right? And what do I have to do in my C++ code to run it? Really appreciate any help, thanks! Rgds Leo 2011/10/11 David Watson dwat...@sdl.com We had this and had to run a step in our patch building scripts to set the codepage to 1251. Target Name=FixCodepage Message Text=Fixing codepage / Exec Command='cscript WiLangId.vbs $(UpdateMSIDir)\$(MSIName) Codepage 0' / /Target See http://msdn.microsoft.com/en-us/library/windows/desktop/aa369791(v=vs.85).asp x For the vbs file. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 11 October 2011 14:01 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error TRCH0228 : The codepages of the outputs donot match Trying to create a patch across WiX versions is not supported. Patching is very fragile and there are too many small changes in the tools that can break patching. That said, you may be able to get this to work by explicitly setting the code page on your Products. It's possible the default in WiX changed (due to some bug) and explicitly setting it might be able to get around it. On Tue, Oct 11, 2011 at 5:54 AM, Leo Koivuniemi universalserial...@gmail.com wrote: I am totally new to wix and have now a project in front of me using it. Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0 to 3.5 of the wix package. I have solved some errors resulting from that, but now I am stuck. When a patch is compiled I get the following error: error TRCH0228 : The codepages of the outputs do not match. One output's codepage is '0' while the other is '1251'. That is strange, because nothing else has changed in the project except from the wix version (still trying to make it run under VS2005 first). Googling I only really get one relevant hit, but the answers or comments don't tell me much. How do I deal with this easily? Anyone, please? - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC - - All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
