The BA runs unelevated so that operations it does are in the correct user
context and it does not modify machine state. This is standard Burn
behavior and it happens any time a Bundle is started elevated.
I don't know the root cause of the issue you are seeing there. There was a
bug a long time ago that looked like that but it appears you are using the
RTM version of WiX v3.7 and the bug was fixed (otherwise, we'd have lots of
people talking about the failure).
Is it possible that something is overzealously cleaning out the %TEMP%
drive? A Process Monitor watching that folder could be interesting. Maybe
some other process is coming along while Burn is working and deleting stuff
out from under it.
Or maybe there is some weird case you've found that exposes a different bug
in Burn. Not enough detail to really understand right now.
On Sat, May 4, 2013 at 1:33 AM, Vic Allen <alphaq...@hotmail.com> wrote:
> Could this be the root cause of a failed installation we are seeing (?):
> Error 0x80070002: Failed to cache bundle from:
> 'C:\Users\user1\AppData\Local\Temp\{6B4546B4-B3AA-4063-821F-4C89938914C9}\.be\Setup.exe'
> to 'C:\ProgramData\Package
> Cache\{6B4546B4-B3AA-4063-821F-4C89938914C9}\Setup.exe'
>
> The install should require elevated privileges as it is perMachine. Why
> would burn be attempting to unelevate? I greatly appreciate any help here.
> > From: r...@robmensching.com
> > Date: Sat, 4 May 2013 00:11:44 -0700
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Understanding Burn log cmdline
> >
> > The user is launching the bundle executable elevated and Burn is
> attempting
> > to unelevate. The GUIDs are cookies to do a secure handshake. It's all
> > internal details and could change in future versions of the engine (all
> the
> > "burn." parameters are like this).
> >
> > You can see all the code in src\burn\engine.
> >
> >
> > On Sat, May 4, 2013 at 12:04 AM, Vic Allen <alphaq...@hotmail.com>
> wrote:
> >
> > > More specifically, what does -burn.unelevated mean? Does it suggest
> the
> > > user is using a non-admin account to perform the install?Also what
> does the
> > > number code following the GUIDs (and the GUIDs for that matter)
> represent?
> > > Is it unique for every installation? When I execute the same burn
> > > executable with a simple click using a non-admin account I simply see
> an
> > > empty string (cmdline: '') for the cmdline in my install.log. I'm
> > > wondering what the user would be doing different to generate that
> entry in
> > > the log. > From: alphaq...@hotmail.com
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Sat, 4 May 2013 02:08:41 +0000
> > > > Subject: [WiX-users] Understanding Burn log cmdline
> > > >
> > > > I'm using Burn v3.7.1224.0. What is the meaning of the following
> > > cmdline present in the install log:
> > > > cmdline: '-burn.unelevated
> > > BurnPipe.{BA274BA7-1C44-402F-9E0C-5919915C3ADC}
> > > {1B81FC8C-86AE-416C-AD37-DC7B377EDBCB} 716'
> > > >
> > > > In other words, under what circumstances would a user execute the
> > > installer that would produce such a cmdline in the log?
> > > >
> > >
> ------------------------------------------------------------------------------
> > > > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > > > It's a free troubleshooting tool designed for production
> > > > Get down to code-level detail for bottlenecks, with <2% overhead.
> > > > Download for free and get started troubleshooting in minutes.
> > > > http://p.sf.net/sfu/appdyn_d2d_ap2
> > > > _______________________________________________
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > > It's a free troubleshooting tool designed for production
> > > Get down to code-level detail for bottlenecks, with <2% overhead.
> > > Download for free and get started troubleshooting in minutes.
> > > http://p.sf.net/sfu/appdyn_d2d_ap2
> > > _______________________________________________
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > It's a free troubleshooting tool designed for production
> > Get down to code-level detail for bottlenecks, with <2% overhead.
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap2
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
