[wix-users] Weird chained EXE behaviour

[Alex Tuppen]

That was our best guess as to what was happening, but it doesn't explain
why the EXE worked for one part of the chain, but not for the other.

On Thu, 7 Sep 2017 at 16:53 Hoover, Jacob <Jacob.Hoover at greenheck.com>
wrote:

> I would verify you didn’t have a “helpful” editor changing - into –.
>
>
>
> *From:* Alex Tuppen [mailto:alex.tuppen at gmail.com]
> *Sent:* Thursday, September 7, 2017 10:51 AM
> *To:* Carlos Sosa <carlos.sosa.us at outlook.com>; WiX Toolset Users Mailing
> List <wix-users at lists.wixtoolset.org>
>
>
> *Cc:* Hoover, Jacob <Jacob.Hoover at greenheck.com>
> *Subject:* Re: [wix-users] Weird chained EXE behaviour
>
>
>
> In the end we tried testing it by removing the EXE from the chain, using
> the bundle to install everything else and then running the EXE outside of
> the installer. This resulted in the same error as before (copy pasting the
> parameters from the XML in Visual Studio), to which my boss suggested
> retyping the parameters, which worked. I have no idea how a bug like this
> works because the exact same characters were used for when the EXE worked
> and when it didn't but the fix worked outside the bundle and again when
> copied back into VS.
>
>
>
> Alex
>
>
>
> On Wed, 6 Sep 2017 at 21:10 Carlos Sosa <carlos.sosa.us at outlook.com>
> wrote:
>
> I have/had a similar problem, while installing in certain sequence my
> bundle fails, if I moved the sequence around then it would work, since the
> order was not important for me, I just changed it.
> Also ".......Note, the bundle will be running this exe elevated if the
> bundle is per-machine, which may be the difference between being in the
> chain verses you running it manually after the fact."  Had this problem
> too, and couldn't get it to work, looks like there was a bug in the Bundle,
> because trying to force it to run "per-machine" would still fail in my case.
>
> I'm very interested to know if you get it to work.
> Best.
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Hoover, Jacob via wix-users
> Sent: Wednesday, September 6, 2017 10:23 AM
> To: Alex Tuppen <alex.tuppen at gmail.com>; WiX Toolset Users Mailing List <
> wix-users at lists.wixtoolset.org>
> Cc: Hoover, Jacob <Jacob.Hoover at greenheck.com>
> Subject: Re: [wix-users] Weird chained EXE behaviour
>
> “an EXE to install the certificate and finish configuration”
>
> Is this a custom exe you wrote? Your bundle log will show you what the
> bundle is doing, but if the fault is inside this custom exe, you will have
> to rely on it for any logs to see what the actual error is. Note, the
> bundle will be running this exe elevated if the bundle is per-machine,
> which may be the difference between being in the chain verses you running
> it manually after the fact.
>
> Are you including the exe twice in the bundle? Bundle authoring and logs
> would help further diagnose.
>
> From: Alex Tuppen [mailto:alex.tuppen at gmail.com]
> Sent: Wednesday, September 6, 2017 11:04 AM
> To: Hoover, Jacob <Jacob.Hoover at greenheck.com>; WiX Toolset Users Mailing
> List <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] Weird chained EXE behaviour
>
> I have done that, it just says that the parameters passed are not allowed,
> but they work fine from the other part of the chain and when run outside
> the bundle. I appreciate that I am clutching at straws but as I have
> nothing to go on I also have nothing to lose by asking just in case someone
> has an idea.
>
> The only thing that I have seen in the bundle's log is that it never says
> that it has applied the EXE during the application stage, but I know it
> runs because I can see it generate logs.
>
> Alex
>
> On Wed, 6 Sep 2017 at 16:54 Hoover, Jacob <Jacob.Hoover at greenheck.com
> <mailto:Jacob.Hoover at greenheck.com>> wrote:
> "Bombs out" isn't very descriptive.  I'd suggest looking at the logs of
> the exe installer (or enable verbose logging if the exe supports it) and
> then look at the actual log to root cause the problem.
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org<mailto:
> wix-users-bounces at lists.wixtoolset.org>] On Behalf Of Alex Tuppen via
> wix-users
> Sent: Wednesday, September 6, 2017 10:47 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:
> wix-users at lists.wixtoolset.org>>
> Cc: Alex Tuppen <alex.tuppen at gmail.com<mailto:alex.tuppen at gmail.com>>
> Subject: [wix-users] Weird chained EXE behaviour
>
> Hi,
>
> I am having some trouble with an EXE in a chain, I have a custom
> bootstrapper which installs different things from the chain based on user
> input. Specifically it installs Microsoft Operations Manager Agent or
> Microsoft Operations Manager Gateway, then runs some MSIs to configure them
> and then an EXE to install the certificate and finish configuration. The
> EXE is behaving strangely though, if I run it after installing the agent it
> works fine, if I run it after installing the gateway however it bombs out.
> I am using exactly the same chain entry for both instances and nothing is
> changing and the EXE behaves correctly outside the bundle.
>
> Does anyone know of anything in a WiX bundle, with a custom bootstrapper,
> which would cause an exe to behave like this?
>
> Kind regards,
>
> Alex
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
>