AWSJIS - Installation messages

This section lists error and warning messages that could be issued.

The message component code is JIS.

AWSJIS002E

An internal error has occurred. The command or script "command_or_script" has failed. The exit code is as follows: "exit_code".If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

See message.

command_or_script is the command that has failed. It might be an operating system command or a Tivoli Workload Scheduler installation script.

exit_code is the error code given by the command or script.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message. The Diagnose Failure window is opened.
  2. If you want to diagnose the problem without leaving the wizard (recommended) select Diagnose failure and click Next, and follow the procedure described in Planning and Installation for diagnosing a failed installation.

    Otherwise, select Quit installation. The wizard closes.

- Silent wizard

Look in the installation log to see if there is any additional information.

Check any available information related to the exit_code. In the case of an operating system command you might have to consult the operating system documentation.

If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

If you think you can solve the problem, make any necessary corrections to the installation environment. Proceed as follows:
- Interactive wizard

Resume the step that has failed.

- Silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Restart the step that failed.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS004E

The version of the Tivoli Workload Scheduler instance selected to upgrade is neither 8.1 nor 8.2.Click Back and select a different, valid instance.

AWSJIS005E

The version of the Tivoli Workload Schedulerinstance selected is not 8.2.Click Back and select a different, valid instance.

AWSJIS006E

No valid instance of Tivoli Workload Scheduler has been found to upgrade.Select a valid instance or make a fresh installation.

Either no instance of Tivoli Workload Scheduler was found at the indicated location, or the instance found is not at the correct version. Only versions 8.3, 8.4, 8.5 or 8.5.1 can be upgraded to version 8.6. All other versions must first be upgraded to 8.3, 8.4, 8.5 or 8.5.1.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message window.
  2. Click Back to return to the previous panel and change the Tivoli Workload Scheduler instance definition to identify an instance of version 8.2, 8.2.1, 8.3 or 8.4, or choose to make a fresh installation.
  3. Click Next to continue.
- Silent wizard
  1. Look in the installation log to see if there is any additional information
  2. Edit the response file used by the silent wizard, changing the parameter that identifies the existing Tivoli Workload Scheduler instance to an instance of version 8.2, 8.2.1, 8.3 or 8.4, or choosing to make a fresh installation.
  3. Rerun the silent wizard.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS007E

An error occurred reading file.

AWSJIS008E

The passwords do not match.Retype the password and the verification password, ensuring that they are both the same.

You have supplied a password for the TWS_user and have confirmed it, but the passwords are different.

The wizard stops.

  1. Click OK to close the error message.
  2. Retype the passwords, ensuring that they are both the same.
  3. Click Next to continue.

AWSJIS009E

The following field: "field_name" is longer than the maximum of "max_length" bytes.

See message.

field_name is the name of the field that is too long.

max_length is the maximum number of bytes it can be.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Re-enter the indicated field, ensuring that it does not exceed the maximum length, and click Next to continue.
- Silent wizard
  1. Edit the response file, and ensure that the field does not exceed the maximum length.
  2. Rerun the silent wizard.

AWSJIS010E

The following field: "field_name" is either not a number or outside the following range: "from_value" - "to_value".

See message.

field_name is the name of the field that is either not a number or out of range.

from_value and to_value indicate the minimum and maximum values it can take.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Re-enter the indicated field, ensuring that the value is a number, that it falls within the indicated range, and click Next to continue.
- Silent wizard
  1. Edit the response file, and ensure that the field value is a number and falls within the indicated range.
  2. Rerun the silent wizard.

AWSJIS011E

The supplied installation path is not valid.

See message. For example, you might have supplied one or more characters that cannot be used in a file path.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Re-enter the installation path, ensuring that the path is fully qualified and valid, and click Next to continue.
- Silent wizard
  1. Edit the response file, and ensure that the installation path is fully qualified and valid.
  2. Rerun the silent wizard.

AWSJIS012E

There is insufficient disk space available in the directory "directory" to complete the installation. The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory.

See message.

directory is the install directory that has insufficient space.

required_space and available_space indicate what space the installation requires and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

- Make space in the original path
If you want to persist with the original installation path, use the operating system's commands and utilities to make more space available. When you have done this, proceed as follows:
Interactive wizard
  1. Click OK to close the error message.
  2. Click Next to continue.
Silent wizard
  1. Rerun the silent wizard.
- Choose another directory
If you cannot make sufficient space, you need to change the installation path to one with sufficient available space. To do this, proceed as follows:
Interactive wizard
  1. Click OK to close the error message.
  2. Reenter the installation path, ensuring that the path is fully qualified and valid, and points to a directory with sufficient space. Click Next to continue.
Silent wizard
  1. Edit the response file, and ensure that the installation path is fully qualified and valid, and points to a directory with sufficient space.
  2. Rerun the silent wizard.

Proceed as follows:

AWSJIS013E

The specified installation path doesn't exist.

AWSJIS017E

You are correcting an installation parameter by editing the parameters of an installation step, but an incorrect parameter has been supplied during the correction.

See message.

The installation cannot continue.

Check the parameters that you have changed or supplied during the resume of an installation, and ensure that you have supplied valid values:
  • If you locate the error, correct it and continue.
  • If you cannot locate the error quit the installation and resume it.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS018E

An internal error has occurred. The directory specified as the location of the existing Tivoli Workload Scheduler instance does not exist.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Click Back to return to the previous panel and change the directory of the Tivoli Workload Scheduler instance, or choose to make a fresh installation.
  3. Click Next to continue.
- Silent wizard
  1. Look in the installation log to see if there is any additional information
  2. Edit the response file used by the silent wizard, changing the parameter that identifies the directory of the existing Tivoli Workload Scheduler instance, or choosing to make a fresh installation.
  3. Rerun the silent wizard.

AWSJIS019E

An internal error has occurred. The directory to be used for the install directory of the embedded WebSphere Application Server does not exist.

The install directory for the embedded WebSphere Application Server is created by the install program within the Tivoli Workload Scheduler install directory. This message could arise if the directory in question has not been created correctly, or has been deleted before being used.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the installation log to see if there is any further information that helps you to understand why the directory could not be found.

The problem is resolved by just rerunning the installation.

- Rerun the interactive wizard
  1. If you are running the interactive wizard, click OK to close the error message window. The Diagnose Failure window is opened.
  2. Select Quit installation. The wizard closes.
  3. If you previously copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS020E

The directory specified as the location of the existing DB2 instance does not exist. Specify the correct location of the DB2 instance.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the path you supplied for the existing DB2 instance that you would like to use with Tivoli Workload Scheduler.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Correct the DB2 instance path and click Next to continue.
- Silent wizard
  1. Edit the response file, changing the DB2 instance path to the correct value.
  2. Rerun the silent wizard.

AWSJIS021E

An internal error has occurred. The application server profile "profile" for the embedded WebSphere Application Server could not be created.

The installation program needs to create an application server profile for the embedded WebSphere Application Server, and then populate it with the information specific to Tivoli Workload Scheduler. This message is displayed because the profile could not be created.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that the computer where you are installing Tivoli Workload Scheduler satisfies the prerequisite requirements of the embedded WebSphere Application Server . These can be found by clicking the System requirements link on the product information Web page for the embedded WebSphere Application Server at www.ibm.com.

Check that there is sufficient space in the standard temporary directory of the computer.

Check that you have copied the installation images correctly to the computer where you are running the installation wizard.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, check the installation log for more information.

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. If you are running the interactive wizard, close the Step Status window and click Finish on the Step List window. The wizard closes.
  2. If you previously copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  3. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS022E

An internal error has occurred. The application server profile archive "profile_archive" for the embedded WebSphere Application Server could not be read.

The installation program needs to create an application server profile for the embedded WebSphere Application Server , and then populate it with the information specific to Tivoli Workload Scheduler. This message is displayed because the profile archive that contains the information needed to populate the profile could not be read.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that you have copied the installation images correctly to the computer where you are running the installation wizard.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, check the installation log for more information.

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. If you are running the interactive wizard, close the Step Status window and click Finish on the Step List window. The wizard closes.
  2. If you previously copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  3. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS023E

An internal error has occurred. The update of the configuration of the embedded WebSphere Application Server has failed.

The embedded WebSphere Application Server is installed with a default configuration, which is then updated for Tivoli Workload Scheduler. The update has failed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that you have copied the installation images correctly to the computer where you are running the installation wizard.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, check the installation log for more information.

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. If you are running the interactive wizard, close the Step Status window and click Finish on the Step List window. The wizard closes.
  2. If you previously copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  3. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS024E

The application server "application_server" could not be started.

The indicated application_server runs Tivoli Workload Scheduler on the embedded WebSphere Application Server, but the application server could not be started after the installation.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the application server's logs to determine why the server could not be started.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you can solve the problem, do so, and proceed as follows:

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Restart the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS025E

An internal error has occurred. The script "script" used by the installation wizard has failed.

See message.

script identifies the script that has failed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the installation log to determine why the script failed.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you can solve the problem, do so, and proceed as follows:

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS029E

An internal error has occurred. The directory where the installation expected to find the JRE files does not exist.

The installation program is trying to locate the directory where the Java Runtime Environment files were unpacked at the beginning of the installation, but has failed to find it. Either the unpacking of the installation bundle failed, or the directory has subsequently been renamed or deleted.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

Ensure that you are not trying to run two installations concurrently, which is not possible.

If you can solve the problem, do so, and proceed as follows:

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS030E

An internal error has occurred. The build file that the installation program expected to find does not exist.

The installation program is trying to locate the build file that was unpacked at the beginning of the installation, but has failed to find it. Either the unpacking of the installation bundle failed, or the file has subsequently been renamed or deleted.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

Ensure that you are not trying to run two installations concurrently, which is not possible.

If you can solve the problem, do so, and proceed as follows:

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS031E

An internal error has occurred. An internal program has failed.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you can solve the problem, do so, and proceed as follows:

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS032E

An internal error has occurred. An internal program has not been supplied with a required parameter.

The internal program that creates the Tivoli Workload Scheduler instance (Ant) is called by the installation program, which supplies the parameters it requires. One of these parameters is missing. It is possible that during a previous resume of a failed installation, a required value was inadvertently deleted from a step or modified.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you have already tried resuming this installation, check that you did not inadvertently invalidate any of the step parameters, by looking at the values in the Properties tab on the Step Status panel of the step that failed. You might have to return to a previous step to be able to modify the field.

If you can solve the problem, do so, and proceed as follows:

In the interactive wizard, if you think you have corrected an error in the step properties, you might be able to resume the modified step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS036W

The temporary directory created previously by the Tivoli Workload Scheduler installation does not exist.

The internal program that cleans up after the Tivoli Workload Scheduler instance is trying to delete the temporary files that the installation used, but the directory that contains those files cannot be found. It might have been deleted or renamed during the installation by a user or process other than the installation. Alternatively, the value of the directory name might have been inadvertently changed during the editing of the data in a step while recovering from an installation failure.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The installation has completed at this point, so remedial action is not necessary. The temporary files might still be present on your disk, and if you can easily find them and delete them, do so. However, they might not be easy to find (if another user or process has changed the directory name) and do not occupy enough space to make it worth while spending time searching for and deleting them.

AWSJIS037W

Message not used.

AWSJIS038E

An internal error has occurred. An unspecified internal error has occurred during the installation process.

The installation process has determined that an error has occurred, but is unable to give any more-detailed information.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

Ensure that you are not trying to run two installations concurrently, which is not possible.

If you can solve the problem, do so, and proceed as follows:

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS039E

Tivoli Workload Scheduler cannot be started.Start it manually.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

However, in both cases the installation is complete, provided that you can solve the reason why Tivoli Workload Scheduler cannot be started.

Look in the Tivoli Workload Scheduler log files to determine why it cannot be started. If you can solve the problem that is revealed, do so. Then start Tivoli Workload Scheduler manually, as described in the User's Guide and Reference.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.
User's Guide and Reference for a description of how to start Tivoli Workload Scheduler.

AWSJIS041E

The installation cannot add the following key to the Windows registry: "registry_key".

The installation was attempting to add the following registry key \IBM\Tivoli Workload Scheduler to the standard HKEY_LOCAL_MACHINE\SOFTWARE registry key.

The attempt has failed, probably because the standard HKEY_LOCAL_MACHINE\SOFTWARE registry key has been deleted or renamed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The product cannot run successfully without the indicated registry key. You are strongly advised to treat this as an internal error. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

However, you might decide to attempt to use regedit to add the key. Bear in mind that Microsoft warn you that the incorrect use of regedit might render the computer unusable. If you do decide to go ahead using regedit, verify that your Windows registry has the key HKEY_LOCAL_MACHINE\SOFTWARE. Add it if it does not. Remember to close regedit before proceeding.

The installation can now be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error message window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS042E

The installation cannot add the following key to the Windows registry: "registry_key" with values "registry_key_values".

The installation is attempting to add the indicated values to a key it expects to exist. Maybe the key does not exist or has been renamed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The product cannot run successfully without the indicated registry key. You are strongly advised to treat this as an internal error. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

However, you might decide to attempt to use regedit to add the key. Bear in mind that Microsoft warn you that the incorrect use of regedit might render the computer unusable. If you do decide to go ahead using regedit, verify that your Windows registry has the indicated key. Add it if it does not. Remember to close regedit before proceeding.

The installation can now be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS043E

The installation cannot delete the following key from the Windows registry: "registry_key".

The installation is attempting to delete the indicated registry key that it expects to exist. Maybe the key does not exist or has been renamed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The product cannot run successfully without deleting the indicated registry key. You are strongly advised to treat this as an internal error. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

However, you might decide to attempt to use regedit to delete the key. Bear in mind that Microsoft warn you that the incorrect use of regedit might render the computer unusable. If you do decide to go ahead using regedit, verify whether your Windows registry has the indicated key. Delete it if it does. Remember to close regedit before proceeding.

The installation can now be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS044E

The installation cannot install the following Windows service: "service_name".

The reason might be that you do not have the correct rights to install services, the service might already exist or the user account name specified might not exist.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Follow these steps:
  1. Using the Windows user account management facilities, check that the user performing the installation exists, and has the right to install services. If not, add this right. Remember to close the user account management facilities window before proceeding.
  2. If the user exists and its rights are correct, open the Windows Services panel. Check if the indicated service already exists. If it does, probably a previous uninstallation of Tivoli Workload Scheduler failed, without deleting the service. If you suspect this to be the case, If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.. Remember to close the Windows Services panel before proceeding.
If you are able to solve the problem so that the installation is capable of installing a service, the installation can be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS045E

The installation cannot delete the following Windows service: "service_name".

The reason might be that you do not have the correct rights to delete services, or the service might not exist.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Follow these steps:
  1. Using the Windows user account management facilities, check that the user performing the installation exists, and has the right to delete services. If not, add this right. Remember to close the user account management facilities window before proceeding.
  2. If the user exists and its rights are correct, open the Windows Services panel. Check if the indicated service already exists. If it does not, it might have been manually deleted in error. If you suspect this to be the case, If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.. Remember to close the Windows Services panel before proceeding. You are not advised to attempt to add the service manually.
If you are able to solve the problem so that the installation is capable of deleting a service, the installation can be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS046E

The installation could not find an operating system dll to complete the user verification tasks.

The installation needs to use a standard operating system dynamic link library (dll) to complete its task of verifying, and if necessary creating, the supplied user.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify that the Path system variable points to the location of all the operating system dlls, and that the dlls are available. Depending on what you find, you might need to reinstall the operating system before continuing with the installation.

If you are able to solve the problem so that the installation is capable of using the operating system dlls to verify and create users, the installation can be resumed at the failed step, as follows:
- Resume the step of the interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed again.
  6. Click Run all to resume the installation from that step.
- Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed, as described above.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS047E

The installation encountered an error running the Tivoli Workload Scheduler Windows configuration script.

The reason for the failure is documented in the installation log file.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the configuration script failed.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS048E

The installation cannot read the following file: "file_name".

The file_name is the fully qualified path of the file that cannot be read.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify that the file exists and has read permission for the user performing the installation. Ensure that it has not been locked by another application, such as a file editor.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the file cannot be read.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS049E

The installation cannot write the following file: "file_name".

The file_name is the fully qualified path of the file that cannot be written.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify that the user performing the installation has write permission for the file. Check if the file exists, and ensure that it has not been locked by another application, such as a file editor.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the file cannot be written.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS050E

The installation cannot move the following file: "file_name".

The file_name is the fully qualified path of the file that cannot be moved.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify that the file being moved has read permission for the user performing the installation. Verify that the directory where the installation wants to move the file to has write permission for the user performing the installation.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the file cannot be moved.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS052E

Composer could not update the database.

If you are upgrading this instance of Tivoli Workload Scheduler, the problem could be that the user who is performing the upgrade is not authorized to use composer. The upgrade process needs to use composer to check the security data contained in the Security file.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If the user who is performing the upgrade is not authorized to use composer, locate and delete the Security file, and resume the final commit phase of the installation. In the absence of a Security file the installation recreates it with the correct rights.

If this not the case you need to find out why the commit phase failed.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why Composer could not update the database.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS053E

The installation could not create the Security file.

See message text.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the Security file could not be created.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS054E

The installation could not run the final installation commit phase.

See message text.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that explain why the installation could not run the final installation commit phase.

If you can solve the problem, do so, and proceed as follows.

You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Status tab set the status to Ready
  2. Click Apply. The Step List window is displayed.
  3. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Resume the step that failed.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS056E

The directory that contains the embedded WebSphere Application Server installation files cannot be found.

The installation program is trying to locate the directory where the embedded WebSphere Application Server files were unpacked at the beginning of the installation, but has failed to find it. Either the unpacking of the installation bundle failed, or the directory has subsequently been renamed or deleted.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The problem might be resolved by rerunning the installation from the beginning.

  • If you are running the interactive wizard, click Cancel to exit from the wizard.
  • If you are running the silent wizard, the wizard has already stopped.

If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.

Rerun the installation. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJIS057E

The tar file that contains the embedded WebSphere Application Server installation files cannot be found.

The installation program is trying to locate the tar file that contains the embedded WebSphere Application Server files, but has failed to find it. Either the unpacking of the installation bundle failed, or the file has subsequently been renamed or deleted.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The problem might be resolved by rerunning the installation from the beginning.

  • If you are running the interactive wizard, click Cancel to exit from the wizard.
  • If you are running the silent wizard, the wizard has already stopped.

If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.

Rerun the installation. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJIS058E

The script db2profile used to create the DB2 environment cannot be found in the DB2 installation directory.

The installation program is trying to locate the db2profile file that contains the DB2 installation files, but has failed to find it. Either the unpacking of the installation bundle failed, or the file has subsequently been renamed or deleted.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Administration and Troubleshooting, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

Ensure that you are not trying to run two installations concurrently, which is not possible.

If you can solve the problem, do so, and proceed as follows:

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJIS059E

The fully qualified domain name of this computer is null. The installation requires the fully qualified domain name to configure Tivoli Workload Scheduler correctly.

The computer where you are installing Tivoli Workload Scheduler is not correctly set up in your network with its fully qualified domain name. Perhaps you are installing Tivoli Workload Scheduler on a new computer which has not yet been configured for network access. The installation program requires the fully qualified domain name (for example, mycomputer.rome.ibm.com) to be defined on the local computer to configure Tivoli Workload Scheduler correctly.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Resolve the problem by configuring the computer for network access.

If you are running the interactive wizard stop the installation program to reconfigure the network access. Do this as follows:
  1. Click OK to close the error popup. The Diagnose Failure window is opened.
  2. Click Quit to close the wizard.
Resume either an interactive or a silent installation from the failed step by rerunning the installation program, adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step. Proceed as follows:
  1. Double-click the failed installation step and the Step Status window opens.
  2. On the Status tab set the status to Ready
  3. Click Apply. The Step List window is displayed again.
  4. Click Run all to resume the installation from that step.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS060E

The supplied TWS_user could not be created.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Administration and Troubleshooting, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that might explain why the user cannot be created.

The probable cause is that in correcting a failed installation using the step resume facility, the TWS_user ID was changed to a non-valid ID. This is because the ID was checked for validity at input, and you would not have been able to start the installation if the user ID was not valid.

The reason why the ID has now been rejected could be one of the following:
  • The user performing the installation does not have the rights to create a user
  • The supplied user name does not satisfy the requirements of the local account policy
  • The supplied password of the TWS_user does not satisfy the requirements of the local security policy
  • The Windows account management administration wizard is open
Correct any errors you find.
You might be able to resume the step, or you might have to rerun the installation from the beginning.
- Interactive wizard
Resume the step of the interactive wizard
  1. On the Properties tab change the TWS_user ID. If it is not available for editing, return to previous steps, until you find one where you can edit the value or values.
  2. Repeat this step for all other steps, checking to see if the user account is included as a property for that step, and changing it if it is. This is because the installation wizard creates each step as a separate action, complete with its properties; changing a value on one does not change it automatically also on the others.
  3. On the Status tab set the status to Ready
  4. Click Apply. The Step List window is displayed.
  5. Click Run all to resume the installation from that step.

If the problem is not resolved, try exiting from the wizard and recommencing the installation, as follows.

Rerun the interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  4. Rerun the wizard.
- Silent wizard
Resume the step of the silent wizard
You cannot troubleshoot a failed installation with the silent wizard. Instead, do as follows:
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Follow the procedure described for the interactive wizard to correct the user ID and resume the installation.
If this does not resolve the problem, try rerunning the silent wizard, as follows.
Rerun the silent wizard.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent wizard.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS061W

The supplied TWS_user exists on the local computer but does not have the correct rights. The installation is attempting to modify the rights.

See message.

The wizard continues. When the installation starts, the wizard attempts to modify the rights of the TWS_user.

None.

AWSJIS063E

The supplied password is incorrect for the supplied TWS_user.

You have specified an existing user but the supplied password is not correct for that user.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Supply a different password or a different user ID and password.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Either change the TWS_user, or its password, (or both) so that the correct password is supplied for the user.
  3. Click Next to continue.
- Silent wizard
  1. Look in the installation log to see if there is any additional information
  2. Edit the response file used by the silent wizard, changing the TWS_user, or its password, (or both), so that the correct password is supplied for the user.
  3. Rerun the silent wizard.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS064E

The supplied TWS_user account cannot be verified automatically. This is because the user running the installation program does not have the Act as part of the operating system privilege, or the password of the user has expired.

The user running an installation on Windows 2000 (but not on Windows XP and later) requires the Act as part of the operating system privilege. The check for this privilege also fails if the password has expired, whether or not the account has the privilege.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Add the privileges to the account of the user running the installation, renew the password, or rerun the installation as a different user. If you change the account on the computer you will almost certainly need to reboot the computer. Thus, in all cases, if you are running the interactive wizard you must stop it, as follows:
  1. Click OK to close the error popup window.
  2. Click Cancel to exit from the installation.

Change the account or its password, or log off and on again using a different user that has the correct privileges or whose password has not expired.

Rerun the wizard from scratch.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID and password, and the time it runs the Create User step, any changes are made to the user ID or its password, either on the computer or in the step properties dialogs as a result of a failed installation. This is unlikely to occur, but if it does you must rerun the installation.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS065E

The user running the installation does not have the correct privileges to verify the privileges of the supplied TWS_user.

The installation program has verified that either the Act as part of the operating system privilege is not required, or is present in the profile of the user running the installation, but the attempt to verify the TWS_user has failed for another reason associated with privileges. It might be that the user does not have the Windows default Administrator privileges.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Add the Windows default Administrator privileges to the account of the user running the installation, or rerun the installation as a different user. If you change the account on the computer you will almost certainly need to reboot the computer. Thus, in either case, if you are running the interactive wizard you must stop it, as follows:
  1. Click OK to close the error popup window.
  2. Click Cancel to exit from the installation.

Change the account, or log off and on again using a different user that has the correct privileges.

Rerun the wizard from scratch.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID, and the time it runs the Create User step, any changes are made to the user ID, either on the computer or in the step properties dialogs as a result of a failed installation. This is unlikely to occur, but if it does you must rerun the installation.

The Planning and Installation Guide: contains details of the privileges required to run the installation.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS066E

The installation was unable to check the existence of the supplied TWS_user.

The user running the installation has the correct privileges to verify the existence of the TWS_user, but a problem associated with the user ID or password has prevented it from doing so. It is possible that the user name or password you supplied contained special characters or characters that do not belong to the codeset of the computer. It is possible that the account management facilities of the computer are in use, not working or are blocked in some other way.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Ensure the following:
  • Ensure that the TWS_user ID and password do not contain any unusual characters that might give codeset translation problems
  • Ensure that the user account management facilities on the computer are not in use by you or any other user
  • Ensure that the user account management facilities are available and working. To do this, attempt to access the details of a user account, but be sure to close the account management facilities window when you have finished
If you have found and fixed a problem with the account management facilities you can continue the installation. Otherwise, close the installation and rerun it as a different user
- Interactive wizard
Continue the installation
  1. Click OK to close the error popup window.
  2. Click Next to continue.
Rerun the installation
  1. Click OK to close the error popup window.
  2. Click Cancel to quit the installation.
  3. Login as a different user.
  4. Rerun the wizard.
- Silent wizard

Just rerun the wizard in either case.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID, and the time it runs the Create User step, any changes are made to the user ID, either on the computer or in the step properties dialogs as a result of a failed installation. This is unlikely to occur, but if it does you must rerun the installation.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS067E

The installation could not modify the privileges of the supplied TWS_user.

You have supplied a TWS_user that exists on the local computer but has insufficient rights. The installation has tried to modify those rights but cannot. Probably, the user that is running the installation does not have the correct rights to modify the supplied user's rights.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Add the Windows default Administrator privileges to the account of the user running the installation, or rerun the installation as a different user. If you change the account on the computer you will almost certainly need to reboot the computer. Thus, in either case, if you are running the interactive wizard you must stop it, as follows:
  1. Click OK to close the error popup window.
  2. Click Cancel to exit from the installation.

Change the account, or log off and on again using a different user that has the correct privileges.

Rerun the wizard from scratch.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID, and the time it runs the Create User step, any changes are made to the user ID, either on the computer or in the step properties dialogs as a result of a failed installation. This is unlikely to occur, but if it does you must rerun the installation.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS068E

The installation could not add the supplied TWS_user to the Administrators group.

You have supplied a TWS_user ID that did not exist on the computer and the installation has created an account for it. However, it could not add the account to the Administrators group. Probably, the user that you are using to run the installation does not have the correct privileges to add a user to that group.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Add the Windows default Administrator privileges to the account of the user running the installation, or rerun the installation as a different user. If you change the account on the computer you will almost certainly need to reboot the computer. Thus, in either case, if you are running the interactive wizard you must stop it, as follows:
  1. Click OK to close the error popup window.
  2. Click Cancel to exit from the installation.

Change the account, or log off and on again using a different user that has the correct privileges.

Rerun the wizard from scratch.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID, and the time it runs the Create User step, any changes are made to the user ID, either on the computer or in the step properties dialogs as a result of a failed installation. This is unlikely to occur, but if it does you must rerun the installation.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS069E

The installation could not find an operating system dll to complete the TWS_user verification tasks.

The installation needs to use a standard operating system dynamic link library (dll) to complete its task of verifying, and if necessary creating, the supplied user.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify that the PATH system variable points to the location of all the operating system dlls, and that the dlls are present (your operating system documentation might identify which dlls are responsible for user account verification). Depending on what you find, you might need to reinstall the operating system before continuing with the installation. Verify also that the user running the installation has execute permission for operating system dlls.

Whatever the solution to the problem, rerun the wizard. If you are running the interactive wizard you need to stop the installation program. Do this as follows:
  1. Click OK to close the error popup.
  2. Click Cancel to close the wizard.

Rerun the wizard from scratch.

Note:This message might also be given when the Create User step is run. This only occurs if, between the time that the wizard validates the input values for the user ID, and the time it runs the Create User step, any changes are made to the dlls. This is unlikely to occur, but if it does you must rerun the installation.

AWSJIS070E

The supplied TWS_user could not be created.

You have supplied a TWS_user ID that did not exist on the computer but the installation has not been able to create it.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error popup window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent wizard, see the installation log file for the error messages that might explain why the user cannot be created.

Ensure the following:
  • Ensure that the TWS_user ID and password respect local security policy
  • Ensure that the user running the installation has the rights to create a user. Remember to close the account management facilities before proceeding. If it does not, add those rights, or run the installation using a user that has those rights.
The problem resolution depends on what you found:
- Problems with an existing <TWS_user> ID or password

Supply a different TWS_user ID and password. As everything in the installation relates to this user, you must rerun the installation, supplying the new TWS_user ID.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Quit to exit from the installation.
  3. Rerun the installation, supplying a different TWS_user ID and password.
Silent wizard
  1. Edit the response file used by the silent wizard, changing the TWS_user and its password.
  2. Rerun the silent wizard.
- Problems with the password supplied for a <TWS_user> that is being created

Supply a different password.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Properties tab change the TWS_user password. If it is not available for editing, return to previous steps, until you find one where you can edit the value or values.
  5. Repeat this step for all other steps, checking to see if the password is included as a property for that step, and changing it if it is. This is because the installation wizard creates each step as a separate action, complete with its properties; changing a value on one does not change it automatically also on the others.
  6. On the Status tab set the status to Ready
  7. Click Apply. The Step List window is displayed.
  8. Click Run all to resume the installation from that step.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the TWS_user password.
  2. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  3. Follow the procedure described for the interactive wizard to correct the user ID and resume the installation.
- Problems with the user privileges
Choose one of these options:
Rerun with a different user
  1. If you are running the interactive wizard you need to stop the installation program . Do this as follows:
    1. Click OK to close the error popup. The Diagnose Failure window is opened.
    2. Click Quit to close the wizard.
  2. Log on as a different user with the Windows default Administrator privileges.
  3. Rerun the installation without a resume. You cannot do a step resume of an installation if you have changed the user that is running it; you must rerun the installation from scratch.
Add the missing privileges to your user profile
  1. If you are running the interactive wizard you need to stop the installation program . Do this as follows:
    1. Click OK to close the error popup. The Diagnose Failure window is opened.
    2. Click Quit to close the wizard.
  2. Add the necessary privileges to the profile of the user running the installation, so that it has the default Administrator privileges (you might need to log on as an Administrator to do this).
  3. Reboot the computer.
  4. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  5. Double-click the failed installation step and the Step Status window opens.
  6. On the Status tab set the status to Ready
  7. Click Apply. The Step List window is displayed again.
  8. Click Run all to resume the installation from that step.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS071E

The supplied TWS_user name incorrectly contains a period.

This message indicates that during the recovery operation of a previously failed installation, you modified the TWS_user name and included a period in the name. The TWS_user ID was validated on input, and the presence of a period would not have allowed the installation to go ahead.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

You must rerun the wizard, reinputting the TWS_user ID as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Quit to exit from the installation.
  3. Rerun the installation, resupplying the TWS_user ID and password.
- Silent wizard
  1. Rerun the silent wizard.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS072E

The supplied TWS_user ID is longer than the maximum length of "maximum_length" bytes.

See message.

maximum_length is the maximum permitted length in bytes of the TWS_user ID.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Back to return to the previous panel and change the TWS_user to a value no longer than the maximum length.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the TWS_user to a value no longer than the maximum length.
  2. Rerun the silent wizard.

AWSJIS073E

The supplied TWS_user "TWS_user_ID" does not exist on the local computer, but the installation cannot create this user, because another object exists with the supplied name.

You have supplied a user ID that does not exist. The installation has tried to create a user with the supplied ID, but has found another object exists (such as a domain or a user group) with the supplied ID.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Choose a different user ID that does not exist on this computer in any form and rerun the installation without a resume. You cannot do a step resume of an installation if you have changed the TWS_user, you must rerun the installation from scratch.

Interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. Rerun the wizard.
Silent wizard.
  1. Rerun the silent wizard.

AWSJIS074E

The supplied TWS_user ID incorrectly contains a period.

This message indicates that during the recovery operation of a previously failed installation, you modified the TWS_user ID and included a period in the name. The TWS_user ID was validated on input, and the presence of a period would not have allowed the installation to go ahead.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

You must rerun the wizard, reinputting the TWS_user ID as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Quit to exit from the installation.
  3. Rerun the installation, resupplying the TWS_user ID and password.
- Silent wizard
  1. Rerun the silent wizard.
The chapter on Troubleshooting installation, migration, and uninstallation in Administration and Troubleshooting for full details of the recovery process from a failed installation.

AWSJIS075E

The supplied TWS_user does not exist. On UNIX platforms the user chosen for the TWS_user must exist with the correct permissions before starting the installation program.

See message text.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Choose an existing user or create an account expressly for the installation. You must rerun the wizard, changing the TWS_user ID as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Quit to exit from the installation.
  3. Rerun the installation, supplying a different TWS_user ID and its password.
- Silent wizard
  1. Edit the response file, changing the TWS_user ID and its password.
  2. Rerun the silent wizard.
The Planning and Installation Guide for information about the required characteristics of the <TWS_user>.

AWSJIS076E

The supplied port: "port_number" is already in use.

See message.

port_number identifies the port that is already in use.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Supply a different port that is not in use.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the port.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the value of the indicated port.
  2. Rerun the silent wizard.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS077E

The user running the installation is not in the Administrator group, or does not have Administrator rights.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The user performing the installation must be both in the Administrator group, and have Administrator rights. Either choose a different Administrator user, or modify the rights, and the group, (or both), of the user performing the installation. In the latter case you might have to reboot the computer. In either case rerun the installation.

- Interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. Log on as a user in the Administrator group, and with Administrator rights.
  4. Rerun the wizard.
- Silent wizard.
  1. Log on as a user in the Administrator group, and with Administrator rights.
  2. Rerun the silent wizard.

AWSJIS078E

The user running the installation is not root.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The user performing the installation must be root. Rerun the installation as root.

- Interactive wizard
  1. Close the Step Status window
  2. Select Quit installation. The wizard closes.
  3. Log on as root.
  4. Rerun the wizard.
- Silent wizard.
  1. Logon as root.
  2. Rerun the silent wizard.

AWSJIS079E

The supplied ports are not unique. Specify a different value for each port.

See message.

port_number identifies the port that is already in use.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the port numbers you have used. Make sure that a unique value has been supplied for each port and that the supplied ports are available.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the port or ports.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the value of the indicated port or ports.
  2. Rerun the silent wizard.

AWSJIS080E

The directory "directory" cannot be created.

See message.

directory identifies the directory that cannot be created.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Ensure the following in the path indicated:
  • Ensure that the directory does not already exist.
  • Ensure that there is sufficient space in the file set for the installation.
  • Ensure that the user running the installation has write permission for that path.
  • Ensure that the directory name is allowed in the system.

When you have located the problem, fix it either by making it possible to use the chosen directory, or by deciding to use a different directory, depending on the nature of the problem.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. If you have decided to use a different directory, change it on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. If you have decided to use a different directory, edit the response file used by the silent wizard, changing the value of the directory.
  2. Rerun the silent wizard.

AWSJIS081E

The directory "directory" does not have write permission.

See message.

directory identifies the directory that does not have write permission for the user running the installation.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Either give write permission in the directory to the user running the installation, or decide to choose a different directory.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. If you have decided to use a different directory, change it on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. If you have decided to use a different directory, edit the response file used by the silent wizard, changing the value of the directory.
  2. Rerun the silent wizard.

AWSJIS082E

The following fields "field1" and "field2" cannot contain the same value.

See message.

field1 and field2 identify two fields that cannot have the same value.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Change one or both of the fields so that they are unique.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change one or both of the fields on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing one or both of the fields.
  2. Rerun the silent wizard.

AWSJIS083E

The directory "directory" is not a valid directory.

See message.

directory is the directory path you have supplied, which is not a valid directory.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Choose a different directory.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the directory on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the value of the directory.
  2. Rerun the silent wizard.

AWSJIS084E

The command line client for Tivoli Workload Scheduler, version 8.6 is already installed in the specified installation location.

The wizard has found an existing installation of the command line client in the chosen installation path.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Either stop the installation, or choose a different directory.

To choose a different directory, proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the directory on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard, changing the value of the directory.
  2. Rerun the silent wizard.

AWSJIS085E

The connection to the database has failed. Check that the DB2 server is running and that the user and password are correct.

The installation is attempting to connect to the database but the connection cannot be established.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that DB2 is up and running. Check that the specified user and password have the rights to connect to the database. Start the database manager, if it is stopped. Connect to the database with a user that has the rights to connect.

If you make a successful connection, resume the installation at the failed step, as follows:
- Interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed installation step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed.
  6. Click Run all to resume the installation from that step.
- Silent wizard
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Follow the procedure described for the interactive wizard and resume the installation.
The chapter on Troubleshooting installation, migration, and uninstallation in Administration and Troubleshooting for full details of the recovery process from a failed installation.

AWSJIS086W

The credentials for using the Tivoli Workload Scheduler command line client are already present on this computer (in the useropts file), but they are overwritten by this installation.

The connection parameters used to connect to the command line client are stored in the local useropts file. When you install the command line client they normally contain default values. They are now overwritten by the actual values determined by the installation wizard.

The wizard proceeds.

None.

AWSJIS088E

An error occurred while stopping the embedded WebSphere Application Server.

See message.

The uninstallation stops.

Check that the credentials supplied for accessing the embedded WebSphere Application Server are correct. If they are not, correct them and retry the uninstallation.

If the credentials are correct, stop the embedded WebSphere Application Server by using the appropriate command, and retry the operation.

The appropriate publications for the embedded WebSphere Application Server for information about the commands.

AWSJIS090E

An error occurred while uninstalling the Tivoli Workload Scheduler instance.

See message.

The uninstallation stops.

Check the log for other messages that might help you to understand why the action failed.

Check that the Tivoli Workload Scheduler instance is defined in the IBM Tivoli Configuration Manager catalog. To do this, follow this procedure:

  1. Set the IBM Tivoli Configuration Manager by running . ./swd_env.sh from the <install_dir>/_uninstall/CLI directory.
  2. Run the command wdlssp
  3. Check if the instance of Tivoli Workload Scheduler is listed.

    If it is not listed, either the instance has already been uninstalled, or it was not installed correctly. In the latter case, see Planning and Installation for details of how to manually complete an installation that could not be uninstalled normally.

    If it is listed, continue the uninstallation using the twsRemove script located in the <install_dir>/_uninstall/ACTIONTOOLS directory.

AWSJIS091E

The uninstall wizard could not find any instances of Tivoli Workload Scheduler on this computer to uninstall.

See message. It is possible that Tivoli Workload Scheduler was not installed correctly, or has already been uninstalled.

The uninstallation stops.

Determine the original installation directory (the Planning and Installation Guide indicates the default directory) and check if it is present. If the installation directory is present on the computer, and contains data, Tivoli Workload Scheduler was not installed correctly. In this case, see Planning and Installation for instructions on uninstalling Tivoli Workload Scheduler manually.

If the installation directory is not present, or contains no data, Tivoli Workload Scheduler has been uninstalled without removing the uninstaller. Locate the uninstaller and delete it.

AWSJIS092E

An error has occurred while uninstalling the Tivoli Workload Scheduler command line client.

See message. It is possible that the Tivoli Workload Scheduler command line client has already been uninstalled.

The uninstallation stops.

Check whether the command line client has been uninstalled by checking the presence of the <TWS_home>/cli directory. If it does not exist, the command line clienthas been uninstalled without removing the uninstaller. Locate the uninstaller and delete it.

If the directory is present, attempt to delete it. If you succeed, the uninstallation is almost complete, so just locate and delete the uninstaller.

If the directory cannot be deleted, a process has locked one or more of the files. Check the Tivoli Workload Scheduler processes running on the computer. If any processes are running, make sure that they have completed all activities and stop them. Rerun the uninstallation.

AWSJIS098E

An internal error has occurred. A program has failed unexpectedly.

See message.

The installation stops.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS099E

The DB2 response file does not exist:

The installation creates a response file to install DB2 silently, based on your input on the DB2 installation wizard panel. This response file cannot be found in the location where it was created. Between the installation step that created the file and the installation step that needed to use the file, the file was moved, deleted or renamed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

You must resume the installation at the step that creates the DB2 response file, as follows:
- Interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Locate the step entitled: Create the DB2 response file.
  4. Double-click the step and the Step Status window opens.
  5. On the Status tab set the status to Ready
  6. Click Apply. The Step List window is displayed.
  7. Click Run all to resume the installation from that step.
- Silent wizard
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Follow the procedure described for the interactive wizard and resume the installation.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS100E

You have supplied a path to identify the supported DB2 installation: "DB2_path" but either no installation exists at that location, or the installation that exists is not a supported version. Supported versions are 9.5 and 9.7. Versions 8.2 (8.1 with Fix Pack 7) and 9.1 are supported during the installation, but you are advised to migrate it to a supported version after completing the installation. For the HP-UX operating system the supported version is 9.1. Version 8.2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation. See the System Requirements document in the Information Center for a detailed explanation of the supported versions. Check the help for this message (in the Messages manual) to determine the correct path to supply.

Possible reasons are:

  • You have identified a DB2 directory, but that directory is not the one where the instance is installed. The correct directory is as follows:
    UNIX

    The fully-qualified path must point to the sqllib directory in the DB2 structure.

    Windows

    The fully-qualified path must identify a tree in the DB2 structure that includes the db2level.exe file.

  • You are installing on a version of DB2 that is not supported.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Install on a supported version of DB2.

If the supplied location is not correct, supply a different DB2 location.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message window.
  2. Change the DB2 location on the wizard panel.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard. Change the DB2 location.
  2. Rerun the silent wizard.

If the

AWSJIS101E

The supplied existing DB2 installation cannot be used because the version is lower than the minimum supported version: 9.5. Versions 8.2 (8.1 with Fix Pack 7) and 9.1 are supported during the installation, but you are advised to migrate it to a supported version after completing the installation. For the HP-UX operating system the supported version is 9.1. Version 8.2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation. see the System Requirements document in the Information Center for a detailed explanation of the supported versions). Check the help for this message (in the Messages manual) to determine the correct path to supply.

You have supplied a path to identify the supported DB2 installation that already exists on this computer. The installation that exists is not a supported version: minimum version is 9.5.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Either supply a different DB2 location, or ask the wizard to install DB2 for you. In this latter event, you must ensure that the computer where you are performing the installation satisfies the DB2 prerequisites.

In either case, proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the DB2 location on the wizard panel or click Back to return to the DB2 Installation Actions panel and choose to install DB2.
  3. Click Next to continue.
- Silent wizard
  1. Edit the response file used by the silent wizard. Change the DB2 location, or select the option to install DB2, and supply all the required DB2-related information.
  2. Rerun the silent wizard.

AWSJIS102E

The port specified for the DB2 instance is not in use.

You have identified the port on which the DB2 server instance is listening, but that port is not in use. Either the DB2 server is not running or you have supplied an incorrect port.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that the DB2 server is active and the DB2 instance port you have supplied is correct.

If the DB2 server is inactive, start the server and continue the installation.

If the DB2 instance port is incorrect, supply a different instance port and continue the installation.

In either case, proceed as follows:
- Interactive wizard
  1. Click OK to close the error popup window.
  2. If the DB2 instance port is incorrect, change it on the wizard panel
  3. Click Next to continue.
- Silent wizard
  1. If the DB2 instance port is incorrect, edit the response file used by the silent wizard. Change the DB2 instance port.
  2. Rerun the silent wizard.

Note:This message might also be given during the installation steps that configure DB2 and verify that it is working correctly. This only occurs if, between the time that the wizard validates the input values for the instance port, and the time it runs these steps, the DB2 server is stopped or its port changed. This is unlikely to occur, but if it does you must rerun the installation.

AWSJIS103E

The installation could not create the backup directory with the supplied name: "backup_directory"

You are running an upgrade and have identified a backup directory that does not yet exist for the previous version of Tivoli Workload Scheduler. However, when the wizard tried to create the backup directory an error was given by the operating system. There might be a problem with permissions or disk space.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the following:
  • Check that the user running the installation has permission to create a directory at that location. If not, change the user permissions or choose to run the installation from a different user. In either case you might need to exit from the installation (for example if you need to reboot your computer after changing user permissions), and rerun it from scratch, as described below.
  • Check that there is sufficient disk space in the fileset of the indicated directory. If not, make more space in the fileset and continue the installation, or go back and change the backup directory to a fileset with sufficient space. Check the size of the current installation to determine how much space is required.
  • Check that the directory name is valid for the operating system. If not, go back and change the backup directory name.
- Rerun the installation
  1. If you are running the interactive wizard, click OK to close the error popup window.
  2. Either log on as a different user or change the user permissions.
  3. Rerun the wizard, interactively or silently, with a different user.
- Continue the installation
Interactive wizard
  1. Click OK to close the error popup window.
  2. If you need to, change the backup directory on the wizard panel
  3. Click Next to continue.
Silent wizard
  1. If you need to, edit the response file used by the silent wizard. Change the backup directory.
  2. Rerun the silent wizard.

AWSJIS104E

The installation could not read the file "backup_program_files_list_file" containing a list of the files that need to be backed up.

You are running an upgrade and have identified a backup directory in which to back up the previous version. To perform the backup the installation needs to access and read a file containing a list of the files that need to be backed up. This file is supplied as part of the installation package. If it cannot be read, it might have been damaged in copying it to the hard disk.

backup_program_files_list_file is the name of the file that contains a list of the program files to backup.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check if the file exists. If it does not, or it seems to have been edited or damaged, you could attempt to replace it from the version on the product CD, after which you can continue the installation. However, if this file is missing or damaged, it is likely that other files are missing or damaged, as well. In this case rerun the installation, either directly from the CD, or by copying the installation files from the CD to hard disk again, ensuring that you use the binary option if the copy mode is ftp.

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. Then click Cancel to exit from the wizard.
  2. Rerun the wizard, interactively or silently.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS105E

The installation could not read the file "backup_config_files_list_file" containing the names of the configuration files that need to be backed up.

You are running an upgrade and have identified a backup directory in which to back up the previous version. To perform the backup the installation needs to access and read a file containing a list of the files that need to be backed up. This file is supplied as part of the installation package. If it cannot be read, it might have been damaged in copying it to the hard disk.

backup_config_files_list_file is the name of the file that contains a list of the configuration files to backup.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check if the file exists. If it does not, or it seems to have been edited or damaged, you could attempt to replace it from the version on the product CD, after which you can continue the installation. However, if this file is missing or damaged, it is likely that other files are missing or damaged, as well. In this case rerun the installation, either directly from the CD, or by copying the installation files from the CD to hard disk again, ensuring that you use the binary option if the copy mode is ftp.

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. Then click Cancel to exit from the wizard.
  2. Rerun the wizard, interactively or silently.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS106E

The path "backup_directory" supplied for the backup directory is too long.

You are running an upgrade and have identified a backup directory that does not yet exist for the previous version of Tivoli Workload Scheduler. However, the supplied directory path is too long.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Back up the Tivoli Workload Scheduler instance selected for upgrade

Check the value of the backup directory path you have chosen. Either choose a different directory in a shorter path, or change the directory names in the path of the chosen directory so that the path is shorter.

Resume the installation, as follows:
- Interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the Back up the Tivoli Workload Scheduler instance selected for upgrade step and the Step Status window opens.
  4. On the Properties tab change the directory path to the new or amended directory you have chosen.
  5. On the Status tab set the status to Ready
  6. Click Apply. The Step List window is displayed.
  7. Click Run all to resume the installation from that step.
- Silent wizard
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Follow the procedure described for the interactive wizard and resume the installation.

AWSJIS107E

The installation cannot rename the file "file".

See message.

file identifies the file that could not be renamed.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that the user running the installation has permission to rename a file at that location. If not, change the user permissions or choose to rerun the installation from a different user. In either case you might need to exit from the installation (for example if you need to reboot your computer after changing user permissions), and rerun it from scratch.

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. Then click Cancel to exit from the wizard.
  2. Either log on as a different user or change the user permissions.
  3. Rerun the wizard, interactively or silently, with a different user.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS109E

You are trying to install Tivoli Workload Scheduler on a workstation where one or more agent processes are still running.You must stop all Tivoli Workload Scheduler processes before installing another instance or upgrading an existing instance.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Stop any active processes as described in the Planning and Installation Guide.

Resume the installation, as follows:
- Interactive wizard
  1. Click OK to close the error popup window. The Diagnose Failure window is opened.
  2. Select Diagnose failure and click Next. The Step List window is opened.
  3. Double-click the failed step and the Step Status window opens.
  4. On the Status tab set the status to Ready
  5. Click Apply. The Step List window is displayed.
  6. Click Run all to resume the installation from that step.
- Silent wizard
  1. Resume the installation adding the parameter -resume. The wizard resumes in interactive mode at the Step List window showing the failed step.
  2. Follow the procedure described for the interactive wizard and resume the installation.

AWSJIS110E

The installation cannot read the file "installation_program_files_list_file" that contains the names of the installation programs.

The installation needs to access and read a file containing a list of the installation program files. If it cannot be read, it might have been damaged in copying it to the hard disk.

installation_program_files_list_file is the name of the file that contains a list of the installation program files.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check if the file exists. If it does not, or it seems to have been edited or damaged, you could attempt to replace it from the version on the product CD, after which you can continue the installation. However, if this file is missing or damaged, it is likely that other files are missing or damaged, as well. In this case rerun the installation, either directly from the CD, or by copying the installation files from the CD to hard disk again, ensuring that you use the binary option if the copy mode is ftp.

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. Than click Cancel to quit the wizard.
  2. Rerun the wizard, interactively or silently.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS111E

The installation was unable to access one or more Windows processes.

You are probably running the installation with a Windows system management application open. Possible applications which must be closed include: Task Manager, Services, Computer Management, and RegEdit.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Verify if the Windows Task Manager, Services, Computer Management, RegEdit or other system management processes are running. If so, close it or them and continue the installation. If none appear to be open, reboot the workstation and rerun the installation.

The following describes how to continue or to rerun the installation:
- Continue the installation
  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.
- Rerun the installation
  1. If you are running the interactive wizard, click OK to close the error popup window.
  2. Reboot the computer.
  3. Rerun the wizard, interactively or silently, with a different user.

AWSJIS112E

The installation cannot start the process "process_name".

The file containing the process might be missing or corrupt.

process_name identifies the process that cannot be run.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are not running the installation from the original CD, delete the copy you have made of the installation directories and recopy the files from the original CD. If you have ftp'd the install files to the local computer, ensure that you specified the binary option. Now rerun the installation.

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. Than click Cancel to quit the wizard.
  2. Rerun the wizard, interactively or silently.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS113E

Either the userdata or the userdata.KEY file, required for the migration of the user information, was not found in the Tivoli Workload Scheduler instance to be upgraded.

In order to import the passwords of the users of the previous version, the upgrade needs to directly access the userdata and userdata.KEY files, which form part of the Mozart database of the instance being upgraded.

One, other, or both of these files could not be found.

These files are required for the correct running of the previous instance of Tivoli Workload Scheduler.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check for the existence of these files in the previous instance of Tivoli Workload Scheduler. Ensure that the user running the installation has read access to them. If the files have been moved, renamed, or deleted, recover them from a backup of the previous Tivoli Workload Scheduler instance, and use the facilities in the instance to check that the data in them is complete.

When you have fixed the problem, continue the installation as follows:
  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.

AWSJIS114E

There is insufficient disk space available in the directory "directory" to perform the installation of the DB2 component.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory.

See message.

directory is the install directory that has insufficient space.

required_space and available_space indicate what space the installation requires and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

- What to do if you can make space

If you want to persist with the original installation path, use the operating system's commands and utilities to make more space available. When you have done this, proceed as follows:

  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.
- What to do if you cannot make space

If you cannot make sufficient space, you need to change the installation path to one with more available space. To do this, proceed as follows:

  • If you are running the interactive wizard, click OK to close the error popup, and click Back to return to where you supplied the installation path, change it, ensuring that it satisfies the operating system's requirements for a valid path, and click Next to continue.
  • If you were running the silent wizard, edit the response file, changing the installation path so that it satisfies the operating system's requirements for a valid path. Rerun the silent wizard.

AWSJIS115E

There is insufficient disk space available in the directory "directory" to complete the installation of the DB2 programs.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory.

See message.

directory is the install directory that has insufficient space.

required_space and available_space indicate what space the installation requires and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

- What to do if you can make space

If you want to persist with the original installation path, you might be able to use the operating system's commands and utilities to make more space available. When you have done this, proceed as follows:

  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.
- What to do if you cannot make space
On Linux and UNIX, the DB2 binaries are installed on a hard-coded path. If there is insufficient space for them, the installation cannot continue, and you must quit the installation and increase the size of the indicated file system before attempting to rerun the installation. The path for the binaries is as follows:
Linux

/opt/ibm/db2/V9.5

UNIX

/opt/IBM/db2/V9.5

AWSJIS116E

There is insufficient disk space available in the directory "directory" to complete the installation of the Tivoli Workload Scheduler database.The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Either make more space available or change the installation directory.

See message.

directory is the install directory that has insufficient space.

required_space and available_space indicate what space the installation requires and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

- What to do if you can make space

If you want to persist with the original installation path, use the operating system's commands and utilities to make more space available. When you have done this, proceed as follows:

  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.
- What to do if you cannot make space

If you cannot make sufficient space, you need to change the installation path to one with more available space. To do this, proceed as follows:

  • If you are running the interactive wizard, click OK to close the error popup, and click Back to return to where you supplied the installation path, change it, ensuring that it satisfies the operating system's requirements for a valid path, and click Next to continue.
  • If you were running the silent wizard, edit the response file, changing the installation path so that it satisfies the operating system's requirements for a valid path. Rerun the silent wizard.

AWSJIS117E

The supplied port: "port_number" is registered for use by another application in the Services file.

See message.port_number is the port that is not free.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the indicated port number on the wizard panel to a value that is not in use.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the indicated port number to a value that is not in use.
  2. Rerun the silent wizard.

AWSJIS119W

The specified user is a domain user. Check that it has the required rights. See Planning and Installation for details.

A domain user must have the following rights:
- On a computer that is a member of a domain
Only a domain user can start the application server process. It must have the following characteristics:
  • It is a member of the domain administrative groups in the domain controller
  • It has the Act as part of the operating system privilege in the Domain Security Policy on the domain controller
  • It has the Act as part of the operating system privilege in the Local Security Policy on the local computer
  • If the server is run as a service, it has the Log on as a service privilege on the local computer.
- On a computer that is a domain controller
It must have the following characteristics:
  • It is a member of the domain administrative groups in the domain controller
  • It has the Act as part of the operating system privilege in the Domain Security Policy on the domain controller
  • If the server is run as a service, it has the Log on as a service privilege on the domain controller

The installation panel flow waits for you to continue.

Check the rights of the domain user and click Next to continue.

AWSJIS120E

The TWS_user ID of the previous instance of Tivoli Workload Scheduler is longer than the maximum of "max_length" bytes. You cannot upgrade this instance of Tivoli Workload Scheduler.

The TWS_user in version 8.6 must be no more than 8 bytes in length. As the TWS_user in the previous instance is longer, you cannot upgrade the instance.

The installation stops.

Click Back to select a different instance. Click Cancel to exit from the wizard.

Perform a fresh installation and then migrate the data independently from the old instance to the new.

Planning and Installation Guide for details of how to migrate data independently.

AWSJIS122W

The user specified for the DB2 installation "user" already exists.You must be absolutely certain that this user was created by a previous installation of DB2 to go ahead. If in any doubt, either go back and choose another user, or delete the user before continuing with the installation, and let the wizard create it for you.

The attributes and permissions of the user ID must be correct for using DB2.

user is the user that already exists.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

You have three options:
- Continue, using the user ID originally chosen (created for a previous installation of DB2)
  • If you are running the interactive wizard, click OK to close the error popup and click Next to continue.
  • If you were running the silent wizard, rerun the wizard without changing the parameters or the response file.
- Delete the user ID, letting the wizard create an ID with the correct attributes
  1. Delete the user ID using the system's facilities
  2. Proceed as follows:
    • If you are running the interactive wizard, click OK to close the error popup and click Next to continue.
    • If you were running the silent wizard, rerun the wizard without changing the parameters or the response file.
- Go back and change the user ID
  • If you are running the interactive wizard, click OK to close the error popup, and click Back to return to where you supplied the user ID, change it to one that was used to create a DB2 instance, and click Next to continue.
  • If you were running the silent wizard, edit the response file, changing the user ID to one that was used to create a DB2 instance. Rerun the silent wizard.

AWSJIS123E

Unable to find the selected instance to uninstall in the Tivoli Workload Scheduler registry file. You cannot uninstall this instance using the wizard.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, cancel the uninstallation.

Uninstall the instance manually.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for instructions on uninstalling Tivoli Workload Scheduler manually.

AWSJIS124E

Unable to find the selected instance of the command line client to uninstall in the Tivoli Workload Scheduler registry file. You cannot uninstall this instance using the wizard.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

If you are running the interactive wizard, cancel the uninstallation.

Uninstall the instance manually.

The chapter on Troubleshooting installation, migration, and uninstallation in Administration and Troubleshooting for instructions on uninstalling Tivoli Workload Scheduler manually.

AWSJIS125E

There is insufficient disk space available in the temporary directory "directory" to complete the installation. The installation requires "required_space" megabytes, but only "available_space" megabytes are available. Make more space available in the temporary installation directory.

See message.

directory is the temporary directory that has insufficient space.

required_space and available_space indicate what space the installation requires and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Make space in the temporary directory. Or, on Windows, you can change the location of the temporary directory, by temporarily or permanently changing the value of the TMP environment variable.

Proceed as follows:
  • If you are running the interactive wizard, click OK to close the error popup, and click Next to continue.
  • If you were running the silent wizard, rerun the wizard.

AWSJIS126E

The user ID "user_ID" must not begin with sys, ibm, or sql, as these are reserved terms.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the indicated user_ID on the wizard panel to a value that does not begin with any of the indicated values.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the indicated user_ID to a value that does not begin with any of the indicated values.
  2. Rerun the silent wizard.

AWSJIS127E

The user ID"user_ID" must not be: admins, guests, local, public, or users, nor any SQL key word, as these are reserved terms.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the indicated user_ID on the wizard panel to a value that is not any of the indicated names.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the indicated user_ID to a value that is not any of the indicated names.
  2. Rerun the silent wizard.

AWSJIS128E

You specified a TWS_user that already owns an existing Tivoli Workload Scheduler instance.Click Back and specify a different user for the TWS_user.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the <TWS_user> ID on the wizard panel to a value that does not own an existing instance.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the <TWS_user> ID to a value that does not own an existing instance.
  2. Rerun the silent wizard.

AWSJIS129E

The field "field_name" is required.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Provide a valid value for the indicated field.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Provide a valid value for the indicated field.
  2. Rerun the silent wizard.

AWSJIS130E

The field "field_name" must contain a valid value.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Provide a valid value for the indicated field.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Provide a valid value for the indicated field.
  2. Rerun the silent wizard.

AWSJIS131E

The character "character" is not valid.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the indicated character to a valid one.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the indicated character to a valid one.
  2. Rerun the silent wizard.

AWSJIS132E

The field "field_name" must not contain blank characters.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Remove the blank characters in the indicated field.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Remove the blank characters in the indicated field.
  2. Rerun the silent wizard.

AWSJIS133E

There is not enough space in the directory "directory_name". The required space is "required_space" MB. The available space is "available_space" MB.

See message.

directory_name identifies the directory with insufficient space.

required_space and available_space tell you how much space is needed and how much is available.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Either make more space in the indicated directory or plan to select a different directory.

Then proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. If you have chosen to select a different directory, enter the name of, or browse for, a directory with sufficient space.
  3. Click Next to continue.
Silent wizard
  1. If you have chosen to select a different directory, edit the response file used by the silent wizard and change the installation directory to one with sufficient space.
  2. Rerun the silent wizard.

AWSJIS134E

No feature has been selected. Click Back and select a feature to install.

See message.

The wizard stops.

  1. Click OK to close the error popup window.
  2. Click Back and select a feature to install.
  3. Click Next to continue.

AWSJIS135E

Unable to establish a connection to host "host_name" on port "port". Check that the DB2 server is up and running and that it is listening on this port.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that you have identified the DB2 server correctly. Check that the DB2 server is up and running and that it is listening on this port.

When the problem has been resolved, proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. If you have incorrectly identified the DB2 server, change the server details.
  3. Click Next to continue.
Silent wizard
  1. If you have incorrectly identified the DB2 server, edit the response file used by the silent wizard and change the DB2 server details.
  2. Rerun the silent wizard.

AWSJIS136E

The supplied password for the user "user" that the wizard must create does not match the security policy of the computer on which you are performing the installation.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the security policy on the computer where you are performing the installation.

Proceed as follows:
Interactive wizard
  1. Click Back to return to the panel where you supplied the indicated user and password.
  2. Change the password to one that matches the security policy and confirm it.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the password for the indicated user to one that matches the security policy.
  2. Rerun the silent wizard.

AWSJIS137E

The supplied password for the DB2 Administrator "DB2_administrator" is incorrect.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the password you have supplied for the DB2 Administrator.

Proceed as follows:
Interactive wizard
  1. Click Back to return to the panel where you supplied the indicated user and password.
  2. Change the password for the DB2 Administrator to the correct value.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the password for the DB2 Administrator to the correct value.
  2. Rerun the silent wizard.

AWSJIS138E

The specified instance name "instance_name" does not exist on the DB2 server.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the instance name you have supplied for the existing DB2 server. Use the DB2 command db2list to list all the instances of the DB2 server.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the instance name to an existing instance.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the existing DB2 server instance name to an existing instance.
  2. Rerun the silent wizard.

AWSJIS139E

No Oracle Database installation exists at the location "oracle_path". The Oracle path must be a search path that includes the Oracle home directory.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the path you supplied for the Oracle Database installation with the Oracle Database administrator. It must be a search path that includes the Oracle home directory.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the path to the correct value.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the path to the correct value.
  2. Rerun the silent wizard.

AWSJIS140E

The Oracle Database installation that you identified is not a supported version. Supported versions are: Oracle Database 10g Release 2 - Enterprise Edition (10.2.0.x) or later, and Oracle Database 11g Release 2 - Enterprise Edition (11.2.0.0) or later. Version 9 Release 2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation (see the System Requirements document in the Information Center for a detailed explanation of the supported versions).

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the path you supplied for the Oracle Database installation. If it is correctly identifying the instance of Oracle you want to use, then the version of that instance is not supported, and you must upgrade it to one of the supported versions. If you cannot upgrade any instance of Oracle to a supported version you must exit from the wizard and only restart it when you have available a supported version of Oracle or DB2, or have planned to install DB2 with the wizard.

If the path you supplied for the Oracle installation is not identifying the instance of Oracle that you want to use, but you can correct it to indicate a supported instance of Oracle without exiting the wizard, proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. If you were incorrectly identifying the version, change the path to the correct value.
  3. Click Next to continue.
Silent wizard
  1. If you were incorrectly identifying the version, edit the response file used by the silent wizard, and change the path to the correct value.
  2. Rerun the silent wizard.

AWSJIS141E

The value supplied for the input text field "input_field" is not valid.Ensure that the value entered complies with Oracle naming rules.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the supplied Oracle data field. It must comply with Oracle naming rules.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the input_field to the correct value.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the input_field to the correct value.
  2. Rerun the silent wizard.

AWSJIS142E

The listener on the Oracle Database server is not responding to the connection test. This might be caused by:an incorrect value specified for the net service name, or the unavailability of the Oracle server listener.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check that the Oracle server listener is available (ask your Oracle administrator if you do not know how). If it is not, get your Oracle server administrator to make the server listener available.

If the server listener is available, check the supplied net service name.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the net service name if it is incorrect.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the net service name if it is incorrect.
  2. Rerun the silent wizard.

AWSJIS143E

The version of the indicated Oracle Database server is not supported. Supported versions are: Oracle Database 10g Release 2 - Enterprise Edition (10.2.0.x) or later, and Oracle Database 11g Release 2 - Enterprise Edition (11.2.0.0) or later. Version 9 Release 2 is supported during the installation, but you are advised to migrate it to a supported version after completing the installation (see the System Requirements document in the Information Center for a detailed explanation of the supported versions).

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the version of the Oracle server. If it is not a supported version you must upgrade it to one of the supported versions. If you cannot upgrade any version of the Oracle server to a supported version you must exit from the wizard and only restart it when you have available a supported version of Oracle or DB2, or have planned to install DB2 with the wizard.

If you can make a supported version of the Oracle server available without exiting the wizard, proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Click Next to continue.
Silent wizard
  1. Rerun the silent wizard.

AWSJIS144E

The specified table space "tablespace_name" does not exist.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the supplied table space name. It must be an existing table space in your chosen Oracle instance.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the table space name to the correct value.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the table space name to the correct value.
  2. Rerun the silent wizard.

AWSJIS145E

The supplied credentials for user "user_ID" are not correct.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the supplied user ID.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the user ID or its password to the correct values.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the user ID or its password to the correct values.
  2. Rerun the silent wizard.

AWSJIS146E

The DB2 Administrator user name "user_name" can not start with an underscore character _.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Supply a valid DB2 Administrator user name.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Supply a valid DB2 Administrator user name.
  2. Rerun the silent wizard.

AWSJIS147E

The DB2 Administrator user name "user_name" can not start with a number.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Supply a valid DB2 Administrator user name.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Supply a valid DB2 Administrator user name.
  2. Rerun the silent wizard.

AWSJIS148E

No instances of Tivoli Workload Scheduler version 8.6 was found to upgrade to Fix Pack 02.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check if there is a valid version of Tivoli Workload Scheduler, version 8.6 installed on the computer.
  • If you are certain that a valid version is installed, perhaps the product registry is not correctly identifying the valid version, in which case you should contact HCL Software Support for assistance.
  • If there is a version of Tivoli Workload Scheduler prior to version 8.6, you must use the product images that allow you to upgrade from a prior version directly to this Fix Pack.
  • If there is no version of Tivoli Workload Scheduler 8.6 installed on the computer, you must make a fresh installation of Tivoli Workload Scheduler, version 8.6 with this Fix Pack.

In all of these cases, exit from the wizard.

AWSJIS149E

One or more errors have occurred during the migration. Check the troubleshooting information in the directory: "directory".

The installation has verified that one or more errors have occurred during the migration of the previous database. The information about what has occurred can be found in the indicated directory. The error is likely to be the failure to migrate an object type, but it may be limited to a problem with a single object. At worst case it might indicate that no data has been migrated. In most cases the errors indicated by this message are due to problems with access to the previous database.

If you are running the interactive wizard, the wizard stops and displays the panel with this message.

If you are running the silent wizard, the wizard completes the installation, but creates a file called migrationErrors in the directory where the installation logs are written (see the Planning and Installation manual for details).

Proceed as follows:
  1. If you are running the interactive wizard, click OK to close the error popup window. The wizard continues to the finish.
  2. Look in the indicated directory and check the files that log the success and failure of the various migration steps.
  3. Solve the problem that has stopped the data from being migrated.
  4. The recovery action depends on the scale of the problem:
    Object not migrated

    If only a few objects have not been migrated, create these objects in the new database using composer.

    Object type not migrated
    • If all objects of an object type from the database did not migrate, run the datamigrate command on that object type.
    • If the migration failed running either optman miggrunnb or optman miggopts, rerun that command.
    All object types not migrated

    Run the migration manually. The original Mozart database has now been deleted, so you must use the version stored in the backup directory that you identified during the installation.

If the wizard does not successfully complete the installation (apart from this message), you will have the opportunity to rerun the step that imports the data. To do this, follow this procedure
  1. Correct the problem that caused the installation to fail.
  2. Correct the problem that caused this message to be displayed, as described above.
  3. Resume the installation from the data import step, setting the statuses of all other steps that follow it to Ready.

AWSJIS150E

The specified user does not exist.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the user name to a valid one.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the user name to a valid one.
  2. Rerun the silent wizard.

AWSJIS151E

The specified password for the user is wrong.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the password to the correct one.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the password to the correct one.
  2. Rerun the silent wizard.

AWSJIS152E

The supplied database schema "schema_name" must already exist when installing a backup master domain manager.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the database schema name you have used. It must be an existing schema in the chosen Oracle instance.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change the schema_name to the correct one.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change the schema_name to the correct one.
  2. Rerun the silent wizard.

AWSJIS153E

The input fields "field_name1" and "field_name2" must have the same value.

This is a generic message indicating that two input fields must have the same value. For example, if you are installing the DB2 server on UNIX, the DB2 instance name and the ID of the DB2 instance owner must be the same.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Check the values of the indicated fields.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change one or both of the indicated fields to have the same value.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change one or both of the indicated fields to have the same value.
  2. Rerun the silent wizard.

AWSJIS154E

The connection to the DB2 database failed. Verify that the following fields are correct: "database_name", "db2_admin_user", "db2_admin_password". If you are using a DB2 Administration Client, verify also that the "db2_client_user" is correct.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change any of the indicated fields that are incorrect.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change any of the indicated fields that are incorrect.
  2. Save the response file.
  3. Rerun the silent wizard.

AWSJIS155E

An error occurred unzipping the archive in the specified directory. Verify that you have the required permissions in the destination directory.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Change any of the indicated fields that are incorrect.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Change any of the indicated fields that are incorrect.
  2. Save the response file.
  3. Rerun the silent wizard.

AWSJIS157E

An internal error has occurred. The application server profile "profile" for the embedded WebSphere Application Server could not be upgraded.

The installation program needs to upgrade an application server profile for the embedded WebSphere Application Server, and then populate it with the information specific to Tivoli Workload Scheduler, version 8.6 . This message is displayed because the profile could not be upgraded.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Check that the computer where you are installing Tivoli Workload Scheduler satisfies the prerequisite requirements of the embedded WebSphere Application Server . These can be found by clicking the System requirements link on the product information Web page for the embedded WebSphere Application Server at www.ibm.com.

Check that there is sufficient space in the standard temporary directory of the computer.

Check that you have copied the installation images correctly to the computer where you are running the installation wizard.

If you are running the interactive wizard, look at the Output tab on the failed installation step for further information. Do the following:
  1. Note down the error code (so that you can later find it in Planning and Installation, if needed)
  2. Click OK to close the error message window. The Diagnose Failure window is opened.
  3. Select Diagnose failure and click Next. The Step List window is opened.
  4. Select the failed installation step and double click it to open the Step Status window.
  5. Select the Output tab.

If you are running the silent installation, check the installation log for more information.

The problem is resolved by just rerunning the installation.
- Rerun the interactive wizard
  1. If you are running the interactive wizard, close the Step Status window and click Finish on the Step List window. The wizard closes.
  2. If you previously copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  3. Rerun the wizard.
- Rerun the silent installation.
  1. If you have copied the installation images to the local hard disk or to a remote workstation, ensure that the entire disk image was copied, and that the binary option was set if ftp was used.
  2. Rerun the silent installation.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS158E

No additional feature is available for the selected instance. Click Back and select another instance.

See message.

The wizard stops.

  1. Click Back and select another instance.
  2. Click Cancel to exit the wizard.

AWSJIS159E

The port "port_num" has been already specified for the "port_name". Specify a different value.

See message.

port_num identifies the port that has been specified and is duplicate.

port_name identifies the name of the port containing the duplicate information.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Check the port numbers you have used. Make sure that a unique value has been supplied for each port and that the supplied ports are available.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message window.
  2. Change the port or ports.
  3. Click Next to continue.
- Silent installation
  1. Edit the response file used by the silent installation, changing the value of the indicated port or ports.
  2. Rerun the silent installation.

AWSJIS160E

The supplied Oracle Database installation does not have the Partitioning Feature enabled. Install and enable this feature on the selected Oracle installation and then continue or rerun the Tivoli Workload Scheduler installation.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

If you are running the interactive wizard, click OK to close the error message window and Cancel to exit from the wizard.

Check the Oracle installation you have selected and install the Partitioning Feature.

Rerun the installation.

AWSJIS161E

The field "field" with value "value" contains national characters.National characters are not supported for this field.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

If you are running the interactive wizard, click OK to close the error popup window and Cancel to exit the wizard.

Check the Oracle installation you have selected and install the Partitioning Feature.

Rerun the installation.

AWSJIS162E

The supplied password contains an unsupported character.The supported characters are as follows: "characters"

See message.

characters identifies the list of supported characters.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Change the password of the specified user.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message window.
  2. Modify the operating system password of the specified user.
  3. Click Next to continue.
- Silent installation
  1. Change the operating system password of the specified user
  2. Edit the response file used by the silent wizard and change the corresponding password field to match the operating system password..
  3. Rerun the silent installation.
The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS164E

The supplied installation path is already being used by another instance ofTivoli Workload Automation or the Tivoli Workload Scheduler command-line client. Choose another path.

A Tivoli Workload Automation instance can only have one instance of each of its constituent products and components installed in it. To install more than one instance of a product or component, you must install them in a different path, thereby creating a second instance of Tivoli Workload Automation.

For example, if you have installed the Tivoli Workload Scheduler master domain manager with the default path, it will have been installed in a path that includes the token TWA, which indicates that this is the first instance of Tivoli Workload Automation products and components on the system. To install a second Tivoli Workload Scheduler component choose any other path that is not the same as, or within, the path of the first instance. Note that if the default path includes the tokenTWA1, there are already two instances of Tivoli Workload Automation on the system on which you cannot install the component. To install a third Tivoli Workload Scheduler component choose any other path that is not the same as, or within, the path of the first two instances.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Reenter the installation path, ensuring that the path does not identify an existing Tivoli Workload Automation instance, and click Next to continue.
- Silent installation
  1. Edit the response file and ensure that the path does not identify an existing Tivoli Workload Automation instance.
  2. Rerun the silent installation.

AWSJIS165E

No valid instance of Tivoli Workload Automation has been specified.Specify a valid instance or install the component in a new instance.

A Tivoli Workload Automation instance can only have one instance of each of its constituent products and components installed in it. To install more than one instance of a product or component, you must install them in a different path, thereby creating a second instance of Tivoli Workload Automation.

For example, if you have installed the Tivoli Workload Scheduler master domain manager with the default path, it will have been installed in a path that includes the token TWA, which indicates that this is the first instance of Tivoli Workload Automation products and components on the system. To install a second Tivoli Workload Scheduler component choose any other path that is not the same as, or within, the path of the first instance. Note that if the default path includes the token TWA1, there are already two instances of Tivoli Workload Automation on the system on which you cannot install the component. To install a third Tivoli Workload Scheduler component, choose any other path that is not the same as, or within, the path of the first two instances.

The silent installation fails.

Proceed as follows:
  1. Edit the response file and ensure that the path does not identify an existing Tivoli Workload Automation instance.
  2. Rerun the silent installation.

AWSJIS166E

No valid action can be performed on the Tivoli Workload Automation instance that has been selected.Select another valid instance in which to install the product or component, or create a new instance.

A Tivoli Workload Automation instance can only have one instance of each of its constituent products and components installed in it. To install more than one instance of a product or component, you must install them in a different path, thereby creating a second instance of Tivoli Workload Automation.

For example, if you have installed the Tivoli Workload Scheduler master domain manager with the default path, it will have been installed in a path that includes the token TWA, which indicates that this is the first instance of Tivoli Workload Automation products and components on the system. To install a second Tivoli Workload Scheduler component choose any other path that is not the same as, or within, the path of the first instance. Note that if the default path includes the tokenTWA1, there are already two instances of Tivoli Workload Automation on the system on which you cannot install the component. To install a third Tivoli Workload Scheduler component choose any other path that is not the same as, or within, the path of the first two instances.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Reenter the installation path, ensuring that the path does not identify an existing Tivoli Workload Automation instance. Click Next to continue.
- Silent installation
  1. Edit the response file and ensure that the installation path does not identify an existing Tivoli Workload Automation instance.
  2. Rerun the silent installation.

AWSJIS167E

The embedded WebSphere Application Server user was not retrieved. Insert it manually.

You have clicked the Retrieve button to retrieve the embedded WebSphere Application Server administration user name. The wizard was unable to retrieve the user name either because the user registry solution you have chosen does not allow user names to be kept in the embedded WebSphere Application Server configuration files, or because the embedded WebSphere Application Server did not respond correctly.

If the user registry solution you have chosen does not allow user names to be kept in the embedded WebSphere Application Server configuration files, the administration user field in the wizard is defaulted as UNKNOWN. Otherwise, the administration user field is left blank.

Obtain the embedded WebSphere Application Server administration user name from the embedded WebSphere Application Server administrator or other person responsible for maintaining the embedded WebSphere Application Server. Enter the value in the administration user field, enter the password and continue.

AWSJIS168E

You cannot upgrade Tivoli Workload Scheduler when it is installed in the root directory.

You have selected to upgrade an instance of a Tivoli Workload Scheduler component but it is installed in the root directory. The upgrade cannot be performed, for technical reasons.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Proceed as follows:
- Interactive wizard
  1. Click OK to close the error message.
  2. Do one of the following:
    • Chose a different instance to upgrade, and click Next to continue.
    • Exit from the wizard and run the parallel upgrade, which requires you to install a fresh instance of the component. See the Planning and Installation Guide for details.
- Silent installation
  1. Do one of the following:
    • Chose a different instance to upgrade, edit the response file to identify it, and rerun the upgrade
    • Run the parallel upgrade, which requires you to install a fresh instance of the component. See the Planning and Installation Guide for details.

AWSJIS169E

No instances of type "type" can be found. Close the Wizard and restart the installation.

AWSJIS170E

No instance of a Tivoli Workload Scheduler component has been found that can be upgraded. The wizard closes when you close the message pop-up.

You have selected an upgrade action for a component of Tivoli Workload Scheduler, but the wizard cannot find any component that can be upgraded.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Proceed as follows:

  1. If you are running the interactive wizard, click OK to close the error message. The wizard closes.
  2. If a Tivoli Workload Scheduler component is installed on the system, check in the Planning and Installation Guide to determine if the component in question can be upgraded (some components must be replaced with a fresh installation of the new version).
  3. Check also in the manual that the version of the component is compatible with the upgrade action.

If none of these actions apply, but the instance of the component exists, the registry may be damaged, and thus is not reporting the presence of the instance. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSJIS171W

You specified a Tivoli Workload Scheduler user name different from the embedded WebSphere Application Server administrator user name.To allow successful connections to the integrated engine,modify the Tivoli Workload Scheduler Security file addingthe embedded WebSphere Application Server administrator user name.

See message.

The wizard completes with this warning.

See message.

AWSJIS172E

The Tivoli Workload Scheduler Oracle database administrator user password must start with an alphabetic character.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click OK to close the error popup window.
  2. Supply a valid Oracle database administrator password.
  3. Click Next to continue.
Silent wizard
  1. Edit the response file used by the silent wizard. Supply a valid Oracle database administrator password.
  2. Rerun the silent wizard.

AWSJIS173E

One or more prerequisite library is missing, as follows: "list_of_missing_libraries". Obtain and install the library, and then rerun the installation.

The wizard requires the use of the standard C libraries, at least one of which is missing.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

Proceed as follows:
Interactive wizard
  1. Click Cancel to close the installation wizard.
  2. Add the required libraries to your system.
  3. Rerun the installation wizard.
Silent wizard
  1. Add the required libraries to your machine.
  2. Rerun the silent wizard.

AWSJIS174W

If you have a job stream called FINAL in the database, it has been backed up to the file Sfinal.extract and then overwritten. If your old final job stream was customized, or is not called FINAL , you must perform some customization steps. See the message help in the Messages manual, or the Planning and Installation Guide, for details.

See message.

See message. If you have a final job stream but it is not called FINAL, it will not have been backed up.

If you had a customized job stream called FINAL in your database, after completing the installation, proceed as follows:
  1. Edit the new FINAL job stream with composer or the Tivoli Dynamic Workload Console
  2. Edit the file Sfinal.extract with a text editor
  3. Make the corresponding customizations to the new FINAL job stream.
  4. Save your new FINAL job stream.
If you had a customized final job stream called by any name other than FINAL in your database, after completing the installation, proceed as follows:
  1. Edit the new FINAL job stream with composer or the Tivoli Dynamic Workload Console
  2. Edit your old final job stream with composer or the Tivoli Dynamic Workload Console
  3. Merge the two job streams so that your new final job stream has the same name and customizations as before (if you want to preserve the naming), plus the new required attributes from the new FINAL job stream.
  4. Save your new final job stream.
If you had a final job stream called by any name other than FINAL in your database, but it is not customized, after completing the installation, proceed as follows:
  1. Delete your old final job stream with composer or the Tivoli Dynamic Workload Console
  2. Rename the FINAL job stream with the name of your old final job stream with composer or the Tivoli Dynamic Workload Console

AWSJIS175W

The table space path "path" already exists and is not empty.Check if the selected path contains table space data of a Tivoli Workload Scheduler database.If yes, continue, otherwise choose another table space path.

See message.

path is the path specified for a Tivoli Workload Scheduler table space.

The installation stops while you determine the correct action to take.

Check the contents of the specified path:
  1. If the path includes table space data for a Tivoli Workload Scheduler database that you want to use for the current installation, you can continue.
  2. If the path does not include table space data for a Tivoli Workload Scheduler database that you want to use for the current installation, choose a different path and continue.

To check if the specified path is in use by a table space in the Tivoli Workload Scheduler database, you can get a DB2 snapshot for table spaces on the Tivoli Workload Scheduler database. Please refer to the DB2 documentation for more information about database snapshots and monitoring features.

AWSJIS176E

The selected table space paths are either equal or one is a subpath of the other:"path1""path2". The paths must be different and one cannot contain the other.

See message.

path1 is the path specified for a Tivoli Workload Scheduler table space.

path2 is the path specified for a Tivoli Workload Scheduler table space.

The installation cannot proceed because either the specified paths are the same or one is a subpath of the other.

Proceed as follows:
Interactive wizard
  1. Click Close to close the Popup Window.
  2. Choose different values for the table space paths, so that they are not the same and that one is not a subpath of the other.
  3. Continue with the installation.
Silent wizard
  1. Choose different values for the table space paths, so that they are not the same and that one is not a subpath of the other.
  2. Rerun the silent wizard.

AWSJIS177E

Authentication failure. The supplied user name or password is incorrect.

See message.

AWSJIS178E

It is not possible to check the specified credentials. embedded WebSphere Application Server stops.

See message.

AWSJIS179W

Unable to establish a connection with the host "host_name" on the "port" port. Verify that the Dynamic Workload Broker is up and running and that it is listening on this port.Click Yes to continue.

See message.

The installation proceeds.

Check that you have specified the correct Dynamic Workload Broker host name. Check that the Dynamic Workload Broker is up and running and that it is listening on this port. If you have incorrectly identified the Dynamic Workload Broker, edit the JobManager.ini file after the installation completed, to indicate the correct Dynamic Workload Broker.

AWSJIS180W

You are activating the dynamic scheduling capability on this master domain manager.This feature requires that all backup master domain managers in the network are at the minimum supported level.See the Planning and Installation Guide for details.Do you want to continue?

See message.

The installation proceeds.

Click Yes to continue, No to change your selection.

AWSJIS181W

Upgrading this instance changes its installation path.Be sure that all file dependencies and jobs running on this instance either do not use the installation path or use it as a variable.Do you want to continue?

The upgrade to the current version changes the installation path of the selected instance.

Before upgrading the selected instance, be sure that no file dependencies or jobs run on the selected instance using the absolute installation path.

The installation proceeds.

Proceed as follows:
  1. Use composer to check if there are file dependencies or jobs using the absolute installation path on this workstation.
  2. If yes, modify them according to the Planning and Installation Guide.
  3. Click Yes to continue, No to change your selection.

AWSJIS185E

There are jobs still running. The operation cannot proceed.

See text.

The operation cannot proceed.

Run the operation again, after having increased the value of the wait parameter.

Planning and Installation Guide

AWSJIS186E

The following processes are still running. Close them before running the operation again.

See text.

The operation cannot proceeds.

Close all the processes and run the operation again.

Planning and Installation Guide

AWSJIS187E

The following processes are still running. Either close them or wait for their completion before running the operation again.

See text.

The operation cannot proceed.

Run installation again.

Planning and Installation Guide

AWSJIS189E

Tivoli Workload Scheduler could not retrieve the job fence value on the workstation for the selected instance.

See text.

The operation cannot proceed.

Select another instance and run the operation again.

Planning and Installation Guide

AWSJIS190E

Tivoli Workload Scheduler could not reset the job fence value on the workstation for the selected instance.

See text.

The operation cannot proceed.

Reset the job fence value on the selected workstation and resume the upgrade process.

Planning and Installation Guide

AWSJIS192E

An incorrect value has been supplied for the parameter: checkJobsLoop.wait. Valid values are integers or -1 to have the product wait indefinitely.

See text.

The operation cannot proceed.

Run the operation again, after having modified the value of the wait parameter.

Planning and Installation Guide

AWSJIS193E

You cannot install the Tivoli Workload Scheduler "component" component using this eImage.

The eImage you downloaded does not contain the images to install the selected component.

The installation does not proceed.

Proceed as follows:
- Silent installation
  1. Do one of the following:
    • Choose a different Tivoli Workload Scheduler component to install, edit the response file to change it, and run the installation again.
    • Download the appropriate Tivoli Workload Scheduler eImage and run the installation again.

AWSJIS194E

You cannot install the runtime for Java jobs using the current eImage.

The eImage you downloaded does not contain the images to install the runtime for Java jobs.

The installation does not proceed.

Proceed as follows:
- Interactive wizard
  1. Perform one of the following actions:
    • If you want to install the runtime for Java jobs, copy the Java extensions eImage into the current eImage directory and proceed.
    • If you do not want to install the runtime for Java jobs, clear Add the runtime for Java jobs, and proceed.

AWSJIS195E

You cannot upgrade the selected Tivoli Workload Automation instance; the Java extensions eImage is required.Copy the required eImage into the current eImage directory and proceed.

The current eImage does not contain the installation files for the runtime for Java jobs.

The upgrade of the selected Tivoli Workload Automation instance is not performed because the runtime for Java jobs cannot be upgraded.

Copy the related eImage into the current eImage directory and proceed.

AWSJIS196E

No valid action can be performed on the selected Tivoli Workload Automation instance from the current eImage.Select a valid instance in which to install the product or component or use a different eImage.

The current eImage does not contain the installation files for adding a new feature or for upgrading the selected Tivoli Workload Automation instance.

If you are running the interactive wizard, the wizard stops.

If you are running the silent installation, the installation fails.

Select a valid instance or download the correct eImage and proceed.

AWSJIS197E

You cannot install the dynamic agent only on a Tivoli Workload Automation instance.

The selected Tivoli Workload Scheduler component cannot be installed on Tivoli Workload Automation instance.

The installation does not proceed.

Select also Fault Tolerant Scheduling to install the fault tolerant agent or install the dynamic agent outside the Tivoli Workload Automation instance.

AWSJIS198W

A problem was found during the check of prerequisites. Are you sure you want to continue with the installation process?

See message.

The installation proceeds if you click Yes,it is paused if you click No.

Click Yes to continue with the installation, No to pause the installation and allow you to solve the error before proceeding.

AWSJIS199E

An error occurred running the option that recreates the Tivoli Workload Scheduler installation registries on the specific path "twa_path". Check the installation log for details.

See message.

If you are running the interactive wizard, the wizard stops.

If you are running the silent wizard, the wizard fails.

The chapter on Troubleshooting installation, migration, and uninstallation in Planning and Installation for full details of the recovery process from a failed installation.

AWSJIS202W

Unable to establish a connection with the host "host_name" on the "port" port. Verify that the master domain manager is up and running and that it is listening on this port.Click Yes to continue.

See message.

The installation proceeds.

Check that you have specified the correct master domain manager host name, that it is up and running, and that it is listening on this port. If you have incorrectly identified the master domain manager, edit the BrokerWorkstation.properties file after the installation completes, to indicate the correct master domain manager.

AWSJIS203W

The upgrade process cannot upgrade the embedded WebSphere Application Server security to Federated Repository. If you do not enable the embedded WebSphere Application Server Federated Repository security mechanism on the Tivoli Workload Automation instance, you cannot install a Tivoli Dynamic Workload Console on the same Tivoli Workload Automation instance. See the message help in the Messages manual, or the Administration Guide, for details.

See message.

See message. The upgrade was performed successfully.

Enable the embedded WebSphere Application Server Federated Repository security mechanism on the Tivoli Workload Automation instance, if you want to install a Tivoli Dynamic Workload Console on the same Tivoli Workload Automation instance. See the Administration Guide, for details.

AWSJIS204E

The eImage on your workstation is corrupt. You must use the UNZIP command to extract the eImage otherwise your fix pack installation fails.

See message text.

The installation cannot proceed.

You must use the UNZIP command to extract the eImage otherwise your fix pack installation fails. For details see the Tivoli Workload Scheduler readme for the fix pack you are installing.

Rerun the installation.