[wix-users] WiX and SCCM [P]

[Hoover, Jacob]

That's assuming Steven is using a RTM release of WiX and not a custom one.  From what my digging is showing, I think 3.10.3 used 3.10.3007.0 for WixStdBA.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Sean Hall
Sent: Monday, May 08, 2017 11:02 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] WiX and SCCM [P]

The Burn log doesn't seem to match the Event Viewer entry, the log is around 10:20 and the Event Viewer is around 14:28.

According to the Event Viewer entry, the bundle seems to have crashed. With any luck, there should be a crash dump file on that machine and you could use the debug symbols from the 3.10.3 release page to find out exactly where it was at the time of the crash.

On Fri, May 5, 2017 at 3:26 PM, Steven Ogilvie <Steven.Ogilvie at titus.com>
wrote:

> Classification: Public
>
> This is WiX 3.10.3
>
> Event viewer:
>
> - <Event 
> xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Application Error" />
>   <EventID Qualifiers="0">1000</EventID>
>   <Level>2</Level>
>   <Task>100</Task>
>   <Keywords>0x80000000000000</Keywords>
>   <TimeCreated SystemTime="2017-05-05T14:28:06.000000000Z" />
>   <EventRecordID>3611</EventRecordID>
>   <Channel>Application</Channel>
>   <Computer>client.tituscloud.local</Computer>
>   <Security />
>   </System>
> - <EventData>
>   <Data>TITUSClassificationSetup.exe</Data>
>   <Data>16.9.10.12</Data>
>   <Data>581cf0a1</Data>
>   <Data>wixstdba.dll</Data>
>   <Data>3.10.3504.0</Data>
>   <Data>581cf0a5</Data>
>   <Data>c0000005</Data>
>   <Data>00001736</Data>
>   <Data>64c</Data>
>   <Data>01d2c5aba0deddfb</Data>
>   <Data>C:\Windows\TEMP\{22915F6C-4F53-4762-8951-65E02A18FC25}\.cr\
> TITUSClassificationSetup.exe</Data>
>   <Data>C:\Windows\TEMP\{180A2C13-F0AA-4193-86D4-
> 776CD289075B}\.ba\wixstdba.dll</Data>
>   <Data>b63c10bf-aed2-4a89-8ca5-7459a1917dce</Data>
>   <Data />
>   <Data />
>   </EventData>
>   </Event>
>
> Bootstrapper log file
>
> Creating a system restore point.
> [0F80:080C][2017-05-05T10:19:26]w363: Could not create system restore 
> point, error: 0x80070422. Continuing...
> ...
> [0A30:0A1C][2017-05-05T10:20:02]i007: Exit code: 0x0, restarting: No
>
> Don't see any other issues in the bootstrapper log file
>
>
> This message has been marked as Public by Steven Ogilvie on May 5, 
> 2017
> 4:26:50 PM. Classification provided by TITUS.
>
>
>
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On 
> Behalf Of Sean Hall
> Sent: May 3, 2017 6:16 PM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] WiX and SCCM
>
> Can you get the Burn log, and any relevant events from the Application 
> or System event log?
>
> On Wed, May 3, 2017 at 12:06 PM, Steven Ogilvie 
> <Steven.Ogilvie at titus.com>
> wrote:
> >
> > Rob/Bob
> >
> > Has anyone else noticed this?
> >
> > Steve
> >
> >
> > -----Original Message-----
> > From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On 
> > Behalf Of Justin Cox
> > Sent: May 2, 2017 6:22 PM
> > To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> > Subject: Re: [wix-users] WiX and SCCM
> >
> > Is your SCCM team running the installer under SYSTEM?  This can 
> > cause those issues, especially if you're using a bootstrapper or 
> > network resources.  In interactive mode, the shell runs as the 
> > logged on user, so that's the only immediate difference I can think of.
> >
> > On Tue, May 2, 2017 at 3:08 PM Steve Ogilvie <SOGILVIE at msn.com> wrote:
> >
> > > Hi folks,
> > >
> > >
> > > Customers have complained that from an old version of our product 
> > > (using WiX 3.10) to newer versions of our product (using WiX 
> > > 3.10.2 and 3.10.3) are complaining that when the WiX installer is 
> > > done SCCM is getting a non zero return value (sometimes code 255 or -1073741819.
> > >
> > >
> > > To fix this they have had to use "requires interactive mode. "
> > >
> > >
> > > Since I don't have SCCM at the company I work for I have been 
> > > using PSEXEC.exe to mimic, PSEXEC -s <install.exe> works while 
> > > PSEXEC <isntall.exe> does not (gets non zeror return value)
> > >
> > >
> > > The MSI"s are all returning 0 and the BootStrapper log is 
> > > returning
> > > 0 as well...
> > >
> > >
> > > Has anyone else seen/heard this issue?
> > >
> > >
> > > Much 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/