windows-installerinstallshieldinstallshield-2015

InstallShield error: "Failed to launch proxy process"


I am trying to build an installer using InstallShield 2015 and during installation it spits out an error like this in the GUI:

The wizard was interrupted before ProductNameGoesHere was installed.

The only problematic line I see in the logs is this:

1-9-2018[11:15:33 PM]: Failed to launch proxy process 'C:\Users\rsheink\AppData\Local\Temp\{21683818-C622-4EE7-B2D1-A407FE37E1E4}\setup64.exe', error 2

Can somebody please help Me with that?


Solution

  • UPDATE: This line is interesting in the log: "UI DLL: Display Error: The installation of TenLira appears to have failed. Do you want to continue the installation?"

    You seem to be running the command line EXE parcel command line: /s /x /v"/qn". So this appears to be an uninstall. Did you try this command line manually? It seems the /x and the /v"/qn" are redundant - both indicating uninstall. The first is a setup.exe-specific command, whereas the latter is passed to msiexec.exe. I would try with one or the other. I would prefer to keep /v"/qn" and remove /x as my first test.

    Or could you just uninstall by product code instead? That should be more reliable, and you could potentially eliminate the whole setup.exe from your bundle? (the cached MSI in %SystemRoot%\Installer should be enough - especially important if the setup.exe is very big). Also try without hard coded logging in the msiexec.exe command if there are problems (perhaps the suite project does its own logging).

    msiexec.exe /x {YOUR-PRODUCT-GUID-HERE} /QN /L*V "C:\msilog.log"

    Quick Parameter Explanation:

    /X = run uninstall sequence
    /QN = run completely silently
    /L*V "C:\msilog.log"= verbose logging at path specified
    {YOUR-PRODUCT-GUID-HERE} = product guid of app to uninstall.
    

    Some links for reference:


    Here is the first answer before the nature of the problem was better understood. I will leave it in:

    This looks quite similar (answer from DebbieL), but it is for Installshield 2012. Could you try the workaround she proposes?

    Remote content replicated here in case the link breaks:

    As stated, this is just a summary from the linked answer by DebbieL. Please peruse the entire thread / answer (there are 3 pages worth of questions and answers).

    Let us know how this works out for you, and if it doesn't work I will try to "evolve" this answer.