X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12 May 2016 01:19 PM by  anon
Exit code -3 from ENVI 5.2 & 5.3 installer
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:81
New Member


--
12 May 2016 01:19 PM
    Customer issue: "Using SCCM to manage our installations of ENVI We have been seeing several cases where the ENVI 5.2 installer just hangs or exits with an exit code of -3. By my count, we have had 286 successful installs and out of those, around 38 failed at least once before successfully installing. I am guessing that there is something else installed before ENVI which is causing the problem or the installer is encountering some error condition. I packaged ENVI 5.3 in the hopes that it would install more successfully. So far, out of 8 install attempts, 2 have failed with the -3 exit code. Is this a known error with installing ENVI? "To install Envi, we use SCCM 2007. The install script first installs the Visual Studio redistributables x86_2010_sp1, x64_2010_sp1, x86_2010_sp1, and x64_2010_sp1. Next we install DirectX. Then we install ENVI using the *.iss files that we recorded using the native installer setup64.exe in “record” mode. We then copy our license file to “C:\Program Files\Exelis\license\license.dat” and then install Hotfix 1 using envi53idl85r1.exe with the “/auto” option. These are all essentially run from a network location. "I will say that of our ENVI 5.3 installs, two appear to have failed with the exit code of -3 for the native installer. One of those machines the install was run again and exited with an exit code of 0 (=success). The second machine got an exit code of -3, but on further investigation of the program folder, it had the identical number of files and folders under “C:\Program Files\Exelis” compared to a machine that got a successful exit code. Attached are three copies of the results of our installation script."

    Deleted User



    New Member


    Posts:81
    New Member


    --
    12 May 2016 01:20 PM
    Please note that although we don't explicitly support the use of SCCM with our InstallShield based ENVI installer, I've heard of at least one case where a user was doing this successfully. However, I've not heard of problems where the ENVI installer was returning an exit status of -3. Out of curiosity, if you have access to a /f2 debug log file produced from an unattended ENVI installation with exit status -3, is there any additional error details from this log? Since you are installing over your network, I wonder if some sort of periodic glitch/delay in network communications, server problems or timing issue could be causing the inconsistent failures. I'm told that for reliability, it's usually better to install from files that are copied to the local machine rather than trying to install over a network, because of these possible types of issues. Consistent with the idea of a separate problem, I noticed that in one of the results file that had been provided, the ENVI installation to the machine failed with exit code -3, where the following file copy error had also occurred: 19:03:01.61 C:\Windows>copy /y "\\machine1\SMSPKGD$\COE00759\Files\license.dat" "C:\Program Files\Exelis\license\license.dat" The system cannot find the path specified. 0 file(s) copied. However, a subsequent successful ENVI installation to the same machine then also showed a successful copy of that same file: 8:49:44.30 C:\Windows>copy /y "\\machine2\SMSPKGD$\COE00759\Files\license.dat" "C:\Program Files\Exelis\license\license.dat" 1 file(s) copied. I hope this can be helpful. Regards, Jim

    Deleted User



    New Member


    Posts:1
    New Member


    --
    01 Jun 2016 10:05 AM
    I have added the verbose logging to our install script and it generated a 16mb log file.It appears that the MSI file is generating a 1603 error. Below is the last couple oflines when the installer appears to bail out.MSI (s) (A4:E8) [11:54:48:037]: Executing op: FileCopy(SourceName=EX9EB4~1.HTM|ExampleRestoreSavedROIs.htm,SourceCabKey=_E45E5AEB86BE1C3C84883BACCA049D34,DestName=ExampleRestoreSavedROIs.htm,Attributes=16384,FileSize=4584,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-2100368678,HashPart2=-1617498022,HashPart3=1100167317,HashPart4=-35430890,,)MSI (s) (A4:E8) [11:54:48:037]: File: c:\Program Files\Exelis\ENVI53\classic\help\Subsystems\Programmers\Content\Additional Topics in ENVI Programming\ExampleRestoreSavedROIs.htm; To be installed; Won't patch; No existing fileMSI (s) (A4:E8) [11:54:48:037]: Source for file '_E45E5AEB86BE1C3C84883BACCA049D34' is compressedMSI (s) (A4:E8) [11:54:48:131]: Internal Exception during install operation: 0xc0000005 at 0x000007FEF7A7C7C1.MSI (s) (A4:E8) [11:54:48:131]: WER report disabled for silent install.MSI (s) (A4:E8) [11:54:48:131]: WER report disabled for non-console install.MSI (s) (A4:E8) [11:54:48:131]: Internal MSI error. Installer terminated prematurely.MSI (s) (A4:E8) [11:54:48:131]: MainEngineThread is returning 1603MSI (s) (A4:18) [11:54:48:131]: RESTART MANAGER: Session closed.MSI (s) (A4:18) [11:54:48:131]: No System Restore sequence number for this installation.Installer terminated prematurely.MSI (c) (BC:F4) [11:54:48:396]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (BC:F4) [11:54:48:396]: MainEngineThread is returning 1601=== Verbose logging stopped: 6/1/2016 11:54:48 ===
    You are not authorized to post a reply.