Re: [WiX-users] Unable to uninstall previously installed product
Hi, I have tried and it seems that it will work if I can pass the following trouble. I get the uninstallstring using:Property Id=REGISTRYFOROLDINSTALLER RegistrySearch Id=OldInstallerRegistryKey Root=HKLM Key=SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\4553c9c9-172b-4d73-97d0-a667d4dd6685 Name=QuietUninstallString Type=file //Property This returns me: C:\Program Files (x86)\MyApplication\ Then I have a custom action to run the uninstaller string.CustomAction Id='uninstallOldInstallation' Property='REGISTRYFOROLDINSTALLER' ExeCommand='-S' Execute='immediate' Return='check' HideTarget='no' Impersonate='no'/CustomAction InstallExecuteSequenceCustom Action=uninstallOldInstallation Before=InstallFilesREGISTRYFOROLDINSTALLER/Custom/InstallExecuteSequence I got the following error in the debug logs:Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: uninstallOldInstallation, location: C:\Program Files (x86)\MyApplication\, command: uninstall.exe -S It should work fine to me but I have no clue why I am getting this error. I tried also type:raw in RegistrySearch but get the same error in the end. I'd appreciate if you could shed some light.Thanks. From: c...@live.com To: wix-users@lists.sourceforge.net Date: Sat, 21 Jun 2014 05:19:49 + Subject: Re: [WiX-users] Unable to uninstall previously installed product I will give it a try and come back if it doesn't work. Thanks a lot. Date: Fri, 20 Jun 2014 14:41:06 -0500 From: jeremi...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Unable to uninstall previously installed product Sorry, I misunderstood as I am not familiar with InstallerJammer. I did find this though. http://stackoverflow.com/questions/14334012/how-can-perform-a-silent-uninstall-with-installjammer Again, I'm not familiar with InstallerJammer and I'm assuming it doesn't use WindowsInstaller??? Since you can have only have one install/uninstall at one time on a windows machine this might not work if you try to uninstall during your new install. On Fri, Jun 20, 2014 at 10:45 AM, Dolevo Jay c...@live.com wrote: Previous installer was InstallJammer. So, what would be the best solution for this? Should I call uninstaller of the previous installation in InstallExecuteSequence ? Any example for this? Date: Fri, 20 Jun 2014 10:30:11 -0500 From: jeremi...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Unable to uninstall previously installed product What was the previous installer? On Fri, Jun 20, 2014 at 9:32 AM, Phill Hogland phogl...@rimage.com wrote: The update behavior of msiexec and the UpdateCode property are specific to MSI based technology. It would not know about other technologies like InstallJammer. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-uninstall-previously-installed-product-tp7595380p7595383.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems
Re: [WiX-users] Unable to uninstall previously installed product
I have found the issue myself. Following code works perfect. RegistrySearch Id=OldInstallerRegistryKey Root=HKLM Key=SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\4553c9c9-172b-4d73-97d0-a667d4dd6685 Name=UninstallString Type=raw /CustomAction Id='uninstallOldInstallation' Property='REGISTRYFOROLDINSTALLER' ExeCommand='/mode silent' Execute='immediate' Return='check' HideTarget='no' Impersonate='no'/CustomAction Thanks a lot. From: c...@live.com To: wix-users@lists.sourceforge.net Date: Mon, 23 Jun 2014 08:14:27 + Subject: Re: [WiX-users] Unable to uninstall previously installed product Hi, I have tried and it seems that it will work if I can pass the following trouble. I get the uninstallstring using:Property Id=REGISTRYFOROLDINSTALLER RegistrySearch Id=OldInstallerRegistryKey Root=HKLM Key=SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\4553c9c9-172b-4d73-97d0-a667d4dd6685 Name=QuietUninstallString Type=file //Property This returns me: C:\Program Files (x86)\MyApplication\ Then I have a custom action to run the uninstaller string.CustomAction Id='uninstallOldInstallation' Property='REGISTRYFOROLDINSTALLER' ExeCommand='-S' Execute='immediate' Return='check' HideTarget='no' Impersonate='no'/CustomAction InstallExecuteSequence Custom Action=uninstallOldInstallation Before=InstallFilesREGISTRYFOROLDINSTALLER/Custom/InstallExecuteSequence I got the following error in the debug logs:Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: uninstallOldInstallation, location: C:\Program Files (x86)\MyApplication\, command: uninstall.exe -S It should work fine to me but I have no clue why I am getting this error. I tried also type:raw in RegistrySearch but get the same error in the end. I'd appreciate if you could shed some light.Thanks. From: c...@live.com To: wix-users@lists.sourceforge.net Date: Sat, 21 Jun 2014 05:19:49 + Subject: Re: [WiX-users] Unable to uninstall previously installed product I will give it a try and come back if it doesn't work. Thanks a lot. Date: Fri, 20 Jun 2014 14:41:06 -0500 From: jeremi...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Unable to uninstall previously installed product Sorry, I misunderstood as I am not familiar with InstallerJammer. I did find this though. http://stackoverflow.com/questions/14334012/how-can-perform-a-silent-uninstall-with-installjammer Again, I'm not familiar with InstallerJammer and I'm assuming it doesn't use WindowsInstaller??? Since you can have only have one install/uninstall at one time on a windows machine this might not work if you try to uninstall during your new install. On Fri, Jun 20, 2014 at 10:45 AM, Dolevo Jay c...@live.com wrote: Previous installer was InstallJammer. So, what would be the best solution for this? Should I call uninstaller of the previous installation in InstallExecuteSequence ? Any example for this? Date: Fri, 20 Jun 2014 10:30:11 -0500 From: jeremi...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Unable to uninstall previously installed product What was the previous installer? On Fri, Jun 20, 2014 at 9:32 AM, Phill Hogland phogl...@rimage.com wrote: The update behavior of msiexec and the UpdateCode property are specific to MSI based technology. It would not know about other technologies like InstallJammer. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-uninstall-previously-installed-product-tp7595380p7595383.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data
[WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's desktop and
run it from there. Any ideas what stands behind 0x80070570 error?
Previously, we used to deploy to our clients using single MSI and had no
such issues, but had to know convert it into series of MSI-s we install
using Wix Boostrapper.
Here is the error log:
[14A0:0310][2014-06-21T20:02:34]i001: Burn v3.8.1128.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe,
cmdline: '-burn.unelevated BurnPipe.{0CC10E48-16BF-4218-9943-634CA2BA234A}
{01AD10FE-F61C-4DE5-B245-B5F3C2D5C5B9} 6072'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234.log'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleName' to value 'TestCompany Client 8.1.229.0'
[14A0:0310][2014-06-21T20:02:34]i100: Detect begin, 2 packages
[14A0:0310][2014-06-21T20:02:34]i000: Registry key not found. Key =
'SOFTWARE\TestCompany\Client Prerequisites'
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: PrerequisitesMsi,
state: Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: ClientMsi, state:
Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i199: Detect complete, result: 0x0
[14A0:148C][2014-06-21T20:02:35]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[14A0:0310][2014-06-21T20:02:35]i200: Plan begin, 2 packages, action:
Install
[14A0:0310][2014-06-21T20:02:35]i052: Condition 'NOT PrerequisitesVersion
OR (PrerequisitesVersion v1.0.0.0)' evaluates to true.
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser, package
scope: PerMachine
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_PrerequisitesMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_0_PrerequisitesMsi.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleRollbackLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi_rollback.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi.log'
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: PrerequisitesMsi,
state: Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: None, cache: Yes, uncache: No, dependency: None
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: ClientMsi, state:
Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[14A0:0310][2014-06-21T20:02:35]i299: Plan complete, result: 0x0
[14A0:0310][2014-06-21T20:02:35]i300: Apply begin
[17B8:0FF4][2014-06-21T20:02:35]i360: Creating a system restore point.
[17B8:0FF4][2014-06-21T20:02:41]i361: Created a system restore point.
[14A0:0310][2014-06-21T20:02:41]i000: Caching bundle from:
'C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\.be\TestCompany
Client Setup.exe' to: 'C:\Users\Opt1\AppData\Local\Package
Cache\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:41]i320: Registering bundle dependency
provider: {b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}, version: 8.1.229.0
[14A0:17AC][2014-06-21T20:02:41]i336: Acquiring container:
WixAttachedContainer, copy from:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe
[14A0:17AC][2014-06-21T20:02:41]i000: Setting string variable
'WixBundleLastUsedSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\'
[14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
all files from container, erf: 1:4:0
[14A0:17AC][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to begin and
wait for operation.
[14A0:17AC][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
payload: a1 from container: WixAttachedContainer
[14A0:17AC][2014-06-21T20:02:41]e312: Failed to extract payloads from
container: WixAttachedContainer to working path:
C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\AA277E16A0A041CAA7D085BEC3F2AE7650F3B2BF,
error: 0x80070570.
[14A0:0310][2014-06-21T20:02:41]e000: Error 0x80070570: Failed while
caching, aborting execution.
[14A0:0310][2014-06-21T20:02:41]i330: Removed bundle dependency provider:
{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}
[14A0:0310][2014-06-21T20:02:41]i352: Removing cached bundle:
{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}, from path:
Re: [WiX-users] heat throws error on Windows 7
It does, indeed. I realized that it runs fine in Cygwin, but not from the Windows commandline. Any idea why that might be? I would prefer not to have to set up Cygwin on our build server. scubasteve2 wrote Does ./MyFolder exist? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-throws-error-on-Windows-7-tp7595399p7595408.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat throws error on Windows 7
That sounds like a permissions problem to me. Check your windows-based ACLs for all files and folders involved in your process. Did you install WIX from a Cygwin command line? -Original Message- From: eric [mailto:eric.bu...@lmco.com] Sent: June-23-14 9:06 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat throws error on Windows 7 It does, indeed. I realized that it runs fine in Cygwin, but not from the Windows commandline. Any idea why that might be? I would prefer not to have to set up Cygwin on our build server. scubasteve2 wrote Does ./MyFolder exist? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-throws-error-on-Windows-7-tp7595399p7595408.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
Some Possibilities:
1.
http://www.sevenforums.com/installation-setup/34736-0x80070570-error-code-install-one-easy-solution.html
2. https://answers.yahoo.com/question/index?qid=20091231164201AA1jCpl
3.
http://superuser.com/questions/432368/installation-error-0x80070570-while-installing-windows-7
Carter
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's desktop and
run it from there. Any ideas what stands behind 0x80070570 error?
Previously, we used to deploy to our clients using single MSI and had no
such issues, but had to know convert it into series of MSI-s we install
using Wix Boostrapper.
Here is the error log:
[14A0:0310][2014-06-21T20:02:34]i001: Burn v3.8.1128.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe,
cmdline: '-burn.unelevated BurnPipe.{0CC10E48-16BF-4218-9943-634CA2BA234A}
{01AD10FE-F61C-4DE5-B245-B5F3C2D5C5B9} 6072'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234.log'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleName' to value 'TestCompany Client 8.1.229.0'
[14A0:0310][2014-06-21T20:02:34]i100: Detect begin, 2 packages
[14A0:0310][2014-06-21T20:02:34]i000: Registry key not found. Key =
'SOFTWARE\TestCompany\Client Prerequisites'
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: PrerequisitesMsi,
state: Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: ClientMsi, state:
Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i199: Detect complete, result: 0x0
[14A0:148C][2014-06-21T20:02:35]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[14A0:0310][2014-06-21T20:02:35]i200: Plan begin, 2 packages, action:
Install
[14A0:0310][2014-06-21T20:02:35]i052: Condition 'NOT PrerequisitesVersion
OR (PrerequisitesVersion v1.0.0.0)' evaluates to true.
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser, package
scope: PerMachine
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_PrerequisitesMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_0_PrerequisitesMsi.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleRollbackLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi_rollback.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi.log'
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: PrerequisitesMsi,
state: Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: None, cache: Yes, uncache: No, dependency: None
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: ClientMsi, state:
Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[14A0:0310][2014-06-21T20:02:35]i299: Plan complete, result: 0x0
[14A0:0310][2014-06-21T20:02:35]i300: Apply begin
[17B8:0FF4][2014-06-21T20:02:35]i360: Creating a system restore point.
[17B8:0FF4][2014-06-21T20:02:41]i361: Created a system restore point.
[14A0:0310][2014-06-21T20:02:41]i000: Caching bundle from:
'C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\.be\TestCompany
Client Setup.exe' to: 'C:\Users\Opt1\AppData\Local\Package
Cache\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:41]i320: Registering bundle dependency
provider: {b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}, version: 8.1.229.0
[14A0:17AC][2014-06-21T20:02:41]i336: Acquiring container:
WixAttachedContainer, copy from:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe
[14A0:17AC][2014-06-21T20:02:41]i000: Setting string variable
'WixBundleLastUsedSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\'
[14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
all files from container, erf: 1:4:0
[14A0:17AC][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to begin and
wait for operation.
[14A0:17AC][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
payload: a1 from container: WixAttachedContainer
[14A0:17AC][2014-06-21T20:02:41]e312: Failed to extract payloads from
container: WixAttachedContainer to working path:
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
Not sure this is the case here. It's not bad RAM or corrupt file, since
once file is copied to user's desktop folder the installation succeeds.
Any other ideas?
On Mon, Jun 23, 2014 at 4:22 PM, Carter Young ecyo...@grandecom.net wrote:
Some Possibilities:
1.
http://www.sevenforums.com/installation-setup/34736-0x80070570-error-code-install-one-easy-solution.html
2. https://answers.yahoo.com/question/index?qid=20091231164201AA1jCpl
3.
http://superuser.com/questions/432368/installation-error-0x80070570-while-installing-windows-7
Carter
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's desktop
and
run it from there. Any ideas what stands behind 0x80070570 error?
Previously, we used to deploy to our clients using single MSI and had no
such issues, but had to know convert it into series of MSI-s we install
using Wix Boostrapper.
Here is the error log:
[14A0:0310][2014-06-21T20:02:34]i001: Burn v3.8.1128.0, Windows v6.1
(Build
7601: Service Pack 1), path:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe,
cmdline: '-burn.unelevated
BurnPipe.{0CC10E48-16BF-4218-9943-634CA2BA234A}
{01AD10FE-F61C-4DE5-B245-B5F3C2D5C5B9} 6072'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234.log'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleName' to value 'TestCompany Client 8.1.229.0'
[14A0:0310][2014-06-21T20:02:34]i100: Detect begin, 2 packages
[14A0:0310][2014-06-21T20:02:34]i000: Registry key not found. Key =
'SOFTWARE\TestCompany\Client Prerequisites'
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: PrerequisitesMsi,
state: Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: ClientMsi, state:
Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i199: Detect complete, result: 0x0
[14A0:148C][2014-06-21T20:02:35]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[14A0:0310][2014-06-21T20:02:35]i200: Plan begin, 2 packages, action:
Install
[14A0:0310][2014-06-21T20:02:35]i052: Condition 'NOT PrerequisitesVersion
OR (PrerequisitesVersion v1.0.0.0)' evaluates to true.
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser, package
scope: PerMachine
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_PrerequisitesMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_0_PrerequisitesMsi.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleRollbackLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi_rollback.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi.log'
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: PrerequisitesMsi,
state: Absent, default requested: Present, ba requested: Present,
execute:
Install, rollback: None, cache: Yes, uncache: No, dependency: None
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: ClientMsi, state:
Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency:
Register
[14A0:0310][2014-06-21T20:02:35]i299: Plan complete, result: 0x0
[14A0:0310][2014-06-21T20:02:35]i300: Apply begin
[17B8:0FF4][2014-06-21T20:02:35]i360: Creating a system restore point.
[17B8:0FF4][2014-06-21T20:02:41]i361: Created a system restore point.
[14A0:0310][2014-06-21T20:02:41]i000: Caching bundle from:
'C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\.be\TestCompany
Client Setup.exe' to: 'C:\Users\Opt1\AppData\Local\Package
Cache\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\TestCompany Client
Setup.exe'
[14A0:0310][2014-06-21T20:02:41]i320: Registering bundle dependency
provider: {b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}, version: 8.1.229.0
[14A0:17AC][2014-06-21T20:02:41]i336: Acquiring container:
WixAttachedContainer, copy from:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe
[14A0:17AC][2014-06-21T20:02:41]i000: Setting string variable
'WixBundleLastUsedSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\'
[14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
all files from container, erf: 1:4:0
[14A0:17AC][2014-06-21T20:02:41]e000: Error
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
How big is the file?? Regardless the error number you indicate only
show the types of errors I put in the list as I googled...
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Not sure this is the case here. It's not bad RAM or corrupt file, since
once file is copied to user's desktop folder the installation succeeds.
Any other ideas?
On Mon, Jun 23, 2014 at 4:22 PM, Carter Young ecyo...@grandecom.net wrote:
Some Possibilities:
1.
http://www.sevenforums.com/installation-setup/34736-0x80070570-error-code-install-one-easy-solution.html
2. https://answers.yahoo.com/question/index?qid=20091231164201AA1jCpl
3.
http://superuser.com/questions/432368/installation-error-0x80070570-while-installing-windows-7
Carter
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's desktop
and
run it from there. Any ideas what stands behind 0x80070570 error?
Previously, we used to deploy to our clients using single MSI and had no
such issues, but had to know convert it into series of MSI-s we install
using Wix Boostrapper.
Here is the error log:
[14A0:0310][2014-06-21T20:02:34]i001: Burn v3.8.1128.0, Windows v6.1
(Build
7601: Service Pack 1), path:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe,
cmdline: '-burn.unelevated
BurnPipe.{0CC10E48-16BF-4218-9943-634CA2BA234A}
{01AD10FE-F61C-4DE5-B245-B5F3C2D5C5B9} 6072'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234.log'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleName' to value 'TestCompany Client 8.1.229.0'
[14A0:0310][2014-06-21T20:02:34]i100: Detect begin, 2 packages
[14A0:0310][2014-06-21T20:02:34]i000: Registry key not found. Key =
'SOFTWARE\TestCompany\Client Prerequisites'
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: PrerequisitesMsi,
state: Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: ClientMsi, state:
Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i199: Detect complete, result: 0x0
[14A0:148C][2014-06-21T20:02:35]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[14A0:0310][2014-06-21T20:02:35]i200: Plan begin, 2 packages, action:
Install
[14A0:0310][2014-06-21T20:02:35]i052: Condition 'NOT PrerequisitesVersion
OR (PrerequisitesVersion v1.0.0.0)' evaluates to true.
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser, package
scope: PerMachine
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_PrerequisitesMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_0_PrerequisitesMsi.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleRollbackLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi_rollback.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi.log'
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: PrerequisitesMsi,
state: Absent, default requested: Present, ba requested: Present,
execute:
Install, rollback: None, cache: Yes, uncache: No, dependency: None
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: ClientMsi, state:
Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency:
Register
[14A0:0310][2014-06-21T20:02:35]i299: Plan complete, result: 0x0
[14A0:0310][2014-06-21T20:02:35]i300: Apply begin
[17B8:0FF4][2014-06-21T20:02:35]i360: Creating a system restore point.
[17B8:0FF4][2014-06-21T20:02:41]i361: Created a system restore point.
[14A0:0310][2014-06-21T20:02:41]i000: Caching bundle from:
'C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\.be\TestCompany
Client Setup.exe' to: 'C:\Users\Opt1\AppData\Local\Package
Cache\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\TestCompany Client
Setup.exe'
[14A0:0310][2014-06-21T20:02:41]i320: Registering bundle dependency
provider: {b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}, version: 8.1.229.0
[14A0:17AC][2014-06-21T20:02:41]i336: Acquiring container:
WixAttachedContainer, copy from:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe
[14A0:17AC][2014-06-21T20:02:41]i000: Setting string variable
'WixBundleLastUsedSource' to value
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
Setup.exe is 56Mb. So there error is not Wix Boostrapper specific you mean
and instead OS specific? Could it be domain permission issues?
On Mon, Jun 23, 2014 at 5:15 PM, Carter Young ecyo...@grandecom.net wrote:
How big is the file?? Regardless the error number you indicate only
show the types of errors I put in the list as I googled...
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Not sure this is the case here. It's not bad RAM or corrupt file, since
once file is copied to user's desktop folder the installation succeeds.
Any other ideas?
On Mon, Jun 23, 2014 at 4:22 PM, Carter Young ecyo...@grandecom.net
wrote:
Some Possibilities:
1.
http://www.sevenforums.com/installation-setup/34736-0x80070570-error-code-install-one-easy-solution.html
2. https://answers.yahoo.com/question/index?qid=20091231164201AA1jCpl
3.
http://superuser.com/questions/432368/installation-error-0x80070570-while-installing-windows-7
Carter
Quoting Anton Iermolenko aiermole...@iopracticeware.com:
Hi,
Wix burn fails to begin installation on some user machines from
C:\SomeFolder\. To resolve it we have to copy package to user's
desktop
and
run it from there. Any ideas what stands behind 0x80070570 error?
Previously, we used to deploy to our clients using single MSI and had
no
such issues, but had to know convert it into series of MSI-s we
install
using Wix Boostrapper.
Here is the error log:
[14A0:0310][2014-06-21T20:02:34]i001: Burn v3.8.1128.0, Windows v6.1
(Build
7601: Service Pack 1), path:
C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe,
cmdline: '-burn.unelevated
BurnPipe.{0CC10E48-16BF-4218-9943-634CA2BA234A}
{01AD10FE-F61C-4DE5-B245-B5F3C2D5C5B9} 6072'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234.log'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleOriginalSource' to value
'C:\Users\Opt1\AppData\Local\TestCompany\TestCompany Client Setup.exe'
[14A0:0310][2014-06-21T20:02:34]i000: Setting string variable
'WixBundleName' to value 'TestCompany Client 8.1.229.0'
[14A0:0310][2014-06-21T20:02:34]i100: Detect begin, 2 packages
[14A0:0310][2014-06-21T20:02:34]i000: Registry key not found. Key =
'SOFTWARE\TestCompany\Client Prerequisites'
[14A0:0310][2014-06-21T20:02:34]i101: Detected package:
PrerequisitesMsi,
state: Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i101: Detected package: ClientMsi,
state:
Absent, cached: None
[14A0:0310][2014-06-21T20:02:34]i199: Detect complete, result: 0x0
[14A0:148C][2014-06-21T20:02:35]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 0
[14A0:0310][2014-06-21T20:02:35]i200: Plan begin, 2 packages, action:
Install
[14A0:0310][2014-06-21T20:02:35]i052: Condition 'NOT
PrerequisitesVersion
OR (PrerequisitesVersion v1.0.0.0)' evaluates to true.
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser,
package
scope: PerMachine
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_PrerequisitesMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_0_PrerequisitesMsi.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleRollbackLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi_rollback.log'
[14A0:0310][2014-06-21T20:02:35]i000: Setting string variable
'WixBundleLog_ClientMsi' to value
'C:\Users\Opt1\AppData\Local\Temp\TestCompany_Client_8.1.229.0_20140621200234_1_ClientMsi.log'
[14A0:0310][2014-06-21T20:02:35]i201: Planned package:
PrerequisitesMsi,
state: Absent, default requested: Present, ba requested: Present,
execute:
Install, rollback: None, cache: Yes, uncache: No, dependency: None
[14A0:0310][2014-06-21T20:02:35]i201: Planned package: ClientMsi,
state:
Absent, default requested: Present, ba requested: Present, execute:
Install, rollback: Uninstall, cache: Yes, uncache: No, dependency:
Register
[14A0:0310][2014-06-21T20:02:35]i299: Plan complete, result: 0x0
[14A0:0310][2014-06-21T20:02:35]i300: Apply begin
[17B8:0FF4][2014-06-21T20:02:35]i360: Creating a system restore point.
[17B8:0FF4][2014-06-21T20:02:41]i361: Created a system restore point.
[14A0:0310][2014-06-21T20:02:41]i000: Caching bundle from:
'C:\Users\Opt1\AppData\Local\Temp\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\.be\TestCompany
Client Setup.exe' to: 'C:\Users\Opt1\AppData\Local\Package
Cache\{b4b622fc-e6fb-4ad9-b36d-248b9515c6e0}\TestCompany Client
Setup.exe'
[14A0:0310][2014-06-21T20:02:41]i320: Registering bundle dependency
provider:
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
There are a couple issues, but You'd need to test them to be certain: 1. 56 MB may be too big to handle efficiently, although I've seen posts from fellow readers with filesizes in the 500MB range. To test this, replace your actual package with a text file. If the Text File installs, we need to test all the files in the installer, one at a time. If the text file fails, check the log, and troubleshoot for 2. 2. You're correct on the Permissions Issue. I have a hunch that one of the files in your installer is being copied from a network location, and the target machine either: A. Does not have access to the network location. B. Does not have permission to write to the %temp% Location, where the files are extracted to before installing. Carter Quoting Anton Iermolenko aiermole...@iopracticeware.com: Setup.exe is 56Mb. So there error is not Wix Boostrapper specific you mean and instead OS specific? Could it be domain permission issues? On Mon, Jun 23, 2014 at 5:15 PM, Carter Young ecyo...@grandecom.net wrote: How big is the file?? Regardless the error number you indicate only show the types of errors I put in the list as I googled... -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper will launch in Win 8 but not Win 7
I spent sometime digging into this using the debugger but I can't seem to
find anything errors. I was digging into the logs for the installs on my
machine, the VM and the other win 7 user machines. All the failed installs
look like this:
[0778:055C][2014-06-23T10:22:04]i000: Loading managed bootstrapper
application.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to create the
managed bootstrapper application.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to create UX.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to load UX.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed while running
[0778:055C][2014-06-23T10:22:05]i410: Variable: DisplayVersion = 1.0.0.0
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleAction = 4
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleElevated = 0
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleLog =
C:\Users\devinm\AppData\Local\Temp\Client_20140623102202.log
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleManufacturer = ME
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleName = Client
Package
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleOriginalSource =
C:\Users\d\Desktop\ClientBundle.exe
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleProviderKey =
{9c172dc5-e2df-4130-be4e-23af428c1bf7}
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleTag =
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleVersion = 1.0.0.0
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to run
per-user mode.
[0778:055C][2014-06-23T10:22:05]i007: Exit code: 0x8013141a, restarting: No
On my personal Win7 machine and any Win8 machine, the bootstrapper runs just
fine and the logs look like this:
[0B74:093C][2014-06-23T09:50:48]i410: Variable: DisplayVersion = 1.0.0.0
[0B74:093C][2014-06-23T09:50:48]i410: Variable: InstallFolder = C:\Program
Files (x86)\Client
[0B74:093C][2014-06-23T09:50:48]i410: Variable: Netfx4FullVersion =
4.5.50938
[0B74:093C][2014-06-23T09:50:48]i410: Variable: Netfx4x64FullVersion =
4.5.50938
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleAction = 4
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleElevated = 1
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleLog =
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleLog_Client =
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752_0_Client.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleManufacturer = ME
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleName = Client
Package
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleOriginalSource =
C:\Users\d\Desktop\ClientBundle.exe
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleProviderKey =
{9c172dc5-e2df-4130-be4e-23af428c1bf7}
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleRollbackLog_Client
=
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752_0_Client_rollback.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleTag =
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleVersion = 1.0.0.0
My assumption is the bootstrapper isn't able to run as elevated and is
failing. I'm not sure why it works on certain machines and not others
though. All of the users in this office are admins and running the file as
admin doesn't seem to change much.
Thanks for the earlier reply.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374p7595415.html
Sent from the wix-users mailing list archive at Nabble.com.
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper will launch in Win 8 but not Win 7
Argh, I apologize, It looks like I was checking the wrong log. Running as admin on the VM spits out similar logs as my machine for elevation. It still won't run on any Win7 machine other than mine, but all the Win8's work just fine. Any ideas as to what would be missing? That debugger you linked was helpful but It's not showing any fails or errors. Thanks Again -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374p7595416.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] 2 questions re build to build stop installing...
Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues signing the engine in the bootstrapper
Ok, I found out that there was an error in the build script - the signing process was being executed twice. The insignia does not handle the extraction of already signed engine well and the behavior is the result of it. After removing the certificate from the extracted engine.exe, the values in the burn section of this engine.exe are left as they were. After signing the engine and reattaching it back to the bundle everything seems fine. But when installing, the bootstrapper expects that those values were zero before signing, so it zeroes them out and breaks the signature of the engine.exe. That's it. PePri -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-signing-the-engine-in-the-bootstrapper-tp7595376p7595418.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 2 questions re build to build stop installing...
Set the ProductCodes to the same value as 14.4.6.7 in both situations Carter Quoting Steve-Ogilvie steven.ogil...@titus.com: Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 2 questions re build to build stop installing...
Our productcodes change build to build (that way when we release a new version the productcode is different, so the new release is an upgrade) So there is no way in WIX with different productcode/same version (diff 4th digit to recognize same version install?) Thanks, Steve From: eyoung100 [via Windows Installer XML (WiX) toolset] [mailto:ml-node+s687559n7595419...@n2.nabble.com] Sent: June-23-14 3:53 PM To: Steven Ogilvie Subject: Re: 2 questions re build to build stop installing... Set the ProductCodes to the same value as 14.4.6.7 in both situations Carter Quoting Steve-Ogilvie [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=0: Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=1 https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=2 https://lists.sourceforge.net/lists/listinfo/wix-users The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595419.html To unsubscribe from 2 questions re build to build stop installing..., click herehttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=7595417code=U3RldmVuLk9naWx2aWVAdGl0dXMuY29tfDc1OTU0MTd8ODU3MjA0NTIw. NAMLhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595420.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 2 questions re build to build stop installing...
It's possible using Upgrade element. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Steve-Ogilvie [mailto:steven.ogil...@titus.com] Sent: Monday, June 23, 2014 12:55 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 2 questions re build to build stop installing... Our productcodes change build to build (that way when we release a new version the productcode is different, so the new release is an upgrade) So there is no way in WIX with different productcode/same version (diff 4th digit to recognize same version install?) Thanks, Steve From: eyoung100 [via Windows Installer XML (WiX) toolset] [mailto:ml-node+s687559n7595419...@n2.nabble.com] Sent: June-23-14 3:53 PM To: Steven Ogilvie Subject: Re: 2 questions re build to build stop installing... Set the ProductCodes to the same value as 14.4.6.7 in both situations Carter Quoting Steve-Ogilvie [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=0: Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questi ons-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=1 https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=2 https://lists.sourceforge.net/lists/listinfo/wix-users The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595419.html To unsubscribe from 2 questions re build to build stop installing..., click herehttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=7595417code=U3RldmVuLk9naWx2aWVAdGl0dXMuY29tfDc1OTU0MTd8ODU3MjA0NTIw. NAMLhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595420.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration
Re: [WiX-users] Issues signing the engine in the bootstrapper
Seems like a reasonable thing to open a bug against Insignia to handle better, if possible. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Peter Prikryl [mailto:peto.prik...@gmail.com] Sent: Monday, June 23, 2014 12:06 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Issues signing the engine in the bootstrapper Ok, I found out that there was an error in the build script - the signing process was being executed twice. The insignia does not handle the extraction of already signed engine well and the behavior is the result of it. After removing the certificate from the extracted engine.exe, the values in the burn section of this engine.exe are left as they were. After signing the engine and reattaching it back to the bundle everything seems fine. But when installing, the bootstrapper expects that those values were zero before signing, so it zeroes them out and breaks the signature of the engine.exe. That's it. PePri -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-signing-the-engine-in-the-bootstrapper-tp7595376p7595418.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 2 questions re build to build stop installing...
The 4th digit is recognized in the Burn Engine but not in the MSI Product.wxs. You must manually write an install condition to check the 4th version number, or use the same product code with an Upgrade condition, ie: If 14.4.6.7 is installed, perform an upgrade install of 14.4.6.8, that way 14.4.6.8 is the nly product listed in Programs and Features. Carter Quoting Steve-Ogilvie steven.ogil...@titus.com: Our productcodes change build to build (that way when we release a new version the productcode is different, so the new release is an upgrade) So there is no way in WIX with different productcode/same version (diff 4th digit to recognize same version install?) Thanks, Steve From: eyoung100 [via Windows Installer XML (WiX) toolset] [mailto:ml-node+s687559n7595419...@n2.nabble.com] Sent: June-23-14 3:53 PM To: Steven Ogilvie Subject: Re: 2 questions re build to build stop installing... Set the ProductCodes to the same value as 14.4.6.7 in both situations Carter Quoting Steve-Ogilvie [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=0: Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=1 https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=2 https://lists.sourceforge.net/lists/listinfo/wix-users The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595419.html To unsubscribe from 2 questions re build to build stop installing..., click herehttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=7595417code=U3RldmVuLk9naWx2aWVAdGl0dXMuY29tfDc1OTU0MTd8ODU3MjA0NTIw. NAMLhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595420.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast
Re: [WiX-users] 2 questions re build to build stop installing...
I tried with UpgradeVersion Property=SAMEFOUND IncludeMinimum=yes OnlyDetect=yes IncludeMaximum=yes Maximum= the build number, i.e. 3.5.32.6/ Condition Message=The same version of [ProductName] is already installed. Setup will now exit.NOT SAMEFOUND OR Installed/Condition But if product version was changed in first 3 digits it still said the above message Any idea what I did wrong? steve From: Rob Mensching-7 [via Windows Installer XML (WiX) toolset] [mailto:ml-node+s687559n7595422...@n2.nabble.com] Sent: June-23-14 4:29 PM To: Steven Ogilvie Subject: Re: 2 questions re build to build stop installing... It's possible using Upgrade element. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Steve-Ogilvie [mailto:[hidden email]/user/SendEmail.jtp?type=nodenode=7595422i=0] Sent: Monday, June 23, 2014 12:55 PM To: [hidden email]/user/SendEmail.jtp?type=nodenode=7595422i=1 Subject: Re: [WiX-users] 2 questions re build to build stop installing... Our productcodes change build to build (that way when we release a new version the productcode is different, so the new release is an upgrade) So there is no way in WIX with different productcode/same version (diff 4th digit to recognize same version install?) Thanks, Steve From: eyoung100 [via Windows Installer XML (WiX) toolset] [mailto:[hidden email]/user/SendEmail.jtp?type=nodenode=7595422i=2] Sent: June-23-14 3:53 PM To: Steven Ogilvie Subject: Re: 2 questions re build to build stop installing... Set the ProductCodes to the same value as 14.4.6.7 in both situations Carter Quoting Steve-Ogilvie [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=0: Hi folks, I have 2 questions... (Using WIX 3.8) 1. MSI I would like to stop build to build installs (bring up warning?) i.e. i have 14.4.6.7 installed, then I run today's build which is 14.4.6.8 (the product code is different, the upgrade code is the same) this is my upgrade element: MajorUpgrade DowngradeErrorMessage=A newer version of $(var.ProductName) is already installed. Setup will now exit. Schedule=afterInstallValidate AllowSameVersionUpgrades=no AllowDowngrades=no/ the .8 version should not allow to be installed since it is the same version 14.4.6 What can I do to stop that?? 2. Bootstrapper... I would like to do the same things, I installed 14.4.6.7 of my application using the bootstrapper (burn) then using today's build I can still install using my bootstrapper version 14.4.6.8 it has different product code and same upgrade code... what can I do for the bootstrapper to warn they already have the same version installed?? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questi ons-re-build-to-build-stop-installing-tp7595417.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=1 https://lists.sourceforge.net/lists/listinfo/wix-users -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list [hidden email]/user/SendEmail.jtp?type=nodenode=7595419i=2 https://lists.sourceforge.net/lists/listinfo/wix-users The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/2-questions-re-build-to-build-stop-installing-tp7595417p7595419.html To unsubscribe from 2 questions re build to build stop installing..., click here NAMLhttp://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context:
Re: [WiX-users] 2 questions re build to build stop installing...
I have: UpgradeVersion OnlyDetect=yes Minimum=$(var.CURRENT_VERSION) IncludeMinimum=yes Maximum=$(var.CURRENT_VERSION) IncludeMaximum=yes Property=SAMEVERSIONDETECTED / CustomAction Id=MyAlreadyUpdated Error=!(loc.MyAlreadyUpdated) / (both ui/exec sequences) Custom Action=MyAlreadyUpdated After=FindRelatedProductsSAMEVERSIONDETECTED/Custom (this is the same stuff I've been using since wix 3.0) Dave From: Steve-Ogilvie steven.ogil...@titus.com To: wix-users@lists.sourceforge.net Sent: Monday, June 23, 2014 1:39 PM Subject: Re: [WiX-users] 2 questions re build to build stop installing... I tried with UpgradeVersion Property=SAMEFOUND IncludeMinimum=yes OnlyDetect=yes IncludeMaximum=yes Maximum= the build number, i.e. 3.5.32.6/ Condition Message=The same version of [ProductName] is already installed. Setup will now exit.NOT SAMEFOUND OR Installed/Condition But if product version was changed in first 3 digits it still said the above message Any idea what I did wrong? -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Applying two patches causes version number confusion
Sorry, due to legal reasons, I cannot really post my Patch wxs file. But it's basically the same file used in both patches. The only difference between patches are: 1. In PatchCreation element, the Id attribute is different, auto-generated GUID is used each time we patch. 2. In Family element, the SequenceStart attribute MAY or MAY NOT be different. Interestingly, the version number does not appear in the Patch wxs file at all. Oh, one other thing, as it was suggested here that the cause maybe due to 4-digit version number vs. 3-digit number. I tested this out, and that's not the reason. If I go from a.b.c.d to a.b.e.f, both will become a.b.e.f, always keeping the highest version number. -Original Message- From: kjk129 [mailto:kjk...@coolblue.com] Sent: Friday, June 20, 2014 11:01 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Applying two patches causes version number confusion Could you post a copy of both of your Patch WXS files? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Applying-two-patches-causes-version-number-confusion-tp7595340p7595395.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
I have been working on a similar problem today, with same error. [14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0 In my case the problem was induced by changes that I made to my mba, so the problem was not intermittent. In my case I had changed the package's download URL, at run-time, in ResolveSource without calling Engine.SetDownloadSource. When I went back and also called Engine.SetDownloadSource I was able to resolve the problem. In a more general but intermittent situation I would guess that download site access issues, for specific Exe/MsiPackages might result in this error. I have read in another thread that there is a one to one relationship between packages available to burn at build-time and the bundle. So when I used to re-build my bundle but not upload all of the packages so that there were older packages, which I thought had not changed, I also had similar issues. When I changed my process to assure that all packages for a bundle were uploaded I did not have those issues again ( until I made a code change to ResolveSource smile/) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Error-0x80070570-Failed-to-extract-all-files-from-container-erf-1-4-0-tp7595406p7595428.html Sent from the wix-users mailing list archive at Nabble.com. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What is the way to keep the cache of ExePackage in a bundle
Hi Wix guys, Please help. I have a bundle, which contains a ExePackage, call it Bundle1 ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=_969092_2 Version=1.0.0.0 Manufacturer=Saar UpgradeCode=8e4795fe-0062-4e65-819f-ad404f881a9c BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / Chain ExePackage Id=EnableWif DetectCondition=WIF_DetectKeyExists Name=packages\sptoolsDependencies\FakeApp2.exe Vital=no Cache=yes Permanent=yes PerMachine=yes SourceFile=..\Redist\Binaries\FakeApp2.exe InstallCondition=(VersionNT = v6.2) / /Chain /Bundle /Wix Now I have a minor upgrade for other package and I update the authoring a bit and get Bundle2: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=_969092_2 Version=1.0.0.1 Manufacturer=Saar UpgradeCode=8e4795fe-0062-4e65-819f-ad404f881a9c BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / Chain ExePackage Id=EnableWif DetectCondition=WIF_DetectKeyExists Name=packages\sptoolsDependencies\FakeApp2.exe Vital=no Cache=yes Permanent=yes PerMachine=yes SourceFile=..\Redist\Binaries\FakeApp2.exe InstallCondition=(VersionNT = v6.2) / /Chain /Bundle /Wix Now, I put bundles on a share server like \\share\test. I install bundle1 and then install bundle2. Then I stop the share. Go to control panel and do a Repair to bundle2 I expect that the cache for the file will then be called. However, setup is prompt for locating Bundle2. Did I authoring anything wrong? Any input will be appreciated! Thanks, Saar -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn - Error 0x80070570: Failed to extract all files from container, erf: 1:4:0
On 6/23/2014 4:50 AM, Anton Iermolenko wrote: [14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency registration on package: PrerequisitesMsi, bundle scope: PerUser, package scope: PerMachine Is this intentional? You might want to make both packages per-machine. [14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0 This is similar to an existing bug: http://wixtoolset.org/issues/4156/. You might want to add your log as a comment in the bug. -- sig://boB http://joyofsetup.com/ -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Applying two patches causes version number confusion
On 6/23/2014 5:17 PM, George Fleming wrote: 1. In PatchCreation element, the Id attribute is different, auto-generated GUID is used each time we patch. That means you're not using WiX to build the patches but a tool like MsiMsp. Nothing WiX can do to change the outcome. That's why pure-WiX patching was built. -- sig://boB http://joyofsetup.com/ -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trying to re-compile
On 6/20/2014 1:24 PM, Kyle Corsi wrote: Error: light.exe : error LGHT0001 : Item has already been added. Key in dictionary: 're g73E8E70EB9CA78EDD5C4CA9264E4E34F' Key being added: 'reg73E8E70EB9CA78EDD5C4CA9 264E4E34F' Which version of WiX are you using? -- sig://boB http://joyofsetup.com/ -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build warning request
On 6/15/2014 3:30 PM, Tunney, Stephen wrote: Think I have time to squeeze this in for 3.9? Depends on the scope of the fix. Deadline for low-bar changes was 6-June. -- sig://boB http://joyofsetup.com/ -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
