To disable InstallShield at Windows startup, launch Task Manager and click the 'Startup' tab. Scroll down the list of startup programs and click on 'InstallShield.' Click the 'Disable' button to prevent the utility from launching again the next time you restart or power on your computer. InstallShield® One-Click Install™ Netscape users: If you are running Java 1.3.1 Virtual Machine, the One-Click Install applet may not run. (This is because version 1.3.1 is not compatible with previous versions.) To fix this, update your Virtual Machine to the latest version, and then restart your browser.

[ Bottom of Page Previous Page Next Page Contents Index ]

Debugging failed InstallShield Multiplatform installations

There are three phases of the InstallShield Multiplatform installation process that can produce problems:

• launching the installer
• navigating through the panels
• installing and configuring the software

Possible problems and troubleshooting tips are provided in the following sections for each phase.

Launching the installer

Because the InstallShield Multiplatform installation process is Java-based, a suitable JVM must be available to run the installation process. The simplest way to accomplish this is by using the provided launcher program install_amos_platform. This program automatically searches for a JVM to use. If it cannot find one, the program installs a JVM temporarily for use during the installation. Some of the common problems that might arise during this phase are:

• Insufficient disk space for the launcher
• Installation program unable to connect to the X11 Windows server
• Using a specific JVM with the launcher
• Viewing the Java console
• Launcher cannot find a JVM or cannot install the temporary JVM

Insufficient disk space for the launcher

There must be enough disk space available to accommodate the temporary JVM that is used to run the installation process. If there is not enough space, the following error message is displayed:

In this case, either free up enough space in your system's temp directory, usually /tmp or /var/tmp, or start the launcher using the command:

Installation program unable to connect to the X11 Windows server

By default, the installation program runs in GUI mode. If the environment variable DISPLAY is not set, the following message is displayed:

Ensure that DISPLAY is pointing to a valid X11 server, usually in the form:

Tivoli Access Manager for Operating Systems does not support InstallShield Multiplatform console mode so non-graphical installations must use the silent installation features.

Using a specific JVM with the launcher

The launcher uses hints to search for a valid JVM. For example, standard JVM locations are /opt/java1.3 and /usr/java. If a JVM is in a non-standard location, it can be used by running the following command:

Viewing the Java console

Use the following syntax to view messages written to the Java console:

Launcher cannot find a JVM or cannot install the temporary JVM

If the launcher program will not start the installation process, use the following syntax to create a log file:

If the log does not point out any obvious problems, the install process can be started by using Java directly, with the following command:

Navigating through the panels

After the installation process has finished initializing, the input panels are presented. It is rare to encounter problems during this phase of the installation. Free the asn.1 compiler for mac. It is a simple process of entering data into input fields. If the process should crash, restart the process as follows, depending on the installation method used.

Using the Java directory

Start the installer using the following command:

Using the is.debug flag causes InstallShield Multiplatform to display a detailed message about the install process. This might indicate a problem with the InstallShield Multiplatform product itself or with the JVM that is being used. If the JVM crashes, perhaps additional flags are need to run the JVM on a particular systems. For example, the JVM needs a large initial heap size. The flag '-Xmssize' can be passed to the JVM via the install_amos_platform.ja file, one flag per line, or directly using the Java command.

Installing and configuring the software

When all the panels have been correctly filled out and the decision to start the installation process has been accepted, the process will attempt to install and configure Tivoli Access Manager for Operating Systems and its prerequisite software. If an error occurs during this phase, check the following log files for more information:

The logs will contain reported errors such as insufficient space to install a software package or that an incorrect password was provided for configuration. If more detail is needed, start the installation process as follows (depending on the method):

[ Top of Page Previous Page Next Page Contents Index ]

The main purpose of this project is the evaluation of StegoHunt, a steganalysis tool used in detecting the presence of data hiding activities using blind detection. StegoHunt claims to quickly detect steganography activities present in a file, group of files, or folders by scanning them against over 1000 data hiding threat applications,. StegoHunt is the industry's leading software tool for discovering the presence of data hiding activities. Recently included in the StegoHunt package are the additional analysis tools, StegoAnalyst and StegoBreak. All logos copyright © 2002 by spy-hunter.com and/or Bill Englehardt, unless otherwise stated. SpyHunter logo and game copyright Midway Games. Spy-hunter.com is in no. StegoHunt Datasheet StegoHunt Datasheet (Spanish) StegoHunt Datasheet (Chinese). StegoHunt is an industry-leading steganography program discovery tool and steganalysis suite. StegoHunt effectively detects the presence of both data hiding programs and the. Stego hunt.

• we are connecting to license server for licensing..For other machines in our team, the commandline version is working but not in my machine.
  • just your machine?? Is DNS resolving the server name OK
    • yes.all other shares are working.
    • its not about shares. if installshield is working on your machine, you might still need another separate license for the iscmdbld part of the app.
• We are connecting to the internal license server for licensing of installshield.
  In my peers machines, iscmdbuild.exe is also working.But it is not in my machine.Even the 'Flexnet Licensing Service' is also running.
  Could you please suggest what I need to check in that machine o troubleshoot the same.
  • 'not working' = fails to launch?? Or can be launched by fails, is there a log or anything in eventvwr?? is it a licensing issue, or do you just think its a license issue
    • When I build the exe using Wizard then it is building correctly.When I do with ISCMDBuild.exe then I am getting the console output as below screenshot.
      http://www.mediafire.com/view/rjafp97c9j0vqpq/ISCmdBuild.exe+error.PNG
      http://www.mediafire.com/download/rjafp97c9j0vqpq/ISCmdBuild.exe+error.PNG
    • Below is the console output, if you can't access the screenshot.
      Microsoft Windows [Version 6.1.7601]
      Copyright (c) 2009 Microsoft Corporation. All rights reserved.
      C:Userskirud01>'C:Program Files (x86)InstallShield2014SystemIsCmdBld.exe'
      -p 'H:ERwin ISMx64ISMERwin Data Modeler r9.64.02_64bit.ism' -r 'Release 1'
      InstallShield (R)
      Release Builder
      Copyright (c) 2013 Flexera Software LLC.
      All Rights Reserved.
      Build started at Aug 19 2016 03:07 PM
      Building Release: Release 1
      ISDEV : fatal error -7159: The product license has expired or has not yet been i
      nitialized.
      Product Configuration 1Release 1 - 1 error(s), 0 warning(s)
      Build finished at Aug 19 2016 03:07 PM
    • Can you check the license status of the iscmdbld from the IDE??