I've heard people not having issues launching Burn from a system service in the past. If you're installing a per-machine Bundle seems like many things might work. If this is the same case that someone pointed me to on StackOverflow then the error messages presented there suggested the service was doing horrible things to the user context and confusing the world.
-----Original Message----- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, December 16, 2013 11:29 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Managed Bootstrapper fails to load - Errror 0x80040150 >>The service runs under a user who is in the local administrators >>group. The BurnBasedSetupKit.exe could very well be invoked by the service when the machine is running but there is no user logged in. [Note: When the BurnBasedSetupKit.exe kit is invoked interactively, everything works fine.] I know this has been discussed on this list before, but I will point out that Burn is not designed to be executed in a service context. I know others have struggled with these issues and some have reported that they got it to work. The problem that you are describing is typical of launching any application of similar complexity, which was not designed to be a service, using a launcher (like AsServiuice.exe). I know it sounds like it should work and it may for simple programs, but I would not do this for Burn. When the interactive user loges on, that user's profile is automatically loaded and various system resources related to using the desktop are initialized as part of the logon process. Those events do not happen when a service is started. Any code which is going to interact with the registry in the context of a user needs to load the user's profile, which probably is not happening in this situation. This is not something one would expect Burn to do. Also in looking at Burn code when it needs to launch another application t calls CreateProcess, whereas service code should initialize desktop structures and pass them to CreateProcessAsUser. So it seems to me that there are lots of ways in which running Burn (or any application not designed to be a Service) as a Service is likely to have issues. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-fails-to-load-Errror-0x80040150-tp7591316p7591342.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
