Thank you very much Rob for this information. The exit code thing was also something I had been meaning to ask about. I had written my own simple "MapExitCode.exe" and "RunCommand.exe" to use within an ExePackage because I couldn't find that type of functionality in Burn. Glad to hear about ExitCode being in the engine.
Thanks for pointing me in the right direction. -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, June 29, 2011 2:13 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn: Is it possible/supported to bootstrap Windows Installer 4.5? Burn will support an immediate (aka: forced) restart. You should map exit codes from the MSI4.5 installer using the ExeEngine/ExitCode element so that restart means force restart. Actually, looking at the documentation, it looks like candle is missing suport for that. Heh, the engine (Burn) supports it but the authoring does not. That's a bug. Anyway, that's how you would solve this. After a force reboot, Burn will automatically resume after the reboot and the user logs in again. Then your MSI should be installed and everything is good. On Tue, Jun 28, 2011 at 2:45 PM, Dan Puza <dp...@ultra-scan.com> wrote: > Here is the situation: > > I am creating a Burn bootstrapper to install my app (an MSI) and its > prerequisites. One of the prereqs is SQL Server 2008. One of SQL > Server's prereqs is Windows Installer 4.5. > > Unsurprisingly, the WI4.5 installer exit code is 0xbc2 REBOOT REQUIRED. > Can I manage reboots with Burn and have it reboot and continue > installation? Is that currently possible? If so, how? Ideally if > the reboot could be suppressed until the end of the install, that > would be great; but it seems that due to the nature of this > bootstrapping, it understandably may not be possible. > > So what ends up happening is that on Windows XP I can run my > bootstrapper and it will install WI4.5, and then fail on my MSI. Then > I can just run the same bootstrapper a second time, and it will be > successful on the second attempt. > > So to me, it seems that the older version of WI is loaded into the > bootstrap process memory at the beginning, then after 4.5 is installed > I can't use WI from that same process to install my MSI. Once a new > bootstrapper process is started, that process loads WI 4.5 into its > memory and can successfully install the MSI. > > I attempted to inject the prescribed steps from this page in between > the > WI4.5 install and my MSI within the same bootstrapper process, but > that did not help. > http://www.myitforum.com/articles/2/view.asp?id=7270 > > The relevant log messages are as follows... > > Burn bootstrapper log: > > [0C58:0C5C][2011-06-28T22:40:07.734-08:00]: Setting string variable > 'ProgressPackageName' to value 'A.msi' > [0C70:0C78][2011-06-28T22:40:07.765-08:00]: Applying package: A.msi, > action: Install, path: C:\Documents and Settings\All Users\Application > Data\Package > Cache\{22760F94-ACC0-4A97-BEE8-FEB4BA520C63}v3.0.0.908\Packages\A.msi, > arguments: '(null)' > [0C70:0C78][2011-06-28T22:40:07.812-08:00]: Error 0x80070641: Failed > to install MSI package. > [0C70:0C78][2011-06-28T22:40:07.812-08:00]: Error 0x80070641: Failed > to execute MSI package. > [0C58:0C5C][2011-06-28T22:40:07.812-08:00]: Error 0x80070641: Failed > to configure per-machine MSI package. > [0C58:0C5C][2011-06-28T22:40:07.812-08:00]: Application requested > retry of > package: A.msi, encountered error: 0x80070641. Retrying... > [0C58:0C5C][2011-06-28T22:40:10.812-08:00]: Setting string variable > 'ProgressPackageName' to value 'A.msi' > [0C70:0C78][2011-06-28T22:40:10.812-08:00]: Applying package: A.msi, > action: Install, path: C:\Documents and Settings\All Users\Application > Data\Package > Cache\{22760F94-ACC0-4A97-BEE8-FEB4BA520C63}v3.0.0.908\Packages\A.msi, > arguments: '(null)' > [0C70:0C78][2011-06-28T22:40:10.812-08:00]: Error 0x80070641: Failed > to install MSI package. > [0C70:0C78][2011-06-28T22:40:10.812-08:00]: Error 0x80070641: Failed > to execute MSI package. > [0C58:0C5C][2011-06-28T22:40:10.812-08:00]: Error 0x80070641: Failed > to configure per-machine MSI package. > [0C58:0C5C][2011-06-28T22:40:10.812-08:00]: Application requested > retry of > package: A.msi, encountered error: 0x80070641. Retrying... > [0C58:0C5C][2011-06-28T22:40:13.812-08:00]: Setting string variable > 'ProgressPackageName' to value 'A.msi' > [0C70:0C78][2011-06-28T22:40:13.812-08:00]: Applying package: A.msi, > action: Install, path: C:\Documents and Settings\All Users\Application > Data\Package > Cache\{22760F94-ACC0-4A97-BEE8-FEB4BA520C63}v3.0.0.908\Packages\A.msi, > arguments: '(null)' > [0C70:0C78][2011-06-28T22:40:13.812-08:00]: Error 0x80070641: Failed > to install MSI package. > [0C70:0C78][2011-06-28T22:40:13.828-08:00]: Error 0x80070641: Failed > to execute MSI package. > [0C58:0C5C][2011-06-28T22:40:13.828-08:00]: Error 0x80070641: Failed > to configure per-machine MSI package. > [0C58:0C5C][2011-06-28T22:40:13.828-08:00]: Application requested > retry of > package: A.msi, encountered error: 0x80070641. Retrying... > [0C58:0C5C][2011-06-28T22:40:16.828-08:00]: Setting string variable > 'ProgressPackageName' to value 'A.msi' > [0C70:0C78][2011-06-28T22:40:16.828-08:00]: Applying package: A.msi, > action: Install, path: C:\Documents and Settings\All Users\Application > Data\Package > Cache\{22760F94-ACC0-4A97-BEE8-FEB4BA520C63}v3.0.0.908\Packages\A.msi, > arguments: '(null)' > [0C70:0C78][2011-06-28T22:40:16.843-08:00]: Error 0x80070641: Failed > to install MSI package. > [0C70:0C78][2011-06-28T22:40:16.843-08:00]: Error 0x80070641: Failed > to execute MSI package. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Error 0x80070641: Failed > to configure per-machine MSI package. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Error 0x80070641: Failed > to execute MSI package. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Error 0x80070641: Failed > to execute apply. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Removing bundle dependency key: > {1367b97f-2b7f-4d0a-8a24-a5f1ef77968e} > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Removing cached bundle: > {1367b97f-2b7f-4d0a-8a24-a5f1ef77968e}, from path: C:\Documents and > Settings\Administrator\Local Settings\Application Data\Package > Cache\{1367b97f-2b7f-4d0a-8a24-a5f1ef77968e} > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Error 0x80004001: UX > cannot erase variables by passing a NULL string, yet. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Error 0x80004001: UX > cannot erase variables by passing a NULL string, yet. > [0C58:0C5C][2011-06-28T22:40:16.843-08:00]: Apply complete, result: > 0x80070641 restart: No > [0C58:0C5C][2011-06-28T22:41:15.375-08:00]: Shutting down, exit code: > 0x80070641 > > > MSI log: > > === Verbose logging started: 6/28/2011 22:40:16 Build type: SHIP > UNICODE > 3.01.4000.4039 Calling process: E:\X\Setup.exe === MSI (c) (70:38) > [22:40:16:828]: Resetting cached policy values MSI (c) (70:38) > [22:40:16:828]: Machine policy value 'Debug' is 0 MSI (c) (70:38) > [22:40:16:828]: ******* RunEngine: > ******* Product: C:\Documents and Settings\All > Users\Application Data\Package > Cache\{22760F94-ACC0-4A97-BEE8-FEB4BA520C63}v3.0.0.908\Packages\A.msi > ******* Action: > ******* CommandLine: ********** MSI (c) (70:38) > [22:40:16:828]: Client-side and UI is none or basic: > Running entire install on the server. > MSI (c) (70:38) [22:40:16:828]: Grabbed execution mutex. > MSI (c) (70:38) [22:40:16:828]: Windows Installer proxy information > not correctly registered > > MSI (c) (70:38) [22:40:16:828]: Failed to connect to server. Error: > 0x80004005 > > MSI (c) (70:38) [22:40:16:828]: Failed to connect to server. > MSI (c) (70:38) [22:40:16:828]: MainEngineThread is returning 1601 === > Verbose logging stopped: 6/28/2011 22:40:16 === > > > > ---------------------------------------------------------------------- > -------- All of the data generated in your IT infrastructure is > seriously valuable. > Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
