New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Burn: Installation does not resume after restart #4486
Comments
Pull request: wixtoolset/wix3#125
|
|
|
Thanks for catching the regression!
|
Hi, [09A8:09A4][2014-08-18T14:46:48]i007: Exit code: 0x80048bc7, restarting: Yes [0924:0928][2014-08-18T14:51:12]i001: Burn v3.9.805.0, Windows v6.1 (Build 7601: Service Pack 1), path: C:\ProgramData\Package Cache{5a62a5a2-7b9f-412b-88aa-0a0a9300262f}\Setup.exe, cmdline: '-burn.unelevated BurnPipe.{98D6FAC4-95F6-40B2-A850-CA2F2051AA80} {2F313167-1712-480A-B60A-BD4943979EB5} 2328 /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3_(Alpha)20140818125149.log" /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3(Alpha)20140818125149.log" /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3(Alpha)_20140818125149.log"'
|
An additional note: On a repair the BundleResumeCommandLine resolves to: Could it be that PlanSetResumeCommand is called more than once and CoreRecreateCommandLine is just appending to what is already there?
|
Can you post a full log?
|
Following the logs for a pristine installation and a repair. Please note that I have forced the restart in case of a successful installation, which means that in repair mode the setup ends up in an infinite loop. [09BC:02F0][2014-08-19T08:34:59]i001: Burn v3.9.805.0, Windows v6.1 (Build 7601: Service Pack 1), path: C:\Users\DSedlmay\Desktop\Debug\Setup.exe, cmdline: '' [0834:0838][2014-08-19T09:06:27]i001: Burn v3.9.805.0, Windows v6.1 (Build 7601: Service Pack 1), path: C:\ProgramData\Package Cache{58b99296-7aa7-4c1e-9d95-80b4a6385df9}\Setup.exe, cmdline: '-burn.unelevated BurnPipe.{92E0AF2F-D3C9-4E1F-B1B2-69922B75B479} {E3523F3A-6402-4F40-837C-02DE3599E2CF} 2088 /modify /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3_(Alpha)20140819090427.log" /modify /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3(Alpha)20140819090427.log" /repair /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\Thermo_Chromeleon_7.3(Alpha)_20140819090427.log"'
|
Opened new bug for duplicate switches as http://wixtoolset.org/issues/4510/.
|
I am just migrating our setup from version 3.6 to version 3.9 RC2.
Some of our packages require a computer restart in the middle and in version 3.6 the installer resumed installation after restart, but does not in version 3.9 RC2.
A short investigation shows that burn writes a key into HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce for being able to resume after a computer restart.
In version 3.6 the key has the following value:
"C:\ProgramData\Package Cache{70f6b4b1-f983-4421-84bb-91eed6199fe2}\Setup.exe" /burn.log.append "C:\Users\XXXXXXXX\AppData\Local\Temp\XXXXXX_XXXXXXXXXX_X.X_XXX_(XXXXX)_20140730171808.log" /uninstall /burn.runonce
whereas in version 3.9 RC2 it is:
/burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\XXXXXX_XXXXXXXXXX_X.X_(XXXXX)20140730170506.log" /burn.log.append "C:\Users\DSedlmay\AppData\Local\Temp\XXXXXX_XXXXXXXXXX_X.X(XXXXX)_20140730170506.log" /burn.runonce
It seems, that instead of the executable name a part of the arguments is duplicated.
I think I can remember to have read once, that resuming the installation - even after a computer crash - is one of the outstanding features of burn. Unfortunately it seems to be broken now.
The text was updated successfully, but these errors were encountered: