Installing exe with .iss setup file. Getting error -3

The Toolkit General Discussion
1

Hi,

I am trying to install Oracle Publisher BI via Intune but am struggling with passing the .iss file for setup using version 4.1.8.

In the Files folder I have OracleAnalyticsPublisherDesktop-8.2.0-win64.exe and setup.iss.

This is what I am currently using as the install task. Still very much getting used to using V4 so any help would be appreciated, just for reference the install command when ran manually as per the docs is below.

Start-ADTProcess -FilePath "OracleAnalyticsPublisherDesktop-8.2.0-win64.exe" -ArgumentList "/S /f1`"$($adtSession.DirFiles)\setup.iss`""```



.\OracleAnalyticsPublisherDesktop-8.2.0-win64.exe /S /f1"D:\Temp\setup.iss"
2

AFAIK this looks correct. What error are you getting?

3

Some log output would be good as well.

4

I can see the installshield show on taskbar and then drops, soon after I get the "Execution failed with exit code 3"

Here is the log.

[Install] :: An unhandled error within [Invoke-AppDeployToolkit.ps1] has occurred.
Error Record:
-------------
 
Message               : Execution failed with exit code [-3].
 
FullyQualifiedErrorId : ProcessExitCodeError,Start-ADTProcess
ScriptStackTrace      : at Start-ADTProcess<Process>, D:\Intune\Apps\Oracle BI\Oracle BI Publisher\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 22554
                        at Install-ADTDeployment, D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Invoke-AppDeployToolkit.ps1: line 162
                        at <ScriptBlock>, D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Invoke-AppDeployToolkit.ps1: line 324
                        at <ScriptBlock>, <No file>: line 1
 
TargetObject          : Process     : System.Diagnostics.Process (OracleAnalyticsPublisherDesktop-8.2.0-win64)
                        LaunchInfo  : ProcessLaunchInfo { FilePath = D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Files\OracleAnalyticsPublisherDesktop-8.2.0-win64.exe, ArgumentList = System.Collections.ObjectModel.ReadOnlyCollection`1[System.String], WorkingDirectory = D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Files, RunAsActiveUser = , UseLinkedAdminToken = False, UseHighestAvailableToken = False, InheritEnvironmentVariables = False, ExpandEnvironmentVariables = False, DenyUserTermination = False, InheritHandles = False, UseUnelevatedToken = False, UseShellExecute = False, Verb = , CreateNoWindow = False, WaitForChildProcesses = False, KillChildProcessesWithParent = False, StreamEncoding = System.Text.SBCSCodePageEncoding, WindowStyle = , ProcessWindowStyle = , PriorityClass = , CancellationToken = , NoTerminateOnTimeout = False }
                        CommandLine : "D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Files\OracleAnalyticsPublisherDesktop-8.2.0-win64.exe" /S /f1"D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Files\setup.iss"
                        ExitCode    : -3
                        StdOut      : {}
                        StdErr      : {}
                        Interleaved : {}
 
PositionMessage       : At D:\Intune\Apps\Oracle BI\Oracle BI Publisher\Invoke-AppDeployToolkit.ps1:162 char:5
                        +     Start-ADTProcess -FilePath "OracleAnalyticsPublisherDesktop-8.2.0 ...
                        +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5

your .iss file is wrong.

Installshield .iss files are VERY limited. They can only handle ONE scenario. If something happens on your target that the iss file was not written to handle, you will get this error.

years ago, before MSI, I had to create a package with 2 .iss files to handle 2 scenarios. I had to detect the differences and select the correct iss file.

6

Cheers, recreated the ISS file on a clone of the EUC device and seems to be alot happier now.

7

Had a few iss issues lately, Leica Cyclone being one and I seem to recall a -3. I think after a device restart it then worked - deployment via intune.

8

IOW: the setup saw a pending Reboot and the .iss file was not able to handle that.

Workaround: before you launch the EXE check for Pending reboots and ask or force a reboot.

9

We had this issue when one of our analysts created the .iss as their own admin rather than system.

Installed on some devices but most failed with -3. was looking for some user interaction and then failing.

They are very sensitive .iss files...