InstallShield error codes for SecureLogin

(Last modified: 05Sep2005)

This document (10088294) is provided subject to the disclaimer at the end of this document.

fact

InstallShield Professional

Novell SecureLogin version 3.5

goal

InstallShield error codes for SecureLogin

fix

Errors that could appear in setup.log

0          Success

-1         General error

-2         Invalid mode

-3         Required data not found in the Setup.iss file

-4         Not enough memory available

-5         File does not exist

-6         Cannot write to the response file

-7         Unable to write to the log file

-8         Invalid path to the InstallShield silent response file

-9         Not a valid list type (string or number)

-10        Data type is invalid

-11        Unknown error during setup

-12        Dialog boxes are out of order

-51        Cannot create the specified folder

-52        Cannot access the specified folder

-53        Invalid option selected

 

Other defined InstallShield errors

 

-5001   Generic error

Possible Solution - (Use RAW mode and Joliet CD format)

-5002   Failed reading media header

-5003   Failed installing kernel

Possible Solution - Workstation needs to be rebooted due to files being locked. Disable anti-virus software prior to starting installation.

-5004   Failed starting kernel

Possible Solution - On Win9x try running DCOM95 or DCOM98. This is typically a problem with DCOM

-5005   Failed opening CAB

Possible Solution - Check security settings. Make sure administrator rights. Don't filter ini files

-5006   Failed installing support

-5007   Failed setting text substitution

-5008   Failed initializing setup info

-5009   Failed getting setup driver

Possible Solution - Make sure there is a TEMP directory. Try deleting contents of TEMP directory prior to installation. Also make sure user is administrator

-5010   Failed initializing properties

-5011   Failed running setup driver

-5012   Failed uninstalling support

Possible Solution - Invalid or corrupt CD media

-5013   Failed to extract file from setup boot file

-5014   Failed to download file [occurs only on internet setup]

-6001   Failed starting the setup launcher

-6002   Failed finding the setup launcher

-6003   Failed loading the setup launcher

Possible Solution - Missing file data1.hdr

-6004   Failed verifying the signature of setup launcher

-6005   Failed installing the setup launcher to proper location

-6006   Failed extracting setup launcher

 

Typically when one of the above error codes is returned by InstallShield an HRESULT will also be returned to provide additional information about the failure.

  

0x80041F40    Can not find corecomp.ini

0x80041F41    corecomp.ini is empty or corrupted

0x80041F42    Can not load the dll inIsCoGetClassObject

0x80042328    Media is not signed

0x80042329    Certificate is invalid

0x8004232A    Digital signature is invalid

0x8004232B    Space is insufficient

0x80042A94    The specified opType’s main opsequence is not present in the log, such as

                        when an old file is opened with the new engine and the. new (engine) code

                        tries to get an opsequence for the newly introduced opType.

0x80042A95    Failed to (re)construct a feature log’s full ID

0x80042A96    A log operation was attempted without opening the log file

0x80042A97    Internal opsequence structure initialization failed

0x80042A98    General failure in Opsequence::GetNext

0x80042A99    General failure in Opsequence:Pop

0x80042A9A   General failure in Opsequence::insert_sequencetuple

0x80042A9B   General failure in Opsequence::delete_sequencetuple

0x80042A9C   Property initialization failure – could occur when setting/getting a

                        property in the LogDB or Feature object

 

Setup Engine error messages

 

0x80040701    Division by zero

0x80040702    Failed to load DLL

0x80040703    Failed to find DLL function

0x80040704    A call to a DLL function resulted in a bad stack. Possible incorrect

                        prototyping, for example, incorrect calling convention

0x80040705    Strin.g accessed out of bounds

0x80040706    Object reference not set

0x80040707    A call to a DLL function failed. A common cause of this error is passing

                        the function an incorrect number of arguments or an incorrect argument

                        data type.

.

document

Document Title: InstallShield error codes for SecureLogin
Document ID: 10088294
Solution ID: NOVL93584
Creation Date: 28Oct2003
Modified Date: 05Sep2005
Novell Product Class:Netware Client

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.