Problems with the interactive wizard

The following problems might be encountered while running the Dynamic Workload Console interactive installation:

The Dynamic Workload Console installation hangs

Problem description:

The installation of the Dynamic Workload Console does not proceed. This occurs regardless of the method you used to install.

Cause and solution

Make sure an active personal firewall is not preventing the installation process from connecting to the network. If it is, allow the connection and then continue with the installation.

Installation hangs during stopWas command

Problem description:

The installation of the Dynamic Workload Console does not proceed.

Cause and solution

The installation of the Dynamic Workload Console does not proceed because the stopWas command is hanging.

To continue the installation, open the Task Manager and locate the Java process of the embedded WebSphere Application Server. This process is the java.exe process with the associated installation username. Stop this process.

Then, find the associated WASService process. This process is the WASService.exe process with the associated the installation username. Stop this process.

Continue with the installation.

Tivoli Integrated Portal installation fails even if into the logs you find successfully installed

Problem description:

You are installing the Tivoli Integrated Portal, either using the wizard or the silent installation, and the installation fails with the following error:

Start installing TIP - Tivoli Integrated Portal 2.2
For log details, please see
C:\Documents and Settings\Administrator\TIPInstaller-00.log
and {install location}\logs.zip
Preparing SILENT Mode Installation...

===========================================================================
GenericInstaller      (created with InstallAnywhere by Macrovision)
---------------------------------------------------------------------------
===========================================================================
Installing...
=============|==================|==================|==================]

Installation Complete.
SUCCESS: The overall installation is successful.
Current OS is Windows XP
Executing
'C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin\tipcli.bat' with arguments:
'Version'

The ' characters around the executable and arguments are
not part of the command.
Execute:Java13CommandLauncher:
Executing
'C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin\tipcli.bat' with arguments:
'Version'

The ' characters around the executable and arguments are
not part of the command.
The following error occurred while executing this line:
C:\temp\TDWC\WEBUI\WINDOWS\xml\commonTargets.xml:1735:
Execute failed: java.io.IOException:
Cannot run program "C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin\tipcli.bat"
in directory "C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin"): 
CreateProcess error=2, The system cannot find the file specified.
****************************************************************************
Installation Complete.
SUCCESS: The overall installation is successful.
Current OS is Windows XP
Executing
'C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin\tipcli.bat' with arguments:
'Version'

The ' characters around the executable and arguments are
not part of the command.
Execute:Java13CommandLauncher:
Executing
'C:\IBM\TWS\TDWC\eWAS\profiles\TIPProfile\bin\tipcli.bat' with arguments:
'Version'

Cause and solution

This error occurs if you remove an instance of the Dynamic Workload Console, and the Tivoli Integrated Portal is also installed in the same path, without running the uninstaller (for example, removing manually only the content of the TWA directory). In this case, the Tivoli Integrated Portal instance remains registered in the Deployment Engine installation registries and when you perform another installation of the Tivoli Integrated Portal the installer reports the error indicated previously.

Run the procedure described in Uninstalling the Dynamic Workload Console and the Tivoli Integrated Portal manually to clean your environment. Restart the installation from the failed step.

Installation from a remote shared folder fails on Windows operating system

Problem description:

You try to install the Dynamic Workload Console on a Windows operating system from a shared network folder that uses Universal Naming Convention (UNC). The installation fails.

Cause and solution

You must map the remote folder locally on the Windows system where you want to install the Dynamic Workload Console and then run the installation using the local path.

Installation fails on a Linux 390 system with a hostname which is not a Fully Qualified Domain Name

Problem description:

You install the Dynamic Workload Console with the embedded WebSphere Application Server on a server with a hostname is not a Fully Qualified Domain Name. The installation fails and the following error is stored in the twainstall.log file:

  ADMU3011E: Server launched but failed initialization. startServer.log,
             SystemOut.log(or job log in zOS) and other log files under
             /oracle/ibm/TDWC/eWAS/profiles/TIPProfile/logs/tdwcserver
             should contain failure information.

  WASX7023E: Error creating "SOAP" connection to host "localhost"; 
  exception information: 
  com.ibm.websphere.management.exception.ConnectorNotAvailableException: 
  com.ibm.websphere.management.exception.ConnectorNotAvailableException: 
  ADMC0016E: The system cannot create a SOAP connector to connect to host 
             localhost at port 28880.

Cause and solution

Run the following command from the system prompt on the Linux 390 system where you tried to install the Dynamic Workload Console:

hostname --fqdn

If the command returns:

hostname: Unknown host

the host name is not resolved. You must specify a hostname with a fully qualified domain name to install the embedded WebSphere Application Server. Update the hostname notation, as explained in the embedded WebSphere Application Server documentation, and then rerun the installation.

Java Virtual Machine (JVM) failure when installing the Dynamic Workload Console on a Red Hat Enterprise Linux (RHEL) Version 5 or a Suse Linux system Version 11

Problem description:

When installing the Dynamic Workload Console on a Red Hat Enterprise Linux Version 5 or a Suse Linux Version 11 system, you might receive the error "Failed to find VM - aborting".

Cause and solution

Linux systems have a security feature named 'Security Enhanced Linux', or SELinux for short. A weaker version of SELinux was included in Red Hat Enterprise Linux Version 4, and was disabled by default. On these versions of Red Hat Enterprise Linux and Suse Linux, this security feature is enabled by default. SELinux helps to keep the host secure from certain types of malicious attacks. However, the default settings have been known in many cases to prevent Java from running properly.

To fix this issue, choose one of the following options:

The Dynamic Workload Console graphical installation and uninstallation fail to start on Red Hat Enterprise Linux (RHEL) Version 5 on x86-64

Problem description:

When launching the Dynamic Workload Console installation or uninstallation wizard in interactive mode on Red Hat Enterprise Linux (RHEL) Version 5 x86-64, you might receive the following error:

For the installation:

The installer is unable to run in graphical mode. 
Try running the installer with the -console or -silent flag.

For the uninstallation:

The uninstaller is unable to run in graphical mode. 
Try running the uninstaller with the -console or -silent flag.

Cause and solution

If you run into this problem, launch the installation or the uninstallation in silent mode. For more information, see Performing a silent installation and Uninstalling in silent mode.

On Windows, the Dynamic Workload Console installation fails if you try to reinstall on a different profile of an external WebSphere Application Server

Problem description:

This situation applies to a Windows operating system. You install the Dynamic Workload Console on a profile, for example, ProfileA, of an existing WebSphere Application Server installation. You remove the Dynamic Workload Console successfully and then try to install it on a different profile of the same WebSphere Application Server. The installation fails.

Cause and solution

A possible cause is that when you removed the Dynamic Workload Console, some files belonging to ProfileA were not removed. To solve this problem, stop ProfileA and then install the Dynamic Workload Console again on the other profile.