Re: [WiX-users] Uninstall Rollback not triggered with WIXFAILWHENDEFERRED
I don't have WixFailWhenDeferred custom action in InstallExecuteSequence. Infact, when I opened the msi in ORCA, the CA was sequenced at 6599 (before InstallFinalize) with condition WIXFAILWHENDEFERRED=1 AND VersionNT 400 This I believe should trigger rollback for both Install and Uninstall. Apparently, I cannot get the msi to rollback on uninstall. I also edited the condition in ORCA to WIXFAILWHENDEFERRED=1 AND VersionNT 400 AND REMOVE=ALL to at least rollback on uninstall (I wouldn't expect this condition to evaluate true for INSTALL). But the msi didn't rollback. The condition on the CA was false and was therefore being skipped. Any other places I could check? Could this be anything to do with Wix 3.8? I had the rollback working for both install and uninstall in one of my earlier projects that used Wix 3.5. Thanks for all suggestions! sangeeta -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-Rollback-not-triggered-with-WIXFAILWHENDEFERRED-tp7598874p7598907.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RegistryKey question
We were looking into allowing our users to use local web pages without the Active X/content warning that this usually provokes (our users are very tech-unsavvy and find having to click this sort of warning to be confusing). Since we need them to generate cookies from these pages we need them to have used, hence the auto-accept. It looked like installing something with: RegistryKey Root=HKLM Key=software\microsoft\internet explorer\main\featurecontrol\FEATURE_LOCALMACHINE_LOCKDOWN Action=createAndRemoveOnUninstall RegistryValue Type=integer Name=iexplore.exe Value=0 KeyPath=yes/ should do the trick, except when the installer ran it seems that all the other featurecontrol keys (e.g., FEATURE_ACTIVEX_REPURPOSEDETECTION) which were present (even if they were only defaults) were deleted! What happened here? WiX 3.7, if it matters. Keith Douglas Programmer Analyst | Programmeur analyste Questionnaire Development Services - CAI Social | Services de développement de questionnaires - IAO Social Jean Talon Building | Immeuble Jean-Talon / Floor | Étage 4 A-3 Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RollbackBoundry - Can't Upgrade or uninstall bundle.
This log was created after there were two of these 'orphaned' entries (for
versions 9.1.0.4 and 9.1.0.5) in the ARP, while running build Bundle 9.1.0.6
as a Upgrade. (These Bundles implement the MajorUpgrade pattern and
increment the last section of the version, based on recent discussion in
wix-devs/online meeting. I had also seen this behavior when I was
incrementing the third section of the version number.)
[0F44:023C][2015-01-15T14:02:12]i001: Burn v3.9.1006.0, Windows v6.2 (Build
9200: Service Pack 0), path: C:\Users\PHogland\AppData\Local\Package
Cache\{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}\Bundle.exe, cmdline:
'-burn.unelevated BurnPipe.{F1C690D8-984B-4FB7-B3D1-233198328EE0}
{05872525-8B04-4EBB-95F8-0BFA92A4F1B6} 3660 -burn.related.update'
[0F44:023C][2015-01-15T14:02:12]i003: This bundle is being run by a related
bundle as type 'Update'.
[0F44:023C][2015-01-15T14:02:12]i000: Initializing string variables ..
[0F44:023C][2015-01-15T14:02:12]i102: Detected related bundle:
{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}, type: Upgrade, scope: PerMachine,
version: 9.1.0.5, operation: MajorUpgrade
[0F44:023C][2015-01-15T14:02:12]i000: DetectedRelatedBundle: e.BundleTag:
Bundle, e.Operation: MajorUpgrade, e.PerMachine: True, e.ProductCode:
{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}, e.RelationType: Upgrade, e.Result:
None, e.Version: 9.1.0.5
[0F44:023C][2015-01-15T14:02:12]i102: Detected related bundle:
{46844853-a369-4dba-b0ff-f03c19165600}, type: Upgrade, scope: PerMachine,
version: 9.1.0.4, operation: MajorUpgrade
[0F44:023C][2015-01-15T14:02:12]i000: DetectedRelatedBundle: e.BundleTag:
Bundle, e.Operation: MajorUpgrade, e.PerMachine: True, e.ProductCode:
{46844853-a369-4dba-b0ff-f03c19165600}, e.RelationType: Upgrade, e.Result:
None, e.Version: 9.1.0.4
... testing package conditions
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: NetFx40ClientWeb,
state: Present, cached: Complete
Here is a log where I later, launched the Bundle on the command line with
-uninstall
[0F98:0EEC][2015-01-15T14:24:03]i001: Burn v3.9.1006.0, Windows v6.2 (Build
9200: Service Pack 0), path: D:\Bundle\Bundle.exe, cmdline: '-uninstall'
[0F98:0EEC][2015-01-15T14:24:03]i000: Initializing string variable
'InstallFolder' to value '[ProgramFilesFolder]Company\'
...
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variable
'WixBundleOriginalSource' to value 'D:\Bundle\Bundle.exe'
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variable
'WixBundleOriginalSourceFolder' to value 'D:\Bundle\'
[0F98:0EEC][2015-01-15T14:24:03]i000: Loading managed bootstrapper
application.
[0F98:0EEC][2015-01-15T14:24:03]i000: Creating BA thread to run
asynchronously.
[0F98:0EEC][2015-01-15T14:24:03]i100: Detect begin, 45 packages (edited out
the many localized copies of packages all marked as Absent)
[0F98:0CB4][2015-01-15T14:24:03]i000: Creating a UI.
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variables and evaluate
conditions.
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: NetFx40ClientWeb,
state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package:
VC2005SP1_2_0_50727_762, state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: VC2008_9_0_21022_08,
state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package:
VC2008SP1_9_0_30729_17, state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package:
VC2008SP1_9_0_30729_4148, state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package:
VC2008_SP1_9_0_30729_4148_x64, state: Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: vc2010_x64, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: vc2010_x86, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: vc2013_x86, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: App1_en_US, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: App2_en_US, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: App3_en_US, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: App4_en_US, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: JavaJre7, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i101: Detected package: App5_en_US, state:
Present, cached: Complete
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variables
[0F98:0EEC][2015-01-15T14:24:03]i000: Invoking automatic plan for uninstall
[0F98:0EEC][2015-01-15T14:24:03]i199: Detect complete, result: 0x0
[0F98:0EEC][2015-01-15T14:24:03]i200: Plan begin, 45 packages, action:
Uninstall
[0F98:0EEC][2015-01-15T14:24:03]w210: Plan skipped due to 1 remaining
dependents
[0F98:0EEC][2015-01-15T14:24:03]i201: Planned package: App5_en_US, state:
Re: [WiX-users] RollbackBoundry - Can't Upgrade or uninstall bundle.
Sorry for the previous post, which I deleted, becuase I cut and pasted one
log in the middle of another log. Lets try again.
This log was created while Upgrading Bundle 9.1.0.6, while Bundle 9.1.0.5
was installed (AND while Bundle 9.1.0.4 was also incorrectly listed in ARP,
as it should have been removed by the Upgrade of 9.1.0.5).
[0F44:023C][2015-01-15T14:02:12]i001: Burn v3.9.1006.0, Windows v6.2 (Build
9200: Service Pack 0), path: C:\Users\PHogland\AppData\Local\Package
Cache\{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}\Bundle.exe, cmdline:
'-burn.unelevated BurnPipe.{F1C690D8-984B-4FB7-B3D1-233198328EE0}
{05872525-8B04-4EBB-95F8-0BFA92A4F1B6} 3660 -burn.related.update'
[0F44:023C][2015-01-15T14:02:12]i003: This bundle is being run by a related
bundle as type 'Update'.
[0F44:023C][2015-01-15T14:02:12]i000: Initializing string variables ..
[0F44:023C][2015-01-15T14:02:12]i102: Detected related bundle:
{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}, type: Upgrade, scope: PerMachine,
version: 9.1.0.5, operation: MajorUpgrade
[0F44:023C][2015-01-15T14:02:12]i000: DetectedRelatedBundle: e.BundleTag:
Bundle, e.Operation: MajorUpgrade, e.PerMachine: True, e.ProductCode:
{0c11c2bc-e9ff-49f2-a75d-0bb7fe269e7b}, e.RelationType: Upgrade, e.Result:
None, e.Version: 9.1.0.5
[0F44:023C][2015-01-15T14:02:12]i102: Detected related bundle:
{46844853-a369-4dba-b0ff-f03c19165600}, type: Upgrade, scope: PerMachine,
version: 9.1.0.4, operation: MajorUpgrade
[0F44:023C][2015-01-15T14:02:12]i000: DetectedRelatedBundle: e.BundleTag:
Bundle, e.Operation: MajorUpgrade, e.PerMachine: True, e.ProductCode:
{46844853-a369-4dba-b0ff-f03c19165600}, e.RelationType: Upgrade, e.Result:
None, e.Version: 9.1.0.4
... testing package conditions
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: NetFx40ClientWeb,
state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package:
VC2005SP1_2_0_50727_762, state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: VC2008_9_0_21022_08,
state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package:
VC2008SP1_9_0_30729_17, state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package:
VC2008SP1_9_0_30729_4148, state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package:
VC2008_SP1_9_0_30729_4148_x64, state: Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: vc2010_x64, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: vc2010_x86, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: vc2013_x86, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: App1_en_US, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: App2_en_US, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: App3_en_US, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: App4_en_US, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: JavaJre7, state:
Present, cached: Complete
[0F44:023C][2015-01-15T14:02:12]i101: Detected package: App5_en_US, state:
Present, cached: Complete
... setting variables
[0F44:023C][2015-01-15T14:02:12]i199: Detect complete, result: 0x0
[0F44:0CC4][2015-01-15T14:02:12]i000: The current version is the same or
newer than the version staged for download.
[0F44:023C][2015-01-15T14:02:17]i500: Shutting down, exit code: 0x0
..list variable values
[0F44:023C][2015-01-15T14:02:17]i410: Variable: WixBundleProviderKey =
{489369B3-B566-428A-84DA-9D052E608903}
[0F44:023C][2015-01-15T14:02:17]i410: Variable: WixBundleTag = Bundle
[0F44:023C][2015-01-15T14:02:17]i410: Variable: WixBundleVersion = 9.1.0.6
[0F44:023C][2015-01-15T14:02:17]i007: Exit code: 0x0, restarting: No
This log was created later when I ran Bundle 9.1.0.6 with -uninstall on the
command line.
[0F98:0EEC][2015-01-15T14:24:03]i001: Burn v3.9.1006.0, Windows v6.2 (Build
9200: Service Pack 0), path: D:\Bundle\Bundle.exe, cmdline: '-uninstall'
[0F98:0EEC][2015-01-15T14:24:03]i000: Initializing string variable
'InstallFolder' to value '[ProgramFilesFolder]Company\'
...
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variable
'WixBundleOriginalSource' to value 'D:\Bundle\Bundle.exe'
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variable
'WixBundleOriginalSourceFolder' to value 'D:\Bundle\'
[0F98:0EEC][2015-01-15T14:24:03]i000: Loading managed bootstrapper
application.
[0F98:0EEC][2015-01-15T14:24:03]i000: Creating BA thread to run
asynchronously.
[0F98:0EEC][2015-01-15T14:24:03]i100: Detect begin, 45 packages (edited out
the many localized copies of packages all marked as Absent)
[0F98:0CB4][2015-01-15T14:24:03]i000: Creating a UI.
[0F98:0EEC][2015-01-15T14:24:03]i000: Setting string variables and evaluate
conditions.
Re: [WiX-users] Bootstrapper for multiple cultures
It worked after I changed my Date Format settings to Japanese :). Before I was only changing the Keyboard and Location settings, but Date Format was still English, so it was still coming up in English. Thanks a lot for the help! Regards Vikas -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598899.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing uncompressed MsiPackage
Sorry again, but I didn't find the answer in the Support Center... Can you give me a little example or a link to the exact place ? Rob Mensching-7 wrote Use the Name attribute. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: manmaor [mailto: manmaor2@ ] Sent: Sunday, January 18, 2015 12:38 PM To: wix-users@.sourceforge Subject: Re: [WiX-users] Installing uncompressed MsiPackage no, when I said : but it require the msi installer to be near the bootstrapper.exe. I meant the installer.msi needed to be in the same directory with the bootstrapper.exe to be installed by the bootstrapper.exe otherwise it wont be installed. but what I need is more like adding the installer.msi as payload and point the MsiPackage to the payload. like : Payload Id=INS SourceFile=installer.msi/ MsiPackage SourceFile=INS Compressed=no/ but this isn't working... -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-uncompressed-MsiPackage-tp7598885p7598898.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] aid debugging complex conditons
The individual property values should be in the log if it's verbose. If they don't appear that typically means they are not being set at all. I've used a debug dialog in similar situations. At the end of the UI sequence have a dialog that's just a display of the property values you're interested in, typically last in the UI sequence. You can condition on a property like UIDEBUG, and you can set that on the command line That can be useful when customers report problems. --- Phil Wilson On Sat, Jan 17, 2015 at 4:46 PM, Matthew O'Connell techsupport...@gmail.com wrote: Say I have a complex boolean expression in, for example, a component condition and it’s not evaluating how I expect. Is there any way to get Windows Installer to ‘echo’ the condition variables as evaluated at install time as an aid to debugging. For example maybe I used (Property1=1) Or Property2 Or Property3 and I’m expecting at least one property to exist or evaluate to true but want to know which one, or want to confirm one part evaluates as I expect. Can I get something like “1=1 Or True Or False” to be output somehow, as you might get with a cmd script for example. At the moment I’ve only got the logs Action=local to show the whole component evaluated to true and the verbose logs properties.. Thanks -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
