[wix-users] Installing using SCCM and Bootstrapper returns -1073741819 [Public]

[Christopher Painter]

Typically but not always.


Can we get more information on how the Burn EXE is being called by SCCM?  Is it a deployment or task sequence?  Package/Program or Application Model?  SCCM Client logs would be helpful but I'm guessing the customer isn't going to want to publish those.


We use a small MSI that we made that puts a shortcut on the desktop that when ran fires up a process as SYSTEM.  This helps us simulate and test most of our SCCM issues before actually putting our builds into SCCM.

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Steven Ogilvie <Steven.Ogilvie at titus.com>
Sent: Thursday, February 9, 2017 7:11 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Installing using SCCM and Bootstrapper returns -1073741819 [Public]

Classification: Public
Further information:

SCCM runs as the local system account.  If they run SCCM as domain admin, then SCCM does not report this error.


This message has been marked as Public by Steven Ogilvie on February 9, 2017 8:11:51 AM. Classification provided by TITUS.





-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Edwin Castro
Sent: February 7, 2017 2:19 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Installing using SCCM and Bootstrapper returns -1073741819

If the bundle log shows that the bootstrapper completed and is returning 0, then it is very unlikely, but not impossible, that the bootstrapper is generating the access violation. If this is really the bootstrapper, then the issue must be in the clean up code that is executed as the bootstrapper is terminating. If this is really in the bootstrapper, then this should reproduce even without SCCM.

--
Edwin G. Castro

On Tue, Feb 7, 2017 at 8:41 AM, Herman van Drie <hvandrie at outlook.com> wrote:
> Dec:-1073741819 = hex:‭FFFFFFFFC0000005‬ --> C0000005 =
> ACCESS_VIOLATION Just out of the blue: are you trying to access something that is already in-use explicitly (file/process)?
>
> Herman
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On
> Behalf Of Steve Ogilvie
> Sent: dinsdag 7 februari 2017 17:37
> To: WiX User List <wix-users at lists.wixtoolset.org>
> Subject: [wix-users] Installing using SCCM and Bootstrapper returns
> -1073741819
>
> Hi folks,
>
> I am using the WiX Bootstrapper/Bundle for launching our installers…
>
> I have a customer issue where our product used to work fine with SCCM
> and now with the last two versions of our product they are getting a
> return value from the Bootstrapper as -1073741819 even though the
> Bootstrapper/bundle log file is returning 0…
>
> Customer using SCCM to install using bootstrapper. BootStrapper for version 3.10 returns 0 and SCCM returns error code 0.  We are using WiX “3.10”
>
> Customer using SCCM to install using bootstrapper. BootStrapper for version 3.10.2 returns 0 but SCCM returns error code -1073741819 .  We are using WiX “3.10.2”.
>
> Do you have any ideas what may be causing the return code of -1073741819?
>
> Thanks,
>
> Steve
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/