Thanks for the confirmation. Our new plan is to figure out what's wrong (or different) with this particular server.
> -----Original Message----- > From: Rob Mensching [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2008 5:47 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] NetFxScheduleNativeImage and logging > > Yes, all of the Exit macros should log. That's why verbose log files > are so useful for us. We get almost a "stack trace" to the exact > failure. At this point, I think you should switch to suspecting the > Windows Installer on this machine. Is it possible that the > ::MsiProcessMessage() is causing the whole thing to blow up? That does > end up as a cross process call I believe so it could be something > screwy on the machine that's causing the failure. > > > > -----Original Message----- > From: John Vottero [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2008 14:23 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] NetFxScheduleNativeImage and logging > > I've been trying to figure out a problem with NetFxScheduleNativeImage > in WiX V2.0.4820. I've been looking at the source code and I thought > that all of the ExitOnFailure(hr, "Some error message") calls were just > dropping the error message. I got that idea from looking at dutil.h > which defines ExitTrace to be nothing. Now, I just realized that > wcautil.h overrides that so that ExitTrace calls WcaLogError. > > Could someone confirm that if NetFxScheduleImage in WiX v2.0.4820 hits > a > line like: > > ExitOnFailure(hr, "failed to schedule > NetFxExecuteNativeImageInstall action"); > > and, hr contains an error, the message *should* be written to the msi > log, right? Since I'm not seeing any of messages in the log, I'm > looking for a code path that fails without calling ExitOnFailure, > right? > > I've compared much of the relevant code in v2.0.4820, v2.0.5805 and > v3.0.4721 and I don't see any significant differences so, if it should > log something in v3.0.4721, I think it should log it in v2.0.4820. > > I have the code path in SchedNetFx narrowed down to the area between > the > end of the loop and the call to WcaFinalize and in that space, two MSI > Record handles are created and closed. That could be the call to > WcaProgressMessage and a call to WcaLog but, I don't get a message in > the log file. > > Thanks! > > > ----------------------------------------------------------------------- > -- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ----------------------------------------------------------------------- > -- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
