Problem |
The administrative command could not be completed because the specified combination of parameters was not valid. Specify either a cluster name or both node and server names. |
User response |
Run the command again with the correct parameters. |
Problem |
The administrative command failed because the specified parameter was not one of the valid values. |
User response |
Correct the specified parameter and run the command again. |
Problem |
The administrative command failed because the specified required parameter was omitted. |
User response |
Run the admininstrative command again, specifying all required parameters. |
Problem |
The administrative command encountered an exception while attempting to remove the event database. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The administrative command encountered one or more errors while attempting to create the event database and data source configuration scripts for the specified database environment. |
User response |
Consult the wsadmin.traceout file to determine the cause of the problem. |
Problem |
The administrative command could not find the specified JDBC provider. |
User response |
Run the command again, specifying the correct JDBC provider. |
Problem |
The administrative command could not find the specified data source. |
User response |
Run the command again, specifying the correct data source. |
Problem |
The specified node name does not refer to a valid node. |
User response |
Run the administrative command again, specifying the correct node name. |
Problem |
The specified server name is not valid for the specified node. |
User response |
Run the administrative command again, specifying the correct node and server. |
Problem |
The specified cluster name does not refer to a valid cluster. |
User response |
Run the administrative command again, specifying the correct cluster name. |
Problem |
The specified server name does not refer to a valid server. |
User response |
Run the administrative command again, specifying the correct server name. |
Problem |
No template with the specified name is present in the configuration respository. |
User response |
Run the command again with the correct template name. |
Problem |
The specified directory does not exist or is not accessible. |
Problem |
The administrative command could not be completed because the specified parameter value is not a positive integer. |
Problem |
The administrative command could not be completed because the specified parameter value is not a positive number. |
Problem |
The specified file does not exist or is inaccessible. |
Problem |
The administrative command encountered one or more errors while attempting to create the event database using the specified database environment. |
Problem |
The administrative command could not create the event database using the specified name because a database with that name already exists. This might be a database belonging to a previous installation of the event service, or a database belonging to another application. |
Problem |
The administrative command cannot automatically create a DB2 event database on a z/OS system. Instead, scripts are provided in the specified directory to manually perform the database creation. |
Problem |
The administrative command cannot automatically remove a DB2 event database from a z/OS system. Instead, scripts are provided in the specified directory to perform the database removal. |
Problem |
The administrative command could not create the Derby event database because a database already exists with the same name and path. This database might belong to a previous installation of the event service or to another application. |
Problem |
The administrative command encountered an exception while attempting to read a file in EBCDIC format. |
Problem |
The specified file could not be deleted because it is locked or inaccessible. |
Problem |
The specified directory could not be deleted because it is locked or inaccessible. |
Problem |
The administrative command encountered an exception while attempting to create the specified file. |
Problem |
To configure the event database, you must specify the class path for either the Toolbox for Java JDBC driver or the native JDBC driver, but not both. The path must indicate the location of the driver, but must not include the name of the jar or zip file. |
Problem |
To configure a Derby event database using the Toolbox for Java JDBC driver, you must specify a host name and port number for the network data source. These parameters are not required for a local data source. |
Problem |
The administrative command failed because the specified parameter exceeded the maximum valid length. |
Problem |
The -createDB parameter can only set to true only if you are configuring the event database on a native OS/400 platform. For all other platforms, this parameter must be set to false. |
Problem |
The specified administrative command could not be completed because the wsadmin parameter was specified, indicating local mode. This mode can be used only on a stand-alone node, not on a federated node or deployment manager. |
Problem |
The administrative command encountered one or more errors while attempting to create the data source for the event service. |
Problem |
The specified buffer pool name is not one of the valid values. Valid buffer pool names include: |
Problem |
The specified database name does not conform to the syntax rules for a DB2 database name. A DB2 database name must be no more than 8 characters in length, and all characters must be from the base character set of the database manager. |
Problem |
The specified location for the Oracle home directory does not exist or is inaccessible. |
Problem |
The specified parameter is required. |
Problem |
The administrative command could not be completed because the specified parameter is not within the valid range. |
Problem |
The specified parameter does not conform to the syntax rules for the administrative command. |
Problem |
The specified parameter value does not conform to the Sybase password requirements. |
Problem |
The specified name does not conform to the syntax rules for a DB2 node name. |
Problem |
The database configuration administrative command creates an output directory in the specified location for the generated database configuration scripts. However, the specified directory already exists. |
Problem |
The administrative command encountered one or more errors while attempting to create the specified directory. |
User response |
The determine the cause of the problem, turn on the wsadmin tool trace options in the properties file profile/properties/wsadmin.properties. Then run the administrative command again and check the trace file profile/log/wsadmin.traceout for messages indicating the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while installing the specified application. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while removing the application. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
See message |
User response | Run the command again with the overrideDataSource parameter set to true. |
Problem |
See message. |
Problem |
To configure the event database, you must specify the class path for either the Toolbox for Java JDBC driver or the native JDBC driver, but not both. The path must indicate the location of the driver, but must not include the name of the jar or zip file. |
Problem |
The AdminTask administrative command encountered an exception while updating the specified application module. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
See message. |
User response |
Run the command again and specify the required parameters. |
Problem |
The administrative command could not create the event database using the specified name because a database with that name already exists. This might be a database belonging to a previous installation of the event service, or a database belonging to another application. |
Problem |
The administrative command could not locate the Derby event database in the specified path. The database must exist in order to create the Common Event Infrastructure tables in it. |
Problem |
This parameter is used only with the Derby Network Server. In order to use the Derby network driver you must provide a hostname and a port on which the database server is running. |