The Setup.exe (or Install.exe) program may produce error messages if it cannot start
properly. In most cases, you'll encounter these messages when a severe error occurs.
Rarely will your end users see these messages. When you get an error message, it
appears in a message box. Every error message has a number.
Error 101
Setup.exe is unable to find an appropriate location to copy temporary
files. Setup.exe intelligently searches all possible locations for free space
to copy temporary files. Check to see enough free space is available and
temporary location is not write-protected. Check the environment variable
TEMP. Make sure it points to a directory location with ample free space.
Error 102
Setup is unable to find a compressed library file required to proceed with
the installation. Check to make sure all required files are located with the
Setup program.
Make sure that _instxx.ex_ is in the source directory. xxx will vary
depending on the operating system. For example, InstallShield3 for
Windows NT (Intel) and Windows 95 require the file _inst32i.ex_, where
32 is for 32 bit and I is for Intel. Also available are: A (Alpha), M (MIPS),
and P (Power PC). InstallShield Express only supports Intel processors.
Error 103
Setup is unable to find _setup.dll, which is needed to complete the
installation. Restart your system and try again.
Check to make sure that _setup.dll is located with the Setup program.
Error 104
Setup is unable to run an intermediate file needed to proceed with the
installation.
Same as Error 105. This error message refers to a different intermediate
file.
Make sure that you are running a normal installation of windows. If you
cannot correct this error and need to contact InstallShield Technical
Support, please give us information about any special configurations
you've defined, and complete details of your environment.
Error 105
Setup is unable to run an intermediate file needed to proceed with the
installation.
Setup.exe launches the installation program after copying it to the hard
disk. You'll see Error 105 when Setup.exe cannot launch the installation
program from the hard disk. This message appears only rarely.
Make sure that you are running a normal installation of windows. If you
need to contact Technical Support, please give us complete information
on your environment and on any special configurations you've defined.
Error 107
Setup is unable to locate the script file that is needed to complete
the installation.
Setup was unable to find a script file named Setup.ins or optionally
another script file that was specified on the command line.
Check to make sure that you have a compiled script file named Setup.ins
or Install.ins co-located with Setup.exe.
Error 110
Setup was started with a command line argument that contained an
incomplete parameter bad_parameter. Check to make sure that the
command line argument is in double quotes or single quotes you cannot
mix and match.
Error 111
Insufficient memory available to run Setup. Close all other applications to
make more memory available and try to run Setup again.
If after closing applications this message continues to appear, reboot your
system.
Error 112
Setup is unable to decompress and copy all the program files needed to
proceed with the installation. Contact your software vendor.
Make sure that you have TEMP environment variable. Also, make sure
there is enough disk space where TEMP directory is located.
Error 201
Setup is unable to initialize the installation program (Install.exe).
InstallShield was internally unable to create a main window or initialize its
window classes. Alternatively, there is not enough memory to register or
create its internal window classes.
This error is highly unlikely under normal circumstances. If it should
occur, reboot the machine and try again. If it persists, contact Technical
Support.
Error 202
Setup is unable to initialize the installation program.
Error 301
Setup was unable to start up the installation program.
Make sure that you have a good copy of Setup.exe on your source disks.
Check also to see if there's enough space on the target disk.
Error 401
String variable is not large enough for string. Please check string declarations.
InstallShield was trying to copy a text string into a string variable.
However, the text string was larger than the length you declared for that
string variable. Before copying a string into a string variable, InstallShield
checks the length of the string variable. There may be instances when
InstallShield3 may be unable to detect such string overwrites. Check the
declared length of the string variables. Increase the length to the
maximum allowed value. Check the logic to make sure that you do not
have a loop that generates strings longer than 512 bytes for Windows 3.1
and 1,024 bytes for Windows NT and Windows 95.
Error 420
Setup is unable to copy the installation support file to a
temporary location.
The _setup.lib file is InstallShield3's user-support file. You copy Setup.lib
to your first distribution disk, and InstallShield3 automatically
decompresses and copies _setup.lib to a temporary location on the
user's hard disk. You'll see this error message if InstallShield3 cannot find
an acceptable temporary location where it can copy the installation
support file, or if there was not enough free disk space to copy the files.
Make sure you have enough free disk space and that the environment
variable TEMP points to a valid location with enough available disk space.
Error 421
Setup is unable to copy the installation support file _setup.lib to a
temporary location. Make more space available and try again.
Setup.exe cannot copy the support files to a temporary location.
Check to see that enough free space and appropriate write privileges are
available.
Error 422
Setup is unable to expand the installation support file .
After copying the _setup.lib file to a temporary location, Setup.exe could
not decompress the support file.
Make sure there is enough free space on the drive that you're using for
temporary storage.
Error 423
Setup is unable to load the installation script file.
Setup.exe is unable to load the script file into memory for processing.
Setup.exe was internally unable to load the script file due to low memory
conditions. On the other hand, it was unable to create its internal data
structures, window classes or other control classes. The script file was
contaminated or damaged, or was not compiled properly.
This error is highly unlikely. If it does occur, (1) recompile the script file,
(2) reboot the machine, and (3) try running InstallShield again with the
new script file.
Error 424
Setup has encountered an internal stack overflow error. Close all
applications, restart the system and try the installation again.
Setup.exe displays this severe error when InstallShield3's internal stack
exceeds its limits. It's highly unlikely that you will see this error message.
Recompile your script and try the installation again under a normal
window's installation.
Error 425
Setup has encountered an incomplete return statement in the script.
Check your script for unmatched return statements.
You cannot use the return statement in a script unless it follows a call
statement. If a return statement is encountered without a call statement,
then the return statement is considered unmatched and you'll see this
error message.
Scan your script file to make sure each return statement is encountered
only after a call statement. Fix the problem and recompile your script.
Error 426
Setup is unable to find the installation script file: script_filename.
Setup.exe was unable to find a script file named Setup.ins or, optionally,
another script file that was specified on the command line.
Error 427
Setup is unable to load the installation script file: script_filename. The
script may be from a previous version or corrupted.
Setup.exe is unable to load the script file into memory for processing. It's
possible that the script file has been corrupted or is otherwise incomplete.
Recompile your script file.
Error 432
Setup has detected that unInstallShield is running.
This error may occur if an installation launches other installations. When
you cancel one of the setups, unInstallShield is removing the files that
were installed while the second setup is launching.
To avoid launching a second setup and have it fail with error 432, first
make sure that the uninstaller is not locked. If it is locked, don't launch
the next setup or wait until it is unlocked.
Error 440
Setup has detected a possible infinite loop in the script with function
function_name. Make sure your are handling the error returns codes
properly.
Setup.exe has detected the possibility there's an infinite loop in the way a
function is used. FileSetPerform and other similar functions have a
specific usage that you must follow. Otherwise, it's possible that the
script could end up in an infinite loop.
For every function that's listed in the Language Reference Guide, there's
an example of how to use the function. If you get this error message,
make sure you've structured your code the same as the example in the
Language Reference Guide.
Error 502
Setup is unable to initialize the installation program. The script file may
be bad.
The script file is corrupted or not enough free memory is available to
execute the script file.
Recompile the script.
Error 701
A division by zero error was detected in the script. Installation will
continue.
In checking your script, Setup.exe detected a division by zero. Installation
will continue.
Examine the logic of your script. Check every division operation and make
sure there's no possibility of a zero value in the denominator.
Error 702
An internal error has occurred. Insufficient memory to allocate buffer.
InstallShield was internally unable to allocate memory to execute an
instruction.
A highly unlikely error. Before contacting Technical Support about this,
make sure you can repeatedly duplicate the error message. Before you
call, send your script and installation disks to InstallShield Technical
Support.
Error 703
An internal read error has occurred on script_filename. Unable to load
installation instructions.
Setup.exe detects that it cannot read the script file from memory.
Recompile the script file and use the new compiled script file. Reboot the
machine and try running Setup.exe again.
Error 704
Script_filename file has become corrupted. Unable to load installation
instructions.
This message appears if Setup.exe detects that script file is corrupted, or
if Setup.exe is unable to load the script file into memory for processing.
Run Windows in standard or enhanced mode. Or make more memory is
available to Windows by removing any memory-resident programs or
network drivers.
Error 3000
Error messages ranging from 3000 to 3021 are internal memory-related
error conditions.
Low memory conditions exist. Internal string variables were overwritten, or
the compiled script file is corrupted. Severe error conditions exist.
Compile your installation again and then test it. Make sure that you are
not exceeding the limits of the string variables that you declared in your
script.