[WiX-users] WiX Chain ARP entries
I have a WiX bundle for different components of our software. Every component has its own msi and installs perfectly. But I want to install the bundle so that for every msi I get an entry in ARP, but I can only get the bundle to appear. How can I force the burn chain to show every component? Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix Upgrades when only revision number changes
I have a setup which works great but has one bug. If only the revision number changes, the setup tells me that this product version is already installed. e.g. I have one msi with version 1.2.3.4 installed and I want to upgrade to 1.2.3.5. This doesn't work for me. I couldn't find any documentation how to solve this. Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Chain ARP entries
Take a look at the MsiPackage/@Visible attribute http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm. Neil I have a WiX bundle for different components of our software. Every component has its own msi and installs perfectly. But I want to install the bundle so that for every msi I get an entry in ARP, but I can only get the bundle to appear. How can I force the burn chain to show every component? Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Upgrades when only revision number changes
This is a limitation of Windows Installer the only way to get around it is to allow same version upgrades but this is not without its own problems primarily that 1.2.3.4 will also downgrade 1.2.3.5 Neil I have a setup which works great but has one bug. If only the revision number changes, the setup tells me that this product version is already installed. e.g. I have one msi with version 1.2.3.4 installed and I want to upgrade to 1.2.3.5. This doesn't work for me. I couldn't find any documentation how to solve this. Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with license agreement text
I have it formatted I think, this is a line from the agreement: Where the Licence has been purchased through a distributor including [DISTRIBUTORNAME] Property: Property Id=DISTRIBUTORNAME Secure=yes Value=Company Ltd/ But it is still only showing [DISTRIBUTORNAME] in the agreement on the dialog. Kind Regards, Natalie Carr -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, December 14, 2012 8:40 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with license agreement text It will work if that column is marked Formatted in the MSI SDK. On Fri, Dec 14, 2012 at 2:37 AM, Natalie Carr natalie.c...@measuresoft.comwrote: Hi I am inserting the license agreement using Text tags with the rft formatting. It is showing up perfectly on the license agreement dialog. However I need to be able to pull a property from the setup and use it in the agreement, I am doing do but the agreement just shows with [PROPERTYNAME] instead of the value. Can this be done? Kind Regards, Natalie Carr -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Chain ARP entries
On 2012-12-17 09:58, Neil Sleightholm wrote: Take a look at the MsiPackage/@Visible attribute http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm. This solved my problem. Thank you very much. I read this page many times and overlooked it every time. Marc -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixMbaPrereqPackageId variable not visible from Fragment element
I'm new to Burn, and was trying my first test dummy setup with GUI that I found here: http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ Solution contains three projects: TestBA.csproj, DummyInstaller.wixproj, and BootstrapperSetup.wixproj. I removed all the MVVM stuff from TestBA project and left there only one MessageBox. TestBA and DummyInstaller projects build just fine, but BootstrapperSetup project could not build giving me this: -- Build started: Project: BootstrapperSetup, Configuration: Debug x86 -- ... E:\delivery\Dev\wix36_public\src\ext\BalExtension\wixlib\Mba.wxs(62,0): error LGHT0197: The Windows Installer XML variable !(wix.WixMbaPrereqPackageId) is unknown. Please ensure the variable is declared on the command line for light.exe, via a WixVariable element, or inline using the syntax !(wix.WixMbaPrereqPackageId=some value which doesn't contain parenthesis). E:\delivery\Dev\wix36_public\src\ext\BalExtension\wixlib\Mba.wxs(62,0): error LGHT0197: The Windows Installer XML variable !(wix.WixMbaPrereqLicenseUrl) is unknown. Please ensure the variable is declared on the command line for light.exe, via a WixVariable element, or inline using the syntax !(wix.WixMbaPrereqLicenseUrl=some value which doesn't contain parenthesis). Done building project BootstrapperSetup.wixproj -- FAILED. BUT, when I move two WixVariable elements from Fragment to Bundle element just above it in Bundle.wxs file then everything builds just fine. What is going on here? WiX version given in Visual Studio about box is Windows Installer XML Toolset 3.6.3303.0. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Network path error
You could try setting Vital=no on the File element. I'm not sure if that applies to removal as well as installation. -Original Message- From: Nirmalraj Durai [mailto:nirmal.du...@gmail.com] Sent: 17 December 2012 06:05 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Network path error Hi all, While installation the installer put a file in network location then during uninstallation i need to remove the file from the network path. But in my case if the network is unreachable the installer through an error message. Here my question is During uninstallation i want to supress the error message if the network path is unreachable. -- Regards, Nirmalraj Durai, - - LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ 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. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Bootstrapper Bundle creating uninstall shortcut in program files
Hey all, Even am in the same boat. How to create a uninstall shortcut in startmenu- program files to uninstall application installed with WiX bootstrapper. I am not getting the product code of bootstrapper, which I would have used for un-installation. looking for same un-install shortcut which is there in Add/Remove program files. Does anybody know, how to get this ? - Akshay -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Bootstrapper-Bundle-creating-uninstall-shortcut-in-program-files-tp7580364p7582405.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix 3.6 and Burn: double click versus command line invocation?
Hi all, I'm putting together an installer to help users get Mercurial running on IIS and I'm using burn for it. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=HgOnIISAssistant Version=1.0.0.0 Manufacturer=HgOnIISAssistant UpgradeCode=EFCC2B74-1D6E-4DE5-9679-5F760D592ED2 BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense/ Chain PackageGroupRef Id=NetFx40Web/ MsiPackage Id=Python26 Name=Python26 SourceFile=..\installers\python-2.6.6.msi DownloadUrl= http://www.python.org/ftp/python/2.6.6/python-2.6.6.msi/ /Chain /Bundle /Wix I'm building in Visual Studio 2010 with Votive, I've encountered an interesting behaviour where if I double click on the built msi, I am advised that This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. However, if I run from the command line - it works fine. I've google'd for similar problems; but I can't see any reference to this behaviour elsewhere - does anyone have any ideas on what could be causing this or on a fix? For completeness I was on 3.5, and upgraded to 3.6. Martin -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Upgrades when only revision number changes
I thought MSI only looked at first three digits, ie change 1.2.3.4 to 1.2.4.4 to affect changes. tenholde -Original Message- From: Marc Fauser [mailto:marc.fau...@gmail.com] Sent: Monday, December 17, 2012 2:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Upgrades when only revision number changes I have a setup which works great but has one bug. If only the revision number changes, the setup tells me that this product version is already installed. e.g. I have one msi with version 1.2.3.4 installed and I want to upgrade to 1.2.3.5. This doesn't work for me. I couldn't find any documentation how to solve this. Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Upgrades when only revision number changes
Hi, MSI is able to store version number information upto four places. In upgrade process it consider version number upto three places only. fourth part will be ignored by its upgrade machinery. Please check /Note that Windows Installer uses only the first three fields of the product version/ note at http://msdn.microsoft.com/en-us/library/windows/desktop/aa370859%28v=vs.85%29.aspx and /Windows Installer only uses the first 3 parts of the version in upgrade scenarios/ at http://wix.sourceforge.net/manual-wix3/major_upgrade.htm Regards, Sanjay Rao On 12/17/2012 5:39 PM, Ed Tenholder wrote: I thought MSI only looked at first three digits, ie change 1.2.3.4 to 1.2.4.4 to affect changes. tenholde -Original Message- From: Marc Fauser [mailto:marc.fau...@gmail.com] Sent: Monday, December 17, 2012 2:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Upgrades when only revision number changes I have a setup which works great but has one bug. If only the revision number changes, the setup tells me that this product version is already installed. e.g. I have one msi with version 1.2.3.4 installed and I want to upgrade to 1.2.3.5. This doesn't work for me. I couldn't find any documentation how to solve this. Best regards, Marc Fauser -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sanjay Rao Digital Media Group, Interra Systems s...@interrasystems.com http://www.interrasystems.com -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] odd behaviour in execution of a generated MSI
Hello, I have created a MSI with WiX (version 3.5.2519.0), this MSI put a CTG.ini to specific folders: C:\Program Files (x86)\IBM\CICS Universal Client C:\Program Files (x86)\IBM\IBM CICS Universal Client The same MSI is executed on 2 computer but: The first computer have this file in the correct folders The second computer don't have this file in folders. I have put this MSI on verbose mode (in attach) on this 2 computers but I don't understand why it's work in the first and not in the second computer. Do you know what is missed ? Thanks for your help. http://about.me/crebassa.gilles -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX book update
Several people from the WiX community lent a hand getting the update to the WiX book into shape. The end result covers more ground than the last version, including, of course, Burn. All in all, I'm very pleased with the end result! It's available for the Kindle on Amazon's site at: http://www.amazon.com/WiX-3-6-Developers-Installer-ebook/dp/B009YW82A0/ref=sr_1_10?ie=UTF8qid=1355752765sr=8-10keywords=wix And the print version should be out soon through Packt Publishers: http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-book-update-tp7582410.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with license agreement text
What he means is that you have to check the documentation to see if it accepts formatted text. If it doesn't it will display the text as is. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: December-17-12 5:26 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Problem with license agreement text I have it formatted I think, this is a line from the agreement: Where the Licence has been purchased through a distributor including [DISTRIBUTORNAME] Property: Property Id=DISTRIBUTORNAME Secure=yes Value=Company Ltd/ But it is still only showing [DISTRIBUTORNAME] in the agreement on the dialog. Kind Regards, Natalie Carr -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, December 14, 2012 8:40 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with license agreement text It will work if that column is marked Formatted in the MSI SDK. On Fri, Dec 14, 2012 at 2:37 AM, Natalie Carr natalie.c...@measuresoft.comwrote: Hi I am inserting the license agreement using Text tags with the rft formatting. It is showing up perfectly on the license agreement dialog. However I need to be able to pull a property from the setup and use it in the agreement, I am doing do but the agreement just shows with [PROPERTYNAME] instead of the value. Can this be done? Kind Regards, Natalie Carr -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with license agreement text
Oh silly me, I found it, unfortunately it does not support embedded properties..thanks Kind Regards, Natalie Carr -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, December 17, 2012 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with license agreement text What he means is that you have to check the documentation to see if it accepts formatted text. If it doesn't it will display the text as is. -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: December-17-12 5:26 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Problem with license agreement text I have it formatted I think, this is a line from the agreement: Where the Licence has been purchased through a distributor including [DISTRIBUTORNAME] Property: Property Id=DISTRIBUTORNAME Secure=yes Value=Company Ltd/ But it is still only showing [DISTRIBUTORNAME] in the agreement on the dialog. Kind Regards, Natalie Carr -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, December 14, 2012 8:40 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem with license agreement text It will work if that column is marked Formatted in the MSI SDK. On Fri, Dec 14, 2012 at 2:37 AM, Natalie Carr natalie.c...@measuresoft.comwrote: Hi I am inserting the license agreement using Text tags with the rft formatting. It is showing up perfectly on the license agreement dialog. However I need to be able to pull a property from the setup and use it in the agreement, I am doing do but the agreement just shows with [PROPERTYNAME] instead of the value. Can this be done? Kind Regards, Natalie Carr -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Example of extracting a file from binary table
Hi does anyone have a full example of extracting a file from the binary table and executing it in C++? I cannot seem get it working at all. Kind Regards, Natalie Carr -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How do to configure a Windows service to Restart the Service upon failure?
I am *not* able to get msiexec.exe to set the recovery option of my Windows service to Restart the Service. Wix 3.6 documentation suggests that I can use ServiceConfigFailureActions to accomplish this. Here is my ServiceInstall element: ServiceInstall Id=ServiceInstallID Name=LPDS Service DisplayName=LaserPro Document Service Description=Allows LaserPro Document Service to be used as a web service. Interactive=no ErrorControl=ignore Start=auto Type=ownProcess Vital=no ServiceConfig FailureActionsWhen=failedToStopOrReturnedError OnInstall=yes OnReinstall=yes OnUninstall=yes / ServiceConfigFailureActions OnInstall=yes OnReinstall=yes OnUninstall=yes ResetPeriod=86400 Command=c:\foo.bat Failure Action=runCommand Delay=1000/ Failure Action=restartService Delay=2000/ /ServiceConfigFailureActions /ServiceInstall I am using msiexec.exe version V 5.0.7601.17514 Error from installation log file: MSI (s) (A0:F8) [08:21:16:136]: Executing op: CacheSizeFlush(,) MSI (s) (A0:F8) [08:21:16:136]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2]) MSI (s) (A0:F8) [08:21:16:142]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:143]: Executing op: ServiceInstall(Name=LPDS Service,DisplayName=LaserPro Document Service,ImagePath=C:\LPDS\CFI\Service.exe,ServiceType=32,StartType=2,ErrorControl=32768,,Dependencies=[~],,,Password=**,Description=Allows LaserPro Document Service to be used as a web service.,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ActionStart(Name=MsiConfigureServices,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ServiceConfigure(,Name=LPDS Service,Event=5,ConfigType=4,Argument=1) MSI (s) (A0:F8) [08:21:16:771]: Changing configuration of service LPDS Service. MSI (s) (A0:F8) [08:21:16:781]: Changed configuration of service LPDS Service with ConfigType SERVICE_CONFIG_FAILURE_ACTIONS_FLAG MSI (s) (A0:F8) [08:21:16:781]: Done changing configuration of service LPDS Service MSI (s) (A0:F8) [08:21:16:781]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:781]: Executing op: ServiceConfigureFailureAction(,Name=LPDS Service,Event=1,,RebootMessage=[~],Command=[~],Actions=1,DelayActions=9000) MSI (s) (A0:F8) [08:21:16:781]: Changing configuration of failure action for service LPDS Service. MSI (s) (A0:F8) [08:21:16:782]: Warning: ResetPeriod is blank. Trying to change current configuration of failure action for service LPDS Service. Replacing with default argument INFINITE MSI (s) (A0:F8) [08:21:16:782]: Error: 5. Failed to change current configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Failed to change configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1939 MSI (c) (D8:DC) [08:21:16:785]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (A0:F8) [08:21:46:995]: Product: LaserPro Document Service -- Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. Here are the rows that WIX generates in the MsiServiceConfig and MsiSErviceConfigFailureActions tables: MsiServiceConfig NameEventConfigType Argument Component_ LPDS_Service.FA LPDS Service 7 4 1 LPDSService.exe MsiServiceConfigFailureActions table contents: MsiServiceConfigFailureActionsNameEvent ResetPeriod RebootMessage CommandActions DelayActions Component_ LPDS_Service LPDS Service 7 86400[~] c:\foo.bat1[~]3
Re: [WiX-users] How do to configure a Windows service to Restart the Service upon failure?
Does it work if, instead of using the ServiceConfigFailureActions and Failure elements, you use the util:ServiceConfig element? It has FirstFailureActionType, SecondFailureActionType and ThirdFailureActionType attributes that you can set to restart, runcommand or reboot. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-to-configure-a-Windows-service-to-Restart-the-Service-upon-failure-tp7582414p7582415.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do to configure a Windows service to Restart the Service upon failure?
Error 5 is access denied. Are you running the installation as administrator ? -Original Message- From: Marty Offe [mailto:marty.o...@harlandfs.com] Sent: 17 December 2012 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How do to configure a Windows service to Restart the Service upon failure? I am *not* able to get msiexec.exe to set the recovery option of my Windows service to Restart the Service. Wix 3.6 documentation suggests that I can use ServiceConfigFailureActions to accomplish this. Here is my ServiceInstall element: ServiceInstall Id=ServiceInstallID Name=LPDS Service DisplayName=LaserPro Document Service Description=Allows LaserPro Document Service to be used as a web service. Interactive=no ErrorControl=ignore Start=auto Type=ownProcess Vital=no ServiceConfig FailureActionsWhen=failedToStopOrReturnedError OnInstall=yes OnReinstall=yes OnUninstall=yes / ServiceConfigFailureActions OnInstall=yes OnReinstall=yes OnUninstall=yes ResetPeriod=86400 Command=c:\foo.bat Failure Action=runCommand Delay=1000/ Failure Action=restartService Delay=2000/ /ServiceConfigFailureActions /ServiceInstall I am using msiexec.exe version V 5.0.7601.17514 Error from installation log file: MSI (s) (A0:F8) [08:21:16:136]: Executing op: CacheSizeFlush(,) MSI (s) (A0:F8) [08:21:16:136]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2]) MSI (s) (A0:F8) [08:21:16:142]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:143]: Executing op: ServiceInstall(Name=LPDS Service,DisplayName=LaserPro Document Service,ImagePath=C:\LPDS\CFI\Service.exe,ServiceType=32,StartType=2,ErrorCon trol=32768,,Dependencies=[~],,,Password=**,Description=Allows LaserPro Document Service to be used as a web service.,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ActionStart(Name=MsiConfigureServices,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ServiceConfigure(,Name=LPDS Service,Event=5,ConfigType=4,Argument=1) MSI (s) (A0:F8) [08:21:16:771]: Changing configuration of service LPDS Service. MSI (s) (A0:F8) [08:21:16:781]: Changed configuration of service LPDS Service with ConfigType SERVICE_CONFIG_FAILURE_ACTIONS_FLAG MSI (s) (A0:F8) [08:21:16:781]: Done changing configuration of service LPDS Service MSI (s) (A0:F8) [08:21:16:781]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:781]: Executing op: ServiceConfigureFailureAction(,Name=LPDS Service,Event=1,,RebootMessage=[~],Command=[~],Actions=1,DelayActions=9000) MSI (s) (A0:F8) [08:21:16:781]: Changing configuration of failure action for service LPDS Service. MSI (s) (A0:F8) [08:21:16:782]: Warning: ResetPeriod is blank. Trying to change current configuration of failure action for service LPDS Service. Replacing with default argument INFINITE MSI (s) (A0:F8) [08:21:16:782]: Error: 5. Failed to change current configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Failed to change configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1939 MSI (c) (D8:DC) [08:21:16:785]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (A0:F8) [08:21:46:995]: Product: LaserPro Document Service -- Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. Here are the rows that WIX generates in the MsiServiceConfig and MsiSErviceConfigFailureActions tables: MsiServiceConfig NameEventConfigType Argument Component_ LPDS_Service.FA LPDS Service 7 4 1 LPDSService.exe MsiServiceConfigFailureActions table contents: MsiServiceConfigFailureActionsNameEvent ResetPeriod RebootMessage CommandActions
[WiX-users] unsubscribe
-- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do to configure a Windows service to Restart the Service upon failure?
To add to what Nick said, here's what I have. It works in WiX 3.5: ServiceInstall Id=InstallMyService ... util:ServiceConfig ServiceName=MyService FirstFailureActionType=restart SecondFailureActionType=restart ThirdFailureActionType=restart ResetPeriodInDays=1 RestartServiceDelayInSeconds=60 / /ServiceInstall -Adam On Mon, Dec 17, 2012 at 11:05 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: Error 5 is access denied. Are you running the installation as administrator ? -Original Message- From: Marty Offe [mailto:marty.o...@harlandfs.com] Sent: 17 December 2012 16:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How do to configure a Windows service to Restart the Service upon failure? I am *not* able to get msiexec.exe to set the recovery option of my Windows service to Restart the Service. Wix 3.6 documentation suggests that I can use ServiceConfigFailureActions to accomplish this. Here is my ServiceInstall element: ServiceInstall Id=ServiceInstallID Name=LPDS Service DisplayName=LaserPro Document Service Description=Allows LaserPro Document Service to be used as a web service. Interactive=no ErrorControl=ignore Start=auto Type=ownProcess Vital=no ServiceConfig FailureActionsWhen=failedToStopOrReturnedError OnInstall=yes OnReinstall=yes OnUninstall=yes / ServiceConfigFailureActions OnInstall=yes OnReinstall=yes OnUninstall=yes ResetPeriod=86400 Command=c:\foo.bat Failure Action=runCommand Delay=1000/ Failure Action=restartService Delay=2000/ /ServiceConfigFailureActions /ServiceInstall I am using msiexec.exe version V 5.0.7601.17514 Error from installation log file: MSI (s) (A0:F8) [08:21:16:136]: Executing op: CacheSizeFlush(,) MSI (s) (A0:F8) [08:21:16:136]: Executing op: ActionStart(Name=InstallServices,Description=Installing new services,Template=Service: [2]) MSI (s) (A0:F8) [08:21:16:142]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:143]: Executing op: ServiceInstall(Name=LPDS Service,DisplayName=LaserPro Document Service,ImagePath=C:\LPDS\CFI\Service.exe,ServiceType=32,StartType=2,ErrorCon trol=32768,,Dependencies=[~],,,Password=**,Description=Allows LaserPro Document Service to be used as a web service.,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ActionStart(Name=MsiConfigureServices,,) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:771]: Executing op: ServiceConfigure(,Name=LPDS Service,Event=5,ConfigType=4,Argument=1) MSI (s) (A0:F8) [08:21:16:771]: Changing configuration of service LPDS Service. MSI (s) (A0:F8) [08:21:16:781]: Changed configuration of service LPDS Service with ConfigType SERVICE_CONFIG_FAILURE_ACTIONS_FLAG MSI (s) (A0:F8) [08:21:16:781]: Done changing configuration of service LPDS Service MSI (s) (A0:F8) [08:21:16:781]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=130) MSI (s) (A0:F8) [08:21:16:781]: Executing op: ServiceConfigureFailureAction(,Name=LPDS Service,Event=1,,RebootMessage=[~],Command=[~],Actions=1,DelayActions=9000) MSI (s) (A0:F8) [08:21:16:781]: Changing configuration of failure action for service LPDS Service. MSI (s) (A0:F8) [08:21:16:782]: Warning: ResetPeriod is blank. Trying to change current configuration of failure action for service LPDS Service. Replacing with default argument INFINITE MSI (s) (A0:F8) [08:21:16:782]: Error: 5. Failed to change current configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Failed to change configuration of failure action for service LPDS Service MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:16:782]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1939 MSI (c) (D8:DC) [08:21:16:785]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2205 2: 3: Error MSI (s) (A0:F8) [08:21:46:995]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (A0:F8) [08:21:46:995]: Product: LaserPro Document Service -- Error 1939. Service 'LaserPro Document Service' (LPDS Service) could not be configured. This could be a problem with the package or your permissions. Verify that you have sufficient privileges to configure system services. Here are the rows that WIX generates in
Re: [WiX-users] odd behaviour in execution of a generated MSI
Could you attach the part of the log into the email message? Attachments don't show up in the forum for me. It could be a couple of things really. Might help to post some of your WiX markup too. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/odd-behaviour-in-execution-of-a-generated-MSI-tp7582409p7582419.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix 3.6 and Burn: double click versus command line invocation?
I don't see your MSI in the bundle's chain. Only the python and .NET ones. Is this the code you wanted to show to the forum? I've gotten that error message once before. It went away after I recompiled through. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-3-6-and-Burn-double-click-versus-command-line-invocation-tp7582406p7582420.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixMbaPrereqPackageId variable not visible from Fragment element
In your Bundle.wxs, if you have: BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost ... /BootstrapperApplicationRef then you also need, after the BootstrapperApplicationRef: WixVariable Id=WixMbaPrereqLicenseUrl Value=... / WixVariable Id=WixMbaPrereqPackageId Value=... / -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixMbaPrereqPackageId-variable-not-visible-from-Fragment-element-tp7582403p7582421.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: upgrades
Finally got the bottom of it... In my MSI I have something like this: Feature Id=DefaultFeature Level=0 Condition Level=1TYPE=1/Condition ComponentGroupRef Id=Test / /Feature The value of TYPE is set by burn and passed in to the MSI. On upgrade I assumed that this value would come from the msiexec command line but it seems that it doesn't and I have to save it and read it in the MSI. Failing to do this causes the install to not unregister the product so burn correctly identifies that the old version is still present. I have to say I am not 100% sure about this and whether there are any other things that could cause it to not unregister the product so I think I will cache all the properties passed in to the MSI. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 December 2012 19:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Ug, I was afraid there was some complex incantation necessary to get the bug to repro because I'm not seeing it in any of my work. I'm good with whichever of those options are best for you. On Thu, Dec 13, 2012 at 9:34 AM, Neil Sleightholm n...@x2systems.comwrote: I have tried a few simple cases and cannot reproduce it (isn't that always the case) but I will try some more. If I raise a defect and mark it private can I attach the logs I have collected or would you prefer I private messaged a location where you can see them. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 December 2012 16:17 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Sorry, I've been heads down with lots of changes going on (seems typical of my adult life in November). I've seen reports of upgrade issues from a few different vectors so I do think there is *something* going on here. But I really don't have any idea right now. What would help most is if someone could take a look at the setup code in wix37\test\data\Burn\BasicTests and add as few extra packages and/or bundles to reproduce the error that you are seeing. If you can do that, I will happily add the extra code to get it wired into the integration tests and track the bug down. That'd be the ideal. While doing that, Neil (or anybody), if you have log files and small bundle code that you can't share here but would be willing to send to me directly, I'd happily take that as well. This will likely be the last bug was take for WiX v3.7... I appreciate any help getting to the root of it. smile/ On Thu, Dec 13, 2012 at 1:56 AM, Neil Sleightholm n...@x2systems.com wrote: New variant today, the uninstall was run twice by burn. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 12 December 2012 22:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Still really struggling to understand this and the more I look the more I think something odd is happening burn. This is the problem: When I run an install created with burn that upgrades an existing install I see that burn runs the new MSI install and then the old MSI uninstall. This only happens for one of four MSIs in the package which were all authored by me in the same way. If I run the MSI outside of burn it does the upgrade and everything looks ok, there is only one entry in ARP programs and the HKCR\Installer registry looks ok. Even running it with burn what is left on the machine after the upgrade is correct and the only reason I notice it is that as part of my uninstall process I stop a tray application running; so with this problem the tray application is not running after the install. I can probably live with this but would really like to understand why burn thinks my application has not upgraded and needs to run the uninstall. In some cases the uninstall phase detects a reboot is required but burn doesn't reflect this in the UI and when you click close the machine reboots without warning. So my question is how does burn detect that an MSI hasn't upgraded and it is necessary to launch another instance to do the uninstall? Any other insights in to this problem would be greatly appreciated. I would also ask you check your logs and see if you are getting the same problem; the key is that there are two log files from the main burn package. Regards Neil -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
Re: [WiX-users] Burn: upgrades
Ahh, yes. Feature Conditions must be used very carefully. If they evaluate to false during uninstall after evaluating to true on install or repair, you can get really unexpected behaviors like this. On Mon, Dec 17, 2012 at 10:15 AM, Neil Sleightholm n...@x2systems.comwrote: Finally got the bottom of it... In my MSI I have something like this: Feature Id=DefaultFeature Level=0 Condition Level=1TYPE=1/Condition ComponentGroupRef Id=Test / /Feature The value of TYPE is set by burn and passed in to the MSI. On upgrade I assumed that this value would come from the msiexec command line but it seems that it doesn't and I have to save it and read it in the MSI. Failing to do this causes the install to not unregister the product so burn correctly identifies that the old version is still present. I have to say I am not 100% sure about this and whether there are any other things that could cause it to not unregister the product so I think I will cache all the properties passed in to the MSI. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 December 2012 19:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Ug, I was afraid there was some complex incantation necessary to get the bug to repro because I'm not seeing it in any of my work. I'm good with whichever of those options are best for you. On Thu, Dec 13, 2012 at 9:34 AM, Neil Sleightholm n...@x2systems.com wrote: I have tried a few simple cases and cannot reproduce it (isn't that always the case) but I will try some more. If I raise a defect and mark it private can I attach the logs I have collected or would you prefer I private messaged a location where you can see them. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 December 2012 16:17 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Sorry, I've been heads down with lots of changes going on (seems typical of my adult life in November). I've seen reports of upgrade issues from a few different vectors so I do think there is *something* going on here. But I really don't have any idea right now. What would help most is if someone could take a look at the setup code in wix37\test\data\Burn\BasicTests and add as few extra packages and/or bundles to reproduce the error that you are seeing. If you can do that, I will happily add the extra code to get it wired into the integration tests and track the bug down. That'd be the ideal. While doing that, Neil (or anybody), if you have log files and small bundle code that you can't share here but would be willing to send to me directly, I'd happily take that as well. This will likely be the last bug was take for WiX v3.7... I appreciate any help getting to the root of it. smile/ On Thu, Dec 13, 2012 at 1:56 AM, Neil Sleightholm n...@x2systems.com wrote: New variant today, the uninstall was run twice by burn. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 12 December 2012 22:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: upgrades Still really struggling to understand this and the more I look the more I think something odd is happening burn. This is the problem: When I run an install created with burn that upgrades an existing install I see that burn runs the new MSI install and then the old MSI uninstall. This only happens for one of four MSIs in the package which were all authored by me in the same way. If I run the MSI outside of burn it does the upgrade and everything looks ok, there is only one entry in ARP programs and the HKCR\Installer registry looks ok. Even running it with burn what is left on the machine after the upgrade is correct and the only reason I notice it is that as part of my uninstall process I stop a tray application running; so with this problem the tray application is not running after the install. I can probably live with this but would really like to understand why burn thinks my application has not upgraded and needs to run the uninstall. In some cases the uninstall phase detects a reboot is required but burn doesn't reflect this in the UI and when you click close the machine reboots without warning. So my question is how does burn detect that an MSI hasn't upgraded and it is necessary to launch another instance to do the uninstall? Any other insights in to this problem would be greatly appreciated. I would also ask you check your logs and see if you are getting the same problem; the key is that there are two log files from the main burn package. Regards Neil
[WiX-users] bootstrapper VERSION_INFO
Hi, To the WiX developers: I was running Process Explorer (sysinternals) and I saw that the Description and Company Name columns only contains one character (the first one set in @Bundle/Name and @Bundle/Manufacturer). On all the processes running on my computer, only the bootstrapper (created with WiX v3.7 RC) has this strange bug, so I don't guess it's a Process Explorer bug. (maybe a unicode problem?! but others program stores it in unicode and are displayed correctly) Note that in Windows it's displayed correctly. Of course this is not a blocking problem, but I was just wondering if something was wrong when WiX updates/creates the resource VERSION_FILE in the final exe. Regards. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapper VERSION_INFO
I found why: when wix updates the bootstraper resource versioninfo, for strings, the wType is not set correctly, wType is 0 instead of 1. see http://msdn.microsoft.com/en-us/library/windows/desktop/ms646987(v=vs.85).aspx Modifying with an hexadecimal editor the wType from 0 to 1 makes the string appear correctly in ProcessExplorer and I guess in some other softwares/places in Windows. Can someone confirm this? On Mon, Dec 17, 2012 at 10:08 PM, up2date.cyb...@gmail.com up2date.cyb...@gmail.com wrote: Hi, To the WiX developers: I was running Process Explorer (sysinternals) and I saw that the Description and Company Name columns only contains one character (the first one set in @Bundle/Name and @Bundle/Manufacturer). On all the processes running on my computer, only the bootstrapper (created with WiX v3.7 RC) has this strange bug, so I don't guess it's a Process Explorer bug. (maybe a unicode problem?! but others program stores it in unicode and are displayed correctly) Note that in Windows it's displayed correctly. Of course this is not a blocking problem, but I was just wondering if something was wrong when WiX updates/creates the resource VERSION_FILE in the final exe. Regards. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Propogating Environmnet variables
We are having issues propagating the environment variables. The setup has a custom action that propagates the environment using the SendMessageTimeOut api SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM) Environment, SMTO_ABORTIFHUNG, 5000, NULL); On a 64 bit OS, both 32 and 64 bit consoles were opened before the install. Ran the install with the above custom action. If a console window is open one doesn't see the custom Environment. But open a new console session and the varaible is listed (for both 32 and 64 bit cosole). Is this the correct behavior? Is there a way for the console window opened before the install to see the custom environment variable. Thanks Mita -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Propogating Environmnet variables
I thought MSI did the send message thing itself and that console windows are never affected by it. On Mon, Dec 17, 2012 at 4:31 PM, Mita Patel mpa...@esri.com wrote: We are having issues propagating the environment variables. The setup has a custom action that propagates the environment using the SendMessageTimeOut api SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM) Environment, SMTO_ABORTIFHUNG, 5000, NULL); On a 64 bit OS, both 32 and 64 bit consoles were opened before the install. Ran the install with the above custom action. If a console window is open one doesn't see the custom Environment. But open a new console session and the varaible is listed (for both 32 and 64 bit cosole). Is this the correct behavior? Is there a way for the console window opened before the install to see the custom environment variable. Thanks Mita -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapper VERSION_INFO
problem comes from: wix37-sources\src\DTF\Libraries\Resources\VersionStringTable.cs (line 81) where verValue.Data is set, and in VersionInfo.cs (line 83): this.isString = false; so we lose the info that verValue is a string. Could it be fixed before final release of WiX 3.7? to reproduce while debugging: Microsoft.Deployment.Resources.ResourceCollection resources = new Microsoft.Deployment.Resources.ResourceCollection(); Microsoft.Deployment.Resources.VersionResource version = new Microsoft.Deployment.Resources.VersionResource(#1, 1033); version.Load(c:\\temp\\burn.exe); resources.Add(version); Microsoft.Deployment.Resources.VersionStringTable strings = version[1033]; strings[CompanyName] = blabla; resources.Save(c:\\temp\\burn2.exe); isString is set to false just after the assignment. Maybe I should not post this on the wix-user list?! On Mon, Dec 17, 2012 at 10:51 PM, up2date cyborg up2date.cyb...@gmail.comwrote: I found why: when wix updates the bootstraper resource versioninfo, for strings, the wType is not set correctly, wType is 0 instead of 1. see http://msdn.microsoft.com/en-us/library/windows/desktop/ms646987(v=vs.85).aspx Modifying with an hexadecimal editor the wType from 0 to 1 makes the string appear correctly in ProcessExplorer and I guess in some other softwares/places in Windows. Can someone confirm this? On Mon, Dec 17, 2012 at 10:08 PM, up2date.cyb...@gmail.com up2date.cyb...@gmail.com wrote: Hi, To the WiX developers: I was running Process Explorer (sysinternals) and I saw that the Description and Company Name columns only contains one character (the first one set in @Bundle/Name and @Bundle/Manufacturer). On all the processes running on my computer, only the bootstrapper (created with WiX v3.7 RC) has this strange bug, so I don't guess it's a Process Explorer bug. (maybe a unicode problem?! but others program stores it in unicode and are displayed correctly) Note that in Windows it's displayed correctly. Of course this is not a blocking problem, but I was just wondering if something was wrong when WiX updates/creates the resource VERSION_FILE in the final exe. Regards. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do to configure a Windows service to Restart the Service upon failure?
On 17-Dec-12 11:43, Marty Offe wrote: I am *not* able to get msiexec.exe to set the recovery option of my Windows service to Restart the Service. Two things: 1. Your authoring doesn't match your MSI tables doesn't match your MSI log. 2. There's no indication in the doc that MsiServiceConfigFailureActions supports running batch files. Try notepad or something else. -- sig://boB http://joyofsetup.com/ -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] bootstrapper VERSION_INFO
On 17-Dec-12 19:57, up2date cyborg wrote: Maybe I should not post this on the wix-user list?! Please file a bug so it doesn't get lost. -- sig://boB http://joyofsetup.com/ -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] odd behaviour in execution of a generated MSI
Here find the content of files:
MSI_NOT_OK.log ==
=== Verbose logging started: 5/12/2012 16:06:02 Build type: SHIP UNICODE
5.00.7600.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell
Dlg
Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell
Dlg
Resetting cached policy values
Machine policy value 'Debug' is 0
*** RunEngine:
*** Product: zSOPRA_Custom_Actions.1.5.0.0.msi
*** Action:
*** CommandLine: **
Machine policy value 'DisableUserInstalls' is 0
Cloaking enabled.
Attempting to enable all disabled privileges before calling Install on
Server
End dialog not enabled
Original package == C:\TEMP\zSOPRA_Custom_Actions.1.5.0.0.msi
Package we're running from == C:\WINDOWS\Installer\e218de80.msi
APPCOMPAT: Uninstall Flags override found.
APPCOMPAT: Uninstall VersionNT override found.
APPCOMPAT: Uninstall ServicePackLevel override found.
APPCOMPAT: looking for appcompat database entry with ProductCode
'{8570C613-A0C5-435F-9224-C795B285385F}'.
APPCOMPAT: no matching ProductCode found in database.
MSCOREE not loaded loading copy from system32
Machine policy value 'DisablePatch' is 0
Machine policy value 'AllowLockdownPatch' is 0
Machine policy value 'DisableLUAPatching' is 0
Machine policy value 'DisableFlyWeightPatching' is 0
APPCOMPAT: looking for appcompat database entry with ProductCode
'{8570C613-A0C5-435F-9224-C795B285385F}'.
APPCOMPAT: no matching ProductCode found in database.
Transforms are not secure.
Note: 1: 2205 2: 3: Control
PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is
'C:\TEMP\logmsi.log'.
Command Line: CURRENTDIRECTORY=C:\TEMP CLIENTUILEVEL=0 CLIENTPROCESSID=4648
PROPERTY CHANGE: Adding PackageCode property. Its value is
'{40D508B6-F92E-4FD7-B5C0-B22C8F6A8526}'.
Product Code passed to Engine.Initialize:
'{8570C613-A0C5-435F-9224-C795B285385F}'
Product Code from property table before transforms:
'{8570C613-A0C5-435F-9224-C795B285385F}'
Product Code from property table after transforms:
'{8570C613-A0C5-435F-9224-C795B285385F}'
Product registered: entering maintenance mode
Determined that existing product (either this product or the product being
upgraded with a patch) is installed per-machine.
PROPERTY CHANGE: Adding ALLUSERS property. Its value is '1'.
PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
Note: 1: 1402 2:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
3: 2
Entering CMsiConfigurationManager::SetLastUsedSource.
Specifed source is not already in a list.
User policy value 'SearchOrder' is 'nmu'
Machine policy value 'DisableBrowse' is 0
Machine policy value 'AllowLockdownBrowse' is 0
Adding new sources is allowed.
Package name retrieved from configuration data:
'zSOPRA_Custom_Actions.1.5.0.0.msi'
Note: 1: 2205 2: 3: Error
Note: 1: 2262 2: AdminProperties 3: -2147287038
Machine policy value 'DisableMsi' is 0
Machine policy value 'AlwaysInstallElevated' is 0
User policy value 'AlwaysInstallElevated' is 0
Product {8570C613-A0C5-435F-9224-C795B285385F} is admin assigned:
LocalSystem owns the publish key.
Product {8570C613-A0C5-435F-9224-C795B285385F} is managed.
Running product '{8570C613-A0C5-435F-9224-C795B285385F}' with elevated
privileges: Product is assigned.
PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\TEMP'.
PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '0'.
PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '4648'.
PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
TRANSFORMS property is now:
PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
SHELL32::SHGetFolderPath returned: C:\Users\_pwillems\AppData\Roaming
SHELL32::SHGetFolderPath returned: C:\Users\_pwillems\Favorites
SHELL32::SHGetFolderPath returned:
C:\Users\_pwillems\AppData\Roaming\Microsoft\Windows\Network Shortcuts
SHELL32::SHGetFolderPath returned: C:\Users\_pwillems\Documents
SHELL32::SHGetFolderPath returned:
C:\Users\_pwillems\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
SHELL32::SHGetFolderPath returned:
C:\Users\_pwillems\AppData\Roaming\Microsoft\Windows\Recent
SHELL32::SHGetFolderPath returned:
C:\Users\_pwillems\AppData\Roaming\Microsoft\Windows\SendTo
SHELL32::SHGetFolderPath returned:
C:\Users\_pwillems\AppData\Roaming\Microsoft\Windows\Templates
SHELL32::SHGetFolderPath returned: C:\ProgramData
SHELL32::SHGetFolderPath returned: C:\Users\_pwillems\AppData\Local
SHELL32::SHGetFolderPath returned: C:\Users\_pwillems\Pictures
SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start
Menu\Programs\Administrative Tools
SHELL32::SHGetFolderPath returned:
Re: [WiX-users] Propogating Environmnet variables
That is how environment variables work, the variables are only read when the environment is started. IIRC you can write applications that monitor for WM_SETTINGCHANGE and update themselves but the standard consoles don't. Neil -Original Message- From: Mita Patel [mailto:mpa...@esri.com] Sent: 18 December 2012 00:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Propogating Environmnet variables We are having issues propagating the environment variables. The setup has a custom action that propagates the environment using the SendMessageTimeOut api SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM) Environment, SMTO_ABORTIFHUNG, 5000, NULL); On a 64 bit OS, both 32 and 64 bit consoles were opened before the install. Ran the install with the above custom action. If a console window is open one doesn't see the custom Environment. But open a new console session and the varaible is listed (for both 32 and 64 bit cosole). Is this the correct behavior? Is there a way for the console window opened before the install to see the custom environment variable. Thanks Mita -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
