Explanation | None |
Action | No user action is required. |
Explanation | None |
Action | No user action is required. |
Explanation | The function cannot create the trace file. |
Action | Verify that the characters of the trace file name are valid for the operating system. The output of the trace is displayed on the console; this output can be captured and sent to IBM service. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The command parameters are incorrectly specified. |
Action | Verify that all of the parameters are valid and spelled correctly. |
Explanation | The backup directory is used to store the configuration information that is migrated to the new release. |
Action | Run the command again and specify the backup directory. |
Explanation | You must access the currently installed WebSphere Application Server directory to obtain the configuration information that is migrating to the new release. |
Action | Run the command again and specify the currently installed WebSphere Application Server directory. |
Explanation | The primary node name is used to call the XMLConfig command to obtain configuration information for the current release. |
Action | Run the command and specify the primary node name. |
Explanation | The specified parameter is not supported by the command. |
Action | Check the spelling of the parameter and run the command again. |
Explanation | Specify optional parameters by entering the name of the parameter, followed by the value of the parameter. |
Action | Run the command again with the correct format for optional parameters. |
Explanation | Migration support is provided for WebSphere version 4 and later. |
Action | If you are migrating to a supported release, verify that the directory name is correct, and rerun the command. |
Explanation | The WASPostUpgrade command is running against an unsupported version of WebSphere Application Server. The WASPostUpgrade command that was invoked might not be using the current version of the WebSphere Application Server directories. |
Action | Invoke the command in the current WebSphere Application Server directory structure. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | Specify a directory so that files containing the configuration information for the current release can be saved. |
Action | Run the command again and specify the name of a directory. |
Explanation | Specify a writeable directory so that files containing the configuration information for the current release can be saved. |
Action | Run the command again and specify the name of a writeable directory. |
Explanation | The system is unable to create a directory with the name that you specified. |
Action | Determine why the directory cannot be created and run the command again. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/, or consult the appropriate operating system documentation. |
Explanation | The migration function cannot find a specific property in an IBM-supplied file. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | During migration processing, the function attempted to call another WebSphere Application Server program; the call cannot be successfully completed. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The call to the WASPostUpgrade command was specified without using the -import keyword to specify a particular XML file. If no file is specified, a file named <samp>websphere_backup.xml</samp> in the backup directory is used. |
Action | Rerun the WASPostUpgrade command using the -import keyword to specify an XML file that was created using the XMLConfig command on an earlier WebSphere Application Server version. |
Explanation | The specified directory on the migration command does not contain a valid <samp>properties/com/ibm/websphere/product.xml</samp> file. |
Action | Rerun the command with a valid WebSphere Application Server XML file name. |
Explanation | The directory that is specified on the migration command does not contain a readable <samp>product.xml</samp> file. |
Action | Rerun the command with a valid WebSphere Application Server directory name. |
Explanation | The file that was specified using the -import keyword is not valid. |
Action | Rerun the command using a valid XML file. |
Explanation | An internal error occurred. The specified file is expected in the new WebSphere Application Server version <samp>bin/migration</samp> subdirectory. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while reading the XML file to import during migration. |
Action | Rerun the command with a valid XML import file. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The function cannot read the specified configuration file. |
Action | If the file is part of the current WebSphere Application Server configuration, restore the configuration from a previous backup and rerun the command. The WASPostUpgrade command saves backup copies of all the configuration files that it attempts to modify. The backup files are in the same directory structure, with time stamps as part of their names. |
Explanation | During WASPostUpgrade processing, an error occurred while importing the specified object. |
Action | See the following errors in the migration log for further details. Correct the problem and rerun the command, or use the WebSphere administrative interfaces to complete the configuration of the specified object. |
Explanation | An attempt to read the specified file failed. |
Action | Verify that the file exists, and rerun the command. |
Explanation | The call to the XMLConfig command to obtain the configuration information for the current release failed. |
Action | Check the log that is created by the command for details, and rerun the command. |
Explanation | The call to the XMLConfig command to obtain the configuration information for the current release failed. |
Action | Check the log that is created by the command for details, and rerun the command. |
Explanation | The document type definition (DTD) file is expected in the new WebSphere Application Server version <samp>bin/migration</samp> subdirectory. |
Action | Check the new <samp>bin/migration</samp> subdirectory for the DTD file. If the file is missing, try to restore it. Verify that the user ID that is running the migration command has sufficient file system authority. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The specified log file is initialized. A new log file is created for each invocation of the migration commands. |
Action | No user action is required. |
Explanation | The specified log file cannot be initialized. No data is saved in a log file, but output is still routed to the administrative console for you to view. |
Action | Check the user file permissions before you run the command again. |
Explanation | This message logs the WebSphere Application Server version number of the backup configuration. |
Action | No user action is required. |
Explanation | The XMLConfig program is being accessed. This program is used to create an XML file that is used to migrate to the new WebSphere Application Server version. |
Action | No user action is required. |
Explanation | The function attempted to capture the output while calling another program during migration. The output was not captured, but the migration command still functions normally. |
Action | Check the migration log file for information about whether the command completed normally. If you are running the WASPreUpgrade function, the file is in the backup directory. If you are running the WASPostUpgrade function, the file is in the new WebSphere Application Server image that is installed in the logs directory. The log name includes a time stamp, so check the log file with the latest creation date. |
Explanation | The function cannot find or copy an expected directory. This missing directory might affect the migration. |
Action | If this source file must be used to create an enterprise application, use a development environment like WebSphere Studio Application Developer, to add the file to the appropriate location in the enterprise application. |
Explanation | The function cannot copy the directory. This problem might affect the migration. |
Action | If the directory must be used to create an enterprise application, use a development environment like WebSphere Studio Application Developer, to add the files from that directory to the appropriate location in the enterprise application. |
Explanation | The function cannot add the specified data source to the JDBC driver. |
Action | After migration is complete, use the system administrative interface to create the data source. The data source must be in the JDBC driver before application servers with data source-dependent deployed applications can start. |
Explanation | The directory was created during normal processing. |
Action | No user action is required. |
Explanation | The function is copying a directory and its contents. |
Action | No user action is required. |
Explanation | An unexpected failure occurred during the creation of a directory. |
Action | Delete or rename the directory, and rerun the function using either the WASPreUpgrade or the WASPostUpgrade command. |
Explanation | An unexpected failure occurred during the creation of a directory. |
Action | Verify that the user ID has sufficient file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected failure occurred when a configuration file was copied. |
Action | If the source file must be used to create an enterprise application, use a development environment such as the WebSphere Studio Application Developer, to add the file to the appropriate location in the enterprise application. |
Explanation | An unexpected failure occurred while copying a configuration file. |
Action | Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected failure occurred while copying a configuration file. |
Action | Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected failure occurred while closing a configuration file. |
Action | Verify that the user ID has the appropriate file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified object is being imported into the new WebSphere Application Server version. The action value relates to the XMLConfiguration action that is associated with the object in the XML file. |
Action | No user action is required. |
Explanation | The specified object is being imported into the new WebSphere Application Server version. |
Action | No user action is required. |
Explanation | The action on the specified object in the input XML file is not supported for migrating objects. Actions that are not supported include delete, export, start, stop, ping, associateclone, or disassociateclone. |
Action | If you need the object created in the new configuration, then either use a different input XML file, modify the input XML file and rerun migration, or use the WebSphere Application Server administrative interfaces to create the object. |
Explanation | The specified configuration file from a previous WebSphere Application Server version is being read. This file is the source for importing objects into the new WebSphere Application Server configuration. |
Action | No user action is required. |
Explanation | The function cannot locate the specified object in the configuration file in the new WebSphere Application Server configuration. This problem usually occurs for configurations with multiple nodes in the same input XML file, where the specified object is not on the migrating node. |
Action | Ignore this message if your configuration has multiple nodes in the same input file and the object that is specified is not on the migrating node. Otherwise, verify that the object needs to be added to the configuration, and use the WebSphere Application Server administrative interfaces to create the object. |
Explanation | The specified object is being added to the configuration of the new WebSphere Application Server version. |
Action | No user action is required. |
Explanation | The specified node entry is ignored because it does not match the migrating node. This problem usually occurs for configurations with multiple nodes in the same input XML file, where the specified object is not on the migrating node. |
Action | Ignore this message if your configuration has multiple nodes in the same input file, and the object that is specified is not on the migrating node. Otherwise, verify that the object needs to be added to the configuration, and use the WebSphere Application Server administrative interfaces to create the object. |
Explanation | An unexpected failure occurred while copying a configuration file. Migration is expected to occur normally. A backup copy of the previous configuration file is not available. |
Action | Verify that the user ID has the appropriate file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected error occurred while trying to save the migrated configuration. |
Action | Verify that the user ID has sufficient file system authority to run the migration command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified entry already exists in the configuration of the new WebSphere Application Server version. The attributes of this entry are being updated. |
Action | No user action is required. |
Explanation | The specified entry is ignored because it does not directly map to the model of the new Application Server configuration. However, any objects that are owned by this entry are added. |
Action | No user action is required. |
Explanation | No objects of the specified type exist to import. |
Action | No user action is required. |
Explanation | The migration function cannot locate the object of the specified type when attempting to migrate it. |
Action | Verify that the object exists in the backup environment that results from the WASPreUpgrade command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The configuration from the prior WebSphere Application Server version is successfully imported into the new WebSphere Application Server version. |
Action | Inspect the WASPostUpgrade log to verify the results. |
Explanation | The configuration file was successfully read. |
Action | No user action is required. |
Explanation | This message follows another message in the log that shows a different program that is being called during migration. This message displays the results of that call. |
Action | No user action is required. |
Explanation | The specified data source is already installed in the Java Database Connectivity (JDBC) driver. |
Action | No user action is required. |
Explanation | The specified entry is ignored because it does not directly map to the model of the new WebSphere Application Server configuration. |
Action | No user action is required. |
Explanation | An error occurred while calling the GenPlugInCfg command at the end of migration. The migration completed normally. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | No Samples are migrated by the WASPostUpgrade command. |
Action | No user action is required. |
Explanation | While attempting to restore the specified file, an unexpected error occurred. The configuration file might not match the rest of the configuration. |
Action | If possible, use one of the backup files with the same name to restore the configuration. |
Explanation | The backup directory that was specified on the command line does not exist. |
Action | Rerun the command with a valid backup directory that was created by the WASPreUpgrade command. |
Explanation | The substitution values can be replaced in the input XML file during migration. These values are specified with the WASPostUpgrade command. |
Action | Rerun the migration command using a valid substitution value. |
Explanation | The Lightweight Third Party Authentication (LTPA) authentication mechanism is not supported by this release. The Simple WebSphere Authentication Mechanism (SWAM) that is supported by this release is set as the active authentication mechanism. |
Action | No user action is required. |
Explanation | An internal error occurred. The specified environment variable must be set for the migration command to run. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified file is being copied. |
Action | No user action is required. |
Explanation | The migration has completed with no warning or error messages. |
Action | No user action is required. |
Explanation | The resource provider is successfully added to the configuration, but its class path information might be incorrect if a prerequisite change is required for the new WebSphere Application Server version. |
Action | Use the WebSphere Application Server administrative interfaces to update the class path value of the specified resource provider. |
Explanation | An unexpected error occurred while updating the server configuration. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected error occurred while calling an internal program. |
Action | Verify that the user ID has the sufficient file sytem authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The call to automatically determine your administrative server name and port failed. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration completed with some warning messages, but no errors occurred. |
Action | For further information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date. |
Explanation | The migration command failed. |
Action | For additional information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date. |
Explanation | The specified object was not configured for the migrated node and was not installed. |
Action | If you need the object installed on the current node, configure and install the object using the WebSphere Application Server administrative interfaces. |
Explanation | You cannot use the -import parameter when configuration information is stored in a database. |
Action | Run the command again without the -import parameter. |
Explanation | The tool cannot find the default XML configuration <samp>server-cfg.xml</samp> file. |
Action | Run the command again using the -import parameter to specify the name of your configuration file. |
Explanation | You cannot automatically migrate applications that require source code changes. |
Action | Implement the source code changes and install the applications. Refer to the information center for details. |
Explanation | The other services that are featured in IBM WebSphere Business Integration Server Foundation must be installed to run the specified service. |
Action | Install the feature, and rerun the command. |
Explanation | The business rule beans that are featured in IBM WebSphere Business Integration Server Foundation must be installed to run business rule beans applications. |
Action | Install the feature, and rerun the command. |
Explanation | The IBM WebSphere Business Integration Server Foundation CORBA C++ SDK must be installed to run CORBA applications. |
Action | Install the feature, and rerun the command. |
Explanation | The migration function cannot automatically migrate the CORBA servers. |
Action | Run the CORBA server registration command for each server that you want to migrate. |
Explanation | An unexpected error occurred while trying to read the specified file. |
Action | Verify that the user ID has the sufficient file system authority to run the migration program has sufficient file system authority. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified backup directory is created from an unsupported version of WebSphere Application Server. |
Action | Rerun the migration command with a valid backup directory that was created by the WASPreUpgrade command. |
Explanation | An unexpected error occurred. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration failed to complete because errors occurred during migration. |
Action | For additional information, check the log file that was created by the migration command in the logs directory, and correct the problems if required. The log name includes a time stamp, so check the log file with the latest creation date. |
Explanation | The specified configuration file, which did not exist in the new WebSphere Application Server configuration, is successfully created. |
Action | No user action is required. |
Explanation | The specified configuration file is ready to be saved. |
Action | No user action is required. |
Explanation | The specified entry in the configuration file does not exist as expected. This configuration file is not valid. |
Action | Either restore a valid backup from a previous configuration, or use the WebSphere Application Server administrative interfaces to fix the settings in the file. |
Explanation | The command that you entered specified more than the maximum number of positional parameters. |
Action | Check the parameters that are specified on the command and run the command again. |
Explanation | The heap size that is specified in the previous version of WebSphere Application Server does not directly map to the new Application Server model because the servers run in different Java virtual machines. This value is ignored. |
Action | Check the specified value for the previous version and determine if the heap sizes need updating in the servers of the new configuration. |
Explanation | The heap size that is specified in the previous version of WebSphere Application Server does not directly map to the new Application Server model because the servers run in different Java virtual machines. This value is ignored. |
Action | Check the specified value for the previous version, and determine if the heap sizes need updating in the servers of the new configuration. |
Explanation | The required steps that save the existing configuration information have started. |
Action | No user action is required. |
Explanation | The configuration information is being read from the database. |
Action | No user action is required. |
Explanation | The files that you need to restore your configuration on the new release are being copied to the backup directory. |
Action | No user action is required. |
Explanation | The process of backing up your previous configuration is complete. |
Action | No user action is required. |
Explanation | The restoration of the previous WebSphere Application Server environment to the configuration of the new WebSphere version has begun. |
Action | No user action is required. |
Explanation | The configuration from the previous WebSphere Application Server version is being imported. |
Action | No user action is required. |
Explanation | The restoration of the previous WebSphere Application Server configuration is complete. |
Action | Display the WASPostUpgrade log, and verify the results. The message that is displayed before this one indicates success, warning, or error. |
Explanation | The specified value is incorrect. |
Action | Consult the help text that is displayed with this message and rerun the command with a correct value. |
Explanation | The specified directory does not exist. |
Action | Create the directory, and rerun the migration command. |
Explanation | The specified value is not a directory. |
Action | Rerun the command with a valid directory name. |
Explanation | More than one directory exists in the WebSphere Application Server configuration. |
Action | Rerun the command specifying the requested directory name by including the noted parameter. |
Explanation | The import of configuration information from the previous release has started. |
Action | No user action is required. |
Explanation | The bootstrap port settings of the previous WebSphere Application Server version are being processed. |
Action | No user action is required. |
Explanation | The bootstrap setting of the name server that is associated with the default server is updating to use the same value as in the previous version of WebSphere Application Server. |
Action | No user action is required. |
Explanation | No bootstrap port setting is specified in the previous version of WebSphere Application Server; the current value does not change. |
Action | No user action is required. |
Explanation | The specified naming context is added to the <samp>namebindings.xml</samp> file. |
Action | No user action is required. |
Explanation | This node is already added to the cell manager configuration. Migration does not run because the configuration is controlled by the cell manager. |
Action | If you want to migrate the node, remove the node from the cell manager configuration, and rerun the command. However, proceed with caution because the configuration is already being managed. |
Explanation | The specified value is enabled in the configuration file; this value was previously disabled. |
Action | No user action is required. |
Explanation | The specified configuration file cannot be enabled. |
Action | Verify that the user ID has the sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified object is converting in the specified file. |
Action | No user action is required. |
Explanation | The specified object is being added to the specified configuration file. |
Action | No user action is required. |
Explanation | An unexpected error occurred. |
Action | Verify that the user ID has the sufficient file system authority to run the migration program. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified port is already used in the reported file. The port assignment is migrated. The port assignment might cause a conflict if both ports are started at the same time. |
Action | Use the WebSphere Application Server administrative interfaces to assign unique port values if necessary. |
Explanation | The attributes of the specified authentication mechanism are being updated. |
Action | No user action is required. |
Explanation | You might need to generate Lightweight Third Party Authentication (LTPA) keys before enabling global security. If global security is enabled, it was disabled during migration. |
Action | Generate the LTPA keys using the WebSphere Application Server administrative interfaces. Refer to the WebSphere Application Server Information Center for details. |
Explanation | The authentication mechanism that was configured in the previous release is not supported by this release. Therefore, if global security was previously enabled, it has been disabled during migration. The only authentication mechanism that is supported is LTPA. |
Action | To enable security, configure the LTPA authentication mechanism using the WebSphere Application Server administrative interfaces. Refer to the WebSphere Application Server Information Center for details. |
Explanation | The attributes of the specified user registry are updated to reflect the information for the specified server ID. |
Action | No user action is required. |
Explanation | The servlet-class attribute of the specified servlet is updated to reflect the package that contains the servlet for this release. Source code changes might be required to reflect the new package of the specified servlet. |
Action | No user action is required. |
Explanation | The tool cannot find servers in the migrated configuration on which to deploy the specified application. |
Action | Check the migration log file to determine if any servers have successfully migrated. If the correct server exists for the application installation, use the WebSphere administrative interfaces to install the application. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration function used the wsadmin command to deploy the specified application. |
Action | No user action is required. |
Explanation | The call to the wsadmin command failed, and the specified application is not deployed. |
Action | To determine why the call to the wsadmin command failed, check the <samp>wsadmin.traceout</samp> file in the logs directory of the installation root of the new version. |
Explanation | The specified application was not installed on this WebSphere Application Server version because it was part of a model or server group configuration that was migrated. |
Action | Refer to the WebSphere Application Server Information Center for details. |
Explanation | Automated migration is not supported for the designated file. |
Action | Refer to the WebSphere Application Server Information Center for details about how to manually migrate the file. |
Explanation | Starting automated migration for the designated directory. |
Action | No user action is required. |
Explanation | Starting automated migration for the file. |
Action | No user action is required. |
Explanation | The migration function cannot apply the version of WebSphere Application Server that is designated as a backup in the specified directory. Either the version in the backup directory is not supported, or the WebSphere products are not compatible. |
Action | Verify that the combination of WebSphere product types is in the backup directory and that the current versions are compatible. |
Explanation | No administrative applications are migrated during the WASPostUpgrade process. |
Action | No user action is required. |
Explanation | Another WebSphere Application Server process has a lock on the configuration directory. |
Action | Close any running WebSphere Application Server processes, and run migration again. |
Explanation | The deployment manager might not have been running during migration. |
Action | Verify that the deployment manager is currently running. Either manually run the syncNode command to update the configuration, or enable the node agent to perform this task automatically the next time that you run the startNode command. |
Explanation | The function is trying to connect to the deployment manager using the specified protocol. |
Action | No user action is required. |
Explanation | The configuration is successfully synchronized. |
Action | No user action is required. |
Explanation | The function cannot create the specified configuration file. |
Action | Verify that the WASPostUpgrade command has the neccesary permissions to create files, and then try the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation services feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation extended messaging feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation scheduler and asynchronous beans feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | IBM WebSphere Business Integration Server Foundation must be installed to run the specified service. |
Action | Install IBM WebSphere Business Integration Server Foundation, and rerun the command. |
Explanation | The IBM WebSphere Business Integration Server Foundation other services feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | IBM WebSphere Business Integration Server Foundation must be installed to use the cluster extensions. |
Action | Install IBM WebSphere Business Integration Server Foundation, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation member manager feature must be installed to run the specified service. |
Action | Install the feature, and run the command again. |
Explanation | The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed to use the container. |
Action | Install the feature, and run the command again. |
Explanation | The existing configuration is saved in the <samp>temp</samp> directory. |
Action | No user action is required. |
Explanation | The IBM WebSphere Business Integration Server Foundation dynamic query feature must be installed to use the dynamic query service. |
Action | Install the feature, and run the command again. |
Explanation | The configuration is not successfully synchronized. |
Action | Either run the synchronization manually, or use deployment manager facilities to perform the synchronization. |
Explanation | This property is not migrating to the new properties file. |
Action | No user action is required. |
Explanation | Leftover properties that are found in the old file are not found in the new file. |
Action | No user action is required, but you might want to review the file and determine why some properties are missing. |
Explanation | Leftover grants that are found in the old file are not found in the new file. |
Action | No user action is required. |
Explanation | The IBM WebSphere Business Integration Server Foundation process choreographer feature must be installed before you can install this enterprise application. |
Action | Install the enterprise application on the server after installing the feature. |
Explanation | An error occurred while migrating the XML file. |
Action | If the file is corrupted, run the command again with a valid copy of the XML file. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | If the dummy key files are used, the path to the key files is not updated. Instead, the new WebSphere Application Server version default path to those files is used. |
Action | If the dummy key files are modified, refer to the WebSphere Application Server Information Center for details about how to proceed. |
Explanation | If the dummy key files are used, the path to the key files is not updated. Instead, the new WebSphere Application Server version default path to those files is used. |
Action | If the dummy key files are modified, refer to the WebSphere Application Server Information Center for details about how to proceed. |
Explanation | While migrating a federated node, the node names of the old and new configurations did not match. This configuration cannot be migrated because the old configuration exists in the deployment manager with the old node name. Using the new node name causes an unacceptable configuration in the deployment manager. |
Action | Uninstall and reinstall WebSphere Application Server using the same node name as the old configuration, or remove the old node from the deployment manager configuration, and manually add this node. |
Explanation | The migration of a deployment manager to the latest release is successful. This migration creates the same port definitions as those on the existing WebSphere configuration. Stop the deployment manager of the existing configuration before starting the deployment manager in the new configuration, and do not use it. Use the deployment manager of the new configuration to manage the environment. |
Action | If you want to use rollback to use the previous WebSphere 5.0 or 5.1 environment instead of WebSphere 6.0 you must re-enable that configuration. To do this go to the /bin directory of the previous WebSphere 5.0 or 5.1 installation and execute the migrationDisablementReversal.jacl script |
Explanation | During a federated migration, a JMX connection must be established with the deployment manager. That connection was not established during this migration attempt. |
Action | Check the original error message and verify that all the connection information is correct. If the information is correct, verify that the deployment manager is running, and that it is listening on the port that is specified in the error message. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The migration of the configuration files, the properties files, or the policy files has caused an error. All changes are rolling back. |
Action | Stop any running processes, like the nodeagents or any other process that can interfere with the processing of the configuration files and run migration again. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date. |
Action | No user action is required. |
Explanation | You can find a complete list of messages in the WASPostUpgrade log file on the deployment manager machine. The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date. |
Action | No user action is required. |
Explanation | During the application installation process of a federated migration, one or more application installations failed. Refer to the log files for details. |
Action | If possible, correct the problems that are recorded in the log files. The WASPostUgrade log file is located in the new installed image of WebSphere Application Server in the logs directory. The file name includes a time stamp, so look for the log with the latest creation date. |
Explanation | The series of steps needed to save the existing configuration information for the profile is starting. |
Action | No user action is required. |
Explanation | The profile must exist before a migration can be performed. |
Action | Rerun the command with the correct profile name, or use the wasprofile command to create the correct profile. |
Explanation | The profile did not exist in the previously installed WebSphere. |
Action | Rerun the command with the correct profile name. |
Explanation | Inform the user that the migration process has not stalled but is executing on the DeploymentManager node. |
Action | No user action is required. |
Explanation | When the -includeApps attribute is set to false, no user applications will be installed |
Action | Install the application using the WebSphere Application Server administration interfaces. |
Explanation | A default profile does not exist and the -oldProfile parameter was not specified. |
Action | Rerun the command with the correct profile name. |
Explanation | An application with the same name already exists in the configuration. |
Action | If you want to deploy the migrated application, uninstall the application with the same name and reinstall the application using the WebSphere Application Server administrative interfaces. |
Explanation | An inconsistency occurred between the files that the migration updated and the configuration. Most likely some system management interface, for example syncNode, wsadmin and so on, has modified the configuration. |
Action | Stop the conflicting system management interface and run migration again. |
Explanation | The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service. |
Action | Install the feature and rerun the command. |
Explanation | The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service. |
Action | Install the feature and rerun the command. |
Explanation | The IBM WebSphere Business Integration Server Foundation feature must be installed to run the specified service. |
Action | Install the feature and rerun the command. |
Explanation | Migration of Embedded JMS to Service Integration Bus failed to execute properly. |
Action | Please see infocenter for further action, if answer is not found in infocenter please contact IBM support. |
Explanation | The application cannot be installed because the required supporting software is not available. |
Action | No user action is required. |
Explanation | Deployment targets need to be identified and specified in the application deployment.xml file. |
Action | Install the application using the WebSphere Application Server administrative interfaces. |
Explanation | All servers must belong to a core group. This server is added to the default core group. |
Action | No user action is required. |
Explanation | The identified setting is deprecated. This value is still used for this release, but will be removed in a later release. |
Action | See the information center for further information about an alternative or replacement setting. |
Explanation | Transports are migrating to corresponding channels in the new release. |
Action | No user action is required. |
Explanation | Each transport is migrated to a new channel and belongs to a new default thread pool. |
Action | No user action is required. |
Explanation | The migration of a deployment manager to the latest release is successful. This migration creates the same port definitions that are in the existing WebSphere Application Server configuration. The node agent of the existing configuration must be stopped before starting the deployment manager in the new configuration. The deployment manager of the new configuration must be used to manage the environment. |
Action | If you want to use rollback to use the previous WebSphere 5.0 or 5.1 environment instead of WebSphere 6.0 you must re-enable that configuration. To do this go to the /bin directory of the previous WebSphere 5.0 or 5.1 installation and execute the migrationDisablementReversal.jacl script |
Explanation | A failure occurred during the federated migration. The deployment manager temp directory contains additional information to resolve the conflict like trace files, log files, configuration files, and so on. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The -serverName is provided, but the -nodeName parameter is missing. The profile that is being used has more than one node. The -nodeName parameter must also be provided. |
Action | Run the command again and provide both parameters. |
Explanation | The parameter was specified when running the command. The value that is specified cannot be found in the profile. |
Action | Run the command again with a correct value for the parameter. |
Explanation | The configuration is saved. |
Action | No user action is required. |
Explanation | A default profile does not exist and the correct profile parameter was not specified. |
Action | Rerun the command with the correct profile name. |
Explanation | All servers must belong to some core group. This server could not be added to the default core group due to some error. |
Action | The server must be added to some core group before it is able to run. This can be done by using the System Management interfaces. |
Explanation | While processing the input configuration no node name matches were found that match the one in the new configuration. This means that only data at the cell level will be migrated. No data for nodes, servers or applications will be added to the new configuration. |
Action | This may be sufficient migration for this configuration but it may not. If it is not then either the existing node name in the new configuration may be incorrect or the input configuration was incorrect. Correct the appropriate values and rerun the WASPostUpgrade command. |
Explanation | While processing a deployment manager configuration a node was attempted to be added to the configuration from the old configuration. However, a node with that name already exists in the configuration at a higher WebSphere Application Server version than exists in the old configuration. It will not be updated. |
Action | No action required by the user. |
Explanation | While processing a configuration a node was attempted to be converted from script compatibility mode. However, that node is not at the latest WebSphere Application Server version. It will not be updated. |
Action | No action required by the user. |
Explanation | While migrating the deployment manager, an error occurred. All changes to the deployment manager node are rolling back. |
Action | No user action is required. |
Explanation | While processing a deployment manager configuration the cell names of the old and new configurations did not match. This is not a supported migration path |
Action | Perform migration again using a profile name with the matching cell name. |
Explanation | While processing a configuration a node was attempted to be migrated into the new configuration. However, that node is not the same type in both configurations. One of the nodes is a deployment manager node while the other is a federated node It will not be updated. |
Action | No action required by the user. |
Explanation | All nodes must belong to a node group. This node is added to the default node group. |
Action | No user action is required. |
Explanation | A generic server manages an external resource. Migration cannot accurately determine which external resources to migrate thus so user intervention is required to back up and verify the setup after migration has is completed. |
Action | After migration and before you delete the old WebSphere Application Server installation, copy any externally referenced files and perform any kind of application-specific setup that relates to this step. |
Explanation | Due to limitations in a mixed-node environment, the -useMetaDataFromBinary attribute has been set to false. The local changes that were part of the enterprise archive (EAR) file are also located in the repository, so the behavior of the application does not change. |
Action | When the application is used for 6.x profiles only, use the administrative console to modify this attribute. |
Explanation | The migration completed with no warning or error messages. |
Action | No user action is required. |
Explanation | The migration completed with some warning messages, but no errors occurred. |
Action | Check the log file that the migration command created in the logs directory, and correct the problems if required. The log name includes a timestamp, so check the log file with the latest creation date. |
Explanation | After the previously successful migration, this configuration was disabled so that it would not interfere with the new configuration. |
Action | If you need to migrate this configuration again, use the migrationDisablementReversal.jacl file in the bin directory to enable the configuration, and then run this command again. |
Explanation | The deployment manager node has a different name in the old configuration than in the new configuration. This name can work, with some side effects. One side effect is that all the node agents that are accessing this configuration must be restarted to communicate. The node name is part of the communications properties. Another side effect can affect administration scripts that are created by users. If these scripts reference the deployment manager node name, they need modification. |
Action | If you do not want this change, create a new profile where the deployment manager node name matches the name in the old configuration and run the migration against this new profile. |
Explanation | The deployment manager must be migrated before you can migrate managed nodes. |
Action | Run the migration utilities to migrate the deployment manager first and then try your managed node migration again. See the WebSphere Application Server Information Center for detailed steps. |
Explanation | Certain files in the V5 environment might be modified during the migration of a V6 deployment manager that manages V5 nodes. By running the backupConfig command against your V5 environment, you provide yourself with an error recovery path. |
Action | Run the backupConfig command against all the V5 nodes that are managed by the V6 deployment manager. |
Explanation | The direct invocation of WASPreUpgrade and WASPostUpgrade is not supported. |
Action | Use the WebSphere z/OS Customization Dialog migration option to invoke the migration utilities. |
Explanation | New release of WebSphere Application Server can not manage nodes prior to 6.0.2.0 without fix. |
Action | User must install required fix to 6.0.0.x and 6.0.1.y nodes prior to migration. |
Explanation | The Deployment Manager for which this node belongs is not the Deployment Manager currently running. |
Action | Shut down the incorrect Deployment Manager and start the Deployment Manager that is currently managing the node to be migrated. |
Explanation | The migration of cloudscape to derby was successfully for this particular database. |
Action | No useraction required. |
Explanation | The migration of cloudscape to derby has failed for this particular database. |
Action | Manual migration of old DataBase to new Database is required. See infocenter for further details. |
Explanation | This error happens if the Deployment Manager configuration contains a node with the same name of a node in the prior release. This happens if the user does an "addNode" in the current release prior to Migration. |
Action | UnFederate the node in the current release and run Migration. |
Explanation | This error occurs when an unsupported server type is encounter. |
Action | Use the migration utilities for the product that this server type belongs too. |
Explanation | This error occurs when -keepAppDirectory true and -appInstallDirectory are both specified. |
Action | Select only one of the two parameters or specify -keepAppDirectory false. |
Explanation | Applications that are already installed in the new profile will not be migrated. |
Action | No user action required. |
Explanation | A variable being used could not be resolved using the defined variables |
Action | Check to see if the variable is being used for a valid reason. If not then no further action is required, if it is then define the variable. |
Explanation | A variable being used could not be resolved using the defined variables |
Action | Check to see if the variable is being used for a valid reason. If not then no further action is required, if it is then define the variable. |
Explanation | To avoid having two DMgr managing the same cell you must shutdown the current version of Deployment Manager when setting -keepDMgrEnabled=true |
Action | Shut down current version of Deployment Manager and perform Migration again. |
Explanation | The file or directory may already exist. To avoid overwriting a valid file or directory we have choosen to not copy the file or directory. |
Action | If the file or directory is required then manually search the WASPreUpgrade backup directory for the file or directory and copy it into the new environment. |
Explanation | Verification of -traceFile location failed. |
Action | Make sure that -traceFile location is not write protected and that the path entered is a valid path. |
Explanation | During the application migration process, one or more applications failed to migrate. Refer to the log files for details. |
Action | If possible, correct the problems that are recorded in the log files. One or more applications may need to be installed manually. |
Explanation | The specified object is being copied to the configuration of the new WebSphere Application Server version. |
Action | No user action is required. |
Explanation | DB2 for zOS Local JDBC Provider (RRS) jdbc provider not supported in destination WebSphere Application Server version, you will need to manually create a DB2 Universal Driver provider as its replacement. |
Action | Manual creation of DB2 Universal Driver provider is required. |
Explanation | Node or Server name specified does not exist. |
Action | Run command again specifying existing Node and Server names. |
Explanation | During a managed node migration any new v6.1 configuration changes that existed prior to running WASPostUpgrade may need to be reapplied after WASPostUpgrade completes. |
Action | Reapply preexisting v6.1 cell level changes once managed node migration has been completed. |
Explanation | A JDBC provider in the previous version did not have a provider type defined. This is a required attribute. The provider type could not be resolved during migration. |
Action | Ensure that each JDBCProvider has a providerType. It is recommended that you delete {0}, unless you have previously configured data sources that still use it. |
Explanation | A feature pack augmented profiles was detected in the target environment. It is currently not supported to migrate into target environment that has been augmented by a feature pack. |
Action | Create a new profile and do not augment the profile. Migrate your source environment into your target environment. Now augment the target environment with feature pack. |
Explanation | This problem is usually caused by parameters that are misspelled or missing. |
Action | Verify that all of the parameters are valid and spelled correctly. Type the command without parameters or arguments to get the correct syntax of the command. |
Explanation | When you specify a file trace, you must also specify the level of detail to write out to trace through the -traceString parameter. |
Action | Add the -traceString parameter. For example: -traceString "*=all=enabled" You must include the quotation marks. |
Explanation | No argument is provided for the specified attribute. For example, the parameter '-traceFile' was used, but '-traceFile /some/path/to/log/file.txt' was required. |
Action | Supply an argument for the specified parameter. |
Explanation | The enterprise archive (EAR) file name is either not an EAR file, or the contents and structure of the EAR file do not follow the Java 2 Platform, Enterprise Edition (J2EE) specification. |
Action | Verify that the path is spelled correctly, and that a valid EAR file is in that location. |
Explanation | A specified parameter is not recognized as a valid parameter. |
Action | Verify spelling and run the command alone, without any parameters or arguments, to get the correct syntax of the command. |
Explanation | No enterprise archive (EAR) file is specified. This file name is the first argument that you pass in after the command. For example: clientUpgrade /ear/file/location/earfile.ear |
Action | Rerun the command with an EAR file as the first argument. |
Explanation | Cannot find the specified EAR file in the given location. |
Action | Verify that the path is spelled correctly and that an EAR file exists in that location. |
Explanation | The specified enterprise archive (EAR) file is a directory. |
Action | Verify that the specified EAR file is an EAR file and not a directory. |
Explanation | The enterprise archive (EAR) file does not contain any client Java archive (JAR) files by the specified name. |
Action | Verify that the EAR file contains the client JAR file that is specified. |
Explanation | The enterprise archive (EAR) file does not contain any client JAR files. |
Action | If the specified EAR file is expected to contain client Java archive (JAR) files, correct the EAR file, and try the command again. |
Explanation | No client Java archive (JAR) file was specified for migration, so all of the client JAR files are migrated. |
Action | No user action is required. |
Explanation | This client Java archive (JAR) file is in the process of migrating. |
Action | No user action is required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The trace cannot be properly set up. The trace might not be working. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | This tool has already migrated the enterprise archive (EAR) file or the JAR file that you attempted to migrate. The file is not modified. |
Action | No user action is required. |
Explanation | The Java archive (JAR) file that you attempted to migrate already exists in a 5.0.x or a 5.1.x format. |
Action | No user action is required. |