Update Installer error codes

When you update WebSphere Commerce with Update Installer (UPDI), error codes are generated when a problem is encountered.Use the error code table to troubleshoot these problems.

Error code categorization

Error codes are numerical and always within the range of 20000 to 20600. Error codes are divided into two major categories, and six subcategories:

Input Validation Log validation
Error codes that are related to the values that you input within the install.txt or uninstall.txt configuration files.
Common input values 20000-20099
Install specific values 20100-20199
Uninstall specific values 20200-20299
Errors codes that are related to the process of installing or uninstalling. They are identified through parsing log output.
Common failures 20300-20399
Install specific failures 20400-20499
Uninstall specific failures 20500-20599

Error codes

Error Solution
20000: Error trying to read response file: input.txt.
  • Ensure that the specified path to the install.txt or uninstall.txt file is correct.
  • Ensure that the install.txt or uninstall.txt file is properly formatted.
20001: WC_Home does not exist.
  • Ensure that the path to WebSphere Commerce is correct.
  • Ensure that the update you are installing is applicable to the version of WebSphere Commerce that is installed.
20002: Instance name cannot be empty. Ensure that the instance name is specified.
20003: update.db can have value of "true" or "false" only. Ensure that the value of update.db is set to either true or false.
20004: update.type can have value of "install" or "uninstall" only. Ensure that the value of update.type is set to either install or uninstall.
20005: XXX_WAS_HOME contains quotation marks ("") in the setenv.sh file. Ensure that the value of XXX_WAS_HOME does not include quotation marks, where XXX is one of the following platforms:
  • AIX
  • LNX
  • SUN
20101: Given maintenance .pak file does not exist: package.pak.
  • Ensure that the full path to the package file is correct.
  • Ensure that the file name of the package is correct. Include the .pak file extension.
20102: Given maintenance directory doesn't exist: \specified\directory\. Ensure that the full path to the directory that contains the maintenance packages you want to install is specified correctly.
20103: The following .pak file in the maintenance pak list does not exist: package.pak.
  • Ensure that the path to the maintenance package is correct.
  • Ensure that the file name of the maintenance package file is correct. Include the .pak file extension.
  • Ensure that each full maintenance package file path is delimited by a semi-colon (;), and that there are no extra characters or values.
20104: License acceptance value must be either "true" or "false". Set the silentInstallLicenseAcceptance and silentInstall3rdPartyLicenseAcceptance variables to true to confirm that you accept the updated terms of use licenses that are required to use WebSphere Commerce.
20201: Backup package cannot be a path. It must be a filename only.
  • Ensure that you include the full package name of an installed maintenance package, including the .pak extension.
  • Ensure that you avoid inputting a file path.
Note: If this value is empty, then the last installed maintenance package is used.
20301: A supported product could not be detected at the specified location for this maintenance package.
  1. Ensure the package that you are installing is appropriate for your installation of WebSphere Commerce.
  2. Ensure that your installation is reporting the correct feature pack, fix pack and product edition information.

    Run the versionInfo script within the WC_installdir/bin/ directory, both with and without the instance name parameter.

    For example, ./versionInfo.sh [WC_installdir/instances/instance_name]

If the version information specified by this script is incorrect, these values can be adjusted manually within the following files:

For the product:
  • WC_installdir/properties/version/COMMERCE.product
  • WC_installdir/properties/version/FEPX.product
For instances:
  • WC_installdir/instances/instance_name/properties/version/COMMERCE.product
  • WC_installdir/instances/instance_name/properties/version/FEPX.product

Where X is the number corresponding to the feature pack level installed.
LinuxAIXNote: You can use a non-root user to launch the WebSphere Commerce Update Installer if the non-root user installed the Update Installer.
20303: Failed to run export EAR command for the given WebSphere Commerce instance "instance_name". The exportear script failed to complete and the exportear_WC_instance_name.log was not generated.
  1. Ensure the config_ant script is running properly by manually starting it from the command line. It is in the WC_installdir/bin/ directory.
  2. Ensure that the WebSphere Application Server SDK level is 7.0.0.9 (Java SDK 1.6.0 SR7 Cumulative Fix) or higher.
20304: Failed to export WebSphere Commerce instance "instance_name" due to a WebSphere Application Server issue. Check the WC_Installdir/logs/update/actions/install/exportear_WC_instance_name.log log file for more details. Contact IBM support for further assistance.

For more information about WebSphere Application Server error codes that you might encounter while using the Update Installer, see WebSphere Application Server error codes.
20305: Failed to deploy WebSphere Commerce instance "instance_name" due to a WebSphere Application Server issue. The deployear script failed to complete and the deployear_WC_instance_name.log was not generated.
  1. Ensure the config_ant script is running properly by manually starting it from the command line. It is in the WC_installdir/bin/ directory.
  2. Ensure that the WebSphere Application Server SDK level is 7.0.0.9 (Java SDK 1.6.0 SR7 Cumulative Fix) or higher.
20306: Failed to deploy WebSphere Commerce instance "instance_name" due to a WebSphere Application Server issue. Check the WC_Installdir/logs/update/actions/install/deployear_WC_instance_name.log log file for more details. Contact IBM support for further assistance.

For more information about WebSphere Application Server error codes that you might encounter while using the Update Installer, see WebSphere Application Server error codes.
20307: An archive file is missing from the product. Contact WebSphere Commerce support for further assistance. Certain archive files are missing from the component that is being updated. Contact IBM support for further assistance.
20308: The WebSphere Commerce Update Installer version does not meet the minimum required version for this maintenance package. Install the latest version of the Update Installer. See Installing the WebSphere Commerce Update Installer.
20309: Unable to reach your WebSphere Application Server administrative server. Ensure that your administrative server is running. Ensure the instance that you are updating is started.
20310: Timed out while exporting EAR.
  • If an EAR log file WC_installdir/logs/update/actions/install/exportear_instance_name.log exists, then the cause of the time out error is due to the WebSphere Application Sever.
    1. Stop the WebSphere Application Server.
    2. Clean the WC_profiledir/wstemp directory.
    3. Restart the WebSphere Application Server.
    4. Retry the installation or uninstall process
  • If the EAR log file does not exist, the most likely cause of the time out error is due to an operating system configuration issue. Ensure that your .profile file is configured correctly. If you have another working environment, compare the two .profile files for any discrepancies.
20401: The specified maintenance package is already installed. A maintenance package with that name is already installed. No action is required.
20402: The specified maintenance package is missing a prerequisite APAR or fix pack. Install the prerequisite or prerequisites and try again.

Read the readme.txt readme file provided with the maintenance package to check the prerequisites that are required.
20403: Applying updates to the database associated with the instance "instance_name" failed or timed out. Check WC_installdir/logs/update/updatedb-instance_name.log for more details. Check the associated database log file, WC_installdir/logs/update/updatedb-instance_name.log for specific errors. Contact IBM support for further assistance.
20404: A valid .pak file does not exist in the current directory. Edit your response file and ensure that you defined the correct location to a valid WebSphere Commerce fix pack .pak file.
20501: Cannot find the backup maintenance package "package.pak". The maintenance package that you are attempting to uninstall was not installed. No action is required.
  • Ensure that its name is correct in the input file. Include the .pak file extension.

  • Check the WC_installdir/properties/version/update/backup/ directory for the maintenance package backup archive.
20502: This maintenance package is a prerequisite for another installed maintenance package. It was not uninstalled. Uninstall the dependent maintenance package or packages and try again.

WebSphere Application Server error codes

You might encounter the following WebSphere Application Server errors when you are exporting or deploying a WebSphere Commerce instance using the Update Installer.
Note: For a complete list of WebSphere Application Server error codes, see WASX.
Error Solution
WASX7280E: Failed to export WebSphere Commerce instance because the specified application does not exist Verify that the specified application name is spelled correctly in your response file.
WASX7115E: The wsadmin tool cannot read the EAR file when preparing to copy the EAR file to a temporary location for processing. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7116E: The wsadmin tool cannot copy the ear file to a temporary location. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7132E: An installation command failed to execute. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem.
WASX7279E: The specified application name already exists. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem.
WASX7281E: The specified file does not exist or is not readable. Verify that the file exists in the following directory and that you have the required permissions to read the file.
  • LinuxAIX/tmp/wcupdate
  • Windows/temp directory. You can navigate to the temp directory by searching for %TEMP% in Windows Explorer.
WASX7323E: The wsadmin tool cannot create a temporary directory. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7324E: The wsadmin tool cannot copy an expanded ear directory to a temporary location. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7336E: A required option is missing for a command to execute. Examine the WC_profiledir/logs/wsadmin.traceout log file to determine the problem. Specify each required option and reinvoke the command.