Quantcast

Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Dan Puza
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

robmen
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 <[hidden email]> 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
> [hidden email]
> 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Dan Puza
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:[hidden email]]
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 <[hidden email]> 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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Klaus Gütter
In reply to this post by robmen
Rob Mensching-7 wrote
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.
Any news on this one?

ExeEngine/ExitCode seems not to be in 3.6 Beta. Is there any workaround?

Regards, Klaus Gütter
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

robmen
Is there a bug trackinng this work? If not, it probably got lost.

On Thu, Dec 15, 2011 at 11:44 AM, Klaus Gütter <[hidden email]>wrote:

>
> Rob Mensching-7 wrote
> >
> > 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.
> >
> Any news on this one?
>
> ExeEngine/ExitCode seems not to be in 3.6 Beta. Is there any workaround?
>
> Regards, Klaus Gütter
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Is-it-possible-supported-to-bootstrap-Windows-Installer-4-5-tp6526800p7098296.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Server Consolidation
> Server virtualization is being driven by many needs.
> But none more important than the need to reduce IT complexity
> while improving strategic productivity.  Learn More!
> http://www.accelacomm.com/jaw/sdnl/114/51507609/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Klaus Gütter-2
Added to bug tracker (#3468329)

Klaus

-----Ursprüngliche Nachricht-----
Von: Rob Mensching [mailto:[hidden email]]
Gesendet: Sunday, 1. January 2012 21:04
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Is there a bug trackinng this work? If not, it probably got lost.

On Thu, Dec 15, 2011 at 11:44 AM, Klaus Gütter <[hidden email]>wrote:

>
> Rob Mensching-7 wrote
> >
> > 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.
> >
> Any news on this one?
>
> ExeEngine/ExitCode seems not to be in 3.6 Beta. Is there any workaround?
>
> Regards, Klaus Gütter
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Is-
> it-possible-supported-to-bootstrap-Windows-Installer-4-5-tp6526800p709
> 8296.html Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ----------------------------------------------------------------------
> -------- 10 Tips for Better Server Consolidation Server virtualization
> is being driven by many needs.
> But none more important than the need to reduce IT complexity while
> improving strategic productivity.  Learn More!
> http://www.accelacomm.com/jaw/sdnl/114/51507609/
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Andrey
In reply to this post by robmen
What I have to do in my custom managed bootstrapper application to support Reboot after installing Windows Installer 4.5 package?

Now in log i see:
[0634:0678][2012-05-31T10:47:55]: Applying execute package: WindowsInstaller45Xp, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\86E1CC622DBF4979717B8F76AD73220CDB70400B\redist\WindowsXP-KB942288-v3-x86.exe, arguments: '"C:\Documents and Settings\All Users\Application Data\Package Cache\86E1CC622DBF4979717B8F76AD73220CDB70400B\redist\WindowsXP-KB942288-v3-x86.exe" /norestart /quiet'
[0480:0428][2012-05-31T10:48:20]: Applied execute package: WindowsInstaller45Xp, result: 0x0, restart: Initiated
[0480:0428][2012-05-31T10:48:20]: Apply complete, result: 0x0, restart: Initiated, ba requested restart:  No
[0480:0428][2012-05-31T10:48:38]: Shutting down, exit code: 0x0

And if I reboot manually then installation continues.

How do I need to reboot right in my custom BA?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Andrey
I found an answer by myself. It's easy:

In a ApplyComplete event handler all I need is

	if (e.Restart == ApplyRestart.RestartRequired || e.Restart == ApplyRestart.RestartInitiated)
	{
		m_Root.State = InstallationState.RebootRequired;
		e.Result = Result.Restart;
	}

But! In my custom BA I have to save the state (options, selected by user) and then restore this state after  reboot, hiding the options UI. Otherwise my bootstrapper UI will start from the beginning and asks all the options again.

So I have one more question: How to detect if installator was run automatically after reboot? Should I save some mark for this before reboot, as I did in a fast-made workaround? Or (I hope!) there is some internally supported by bootstrapper engine way?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Burn: Is it possible/supported to bootstrap Windows Installer 4.5?

Bob Arnson-6
On 31-May-12 04:41, Andrey wrote:
> So I have one more question: How to detect if installator was run
> automatically after reboot?
See the resumeType passed in the BOOTSTRAPPER_COMMAND.

--
sig://boB
http://joyofsetup.com/


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Loading...