WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Error messages: installation, profile creation and augmentation

The following lists some of the most commonly found error messages encountered when installing WebSphere ESB.

Note: For information about messages that might be generated by the installation of WebSphere Application Server Network Deployment, refer to the troubleshooting information available at the WebSphere Application Server Network Deployment information center.

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact WebSphere ESB support for further assistance.

Invalid node name/Invalid host name/Invalid cell name: The name starts with an invalid character.

Check that the node name, host name, and cell name contain a valid sequence of characters. Use the IBM defaults provided or make sure that your names do not use disallowed characters, as described below:

A node name or a cell name cannot have any spaces, and the following characters are not allowed: / \ * , : ; = + ? | < > & % ’ ". A host name cannot have any spaces, cannot start with any of the above characters, and cannot be surrounded by brackets ( [ ] ).

The Location of JDBC driver classpath files is invalid.

The remainder of this message says: The following files could not be found. list of files Please reenter the directory for the Location of the JDBC driver classpath files. For the given panel's database configuration, the Profile wizard will verify that the necessary jar files exist for the JDBC driver. If the Profile wizard can't verify that the files exist (each database type has a different set), it will present you with this message along with the list of files. This should help you find the correct directory to specify.

Profile is in use. Stop the server before continuing.

The Profile wizard will not augment an existing profile if it is currently running. You do not need to exit the Profile wizard; shut down the server and then continue with the Profile wizard.

Concurrent profile creation, augmentation, or deletion is not supported.

The remainder of this message says: Wait until the current creation or deletion operation is complete before continuing. When a profile is being created, augmented, or deleted, a global lock is made on the Profile Registry. This lock prevents other changes (create/augment/delete) from occurring at the same time.

Solution: Run only one instance of any Profile wizard at a time. Wait until the other creation, augmentation, or deletion process is finished before continuing. If you determine that no other creation, augmentation, or deletion process is running, manually release the profileRegistry.xml lock, which might have been left over from the prior installation attempt. To release this lock, delete the file install_root/properties/profileregistry.xml_LOCK.

The Installation wizard cannot install WebSphere ESB.

The log file entry is: The Installation Wizard cannot install WebSphere ESB. The installation response file for WebSphere Application Server Network Deployment, responsefile.nd.txt, was not found.

Possible solution: If the installation image was copied from one location to another (for example, from a product CD to your C:\ drive, on Windows) make sure you also copy the WAS directory (containing the file responsefile.nd.txt) and that it exists in the same root directory as the WBI directory for the installation image.

Supported IBM JDK was not found.

The log file entry is: Supported IBM JDK was not found. The IBM JDK shipped with this product must be located at <install_image_root>/JDK. Please correct this problem and try again.

Possible solution: If the installation image was copied from one location to another (for example, from a product CD to your C:\ drive, on Windows) make sure you also copy the JDK directory and that it exists in the same root directory as the WBI directory for the installation image. Then launch the installation program again (WBI/install on Linux or UNIX operating systems or WBI\install.exe on Windows operating systems).

A supported version of IBM WebSphere Application Server was not found.

The log file entry is: A supported version of IBM WebSphere Application Server was not found. The installation files for the version of IBM WebSphere Application Server Network Deployment shipped with this product must be located at <install_image_root>/WAS. Please correct this problem and try again.

This error occurs if the version of WebSphere Application Server Network Deployment shipped with WebSphere ESB is not detected in the installation image root directory, and either you are trying to install a new instance of WebSphere Application Server Network Deployment for use with WebSphere ESB or the Installation wizard is attempting to upgrade your existing WebSphere Application Server installation to the supported level.

If the installation image was copied from one location to another (for example, from a product CD to your C:\ drive, on Windows) make sure you also copy the WAS directory and that it exists in the same root directory as the WBI directory for the installation image.

There is insufficient free disk space on the system.

LINUX platforms UNIX platforms On Linux and UNIX platforms: The log file entry is: There is insufficient free disk space on the system. /tmp Required: 535 MB. Available: n MB. Please ensure there is enough free disk space on all required filesystems and retry the operation.

A total of 535 MB of /tmp disk space is required on Linux and UNIX platforms when the WebSphere ESB Installation wizard silently installs WebSphere Application Server Network Deployment or needs to upgrade an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment to the supported level.

Previous WebSphere ESB uninstallation failed.

The log file entry is: A previous attempt to uninstall WebSphere ESB failed for the following installation location: <install_root>. Follow the instructions on preparing for reinstallation after a failed uninstallation in the product information center to uninstall WebSphere ESB and then reinstall the product before attempting to use it.

This error occurs in the Installation wizard if you attempt to add features or launch the Profile wizard for an installation of WebSphere ESB that is no longer valid.

For more information, refer to the instructions for Preparing for reinstallation after a failed uninstallation.

WebSphere ESBv installation not valid

The log file entry is: The selected installation of WebSphere ESB is no longer valid since the underlying WebSphere ESBproduct has been uninstalled. Please uninstall WebSphere ESBfrom the following location: <install_root>. You must then reinstall WebSphere ESB before attempting to use the product.

This error occurs in the Installation wizard if you attempt to add features or launch the Profile izard for an installation of WebSphere ESB that is no longer valid because the underlying WebSphere Application Server is uninstalled.

INFO: The Common Event Infrastructure application was not uninstalled because it is being used by other products.

When uninstalling WebSphere ESB, this message will be logged if the Common Event Infrastructure application is in use by products other than the instance of WebSphere ESB that you are uninstalling.

INFO: WebSphere Application Server was not uninstalled because it is being used by the Common Event Infrastructure application.

When uninstalling WebSphere ESB, this message will be logged if the underlying WebSphere Application Server is still in use by another product using the Common Event Infrastructure and therefore cannot be uninstalled.

A suitable JVM could not be found.

If you get the message "A suitable JVM could not be found. Please run the program again using the option -is:javahome <JAVA HOME DIR>," it is because the JDK shipped with WebSphere ESB could not be found. If the installation image was copied from one location to another (for example, from the product CD to your C:\ drive, on Windows) make sure you also copy the JDK directory and that it exists in the same root directory as the WBI directory for the installation image.

Error: The input line is too long

For Windows platforms On Windows platforms: This is a profile creation error. It can occur during installation or when using the Profile Wizard.

Installation problem (Complete installation only)

The following error within a log in the install_root\profiles\default\logs directory indicates that a wsadmin action has failed to create a profile for a Complete installation. The failure is because the length of the file path and the node name on the command string has caused the entire command to exceed the operating system limit for command length.
The input line is too long.

The installation directory path must be no longer than 60 characters.

  • Option 1: If the installation failed, reinstall the WebSphere ESB using a shorter directory path and a shorter node name.

    The node name field is available during a custom installation. The length of the default node name is usually short enough. Avoid using a node name that is longer than 10 characters if possible.

  • Option 2: If the installation was successful but the ISMPWSProfileLaunchAction failed, use the Profile wizard to create the profile. Use a shorter profile directory path, a shorter profile name, and a shorter node name when creating the profile.

    You can select your own profiles path, which could be C:\profiles, for example.

    You can select your own profile name.

    Verify from the install_root/logs/wbi/log.txt file that the ISMPConfigManagerLaunchAction is successful.

    Examine the following messages in the log.txt file to determine whether the installation was successful. If so, you can run the Profile wizard to create the default profile.
    (date time), Install, 
         com.ibm.ws.install.ni.ismp.actions.ISMPConfigManagerLaunchAction, 
         msg1, INSTCONFSUCCESS: Post-installation configuration is successful.
    (date time), Install, 
         com.ibm.ws.install.ni.ismp.actions.ISMPWSProfileLaunchAction, 
         err, INSTCONFFAILED: Cannot complete required configuration actions 
         after the installation. The configuration failed. The installation is 
         not successful. Refer to 
         C:\Program Files\IBM\WebSphere\ProcServer\logs\wasprofile\
            wasprofile_create_default.log for more details.
    (date time), Install, 
         com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, 
         msg1, Profile Creation is finished.
    (date time), Install, 
         com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, 
         msg1, INSTCONFFAILED

Profile Wizard problem

The following error within a log in the profile_root\logs directory indicates that a wsadmin action has failed to create a profile. The variable profile_root represents the installation location of the WebSphere ESB profile (by default, install_root/profiles/profile_name on Linux and UNIX platforms and install_root\profiles\profile_name on Windows platforms). The failure is because the length of the file path, the cell name, and the node name on the command string has caused the entire command to exceed the operating system limit for command length.
The input line is too long.

The number of characters in the profile_root must be no more than 80 characters.

If your directory path is 80 characters or less and you still have a problem, edit the install_root\bin\setupCmdLine.bat file to make it use the Windows subst command. The subst command maps an entire path to a virtual drive. After editing the file, run the Profile Wizard again. If changing the setupCmdLine.bat file does not fix the problem, you can install WebSphere ESB using a shorter installation path, such as C:\WPS.

See "The input line is too long" section of "Problems starting or using the wsadmin command" on the WebSphere Application Server Network Deployment information center for a description of how to edit the setupCmdLine.bat file.

Note: The following file systems will be expanded during the installation

For AIX platforms On AIX platforms: You can allocate expansion space for directories on AIX. If the Installation Wizard does not have enough space, InstallShield for MultiPlatforms (ISMP) issues a system call for more space that increases the space allocation dynamically. The message you might see when this occurs for the /usr directory is similar to the following example:

NOTE: The following file systems will be expanded during the installation: /usr

The disk space is nn Mbyte less than required. The installation cannot continue.

LINUX platforms UNIX platforms On Linux and UNIX platforms: If the file system is not dynamically expandable, an insufficient amount of disk space results in a message that is similar to the following example:

The disk space is 33 Mbyte less than required. The installation cannot continue.

Specify a different directory or perform a manual uninstall

This error indicates that you deleted the installation root directory before using the uninstaller program to remove the product. Now you are attempting to reinstall into the same directory.

To correct the problem, you must remove registry entries that can prevent you from reinstalling the product into the original directory.

To "clean" your system in this way, refer to the instructions for Preparing for reinstallation after a failed uninstallation.

The warning entry in the $TMP/log.txt file is:
(Month day, year time), Install, 
   com.ibm.ws.install.ni.ismp.actions.ISMPWarningDialogAction, 
   wrn, Specify a different directory or perform a manual uninstall 
   to remove all packages before reinstalling to the same directory.

Error writing file = There may not be enough temporary disk space.

Error writing file =  There may not be enough temporary disk space. 
Try using -is:tempdir to use a temporary directory on a partition
 with more disk space.

This error can occur when you have not provided enough temp space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.

For more information about creating profiles, see Creating and augmenting profiles using the Profile wizard.

Error: localhost is not a valid host name for remote access

This error occurs when you enter localhost as the value for the Host name field in the Profile wizard.

The host name is the network name for the physical machine on which the node is installed. The host name must resolve to a physical network node on the server. When multiple network cards exist in the server, the host name or IP address must resolve to one of the network cards. Remote nodes use the host name to connect to and to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.

If you define coexisting nodes on the same computer with unique IP addresses, define each IP address in a domain name server (DNS) look-up table. Configuration files for stand-alone servers do not provide domain name resolution for multiple IP addresses on a machine with a single network address.

The value that you specify for the host name is used as the value of the hostName property in configuration documents for the stand-alone WebSphere ESB. Specify the host name value in one of the following formats:
  • Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com
  • The default short DNS host name string, such as xmachine
  • Numeric IP address, such as 127.1.255.3

The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the WebSphere ESB configuration. This value for host name is particularly useful if you plan to change the IP address frequently when using Dynamic Host Configuration Protocol (DHCP) to assign IP addresses. A format disadvantage is being dependent on DNS. If DNS is not available, then connectivity is compromised.

The short host name is also dynamically resolvable. A short name format has the added ability of being redefined in the local hosts file so that the system can run the WebSphere ESB even when disconnected from the network. Define the short name to 127.0.0.1 (local loopback) in the hosts file to run disconnected. A format disadvantage is being dependent on DNS for remote access. If DNS is not available, then connectivity is compromised.

A numeric IP address has the advantage of not requiring name resolution through DNS. A remote node can connect to the node you name with a numeric IP address without DNS being available. A format disadvantage is that the numeric IP address is fixed. You must change the setting of the hostName property in configuration documents whenever you change the machine IP address. Therefore, do not use a numeric IP address if you use DHCP, or if you change IP addresses regularly. Another format disadvantage is that you cannot use the node if the host is disconnected from the network.

The installer could not successfully add the product information into the RPM database.

LINUX platforms On Linux platforms: If the last line in the install_root/logs/wbi/log.txt file is something similar to the following example, the problem might be a corrupt RedHat Package Manager (RPM) database:
(date, time), 
Plugin.Install, 
com.ibm.wizard.platform.linux.LinuxProductServiceImpl, 
wrn, The installer could not successfully add the product 
information into the RPM database. Installation will continue 
as this is not critical to the installation of the product.
Run the following command to verify that the problem is a corrupt RPM database:
rpm -q --all

If the command hangs, the problem is a corrupt RPM database.

Error: java.io.IOException: konqueror: not found

LINUX platforms UNIX platforms On Linux and UNIX platforms: The ISMP Launch Browser action throws the following exception on Linux and UNIX systems:

com.installshield.wizardx.actions.LaunchBrowserAction, err, java.io.IOException: 
konqueror: not found
STACK_TRACE: 11
java.io.IOException: konqueror: not found
       at java.lang.UNIXProcess.forkAndExec(Native Method)
       at java.lang.UNIXProcess.<init>(UNIXProcess.java:72)
       at java.lang.Runtime.execInternal(Native Method)
       at java.lang.Runtime.exec(Runtime.java:602)
       at java.lang.Runtime.exec(Runtime.java:524)
       at java.lang.Runtime.exec(Runtime.java:490)
       at com.installshield.util.BrowserLauncher.openURL
(BrowserLauncher.java:578)
       at com.installshield.wizardx.actions.LaunchBrowserAction.execute
(LaunchBrowserAction
.java:62)
       at com.installshield.wizard.RunnableWizardBeanContext.run
RunnableWizardBeanContext.
java:21)

This action searches for a Netscape, Mozilla, or Konqueror browser for displaying an HTML page or a Web site. In the case of the Web server plug-ins for WebSphere Application Server, the target page is the Plug-ins roadmap. Even though the ISMP Launch Browser action might find Mozilla or Netscape, the exception is thrown and a log entry occurs.

You can safely ignore this error.


Reference topic

Terms of Use | Rate this page

Timestamp iconLast updated: 12 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\iins_errinstall.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)