- CEPBankServACH0606:
- Explanation: An internal error occurred in the cassette. The exception text will help
Action: If some required operation or service is not functioning properly, contact
- CEPBankServACH1001:
- Explanation: This is an internal cassette error.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH1002:
- Explanation: The BankServACH Cassette has started and is ready to accept commands.
Action: None
- CEPBankServACH1003:
- Explanation: The BankServACH Cassette is no longer active.
Action: None
- CEPBankServACH2000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH2001:
- Explanation: The specified merchant already has an account for the specified account
Action: Try to create the account again, but specify an account number that
- CEPBankServACH2002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH2003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH2004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH2005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH2006:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPBankServACH2007:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPBankServACH2008:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPBankServACH2009:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPBankServACH2010:
- Explanation: A bad return code ("QD") was returned in the batch settlement response.
Action: Contact the BankServ host representative to determine why the batch already exists.
- CEPBankServACH2011:
- Explanation: The specified merchant already has an account. There can be only one account
Action: Use the account that is already defined for this merchant.
- CEPBankServACH3000:
- Explanation: The specified batch for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the batch exists for the merchant.
- CEPBankServACH3001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH3002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH3003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH3004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH3005:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3007:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3011:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3013:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3015:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3016:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH3017:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH4000:
- Explanation: The specified order for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the order exists for the merchant.
- CEPBankServACH4001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH4002:
- Explanation: An SQL exception occurred while attempting to close an SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH4003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH4004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH4005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH4006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH5000:
- Explanation: The specified payment was not found in the WebSphere Commerce Payments database.
Action: Ensure that the payment exists for the merchant and
- CEPBankServACH5001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH5002:
- Explanation: An SQL exception occurred while attempting to close an SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH5003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH5004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH5005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH5006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPBankServACH7000:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7001:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7002:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7003:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7004:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7005:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH7006:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH8000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH8001:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH9000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH9001:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH9002:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH9003:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPBankServACH9005:
- Explanation: Unable to encrypt or decrypt the PAN or expiration date.
Action: Contact your IBM support representative.
- CEPBankServACH9006:
- Explanation: An incorrect value was entered in the referenced protocol data.
Action: Reissue the command with a valid value.
- CEPCustomOffline1000:
- Explanation: The Cassette is now accepting requests.
Action: None
- CEPCustomOffline1001:
- Explanation: The Cassette is no longer accepting requests.
Action: None
- CEPCustomOffline1002:
- Explanation: Check with development as to the availability of this method if you have
Action: Contact your IBM support representative.
- CEPCustomOffline1003:
- Explanation: None
Action: Check with your developer for possible reasons as to why this happened.
- CEPCustomOffline2000:
- Explanation: An SQL exception occurred while accessing the CUSTOMACCOUNT table. This
Action: Check the connection to the database to make sure that there is not a problem
- CEPCustomOffline2001:
- Explanation: An SQL exception occurred while closing CUSTOMACCOUNT table. The SQL exception
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline2003:
- Explanation: This insertion is only supposed to insert one row, but more than one row
Action: None
- CEPCustomOffline2004:
- Explanation: An SQL exception occurred while inserting a row into the CUSTOMACCOUNT
Action: Check the connection to the database to make sure that there is not a problem
- CEPCustomOffline2005:
- Explanation: The update should have changed only one row but more than one row were
Action: None
- CEPCustomOffline2006:
- Explanation: SQL exception occurred while reading a WebSphere Commerce Payments database table. The SQL exception
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline2007:
- Explanation: The deletion is only supposed to delete one row, but more than one row
Action: Contact your IBM support representative.
- CEPCustomOffline2008:
- Explanation: An SQL exception occurred while inserting a row into the CUSTOMACCOUNT
Action: Check the connection to the database to make sure that there is not a problem
- CEPCustomOffline2009:
- Explanation: The socket connection that performs the communication between the cassette
Action: If the problem persists, contact your IBM service representative.
- CEPCustomOffline2010:
- Explanation: The transaction used in the request is not a valid one. This is not expected
Action: Contact your IBM support representative.
- CEPCustomOffline3000:
- Explanation: An SQL query of CUSTOMBATCH table should have returned only one row but
Action: Contact your IBM support representative.
- CEPCustomOffline3001:
- Explanation: An SQL query of CUSTOMBATCH table should have returned only one row but
Action: Contact your IBM support representative.
- CEPCustomOffline3002:
- Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline3003:
- Explanation: An SQL exception occurred while closing the CUSTOMBATCH table query. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline3004:
- Explanation: This insertion is only supposed to insert one row, but more than one row
Action: Contact your IBM support representative.
- CEPCustomOffline3005:
- Explanation: SQL exception occurred while inserting into the CUSTOMBATCH table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline3006:
- Explanation: The update is only supposed to affect one row, but more than one row was
Action: Contact your IBM support representative.
- CEPCustomOffline3007:
- Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline3008:
- Explanation: An SQL delete of CUSTOMBATCH table should have returned only one row but
Action: Contact your IBM support representative.
- CEPCustomOffline3009:
- Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline3010:
- Explanation: This is a sanity check in the processing of request. A user may not see
Action: Contact your IBM support representative.
- CEPCustomOffline3011:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3012:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3013:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3014:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3015:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3016:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3017:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3018:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline3019:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPCustomOffline4000:
- Explanation: An SQL query of the CUSTOMORDER table should have returned only one row
Action: Contact your IBM support representative.
- CEPCustomOffline4001:
- Explanation: An SQL query of the CUSTOMORDER table should have returned one row but
Action: Contact your IBM support representative.
- CEPCustomOffline4002:
- Explanation: An SQL exception occurred while querying the CUSTOMORDER table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline4003:
- Explanation: An SQL exception occurred while closing the CUSTOMORDER table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline4004:
- Explanation: An SQL insertion into the CUSTOMORDER table should have inserted one row
Action: Contact your IBM support representative.
- CEPCustomOffline4005:
- Explanation: An SQL exception occurred while inserting into the CUSTOMORDER table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline4006:
- Explanation: An SQL update of the CUSTOMORDER table should have updated one row but
Action: Contact your IBM support representative.
- CEPCustomOffline4007:
- Explanation: An SQL exception occurred while updating the CUSTOMORDER table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline4008:
- Explanation: An SQL delete of the CUSTOMORDER table should have deleted one row but
Action: Contact your IBM support representative.
- CEPCustomOffline4009:
- Explanation: An SQL exception occurred while deleting an order from the CUSTOMORDER
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline4010:
- Explanation: While closing a batch, it was discovered that the batch contained a payment
Action: Contact your IBM support representative.
- CEPCustomOffline4011:
- Explanation: While closing a batch, it was discovered that the batch contained a credit
Action: Correct the state and close the batch again.
- CEPCustomOffline5000:
- Explanation: While querying for a payment, it returned multiple entries. This condition
Action: Contact your IBM support representative.
- CEPCustomOffline5001:
- Explanation: While querying for a payment that should have returned one row, nothing
Action: Contact your IBM support representative.
- CEPCustomOffline5002:
- Explanation: An SQL exception occurred while querying from the CUSTOMPAYMENT table.
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline5003:
- Explanation: An SQL exception occurred while closing from the CUSTOMPAYMENT table query.
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline5004:
- Explanation: An SQL insertion into the CUSTOMPAYMENT table should have inserted one
Action: Contact your IBM support representative.
- CEPCustomOffline5005:
- Explanation: An SQL exception occurred while inserting a new payment into from the
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline5006:
- Explanation: While updating a payment that should have affected one row, multiple rows
Action: Contact your IBM support representative.
- CEPCustomOffline5007:
- Explanation: An SQL exception occurred while updating the CUSTOMPAYMENT table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline5008:
- Explanation: While deleting a payment that should have affected one row, multiple rows
Action: Contact your IBM support representative.
- CEPCustomOffline5009:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline5010:
- Explanation: While closing a batch, it was discovered that the batch contained a payment
Action: Contact your IBM support representative.
- CEPCustomOffline6000:
- Explanation: While querying the CUSTOMCREDIT table, it was supposed to return one row
Action: Contact your IBM support representative.
- CEPCustomOffline6001:
- Explanation: While querying the CUSTOMCREDIT table, it should have returned one row
Action: Contact your IBM support representative.
- CEPCustomOffline6002:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline6003:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline6004:
- Explanation: While querying the CUSTOMCREDIT table, it should have returned one row
Action: Contact your IBM support representative.
- CEPCustomOffline6005:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline6006:
- Explanation: While updating the CUSTOMCREDIT table, it should have updated one row but
Action: Contact your IBM support representative.
- CEPCustomOffline6007:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline6008:
- Explanation: While deleting a row from the CUSTOMCREDIT table, it should have deleted
Action: Contact your IBM support representative.
- CEPCustomOffline6009:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline6010:
- Explanation: While closing a batch, it was discovered that the batch contained a credit
Action: Contact your IBM support representative.
- CEPCustomOffline7000:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline7001:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline7002:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline7003:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPCustomOffline7004:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0000:
- Explanation: This is used to display the Framework version number in the error log.
Action: Contact your IBM support representative.
- CEPFW0100:
- Explanation: A Payment API command was received whose command name is not recognized
Action: If the command was sent to the Payment API port by a user application,
- CEPFW0101:
- Explanation: An SQL exception occurred while IBM WebSphere Commerce Payments attempted to reference the order
Action: Test the connection to the database and list the table ETORDER to make
- CEPFW0102:
- Explanation: The approve or deposit flag specified on a RECEIVEPAYMENT or APPROVE API
Action: Reissue the command with the correct value parameter.
- CEPFW0103:
- Explanation: A required parameter was not provided in the specified command.
Action: Reissue the command with the required parameter.
- CEPFW0104:
- Explanation: The specified parameter has a minimum length.
Action: Reissue the command with a valid parameter value.
- CEPFW0105:
- Explanation: The CURRENCY parameter specified on the Payment API command must match
Action: Reissue the command with the correct currency.
- CEPFW0106:
- Explanation: The Merchant specified has not been configured to use the specified payment
Action: Change the PAYMENTSYSTEM parameter on the RECEIVEPAYMENT call to use a
- CEPFW0107:
- Explanation: When specifying a known ISO 4217 currency, the AMOUNTEXP10 parameter must
Action: Reissue the command with the correct AMOUNTEXP10 (or omit it altogether).
- CEPFW0108:
- Explanation: The length of a command parameter exceeded the maximum number of bytes.
Action: Reissue the command with a valid parameter value.
- CEPFW0109:
- Explanation: The specified parameter must contain a numeric value.
Action: Reissue the command with a valid parameter value.
- CEPFW0110:
- Explanation: The specified parameter must contain a numeric value greater than the
Action: Reissue the command with a valid parameter value.
- CEPFW0111:
- Explanation: The specified parameter must contain a numeric value no larger than the
Action: Reissue the command with a valid parameter value.
- CEPFW0112:
- Explanation: The value specified for the CURRENCY parameter does not contain the number
Action: Reissue the command with a valid CURRENCY value.
- CEPFW0113:
- Explanation: The value specified for CURRENCY is not a recognized country/region code
Action: Reissue the command with a valid CURRENCY value.
- CEPFW0123:
- Explanation: The AMOUNTEXP10 specified on the Payment API command must match the AMOUNTEXP10
Action: Reissue the command with a matching AMOUNTEXP10 value.
- CEPFW0126:
- Explanation: The amount specified is either negative, which is never valid or is 0 and
Action: Reissue the command with a valid Amount value.
- CEPFW0127:
- Explanation: The Content Type and Charset are the two parts of the CONTENTTYPECHARSET
Action: Correct the value specified for the CONTENTTYPECHARSET.
- CEPFW0148:
- Explanation: The BATCHNUMBER on a Payment API command must be greater than zero.
Action: Reissue the command with a valid BATCHNUMBER parameter.
- CEPFW0150:
- Explanation: The order specified in the API command has not been associated with an
Action: Associate the order with an account number and reissue the command.
- CEPFW0151:
- Explanation: A request has been made to perform an API command on a payment that does
Action: Create a payment via the {0} command.
- CEPFW0152:
- Explanation: A request has been made to perform an API command on a credit that does
Action: Create a credit via the {0} command.
- CEPFW0153:
- Explanation: A {0} API command was issued, but no batch
Action: Verify that you have entered the correct values for the BATCHNUMBER and
- CEPFW0154:
- Explanation: A {0} or {1} or {2} API command was issued, but no account was
Action: Check that you have entered the correct {0} and {1} for the API.
- CEPFW0155:
- Explanation: A {0} or {1} or {2} API command was issued, but no merchant was
Action: Check that you have entered the correct merchant number for the API.
- CEPFW0156:
- Explanation: A administration API command was issued, but no cassette was found matching
Action: Check that you have entered the correct cassette number for the API.
- CEPFW0157:
- Explanation: An administration API command was issued, but no merchant was found matching
Action: Check that you have entered the correct merchant number for the API.
- CEPFW0158:
- Explanation: An API command operated on Orders was issued, but no merchant was found
Action: Check that you have entered the correct merchant number for the API.
- CEPFW0159:
- Explanation: An API command operated on Orders was issued, but no account was found
Action: Check that you have entered the correct account number for the API.
- CEPFW0160:
- Explanation: The specified parameter contains leading zeros, which are not valid.
Action: Reissue the command with a valid parameter value.
- CEPFW0162:
- Explanation: The AMOUNT parameter on a Payment API command must be less than or equal
Action: Correct the amount specified on the command.
- CEPFW0163:
- Explanation: The specified parameter on a Payment API command must be number and between
Action: Correct the value specified on the command for the parameter.
- CEPFW0202:
- Explanation: An SQL exception occurred while attempting to create an object int the
Action: Check the connection to the database to make sure that there is not a problem
- CEPFW0203:
- Explanation: An SQL exception occurred while updating an object in WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPFW0204:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPFW0205:
- Explanation: An SQL exception occurred while accessing WebSphere Commerce Payments database. This could
Action: Check the connection to the database to make sure that there is not a problem
- CEPFW0206:
- Explanation: A protocol message was received from a cardholder; no matching order was
Action: If there is a related message logged for this error, check to see if there
- CEPFW0207:
- Explanation: A Java exception occurred while processing a message received from a Payment
Action: See if there is a related message logged for this error; follow the instructions
- CEPFW0208:
- Explanation: A protocol message was received from a cardholder; no matching merchant
Action: Contact your IBM support representative.
- CEPFW0209:
- Explanation: A value was specified in the PAYMENTTYPE field of a payment system profile
Action: Delete or correct the database record in the PaymentSystem database record
- CEPFW0301:
- Explanation: An I/O exception occurred while reading from the Payment Gateway on the
Action: Verify that the communication between WebSphere Commerce Payments and the Acquirer is valid.
- CEPFW0344:
- Explanation: An SQL exception occurred while retrieving an order from the Order table.
Action: Test the connection to WebSphere Commerce Payments database, verify that this order is in the
- CEPFW0358:
- Explanation: There was an unexpected error while attempting to process this command.
Action: This is an internal WebSphere Commerce Payments error. Contact your IBM support representative.
- CEPFW0412:
- Explanation: An SQL exception occurred while writing a payment system profile to the
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0413:
- Explanation: An SQL exception occurred while retrieving the PaymentSystem Configuration
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0414:
- Explanation: Both of the MERCHANTNAME and PAYMENTSYSTEMNAME fields of the Payment System
Action: Verify that both fields are filled in on WebSphere Commerce Payments Configuration table.
- CEPFW0415:
- Explanation: A value was specified for the MERCHANTNAME field of an Acquirer Profile
Action: Correct the value of MERCHANTNAME in the Payment System Configuration table.
- CEPFW0428:
- Explanation: The JDBC driver name specified was not found in WebSphere Commerce Payments environment. The
Action: Ensure JDBC driver name is typed correctly and CLASSPATH specifies the
- CEPFW0429:
- Explanation: The JDBC driver name was not specified on the DBDriver parameter in the
Action: Ensure JDBC driver name is specified on the DBDRIVER parameter.
- CEPFW0430:
- Explanation: The JDBC driver class is not specified in the CLASSPATH environment variable.
Action: Ensure that the CLASSPATH contains the path to the JDBC Driver class.
- CEPFW0431:
- Explanation: Attempting to instantiate a JDBC Driver that is an interface or abstract
Action: Ensure that the JDBC driver being used is not an interface or abstract
- CEPFW0435:
- Explanation: The JDBC URL was not initialized.
Action: Consult the database vendor documentation to determine the proper JDBC
- CEPFW0436:
- Explanation: WebSphere Commerce Payments database owner was not set on the DBOWNER parameter in the PaymentServlet
Action: Provide WebSphere Commerce Payments database owner on the DBOWNER parameter.
- CEPFW0437:
- Explanation: WebSphere Commerce Payments database user ID was not initialized in the PaymentServlet init
Action: Provide WebSphere Commerce Payments database user ID on the DBUSERID parameter.
- CEPFW0438:
- Explanation: WebSphere Commerce Payments database or root password was not initialized in the PaymentServlet
Action: Provide WebSphere Commerce Payments required password in the PaymentServlet init parameters.
- CEPFW0459:
- Explanation: This error may be caused by:
Action: Supply the correct login, password, JDBC driver, and URL address for the
- CEPFW0460:
- Explanation: This error may be caused by:
Action: Verify that the database field definitions match what is required by WebSphere Commerce Payments.
- CEPFW0461:
- Explanation: This error may have occurred because the database connection no longer
Action: The database may have been closed or shut down before WebSphere Commerce Payments connection
- CEPFW0462:
- Explanation: An SQL exception has occurred while closing a prepare statement since the
Action: The connection with the database has been lost before closing the SQL prepare
- CEPFW0465:
- Explanation: An error may have occurred while creating the database''s metadata.
Action: The database URL may not exist or is invalid. Also, the connection to the
- CEPFW0467:
- Explanation: IBM WebSphere Commerce Payments could not successfully perform an SQL command against the Cassette
Action: Provide the required information and retry the command.
- CEPFW0468:
- Explanation: Payment cassettes add an entry to the Cassette Configuration table when
Action: Restore the SET cassette configuration or install another payment cassette.
- CEPFW0469:
- Explanation: SQL exception occurred while reading a WebSphere Commerce Payments database table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0470:
- Explanation: SQL exception occurred while executing an SQL command on a WebSphere Commerce Payments database
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0471:
- Explanation: SQL exception occurred while constructing an SQL statement for a WebSphere Commerce Payments database
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0472:
- Explanation: A required object of the specified type for the command was not found.
Action: Ensure that an object corresponding to the identifiers presented does exist.
- CEPFW0473:
- Explanation: The specified command requires certain administration objects to be active.
Action: Ensure that all relevant objects are active by enabling them through the
- CEPFW0500:
- Explanation: A request has been made to perform an API command, which try to create
Action: Change the parameters to create a different object of the same type. You
- CEPFW0501:
- Explanation: A request has been made to perform an API command to modify or delete an
Action: You can issue a query to find out which objects are available in the system.
- CEPFW0502:
- Explanation: A request has been made to perform an API command to the specified object.
Action: You can issue a query to find out the status of those required objects.
- CEPFW0503:
- Explanation: A value retrieved from the database has an invalid value. This could be
Action: Ask your database administrator to check the database. Contact your IBM
- CEPFW0504:
- Explanation: The commit operation failed. WebSphere Commerce Payments will retry the commit operation.
Action: You may not need to take any actions unless the retry fails.
- CEPFW0606:
- Explanation: An internal error occurred in WebSphere Commerce Payments.
Action: Look for a CEPFW0606 message that corresponds to this. If there is a corresponding
- CEPFW0612:
- Explanation: An internal error occurred in WebSphere Commerce Payments.
Action: If some required operation or service is not functioning properly, contact
- CEPFW0617:
- Explanation: An I/O exception occurred when WebSphere Commerce Payments attempted to open a socket to the
Action: Test the connection to the host name specified. Verify that the specified
- CEPFW0619:
- Explanation: An error has occurred that has caused WebSphere Commerce Payments to not initialize.
Action: Try to resolve the problem by using the exception data. Otherwise contact
- CEPFW0620:
- Explanation: The specified user attempted an operation for which the user is not authorized.
Action: Contact a user with more authority than this user or give this user the
- CEPFW0621:
- Explanation: The realm specified in the file determines the base set of users that may
Action: Specify a valid WebSphere Application Server realm name in the file.
- CEPFW0622:
- Explanation:
Action: Refer to the SQL state information to get specific details about the nature
- CEPFW0701:
- Explanation: An unhandled exception has occurred that has caused WebSphere Commerce Payments to terminate
Action: Contact your IBM support representative.
- CEPFW0702:
- Explanation: WebSphere Commerce Payments has started successfully.
Action: None
- CEPFW0703:
- Explanation: WebSphere Commerce Payments has stopped.
Action: None
- CEPFW0704:
- Explanation: WebSphere Commerce Payments does not have access to the specified path, or the path is not
Action: Check the existence of the directory and retry the operation.
- CEPFW0705:
- Explanation: WebSphere Commerce Payments does not have write permissions for the specified path.
Action: Either change the permissions of the specified directory or select a valid
- CEPFW0707:
- Explanation: WebSphere Commerce Payments could not start due to missing parameters.
Action: Start WebSphere Commerce Payments using the following parameters:
- CEPFW0711:
- Explanation: The Java layer has thrown an exception.
Action: Use the stack trace and surrounding messages to resolve the error.
- CEPFW0712:
- Explanation: The Merchant attempted to create an order using an existing order number.
Action: Use a unique order number.
- CEPFW0713:
- Explanation: The Merchant attempted to create a payment using an existing payment number.
Action: Use a unique payment number.
- CEPFW0714:
- Explanation: The Merchant attempted to create a credit using an existing credit number.
Action: Use a unique credit number.
- CEPFW0715:
- Explanation: The Merchant attempted to open a batch using an existing {0}.
Action: Use a unique BATCHNUMBER for each batch.
- CEPFW0716:
- Explanation: WebSphere Commerce Payments has registered with the Work Load Manager and Domain Name Server
Action: None
- CEPFW0717:
- Explanation: WebSphere Commerce Payments has registered with the Work Load Manager and net.dispatcher for
Action: None
- CEPFW0719:
- Explanation: Unrecognized command line parameter detected.
Action: Start WebSphere Commerce Payments using the following parameters:
- CEPFW0720:
- Explanation: The cassette failed to successfully execute one of its startup functions.
Action: Look for a more specific error message from the cassette.
- CEPFW0721:
- Explanation: Cassettes must implement all of the IBM WebSphere Commerce Payments''s Cassette Programming
Action: Check the exception text for the name of the missing method.
- CEPFW0722:
- Explanation: The Java runtime could not find the Cassette class.
Action: Make sure your class path points to the zip file containing the Cassette
- CEPFW0723:
- Explanation: An instance exception occurred while attempting to load the specified cassette.
Action: Contact your IBM support representative.
- CEPFW0724:
- Explanation: An invalid access exception occurred while attempting to load the specified
Action: Contact your IBM support representative.
- CEPFW0725:
- Explanation: An invalid argument exception occurred while attempting to load the specified
Action: Contact your IBM support representative.
- CEPFW0726:
- Explanation: There was an error trying to register WebSphere Commerce Payments with the Work Load Manager/Domain
Action: Verify that there is an active Domain Name Server for the sysplex. Verify
- CEPFW0728:
- Explanation: There was an error while trying to open the log file for writing.
Action: Verify that the log path specified in WebSphere Commerce Payments profile is valid and that WebSphere Commerce Payments has
- CEPFW0731:
- Explanation: The named cassette has stopped.
Action: None
- CEPFW0732:
- Explanation: None
Action: None
- CEPFW0733:
- Explanation: There are no payment cassettes currently entered in the cassette configuration
Action: None
- CEPFW0734:
- Explanation: There are no payment cassettes currently entered in the cassette configuration
Action: None
- CEPFW0735:
- Explanation: A list of the payment cassettes that have been entered in the cassette
Action: None
- CEPFW0736:
- Explanation: A list of the payment cassettes that are currently able to process requests
Action: None
- CEPFW0737:
- Explanation: The command entered at the operator console was not a valid WebSphere Commerce Payments command.
Action: Enter a valid WebSphere Commerce Payments command at the operator console
- CEPFW0738:
- Explanation: The command entered at the operator console completed with the specified
Action: If the primary and secondary return codes are not 0, look up the return
- CEPFW0740:
- Explanation: The syntax of the operator command was not correct.
Action: Correct the command syntax and re-enter the operator command.
- CEPFW0756:
- Explanation: The specified cassette is already accepting requests.
Action: Contact your IBM support representative.
- CEPFW0757:
- Explanation: The specified cassette is not currently accepting requests.
Action: Contact your IBM support representative.
- CEPFW0758:
- Explanation: The specified cassette has not been installed.
Action: If the cassette has not been installed, install it and add the cassette
- CEPFW0761:
- Explanation: An error of the type specified in the message occurred when the BECOME
Action: Contact the WebSphere Commerce Payments administrator with the exception information.
- CEPFW0762:
- Explanation: WebSphere Commerce Payments BECOME command is valid only for stopped WebSphere Commerce Paymentss.
Action: Re-enter the command with the name of the stopped WebSphere Commerce Payments whose pending
- CEPFW0763:
- Explanation: The BECOME command was entered on the operator console, but no target name
Action: Re-enter the command with the name of the host whose pending WebSphere Commerce Payments transactions
- CEPFW0764:
- Explanation: The cassette did not process the API request successfully. An API response
Action: Contact the service group for this cassette for resolution.
- CEPFW0765:
- Explanation: An API request was received without a dtdPath parameter. In response, WebSphere Commerce Payments attempted
Action: Correct the WebSphere Application Server classpath so that it includes WebSphere Commerce Payments DTD
- CEPFW0766:
- Explanation: An API request was received without a dtdPath parameter. In response WebSphere Commerce Payments attempted
Action: Correct WebSphere Commerce Payments DTD file. Otherwise, contact your IBM support representative.
- CEPFW0810:
- Explanation: Unable to encrypt/decrypt the encryption key. The CEPFW0711 error message
Action: Make sure that the root password is correct. Otherwise, contact IBM service.
- CEPFW0811:
- Explanation: The encryption key type requested is not support.
Action: Only request supported encryption key.
- CEPFW0812:
- Explanation: Unable to generate the encryption/decryption key. The CEPFW0711 error message
Action: Contact IBM service.
- CEPFW0813:
- Explanation: The eTill.RealmClass setting in the PaymentServlet init parameters identifies
Action: Set eTill.RealmTraceFlag=1 in the PaymentServlet init parameters to enable
- CEPFW0814:
- Explanation: Unable to encrypt data such as the Registration Form, the Registration
Action: Contact your IBM support representative.
- CEPFW0815:
- Explanation: Unable to decrypt data such as the Registration Form, the Registration
Action: Contact your IBM support representative.
- CEPFW0816:
- Explanation: WebSphere Commerce Payments is configured to use a realm for which there is no associated realm
Action: If WebSphere Commerce Payments will not start due to a realm error, check that there is a file
- CEPFW0817:
- Explanation: WebSphere Commerce Payments requires an instance password to encrypt sensitive data on the
Action: Enter the correct WebSphere Commerce Payments instance password.
- CEPFW0818:
- Explanation: WebSphere Commerce Payments requires an instance password to encrypt sensitive data on the
Action: Enter the correct WebSphere Commerce Payments instance password.
- CEPFW0819:
- Explanation: The IBMPayServer and StopIBMPayServer programs use CAL to communicate with WebSphere Commerce Payments Application
Action: Check that WebSphere Application Server is running and use the Administrator''s
- CEPFW0821:
- Explanation: WebSphere Commerce Payments start up processing did not complete successfully.
Action: Look in the Programmer''s Guide to determine the explanation for the combination
- CEPFW0822:
- Explanation: WebSphere Commerce Payments stop processing did not complete successfully.
Action: Look in the {0} to determine the explanation for the combination of primary and secondary
- CEPFW0823:
- Explanation: The password change request was successfully processed.
Action: None
- CEPFW0826:
- Explanation: An error occurred while attempting to decrypt the encryption key. The Payments
Action: Ensure that the Payments instance password is correct. Otherwise, contact
- CEPFW0830:
- Explanation: You tried to perform a command that relies on WebSphere Commerce Payments being started. However, WebSphere Commerce Payments has
Action: Use the IBMPayServer command to start WebSphere Commerce Payments and enter the Payments instance
- CEPFW0832:
- Explanation: An attempt was made to change the message or trace configuration of the
Action: Use the WebSphere Application Server Administrator''s Console to manage
- CEPOfflineCard1000:
- Explanation: The Cassette is now accepting requests.
Action: None
- CEPOfflineCard1001:
- Explanation: The Cassette is no longer accepting requests.
Action: None
- CEPOfflineCard1002:
- Explanation: Check with development as to the availability of this method if you have
Action: Contact your IBM support representative.
- CEPOfflineCard1003:
- Explanation: None
Action: Check with your developer for possible reasons as to why this happened.
- CEPOfflineCard2000:
- Explanation: An SQL exception occurred while accessing the OFFLINECARDACCOUNT table.
Action: Check the connection to the database to make sure that there is not a problem
- CEPOfflineCard2001:
- Explanation: An SQL exception occurred while closing OFFLINECARDACCOUNT table. The SQL
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard2003:
- Explanation: This insertion is only supposed to insert one row, but more than one row
Action: Contact your IBM support representative.
- CEPOfflineCard2004:
- Explanation: An SQL exception occurred while inserting a row into the OFFLINECARDACCOUNT
Action: Check the connection to the database to make sure that there is not a problem
- CEPOfflineCard2005:
- Explanation: The update should have changed only one row but more than one row were
Action: Contact your IBM support representative.
- CEPOfflineCard2006:
- Explanation: SQL exception occurred while reading a WebSphere Commerce Payments database table. The SQL exception
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard2007:
- Explanation: The deletion is only supposed to delete one row, but more than one row
Action: Contact your IBM support representative.
- CEPOfflineCard2008:
- Explanation: An SQL exception occurred while inserting a row into the OFFLINECARDACCOUNT
Action: Check the connection to the database to make sure that there is not a problem
- CEPOfflineCard2009:
- Explanation: The socket connection that performs the communication between the cassette
Action: If the problem persists, contact your IBM support representative.
- CEPOfflineCard2010:
- Explanation: The transaction used in the request is not a valid one. This is not expected
Action: Contact your IBM support representative.
- CEPOfflineCard3000:
- Explanation: An SQL query of OFFLINECARDBATCH table should have returned only one row
Action: Contact your IBM support representative.
- CEPOfflineCard3001:
- Explanation: An SQL query of OFFLINECARDBATCH table should have returned only one row
Action: Contact your IBM support representative.
- CEPOfflineCard3002:
- Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard3003:
- Explanation: An SQL exception occurred while closing the OFFLINECARDBATCH table query.
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard3004:
- Explanation: This insertion is only supposed to insert one row, but more than one row
Action: Contact your IBM support representative.
- CEPOfflineCard3005:
- Explanation: SQL exception occurred while inserting into the OFFLINECARDBATCH table.
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard3006:
- Explanation: The update is only supposed to affect one row, but more than one row was
Action: Contact your IBM support representative.
- CEPOfflineCard3007:
- Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard3008:
- Explanation: An SQL delete of OFFLINECARDBATCH table should have returned only one row
Action: Contact your IBM support representative.
- CEPOfflineCard3009:
- Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard3010:
- Explanation: This is really a sanity check in the processing of request. A user may
Action: Contact your IBM support representative.
- CEPOfflineCard3011:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: Contact your IBM support representative.
- CEPOfflineCard3012:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3013:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3014:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3015:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3016:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3017:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3018:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard3019:
- Explanation: This is an internal test to assure that further processing does not fail.
Action: None
- CEPOfflineCard4000:
- Explanation: An SQL query of the OFFLINECARDORDER table should have returned only one
Action: Contact your IBM support representative.
- CEPOfflineCard4001:
- Explanation: An SQL query of the OFFLINECARDORDER table should have returned one row
Action: Contact your IBM support representative.
- CEPOfflineCard4002:
- Explanation: An SQL exception occurred while querying the OFFLINECARDORDER table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard4003:
- Explanation: An SQL exception occurred while closing the OFFLINECARDORDER table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard4004:
- Explanation: An SQL insertion into the OFFLINECARDORDER table should have inserted one
Action: Contact your IBM support representative.
- CEPOfflineCard4005:
- Explanation: An SQL exception occurred while inserting into the OFFLINECARDORDER table.
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard4006:
- Explanation: An SQL update of the OFFLINECARDORDER table should have updated one row
Action: Contact your IBM support representative.
- CEPOfflineCard4007:
- Explanation: An SQL exception occurred while updating the OFFLINECARDORDER table. The
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard4008:
- Explanation: An SQL delete of the OFFLINECARDORDER table should have deleted one row
Action: Contact your IBM support representative.
- CEPOfflineCard4009:
- Explanation: An SQL exception occurred while deleting an order from the OFFLINECARDORDER
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard4010:
- Explanation: While closing a batch, it was discovered that the batch contained a payment
Action: Contact your IBM support representative.
- CEPOfflineCard4011:
- Explanation: While closing a batch, it was discovered that the batch contained a credit
Action: Contact your IBM support representative.
- CEPOfflineCard5000:
- Explanation: While querying for a payment, it returned multiple entries. This condition
Action: Contact your IBM support representative.
- CEPOfflineCard5001:
- Explanation: While querying for a payment that should have returned one row, nothing
Action: Report the problem to your IBM support representative.
- CEPOfflineCard5002:
- Explanation: An SQL exception occurred while querying from the OFFLINECARDPAYMENT table.
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard5003:
- Explanation: An SQL exception occurred while closing from the OFFLINECARDPAYMENT table
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard5004:
- Explanation: An SQL insertion into the OFFLINECARDPAYMENT table should have inserted
Action: Contact your IBM support representative.
- CEPOfflineCard5005:
- Explanation: An SQL exception occurred while inserting a new payment into from the
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard5006:
- Explanation: While updating a payment that should have affected one row, multiple rows
Action: Contact your IBM support representative.
- CEPOfflineCard5007:
- Explanation: An SQL exception occurred while updating the OFFLINECARDPAYMENT table.
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard5008:
- Explanation: While deleting a payment that should have affected one row, multiple rows
Action: Contact your IBM support representative.
- CEPOfflineCard5009:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard5010:
- Explanation: While closing a batch, it was discovered that the batch contained a payment
Action: Change the payment state and close the batch again.
- CEPOfflineCard6000:
- Explanation: While querying the OFFLINECARDCREDIT table, it was supposed to return one
Action: Contact your IBM support representative.
- CEPOfflineCard6001:
- Explanation: While querying the OFFLINECARDCREDIT table, it should have returned one
Action: Contact your IBM support representative.
- CEPOfflineCard6002:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6003:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6004:
- Explanation: While querying the OFFLINECARDCREDIT table, it should have returned one
Action: Contact your IBM support representative.
- CEPOfflineCard6005:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6006:
- Explanation: While updating the OFFLINECARDCREDIT table, it should have updated one
Action: Contact your IBM support representative.
- CEPOfflineCard6007:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6008:
- Explanation: While deleting a row from the OFFLINECARDCREDIT table, it should have
Action: Contact your IBM support representative.
- CEPOfflineCard6009:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6010:
- Explanation: While closing a batch, it was discovered that the batch contained a credit
Action: Change the credit state and close the batch again.
- CEPOfflineCard6100:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6101:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6102:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard6103:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard7000:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard7001:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard7002:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard7003:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPOfflineCard7004:
- Explanation: The SQL exception text describes the exception and provides SQL state information
Action: Refer to the SQL state information to get specific details about the nature
- CEPPaymentech0606:
- Explanation: An internal error occurred in the cassette. The exception text will help
Action: If some required operation or service is not functioning properly, contact
- CEPPaymentech1001:
- Explanation: This is an internal cassette error.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech1002:
- Explanation: The Paymentech Cassette has started and is ready to accept commands.
Action: None
- CEPPaymentech1003:
- Explanation: The Paymentech Cassette is no longer active.
Action: None
- CEPPaymentech2000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech2001:
- Explanation: The specified merchant already has an account defined. Each merchant can have
Action: Try to create the account again but specify a different merchant number, or
- CEPPaymentech2002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech2003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech2004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech2005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech2006:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPPaymentech2007:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPPaymentech2008:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPPaymentech2009:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPPaymentech2010:
- Explanation: A bad return code ("QD") was returned in the batch settlement response.
Action: Contact the Paymentech host representative to determine why the batch already exists.
- CEPPaymentech2011:
- Explanation: The specified merchant already has a division for the specified division
Action: Try the request again, but specify a division number that
- CEPPaymentech2012:
- Explanation: The specified merchant already has a division defined for the specified currency
Action: Re-attempt the request, specifying a currency code that
- CEPPaymentech3000:
- Explanation: The specified batch for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the specified batch exists for the specified merchant.
- CEPPaymentech3001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech3002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech3003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech3004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech3005:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3007:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3008:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3009:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3010:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3011:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3012:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3013:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3014:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3015:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3016:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3017:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3018:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3019:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3020:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3021:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech3022:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech4000:
- Explanation: The specified order for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the order exists for the merchant.
- CEPPaymentech4001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech4002:
- Explanation: An SQL exception occurred while attempting to close a SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech4003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech4004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech4005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech4006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech4007:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech5000:
- Explanation: The specified payment was not found in the WebSphere Commerce Payments database.
Action: Ensure that the payment exists for the merchant and
- CEPPaymentech5001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech5002:
- Explanation: An SQL exception occurred while attempting to close a SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech5003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech5004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech5005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech5006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech5007:
- Explanation: The RFR response returned from Paymentech indicated that an error occurred
Action: Contact your Paymentech representative to determine why the deposit was
- CEPPaymentech6000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech6001:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech6002:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech6003:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech6004:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM support representative.
- CEPPaymentech6005:
- Explanation: The specified credit was not found in the WebSphere Commerce Payments database.
Action: Ensure that the specified credit exists for the specified merchant and
- CEPPaymentech6006:
- Explanation: The Request For Response (RFR) response returned from Paymentech indicated that an error occurred
Action: Contact your Paymentech representative to determine why the refund was
- CEPPaymentech7000:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7001:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7002:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7003:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7004:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7005:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech7006:
- Explanation: An SQL exception occurred while processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech8000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech8001:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech9000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech9001:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech9002:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech9003:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPPaymentech9005:
- Explanation: Unable to encrypt/decrypt the PAN or expiration date.
Action: Contact your service representative.
- CEPVisaNet0606:
- Explanation: An internal error occurred in the cassette. The exception text will help
Action: If some required operation or service is not functioning properly, contact
- CEPVisaNet1001:
- Explanation: This is an internal cassette error.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet1002:
- Explanation: The VisaNet Cassette has started and is ready to accept commands.
Action: None
- CEPVisaNet1003:
- Explanation: The VisaNet Cassette is no longer active.
Action: None
- CEPVisaNet2000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet2001:
- Explanation: The specified merchant already has an account for the specified account
Action: Re-attempt the CreateAccount request, specifying an account number that
- CEPVisaNet2002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet2003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet2004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet2005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet2006:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPVisaNet2007:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPVisaNet2008:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPVisaNet2009:
- Explanation: A bad return code ("RB") was returned in the batch settlement response.
Action: Use the information provided in the message to try to do batch reconciliation.
- CEPVisaNet2010:
- Explanation: A bad return code ("QD") was returned in the batch settlement response.
Action: Contact the VisaNet host representative to determine why the batch already exists.
- CEPVisaNet2011:
- Explanation: The card used in the transaction is not a commercial card. The purchase card data associated with the payment has been ignored.
Action: Contact cardholder to ensure that future transactions are made with a valid commercial card.
- CEPVisaNet2012:
- Explanation: The specified merchant already has an account for the specified Store Number and
Action: Re-attempt the CreateAccount request, specifying an account that
- CEPVisaNet3000:
- Explanation: The specified batch for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the specified batch exists for the specified merchant.
- CEPVisaNet3001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet3002:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet3003:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet3004:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet3005:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3007:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3008:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3009:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3010:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3011:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3012:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3013:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet3014:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet4000:
- Explanation: The specified order for the specified merchant was not found in the WebSphere Commerce Payments
Action: Ensure that the specified order exists for the specified merchant.
- CEPVisaNet4001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet4002:
- Explanation: An SQL exception occurred while attempting to close a SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet4003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet4004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet4005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet4006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet4007:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet5000:
- Explanation: The specified payment was not found in the WebSphere Commerce Payments database.
Action: Ensure that the specified payment exists for the specified merchant and
- CEPVisaNet5001:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet5002:
- Explanation: An SQL exception occurred while attempting to close a SQL SELECT statement.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet5003:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet5004:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet5005:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet5006:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet6000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet6001:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet6002:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet6003:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet6004:
- Explanation: This is an internal error in the cassette.
Action: If the problem persists, contact your IBM service representative.
- CEPVisaNet6005:
- Explanation: The specified credit was not found in the WebSphere Commerce Payments database.
Action: Ensure that the specified credit exists for the specified merchant and
- CEPVisaNet7000:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7001:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7002:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7003:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7004:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7005:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet7006:
- Explanation: An SQL exception occurred processing a result set that was obtained by
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet8000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet8001:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet9000:
- Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet9001:
- Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet9002:
- Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet9003:
- Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database.
Action: Check the connection to the database to make sure that there is not a problem
- CEPVisaNet9005:
- Explanation: Unable to encrypt/decrypt the PAN or expiration date.
Action: Contact your service representative.
- CMN0001E: The database returned the following error code: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: If any exception, other than some type of ECException, is raised while DeleteAuctionTaskCmdImpl is calling the task command GenericInventoryAdjustCmd then this message is raised along with an ECSystemException.
The error code value contains details of the originally raised exception.Action: View the error code information, correct any problems, and rerun the command.
- CMN0009S: Component {0} is enabled.
- Explanation: This is a status message to indicate the component is enabled.
Action: No action required.
- CMN0010S: Component {0} is disabled.
- Explanation: This is a status message to indicate the component is disabled.
Action: No action required.
- CMN0103E: Could not obtain the key from the registry. CMN3101E The system is unavailable due to {0}.
- Explanation: The key could not be obtained from the registry, because the registry could be empty or it has not been initialized.
Action: Ensure the registry was initialized and contains the valid entries. During the servlet startup, restart the instance and try again. If the error occurred during refresh registry, retry to refresh the registry identified by the class name.
- CMN0108E: Could not locate the command because the command registry has not been initialized. CMN3101E The system is unavailable due to {0}.
- Explanation: The command registry was not initialized successfully. The instance cannot be started.
Action: Review the WebSphere Commerce log file to check if there was an error during the servlet initialization. If an error is found, fix the servlet startup error and then retry.
- CMN0109E: Could not locate the view because the view registry has not been initialized. CMN3101E The system is unavailable due to {0}.
- Explanation: The view registry was not initialized successfully. The instance cannot be started.
Action: Review the WebSphere Commerce log file to check if there was an error during the servlet initialization. If an error is found, fix the servlet startup error and then retry.
- CMN0111E: Server cannot instantiate command {0} for view task {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command factory cannot instantiate the view command. The command class name or the view name is incorrect.
Action: Ensure the command class name is valid and the view exists in the view registry. Review the WebSphere Commerce log to make sure the servlet starts successfully.
- CMN0113E: License check failed. {0}. License check failed. {0}.
- Explanation: The license check fails during the servlet initialization. This a warning message and indicates the need for a proper license to run WebSphere Commerce.
Action: Ensure the license is valid. Check for the existence of the certificate and nodelock files in the license\lum directory.
- CMN0114E: License check failed. There are not enough store licenses. The server is configured for {0} store(s) but {1} stores are defined. License check failed. There are not enough store licenses. The server is configured for {0} store(s) but {1} stores are defined.
- Explanation: The number of stores trying to initialize is greater than the number of store licenses for the server.
Action: Check the number of stores defined when the instance was created and ensure it is not more than the maximum number of stores in the server.
- CMN0114W: License check failed. There are not enough store licenses. The server is configured for {0} store(s) but {1} stores are defined. License check failed. There are not enough store licenses. The server is configured for {0} store(s) but {1} stores are defined.
- Explanation: The number of stores trying to initialize is greater than the number of store licenses for the server.
Action: Check the number of stores defined when the instance was created and ensure it is not more than the maximum number of stores in the server.
- CMN0205E: Command {0} failed to verify mandatory input parameters. CMN3101E The system is unavailable due to {0}.
- Explanation: The command failed to verify the mandatory input parameters. Some mandatory parameter(s) is/are missing.
Action: Provide all the mandatory input parameters to the command according to the product documentation and re-execute it.
- CMN0208E: Command {0} failed to process. Error: {1} CMN3101E The system is unavailable due to {0}.
- Explanation: Exception occurred when the command was executed.
Action: Fix the problem according to the exception information as shown.
- CMN0211E: The URL command, {0}, failed. CMN3101E The system is unavailable due to {0}.
- Explanation: The current command tried to invoke another task command, but the command factory failed to create an instance of that command. Another possibility is that an exception has been thrown while accessing a method of the task command.
Action: Check to ensure the task command in which the current command is trying to invoke, has been registered in CMDREG, and the name matches the one used by the command factory. Also, ensure that the task command does not encounter any exceptions during its execution.
- CMN0215E: The Environment variable ''{0}'' is missing. CMN3101E The system is unavailable due to {0}.
- Explanation: The cashier extension function expects the environment variable in the list of input parameters.
Action: Ensure that the payment command sets the appropriate environment variable before calling the cashier function. If the payment command does not expect the cashier extension function to be called, review the cashier profile to ensure that there are no ExtensionValue elements in any of the Parameter elements. Update the cashier profile if necessary, and retry the command.
- CMN0301S: Checking Order inventory.
- Explanation: The command is about to call the appropriate inventory task command. If ATP inventory is enabled (STORE.QUOTEGOODFOR is not zero), then the AllocateInventory task command is about to be called. Otherwise, the ResolveFulfillmentCenter task command is about to be called.
Action: No action required.
- CMN0302S: Updating OrderItem prices.
- Explanation: The command is about to obtain current prices for the OrderItem objects in the Order (unless their PREPAREFLAGS column specifies the PriceOverride bit flag).
Action: No action required.
- CMN0303S: Updating OrderItem Addresses.
- Explanation: The command is about to obtain current address objects for the shipping addresses for the OrderItem objects in the Order. If the user has changed the shipping address information, the OrderItem objects will be changed to refer to the changed shipping address information, located via the NICKNAME column of the ADDRESS table.
Action: No action required.
- CMN0306S: Calculating Order totals.
- Explanation: The command is about to update SubOrder objects in the SUBORDERS table, calculate the TOTALPRODUCT column value in the ORDERS table, and call the SummarizeCalculationUsage calculation methods (for example, to update the TOTALSHIPPING, TOTALTAX, and TOTALTAXSHIPPING columns of the ORDERS table).
Action: No action required.
- CMN0401E: A thread failed to start: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: This message is logged when an error occurs while attempting to dispatch a thread in the scheduler. The substitution text displays why the problem occurred.
Action: View the substitution text, correct any problems, and rerun the command.
- CMN0402E: Store Services cannot open the following file {0}. Ensure that the file exists and has the appropriate file permissions. CMN3101E The system is unavailable due to {0}.
- Explanation: When Store Services attempted to open the specified file, a general exception produced by failed I/O operations occurred.
This exception occurred because the file does not exist or it is inaccessible. The file may be inaccessible if it is read-only, and Store Services attempted to open it in order to write to it.Action: 1. Ensure the file exists. 2. Ensure the file has the appropriate file permissions. 3. Review the WebSphere Commerce log files. The location of the log files is specified in the Configuration Manager.
- CMN0423E: Unable to format the message: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified arguments are not valid. The error may be caused by missing arguments or arguments that are not of the right class for the specified format.
Action: Check if there is any missing arguments and the object types of the arguments are correct.
- CMN0499E: An error occurred when the system tried to create the log file {0}. Review the WebSphere Commerce log for more details. CMN3101E The system is unavailable due to {0}.
- Explanation: The log file cannot be created due to system error. As a result, the log file is not generated.
Action: Review the WebSphere Commerce log for more details.
- CMN0518E: The merchant key is corrupted; please re-encrypt the key and reset your merchant key. CMN3101E The system is unavailable due to {0}.
- Explanation: Server could not initialize the merchant key for encryption.
Action: Ensure the merchant key is valid. Re-encrypt the merchant key and reset the key.
- CMN0521E: The request cannot be processed because it contains prohibited attribute names. CMN3101E The system is unavailable due to {0}.
- Explanation: One or more attribute names in the request are prohibited. The prohibited attributes have been specified in the configuration.
Action: Ensure the attribute name that are currently prohibited are not regularly used attribute names.
- CMN0522E: The request cannot be processed because it contains prohibited characters. CMN3101E The system is unavailable due to {0}.
- Explanation: One or more attribute values in the request are prohibited. The prohibited characters in the attribute values have been specified in the configuration.
Action: Ensure the characters in attribute values that are currently prohibited are not regularly used attribute values.
- CMN0525E: UserTraffic error: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: This error message indicates that either the AccessLogginEventListener or UserTrafficEventListener event listeners were not able to write cached data into their respective tables due to an exception thrown from an access bean.
Action: 1. Ensure that the WebSphere Commerce database is configured and working correctly. Retrace your steps on installing and setting up the database carefully.
2. Examine the WebSphere Commerce log files that are located in the logs subdirectory. If there is a different database or access bean exception thrown within the same transaction or request that puts the database in rollback state, this error message is simply a result of the previous exception. - CMN0601E: CMN3101E The system is unavailable due to {0}.
- Explanation: This message is for reference purposes only when there is a problem closing the directory's context. The purpose of closing the context is to release this context's resources immediately, instead of waiting for them to be released automatically by the garbage collector later on.
Action: No action required.
- CMN0602E: CMN3101E The system is unavailable due to {0}.
- Explanation: To plug in the directory, you must provide the appropriate settings for the directory environment. When the properties provided are invalid or insufficient, the context can not be initialized. Sometimes, this is caused by connection problems.
Action: 1. Check that the directory server is running and that the conneciton is on.
2. Check the directory environment properties, such as the directory URL, directory type (SecureWay, Domino, ActiveDirectory or others), authentication credentials and principal, service provider interface (SPIs), and access object class. - CMN0603E: The directory configuratoin data can not be loaded because the configuration information is invalid or insufficient. Specicifally, the system found the following problem: {0}.
- Explanation: The directory configuratoin data can not be loaded because the configuration information is invalid or insufficient. To plug in the directory, the specified directory configuration data must be loaded into the application. If the provided directory information is invalid or insufficient, the directory server can not be initialized.
Action: Check the following paramters in the directory configuration properties settings: 1. The directory configuration file exists and it is not empty. 2. The directory URL is provided and correct. 3. The directory type is indicated. For example, IBM Directory Server (SecureWay). 4. The directory authentication credentials and principal are provided. 5. The acess object class of the directory is correct. 6. The directory service provider interface (SPIs) is provided.
- CMN0604E:
- Explanation: An authentication error ocurred because the credentials you supplied are invalid or failed to authenticate the user to the directory service.
Action: Re-attempt the authentication by updating the resolved context's environment properties with the appropriate credentials.
- CMN0605E: An error occurred while retrieving attributes from the directory: {0}
- Explanation: This error occurs when retrieving the directory object along with all the attributes.
Action: 1. Check that the directory server is running and that the conneciton is on.
2. Check if the directory object exists. - CMN0606E: An error occurred while retrieving the object from the directory: {0}
- Explanation: This error occurs when the directory server looks up the required directory object for a specified directory object.
Action: 1. Check that the directory server is running and that the conneciton is on.
2. Check if the directory object exists. - CMN0608E: An error occurred while creating the object in the directory: {0}
- Explanation: This error occurs while creating and binding a user on a directory server with one or more invalid or insufficient attribute values.
Action: Check the user attributes to see if mandatory attributes are missing or ensure that the specified input attribute values are valid.
- CMN0611E: An error occurred while modifying attributes in directory: {0}
- Explanation: This error occurs when modifying attribute values in a directory or when updating the directory attribute. The directory attributes should be in sync with the database attributes.
Action: 1. Make sure the attribute exists.
2. Check if the values to be modified to meet the defined attribute definition (such as, data type of the attribute, value length, read only, or support for multiple values). - CMN0612E: An error occurred while updating data to the directory: {0}
- Explanation: This error occurs while synchonizing the mapping between the directory server objects with specified application component objects. In WebSphere Commerce application, the component name is called "UserSubsystem".
Action: Check the configuration settings to ensure that the "UserSubsystem" component name is used to identify the user subsystem component within WebSphere Commerce, and to ensure that the component is enabled.
- CMN0613E: An error occurred while synchronizing data to the database because the following method is missing: {0}.
- Explanation: This error occurs while synchronizing the directory data to the database. The class or the method called is invalid.
Action: Check the application class path to ensure that the class or the class with the calling method are in the path.
- CMN0615E: The X509 Client Certificate is invalid.
- Explanation: The X509 certificate is invalid for the user. The HTTP session cannot proceed with the wrong X509 client certificate.
Action: Ensure the logon ID belongs to a valid X509 user.
- CMN0924E: Login from this user device is not allowed. CMN3101E The system is unavailable due to {0}.
- Explanation: The user is not registered to use the PvC device to log onto WebSphere Commerce.
Action: Create an entry in the USERPVCDEV table, mapping the user to the PvC device format ID.
- CMN1003E: The command failed to execute due to a missing parameter. CMN3101E The system is unavailable due to {0}.
- Explanation: One or more of the command's mandatory parameters was not supplied.
Action: View the Command Reference in the online help to determine the mandatory set of parameters that must be supplied to this command.
- CMN1004S: The interest item list {0} does not exist for customer {1}.
- Explanation: The specified interest item list does not exist for the given user.
Action: Ensure that the interest item list reference number parameter of the command refers to a valid interest item list for the user.
- CMN1009E: The command was unable to retrieve the SKU number from the environment. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not resolve the supplied attibute value parameters to a unique SKU.
Action: Modify the attribute value parameters to represent an existing SKU. Use the WebSphere Commerce Accelerator to view and modify the attribute values assigned to a SKU.
- CMN1009S: Order {0} is stale, according to STORE.QUOTEGOODFOR. Repreparing the Order and recalculating the Order totals.
- Explanation: The command has determined that too much time has passed since the Order was most recently prepared, and is about to reprepare the Order by calling the PrepareOrder task command.
The task command is responsible for obtaining current prices and re-calculating calculation usage amounts such as discounts, shipping charges, and taxes.Action: No action required.
- CMN1011S: Invoking stored procedure {0}.
- Explanation: The specified stored procedure is about to be invoked.
Action: No action required.
- CMN1012S: Exiting stored procedure {0}.
- Explanation: The specified stored procedure has returned.
Action: No action required.
- CMN1013E: The command is unable to load the current Address object for the Address object with AddressId {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Users identify their Addresses by unique nicknames. When a user modifies an Address, a new Address object is created with the same nickname. The previous version remains in the database. That way, previously submitted Orders that reference the Address with that nickname actually reference the previous Address version, the version that was current when the Order was submitted. The status attribute value for a previous version of an Address object is 'T'.
Commands that work with Orders not yet submitted ("shopcarts") need to make sure that the Addresses they refer to are the most recent ("current") version. The status attribute value for a current version of an Address object is 'P'.
This error message was issued because a command was unable to locate the most recent version of the specified Address object.
Action: Check the ADDRESS table to see if there is an Address object with the specified addressId attribute in the ADDRESS_ID column. If its status attribute in the STATUS column is not 'P', then check to see if there is another Address object with the same nickname and memberId attributes with a status attribute value of 'P'.
- CMN1013S: Allocating inventory for the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is attempting to allocate inventory for the specified OrderItems.
Action: No action required.
- CMN1014S: Backordering the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is attempting to backorder inventory for the specified OrderItem objects, by calling the AllocateExpectedInventory task command for each OrderItem.
Action: No action required.
- CMN1015S: Reversing inventory allocations for the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is about to reverse (de-allocate) inventory allocations or backorders for the specified OrderItem objects.
Allocated inventory is reversed by calling the DeallocateExistingInventory task command. Backorders are reversed by calling the DeallocateExpectedInventory task command.Action: No action required.
- CMN1016S: Merging the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is merging the specified OrderItem objects.
Action: No action required.
- CMN1017S: Remerging the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is re-merging the specified OrderItem objects.
OrderItem objects can be re-merged only if they all originated from the same OrderItem (have the same value in the CORRELATIONGROUP column of the ORDERITEMS table), which was split during inventory allocation, due to insufficient inventory at one or more fulfillment centers.Action: No action required.
- CMN1018S: Checking inventory availability for the following OrderItems: {0}.
- Explanation: The AllocateInventory task command is abut to call the CheckInventoryAvailability task command for the specified OrderItem objects.
Action: No action required.
- CMN1019S: Can not allocate inventory for order item {0} since its inventory status is {1}.
- Explanation: The task command is not attempting to allocate inventory for the specified OrderItem, since its inventoryStatus attribute (column INVENTORYSTATUS in the ORDERITEMS table) has the specified value, which indicates that the inventory allocation for the OrderItem should not be changed.
Action: No action required.
- CMN1022E: Order {0} is not locked, but it should be locked. CMN3101E The system is unavailable due to {0}.
- Explanation: The command will not process an unlocked Order. The Order has been changed or unlocked since it was most recently prepared.
Action: To lock an Order, prepare it using the OrderPrepare command.
- CMN1023S: Allocated inventory in the quantity of {0} for order item {1} from fulfillment center {2}.
- Explanation: The AllocateExistingInventory task command successfully allocated inventory as specified.
The specified OrderItem object indicates a specified item in the ITEMSPC table, and the specified item indicates a base item in the BASEITEM table. The quantity allocated is indicated in integer units; each unit represents a quantity as specified by the QUANTITYMULTIPLE and QUANTITYMEASURE columns of the BASEITEM table.Action: No action required.
- CMN1024S: Referral interface policy for trading agreement {0} and user {1} does not allow processing backorders.
- Explanation: The specified referral interface policy for the specified trading agreement does not allow such an OrderItem to be processed if its quantity attribute value exceeds its availableQuantity attribute value.
Action: No action required.
- CMN1030E: The command was unable to display category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The category is not in the published state for the given language.
Action: Ensure that the category is in the published state for the given language by using the Commerce Accelerator to view the category's properties. Alternatively, check that the PUBLISHED column in the CATGRPDESC table is set to 1 for the category in the given language.
- CMN1031E: The command was unable to view category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: A JSP template does not exist for the specified category.
Action: Ensure that there is a JSP template registered in the DISPCGPREL table for the specified category, current store, and current language.
- CMN1033E: Product {0} is not published. CMN3101E The system is unavailable due to {0}.
- Explanation: The catalog entry is marked "not-published" in the database for the given language.
Action: Use the WebSphere Commerce Accelerator to mark the catalog entry as published. Alternatively, set the PUBLISHED field to "1" in the CATENTDESC table for the catalog entry in the given language.
- CMN1034E: Product {0} is not viewable. CMN3101E The system is unavailable due to {0}.
- Explanation: The catalog entry is marked "not-published" in the database for the given language.
Action: Use the WebSphere Commerce Accelerator to mark the catalog entry as published. Alternatively, set the PUBLISHED field to "1" in the CATENTDESC table for the catalog entry in the given language.
- CMN1038E: Server can not create cookie. Please ensure that your browser accepts cookies. CMN3101E The system is unavailable due to {0}.
- Explanation: Web controller cannot find the acceptance cookie.
Action: No action required.
- CMN1039E: An invalid cookie was received for the user, your logonId may be in use by another user. CMN3101E The system is unavailable due to {0}.
- Explanation: The cookie has not been received by the server or it has been tampered with, or the user id is being used by another user.
Action: Ensure the cookie is being received by the server and the user is using the correct logonId. Also check if there are any logon violations.
- CMN1044E: An error occurred while deleting a SubOrder object. CMN3101E The system is unavailable due to {0}.
- Explanation: A system error occurred while attempting to remove a SubOrder enterprise bean object.
Action: Look in the Websphere Commerce error log for other error messages that may indicate why the error occurred.
- CMN1048E: The command is unable to find any Order objects on which to operate. CMN3101E The system is unavailable due to {0}.
- Explanation: The parameters passed to the command did not identify any Orders.
This could happen, for example, if the command was passed the "*" order abbreviation, but there were no Order objects for the current user with a status attribute value of "P". The command returned the OrderNoneErrorView.Action: No action required.
- CMN1057E: Failure finding the e-mail address for user: {0} CMN3101E The system is unavailable due to {0}.
- Explanation: The e-mail address for the specified user was not found.
Action: Either modify the user's e-mail address to the correct address or change the e-mail address being searched for.
- CMN1059E: An unknown exception {0} has been generated by the notification system. CMN3101E The system is unavailable due to {0}.
- Explanation: If an Exception is raised in AuctionNotificationCmdImpl, this message is raised along with an ECSystemException. The details of the unknown exception is included in the substitution text.
There are the following cases in which this may occur:
1) while invoking the NotifyStartAuctionCmd task command
2) while invoking the NotifyCompleteOrderCmd task command for a particular bid
3) while invoking the NotifyCloseAuctionCmd task command
Action: View the substitution text, correct any problems, and rerun the command.
- CMN1062E: Messaging system failed to send a notification message in the class indicated above. CMN3101E The system is unavailable due to {0}.
- Explanation: The messaging system is not able to send a notification message (usually an email) invoked by the command as shown. Some connection or interaction specification attributes used to send the message may not be correctly configured.
Action: Identify the failure command and the corresponding MSGTYPE_ID and make sure the message type has been properly assigned to the correct transport, and that the corresponding mandatory attributes have been set. For example, when sending an e-mail, the sender address must be a valid email address.
- CMN1087E: The currency attribute of the command is not set. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the currency command parameter. The command is unable to proceed.
Action: Verify and correct the DTD file corresponding to the command ensuring it contains a mandatory currency element.
- CMN1088E: The shopper reference number attribute of the command was not set. CMN3101E The system is unavailable due to {0}.
- Explanation: The WebSphere Commerce runtime did not set the user ID in the command context.
Action: Contact your IBM support representative.
- CMN1111E: The mandatory totalAmount command parameter was not set by the setTotalAmount() method or is null. CMN3101E The system is unavailable due to {0}.
- Explanation: The DoPayment task command expects the mandatory totalAmount command parameter to be set by the setTotalAmount() method before the execute() method is called. The totalAmount command parameter was not set or is null.
Action: Ensure that the command that calls the DoPayment task command is correctly setting the totalAmount parameter before calling the execute() method.
- CMN1112E: An error occurred while creating the payment method record for order {0}. Order processing failed. CMN3101E The system is unavailable due to {0}.
- Explanation: A javax.ejb.CreateException error occurred while creating an ORDPAYMETHOD record for the order.
Action: Check the WebSphere Application Server EJB error log to find the source of the problem.
- CMN1117E: No order item can be found for ORDERS_ID {0} in table ORDERITEMS. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified order item does not have any corresponding records in the ORDERITEMS table. An incorrect orders_ID argument may have been specified. The message cannot be sent.
Action: Check to ensure the correct orders_ID is specified in the calling command.
- CMN1118E: The command requires an order list attribute. CMN3101E The system is unavailable due to {0}.
- Explanation: The called command requires a list of orders.
Action: Check your invocation of this command. Make sure a list of orders in the correct format is supplied.
- CMN1122E: The command failed due to a missing category number. CMN3101E The system is unavailable due to {0}.
- Explanation: The command requires a category reference number.
Action: Run the command again with the appropriate category reference number.
- CMN1123E: The parameter URL is mandatory, but has not been specified. CMN3101E The system is unavailable due to {0}.
- Explanation: The parameter URL is mandatory, but has not been specified.
Action: Make sure you specify the parameter URL when you call the command.
- CMN1125E: The mandatory paymentAttributes command parameter was not set by the setPaymentAttributes() method or is null. CMN3101E The system is unavailable due to {0}.
- Explanation: The DoPayment task command expects the mandatory paymentAttributes command parameter to be set by the setPaymentAttributes() method before the execute() method is called. The paymentAttributes command parameter was not set or is null.
Action: Ensure that the command that calls the DoPayment task command is correctly setting the paymentAttributes parameter before calling the execute() method.
- CMN1128E: The command failed due to a missing catalog reference number. CMN3101E The system is unavailable due to {0}.
- Explanation: The command requires a catalog reference number.
Action: Run the command again with the appropriate catalog reference number.
- CMN1131E: The root node name {0} is invalid. The following root node names are supported: {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command encountered an invalid root node name while parsing an input XML string.
Action: Determine which command was executing, and the XML string that was passed to it as input. Examine the XML string in error, and determine how it was produced. Fix the program that produced it so that it produces one of the specified valid root names.
- CMN1132E: When parsing the input XML string, the following error occurred: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command encountered the specified error while parsing the input XML string.
Action: Determine which command was executing, and the XML string that was passed to it as input. Examine the XML string in error, and determine how it was produced. Fix the program that produced it.
- CMN1200E: Failed to get the current timestamp in the system. CMN3101E The system is unavailable due to {0}.
- Explanation: Failed to get the current time stamp while adding a broadcast job command.
Action: Review the WebSphere Commerce log to check if there are any server errors and exceptions.
- CMN1214E: An invalid job reference number is specified in the scheduler. CMN3101E The system is unavailable due to {0}.
- Explanation: The job reference number could not be found. The job command could not be edited by using the job reference number.
Action: Ensure the job reference number is not null and is a valid job reference number in the scheduler job entries.
- CMN1217E: The command was unable to retrieve the attributes for category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: There are no attributes for the specified category in the given language.
Action: Add the attributes to the CATGRPATTR table.
- CMN1218E: The command was unable to retrieve the description for category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command did not find a description for specified category in the given language.
Action: Use the WebSphere Commerce Accelerator to create a new description in the given language, or alternatively add the description to the CATGRPDESC table.
- CMN1219E: The command was unable to retrieve the description for catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command did not find a description for specified catalog entry in the given language.
Action: Use the WebSphere Commerce Accelerator to create a new description in the given language, or alternatively add the description to the CATENTDESC table.
- CMN1220E: Store {1} was unable to process catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified catalog entry is not associated to the given store.
Action: Create an association between the catalog entry and the store in the STORECENT table. Alternatively, create an association in the STORECENT table between the catalog entry and a store to which the given store is related in the STOREREL table.
- CMN1223E: The command was unable to process catalog group {0}. Either it does not exist in the catalog, or it cannot be processed in store {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The catalog group is either not associated to the specified store or the catalog group does not exist.
Action: Ensure that the catalog group exists in the CATGROUP table and that the STORECCGRP table associates this catalog group to the specified store. Alternatively, ensure that the catalog group has an entry in the STORECGRP table for a store to which the specified store is related.
Use the STOREREL table to determine if the specified store is related to any other stores. - CMN1224E: The value of the {0} parameter is not consistent with the value of the {1} parameter. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was passed two conflicting parameter values.
Action: Change the calling code to specify only one of the two parameter values.
- CMN1225E: Neither the {0} parameter nor the {1} parameter were provided to this command, and at least one is required to complete the command. CMN3101E The system is unavailable due to {0}.
- Explanation: Neither of the specified parameters were provided to the command, but the command requires that one of them must be provided.
Action: Inspect the Websphere Commerce error log to determine the controller command that was executing. Then determine the caller of the command and inspect the calling code to determine why at least one of the specified parameters was not provided.
- CMN1226E: Store {1} was unable to process catalog {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified catalog is not associated to the given store.
Action: Create an association between the catalog and the store in the STORECAT table. Alternatively, create an association in the STORECAT table between the catalog and a store to which the given store is related in the STOREREL table.
- CMN1227E: The command was unable to process catalog {0}. Either it does not exist, or it cannot be processed in store {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The catalog is either not associated to the store or the catalog does not exist.
Action: Ensure that the catalog exists in the CATALOG table and that the STORECAT table associates this catalog to the specified store. Alternatively, ensure that the catalog has an entry in the STORECAT table for a store to which the specified store is related.
Use the STOREREL table to determine if the specified store is related to any other stores. - CMN1230E: The command was unable to process the bundle as a unit. The command requires that each constituent bundle component is processed individually. CMN3101E The system is unavailable due to {0}.
- Explanation: A bundle cannot be directly added to a shopping cart. Each component of the bundle must be added separately to the order.
Action: Call the appropriate "add to order" command, with each of the bundle components separately defined as parameters to the command.
- CMN1231E: User {0} does not have permission to access order {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified Order is not for the specified user. The command only works on Orders for the current user.
Action: Check the calling code to determine how the command was invoked on an Order that is not for the current user. If the current user has permission to use the ForUserId parameter, consider specifying the ForUserId parameter, specifying the memberId attribute of the Order.
- CMN1232E: CMN3101E The system is unavailable due to {0}.
- Explanation: The command received the specified parameter value, but cannot determine the set of Order objects to which it refers.
Action: Refer to the online command documentation to determine possible Order abbreviations for the command. Change the command caller to specify either the reference number of an existing Order object, or a valid Order abbreviation.
- CMN1233E: CMN3101E The system is unavailable due to {0}.
- Explanation: The command received the specified parameter value, but cannot determine the set of OrderItem objects to which it refers.
Action: Refer to the online command documentation to determine possible OrderItem abbreviations for the command. Change the command caller to specify either the reference number of an existing OrderItem object, or a valid OrderItem abbreviation.
- CMN1239E: The OrderCopy command has failed with error code {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The CheckOrderCopy task command implementation has denied the current user access to an Order object. This message is not issued by the current Websphere Commerce default implementation. In a previous version of WebSphere Commerce, this message was issued when the user tried to copy from or to another user's Order.
Action: Refer to the documentation for the currently installed default implementation of the CheckOrderCopy task command.
- CMN1245E: Server fails to redirect to the view {0}. {1} CMN3101E The system is unavailable due to {0}.
- Explanation: The server failed to build the redirect URL, or the URL could not be reached.
Action: Review the WebSphere Commerce log file to verify the view name and request properties.
- CMN1246E: CMN3101E The system is unavailable due to {0}.
- Explanation: The server could not send a text document out because an I/O exception occurred.
Action: Review the WebSphere Commerce log file to check if any I/O stream error was reported.
- CMN1248E: Order {0} cannot be processed in store {1} because it is not owned by that store. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified order is not owned by the specified store, and so cannot be processed in that store.
Action: Inspect the Websphere Commerce error log to determine the controller command that was executing. Then determine why the command accessed an order that is not owned by the specified store. For example, if the order was specified as an input parameter, determine the caller of the command and inspect the calling code to determine how that input parameter obtained its value. If the Order was created by the OrderSchedule command, check the STOREENT_ID column of the SCHCONFIG table, and the STORE_ID of the Order specified by the corresponding row in the SCHORDERS table.
- CMN1249E: The command could not find a specified item for the catalog entry of the order item. CMN3101E The system is unavailable due to {0}.
- Explanation: When available to promise (ATP) inventory is enabled (STORE.ALLOCATIONGOODFOR is not zero), each catalog item, package, and dynamic kit in the CATENTRY table must have a corresponding specified item in the ITEMSPC table.
Action: Check the STORE.ALLOCATIONGOODFOR column to see if ATP inventory is enabled. If ATP inventory is enabled, make sure that all catalog items (CATENTRY.CATENTTYPE_ID ItemBean), packages (CATENTRY.CATENTTYPE_ID PackageBean), and dynamic kits (CATENTRY.CATENTTYPE_ID DynamicKitBean) sold by the store (see the STORECENT table) have a corresponding specified item in the CATENTRY.ITEMSPC_ID column.
- CMN1251E: The store is currently unavailable. Try again later. The store is currently unavailable. Try again later.
- Explanation: A system exception occurred when processing the request. This exception may require action by the Site Administrator.
Action: Check the WebSphere Commerce log files to determine the underlying cause of the problem. Take the appropriate action as described in the log files.
- CMN1253E: No ShippingArrangement object enables store {1} to ship using shipping mode {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: A shipping mode must have an active ShippingArrangement before it can be used.
Action: Check the SHPARRANG table to make sure an active ShippingArrangement specifies the shipping mode. Check the StartDate and EndDate values.
- CMN1254E: Order notification for store {0} cannot be sent because its contact address does not define an e-mail address. CMN3101E The system is unavailable due to {0}.
- Explanation: The OrderProcess command was called with the notifyMerchant parameter value of "1". However, the Store has not defined a contact address, in the current Language, with an e-mail address.
The reference number of the Store's contact address is defined in the STADDRESS_ID_CONT column of the STOREENTDS table. The e-mail address is stored in the EMAIL1 column of the STADDRESS table.Action: Use the Store Profile notebook to define a contact address, including the e-mail address, for the Store. To access this notebook, log onto the WebSphere Commerce Accelerator, select the Store menu, then the "Change profile" option.
- CMN1261E: The order (idtext={0}) has a wrong order relation type: {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified Order is referred to by the CHILD_ID column of a row in the ORDQUOTREL table, but its RELTYPE column value is not appropriate for the command being executed. For example, if the OrderProcess command was used to process this Order, the RELTYPE column should have the value of "selection".
Action: Check the calling program to understand why it is calling the command specifying an Order that is a child with an inappropriate relationship type.
- CMN1263E: The mapping record from the external quantity unit {0} and standard {1} is missing from table QTYUNITMAP. CMN3101E The system is unavailable due to {0}.
- Explanation: A message was received from an external system that is using a PolicyCommand that uses the specified unit of measurement standard (defined as the value for the uomStandard property in the PROPERTIES column of the POLICYCMD table). The message specified a unit of measure code that was not found in the UOMCODE column of the QTYUNITMAP table for that unit of measurement standard.
Action: Check that the uomStandard property in the POLICYCMD table is correct. Check to make sure all the unit of measurement codes that the external system can return are defined in the QTYUNITMAP table for that external unit of measurement standard.
- CMN1264E: The mapping record from the WebSphere Commerce quantity unit {0} to standard {1} is missing from table QTYUNITMAP. CMN3101E The system is unavailable due to {0}.
- Explanation: WebSphere Commerce attempted to send a message to an external system that is using a PolicyCommand that uses the specified unit of measurement standard (defined as the value for the uomStandard property in the PROPERTIES column of the POLICYCMD table).
It was unable to find a mapping in the QTYUNITMAP table from the specified quantity unit of measure code to an external unit of measure code for the specified unit of measurement standard.Action: Check that the uomStandard property in the POLICYCMD table is correct. Check to make sure all the unit of measurement codes that the external system can accept are defined in the QTYUNITMAP table for that external unit of measurement standard.
- CMN1265E: The currency {0}, of the response, is not supported by store {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command is not able create a quotation order for the specified store because the price and availability response message contained amounts in a currency not supported by the store.
The SETCURR table contains a row for each currency defined to WebSphere Commerce. A store supports all currencies specified in the CURLIST table for its store and store group, as well as its default currency specified in the SETCCUR column of the STOREENT table for its store or store group.Action: If the currency of the response is correct, then use WebSphere Commerce Accelerator to define and support the specified currency for the specified store. Otherwise, if the currency of the response is not correct, determine why the response specified that currency.
- CMN1266E: The currency of all items in the response are not the same. The two differing values are {0} and {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command is not able create a quotation order for the specified store because the price and availability response message contained amounts in more than one currency.
Action: Determine why the response returned amounts in more than one currency.
- CMN1267S: The order quotation request for store ID {0}, contract ID {1}, parent order ID {2}, and quotation type {3} contains no items. The request is ignored.
- Explanation: The orderId parameter passed to the OrderQuotationRequest specified an order that contained no items. No request was sent.
Action: No action required.
- CMN1268E: The quotation contains a reference to lineNumber {0} which does not exist in the original request. The quotation is ignored. CMN3101E The system is unavailable due to {0}.
- Explanation: Each line item in a price and availability response specifies a line number that indicates the original OrderItem for which this line item is a response. However, a response was received that contained a line item whose line number did not refer to an OrderItem in the original Order for which a response was requested. The response has been ignored.
This could happen if the original Order has been deleted or modified since the response was requested. This situation can occur normally if the customer changes the original request before the response is received, and in that case does not indicate an error. Otherwise, it could indicate that the external system did not properly form the line item in the response.
Action: Verify that price and availability responses can be obtained from the external system. If they can be obtained, then this is probably a normal occurrence, due to slow response from the external system, or impatience on the part of the customer.
- CMN1269E: The OrderQuotationRel abbreviation {0} is invalid. CMN3101E The system is unavailable due to {0}.
- Explanation: The command expected a valid OrderQuotationRel abbreviation, in order to identify one or more OrderQuotationRel objects. But the specified abbreviation is not valid.
Action: Refer to the online documentation for the "Order subsystem commands" for a list of valid OrderQuotationRel abbreviations. Use the trace facility to determine the command that was being executed, and determine the caller (usually a java server page) of the command. Change the caller to specify a valid OrderQUotationRel abbreviation.
- CMN1270E: OrderQuotationRel {0} does not exist. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified parameter value was passed to a controller command. However, it does not indicate an existing OrderQuotationRel object in the ORDQUOTREL database table. It may be that the specified OrderQuotationRel object has been removed from the database before the command was invoked.
Action: Inspect the logic of the calling program to determine how an obsolete OrderQuotationRel identifier was obtained. Consider using an OrderQuotationRel abbreviation, if appropriate. (Refer to "Order subsystem commands" in the online documentation.)
- CMN1271E: The following orders were not processed: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The OrderProcess command has set the OrderProcessErrorView error view, and has passed more details in the ordersExceptions and ordersSucceeded properties.
Action: The customer can view which orders were not processed, and why. The customer can modify those orders and re-submit them by re-invoking the OrderProcess command.
- CMN1272E: Order {0} was not processed due to quote expiration. CMN3101E The system is unavailable due to {0}.
- Explanation: The OrderProcess command discovered that the number of seconds specified in the QUOTEGOODFOR column of the STORE database table have passed since the Order was most recently prepared using the OrderPrepare command. The OrderProcess command invoked the OrderPrepare command, and found that the re-calculated total amount payable had changed. The quoteExpiredURL and quoteExpiryPolicy parameters indicated that the Order should not be processed in this case.
Action: The customer can view the Order and accept the changed total amount by re-invoking the OrderProcess command.
- CMN1273E: Order {0} was not processed due to insufficient inventory for some of its order items. CMN3101E The system is unavailable due to {0}.
- Explanation: The OrderProcess command was unable to allocate or backorder all items for an order. This could occur if an item has been discontinued and has insufficient available inventory.
Action: No action required.
- CMN1274E: Order {0} was not processed due to changes in availability times for some of its order items. CMN3101E The system is unavailable due to {0}.
- Explanation: The availabilityChangeURL parameter was specified, and the OrderProcess command has discovered that availability times for some order items have moved into the future by more than the number of seconds specified by the maxAvailabilityChange parameter, since the order was most recently prepared using the OrderPrepare command.
Action: No action required.
- CMN1350E: The returns component could not determine the credit vehicle of return {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The returns component systematically determines how to refund a customer for a return. It chooses the payment vehicle used for the most recent order participating in a return. This determination will fail if there are no orders participating in a return. This will happen if only catalog items are added to a return.
Action: Add an order item to the return, change the refund to zero and mark the merchandise as not required to be physically returned.
- CMN1351E: The returns component could not determine the return fulfillment center for return {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The returns component systematically determines to which fulfillment center a customer should send their return merchandise. It chooses the fulfillment center marked as the default return fulfillment center for the store.
Action: Make sure that there is an entry in the database for store.rtnffmctr_id.
- CMN1352E: The returns component could not initiate the refund for return {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The returns component attempted to issue a refund but the payments component did not accept the transaction request. The returns component will retry on its next iteration.
Action: Make sure the payment system is functioning properly.
- CMN1501E: User {1} does not have the authority to perform action {2} on resource {3} for command {0}. User {1} does not have the authority to perform action {2} on resource {3} for command {0}.
- Explanation: The predefined access control policy cannot not be fulfilled.
The user is not authorized to execute the command.Action: Check the access control policy to make sure the user has the correct authority to execute the command. If not, contact your system administrator to set up the correct authority for the user.
- CMN1504E: The command was unable to create or update the interest item. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not create or retrieve the interest item with the specified parameters.
Action: Ensure that the interest item list exists and that the catalog entry reference number supplied refers to a valid item.
- CMN1505E: The command was unable to create or update the interest item list. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not create or retrieve the interest item list with the specified parameters.
Action: Ensure that the interest item list exists and that the supplied interest item list identifier is valid.
- CMN1507E: The command failed to delete interest item list {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified interest item list does not exist.
Action: Verify that the interest item list represented by the interest item list reference number parameter of the command exists in the IITEMLIST table.
If necessary, modify the command parameters and retry the delete operation for an interest item list that does exist. - CMN1508E: The command failed to delete interest item {0} from interest item list {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified interest item does not exist.
Action: Verify that the interest item represented by the interest item reference number parameter of the command exists in the IITEM table.
If necessary, modify the command parameters and retry the delete operation for an interest item that does exist. - CMN1510E: The interest item {0} already exists in interest list {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The interest item is already in the specified interest item list.
Action: Modify the parameters of the command to add the specified interest item into an alternate interest item list.
- CMN1512E: The command failed to mark the interest item list {0} as current for user {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Eiter the specified interest item list does not exist, or it is already a "current" interest item list for the user.
Action: Ensure that the interest item list reference number command parameter refers to a valid interst item list that is available to the user.
- CMN1514E: The command failed to retrieve the current interest item lists for user {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The user does not have any interest item lists that are marked "current".
Action: Use the SetInterestItemList command to set at least one interest item list as "current". Alternativley, update the CIITEMLIST table to add current interest item lists for a user.
- CMN1515E: The search engine failed to parse the search configuration file because duplicate table join relationship entries were found. Entries have already been defined using the keys {0} and {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The search engine uses search.xml file to obtain table join releationships when building SQL. If a duplicate table name pair relationship is defined, this error message is thrown to indicate duplicate entries are not permitted. The short description should be updated to read as follows: The search engine failed to parse the search configuration file, duplicate table join releationship entries found. An entry is already defined under keys "{0}" and "{1}".
Action: Administrators should reconcile and remove any duplicate entries in this file.
- CMN1516W: Generic warning message: {0}.
- Explanation: This message displays a generic warning. The substitution text will contain the real warning message.
Action: View the substitution text for the real warning message.
- CMN1519I: WebSphere Commerce status message: {0}.
- Explanation: Status message only.
Action: No action required.
- CMN1526E: Order {0} must be in status ''C'' or ''R'' to be released to fulfillment. CMN3101E The system is unavailable due to {0}.
- Explanation: The order must be completed before release to fulfillment can take place.
Action: Ensure that the end user can only select an order to release to fulfillment that has status "C" or "R"
- CMN1528E: Order item {0} does not meet the criteria for release to fulfillment. CMN3101E The system is unavailable due to {0}.
- Explanation: For an order item to be released to fulfillment, its inventory must already be allocated and it may not already have been released.
Action: Ensure that the end user can only select order items that are releasable.
- CMN1529E: The following order items do not meet the criteria for release to fulfillment: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: For order items to be released to fulfillment, their inventory must already be allocated and they may not already have been released.
Action: Ensure that the end user can only select order items that are releasable.
- CMN1530E: The command cannot process order {0} that is not owned by the current store. CMN3101E The system is unavailable due to {0}.
- Explanation: This command requires the order to be for the currently selected store.
Action: Ensure that the user interface only allows the user to select an order that is part of the current store and ensure the correctness of the store ID that is passed to this command.
- CMN1531S: Order item {0} cannot be allocated after changing to fulfillment center {1}.
- Explanation: The command attempts to change the fulfillment center assignment of the specified order item. However, after the change, the command could no longer allocate the inventory for the item.
The fulfillment center assignment is not performed for the order item and any changes made to the order by this command are rolled back. The command continues with other unprocessed orders if any.Action: Check the log for other error messages preceeding this message. Correct the error and retry the command. Alternatively, specify a different fulfillment center assignment for the order item and retry the command.
- CMN1532S: Order items {0} cannot be allocated after changing to the respective fulfillment center in this set: {1}.
- Explanation: The command attempts to change the fulfillment center assignment of the specified order items. However, after the change, the command could no longer allocate the inventory for the items.
The fulfillment center assignment is not performed for the order items and any changes made to the order by this command are rolled back. The command continues with other unprocessed orders if any.Action: Check the log for other error messages preceeding this message. Correct the error and retry the command. Alternatively, specify a different fulfillment center assignment for the order items and retry the command.
- CMN1533S: No order items were specified for order {0}.
- Explanation: To run this command you must specify the order ID as well as the order item IDs within the order that you want the command to process.
If no order item IDs are specified for the order, the command skips the order and continues with other unprocessed orders.Action: Specify the order item IDs and retry the command.
- CMN1534S: Payment authorization for the order has expired and re-authorization is still pending.
- Explanation: This command requires payment authorization to be completed for the order or order items before proceeding with the processing of the order. However, payment authorization has expired. The command skips the order and continues with other unprocessed orders if any. After completing the processing of the other orders, the command retrys the order with the expired payment authorization but the re-authorization has not completed or is pending. The command rolls back any changes made to the order items of the order.
Action: Wait for the payment re-authorization to complete and retry the command.
- CMN1535S: Payment authorization for the order has expired and re-authorization has failed.
- Explanation: This command requires payment authorization to be completed for the order or order items before proceeding with the processing of the order. However, payment authorization has expired and re-authorization (if attempted) has failed. The command rolls back any changes made to the order items of the order and continues with other unprocessed orders if any.
Action: Correct the payment authorization problem perhaps by attempting to manually re-authorize the payment from the WebSphere Commerce Payments user interface. Retry the command. Different payment method may require different recovery action for authorization expiry including calling the human operator at the payment processor which rejected the payment re-authorization. By attempting to manually re-authorize the payment from the WebSphere Commerce Payments user interface, you may get a clearer indication of the error that causes the failure.
- CMN1536E: Store {0} does not have default fulfillment center setup.
- Explanation: The command requires that the store identifies a default fulfillment center in the FFMCENTER_ID column of the STORE table.
Action: Make sure that the FFMCENTER_ID column of the STORE table specifies a default fulfillment center for the store.
- CMN1537E: The inventory adjustment code {0} not exist for store {1}.
- Explanation: The BatchAvailabilityResponse command uses the specified inventory adjustment code, but that code is not defined for the specified store in the INVADJCODE table. The inventory adjustment was not made.
Action: Use the fulfillment user interface to define the specified inventory adjustment code.
- CMN1538E: Store {1} cannot determine the specified item for part number {0}.
- Explanation: The command cannot find the specified part number in the ITEMSPC table.
Action: Ensure there is a row in the ITEMSPC for all valid part numbers.
- CMN1540E: Unable to process order {0} because it contains backordered order items.
- Explanation: The customer attempted to process an Order in which some of the OrderItems in the Order indicate a quantity attribute that exceeds the availableQuantity attribute value. However, the referral interface policy for the applicable trading agreement does not allow such an Order to be processed.
Action: The customer can reduce the requested quantities to be no greater than the availableQuantity attribute values and then re-attempt to process the Order.
- CMN1601E: The command was unable to add the attribute. CMN3101E The system is unavailable due to {0}.
- Explanation: The attribute for the specified language already exists.
Action: Use the AttributeUpdate command to modify the properties of the existing attribute.
- CMN1602E: The command was unable to update attribute {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified attribute does not exist in the given language.
Action: Use the AddAttribute command to create the attribute in the specified language.
- CMN1603E: The command was unable to delete attribute {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified attribute does not exist in the given language.
Action: Verify that the attribute represented by the attribute reference number and language parameters of the command exist in the ATTRIBUTE table. If necessary, modify the command parameters and retry the delete operation for an attribute that does exist.
- CMN1604E: The command was unable to add the attribute value. CMN3101E The system is unavailable due to {0}.
- Explanation: The attribute value for the specified attribute and language already exists.
Action: Use the AttributeValueUpdate command to modify the properties of the existing attribute value.
- CMN1605E: The command was unable to update attribute value {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified attribute value does not exist in the given language.
Action: Use the AttributeValueAdd command to create the attribute value in the specified language.
- CMN1606E: The command was unable to delete attribute value {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified attribute value does not exist in the given language.
Action: Verify that the attribute value represented by the attribute value reference number and language parameters of the command exist in the ATTRVALUE table. If necessary, modify the command parameters and retry the delete operation for an attribute value that does exist.
- CMN1609E: The command was unable to delete catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the catalog entry object due to a system error. Ensure that the catalog entry object has previously been created.
Action: Check the command parameters including the catalog entry reference number and the catalog entry partnumber.
- CMN1610E: The command was unable to add a description to the catalog entry. CMN3101E The system is unavailable due to {0}.
- Explanation: The description for the catalog entry in the specified language already exists.
Action: Use the CatalogEntryUpdate command to modify the properties of the existing catalog entry description.
- CMN1611E: The command was unable to update the description for catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not update the description object for the catalog entry in the given language due to a system error. Ensure that the catalog entry exists.
Action: If the catalog entry object does not exist in the given language, use the CatalogEntryAdd command to create a new catalog entry.
- CMN1613E: The command was unable to add the catalog group. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not create the catalog group object due to a system error. Ensure that the catalog group object has not previously been created and that a catalog description object does not exist for the given language.
Action: If the catalog group already exists, use the CatalogGroupUpdate command to modify the catalog group object's properties, or the CatalogGroupDelete command to delete the catalog group object.
- CMN1614E: The command was unable to update catalog group {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not update the catalog group object due to a system error. Ensure that the catalog group object exists.
Action: If the catalog group object does not exist, use the CatalogGroupAdd command to create it.
- CMN1615E: The command was unable to delete catalog group {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the catalog group object due to a system error. Ensure that the catalog group object has previously been created.
Action: Check the command parameters including the catalog group reference number and the catalog group identifier.
- CMN1616E: The command was unable to add a description to catalog group {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not create the description object for the catalog group in the given language due to a system error. Ensure that the description for the catalog group in the given language does not exist.
Action: If the catalog group description object already exists in the given language, use the CatalogGroupUpdate command to modify the catalog group description object's properties.
- CMN1617E: The command was unable to update the description for catalog group {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not update the description object for the catalog group in the given language due to a system error. Ensure that the catalog group exists.
Action: If the catalog group object does not exist in the given language, use the CatalogGroupAdd command to create a new catalog group.
- CMN1619E: The command was unable to add the catalog. CMN3101E The system is unavailable due to {0}.
- Explanation: A catalog with the specified catalog identifier already exists and you are not permitted to have two catalogs that have the same catalog identifier.
Action: Either use the CatalogUpdate command to modify the properties of one catalog and give it a unique catalog identifier, or use the CatalogDelete command to delete one of the catalogs.
- CMN1620E: The command was unable to update catalog {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified catalog does not exist.
Action: Use the CatalogAdd command to create the specified catalog, then retry the update.
- CMN1621E: The command was unable to delete catalog {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified catalog does not exist.
Action: Verify that the catalog represented by the catalog reference number and catalog identifier parameters of the command exists in the CATALOG table.
If necessary, modify the command parameters and retry the delete operation for a catalog that does exist. - CMN1622E: The command was unable to add the list price. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not add the list price due to a system error. Ensure that the list price has not previously been created for the given catalog entry and that the currency of the price is valid.
Action: If the list price already exists for the catalog entry in the given currency, use the ListPriceUpdate command to modify the amount, or the ListPriceDelete command to delete the list price.
- CMN1623E: The command was unable to update the list price for catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not update the list price for the given catalog entry object due to a system error. Ensure that the catalog entry object exists and that the given currency is valid.
Action: If the catalog entry object does not exist, use the CatalogEntryAdd command to create it.
- CMN1624E: The command was unable to delete the list price for catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the list price due to a system error. Ensure that the list price has previously been created in the given currency.
Action: Check the command parameters including the catalog entry reference number and the currency.
- CMN1625E: The command was unable to add an offer. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not add the offer due to a system error. Ensure that the offer has not previously been created for the given catalog entry and that the currency of the price is valid.
Action: If the offer already exists for the catalog entry, use the OfferUpdate command to modify the offer's properties, or the OfferDelete command to delete the offer.
- CMN1626E: The command was unable to update offer {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not update the offer due to a system error. Ensure that the offer object exists.
Action: If the offer object does not exist for the given catalog entry, use the OfferAdd command to create it.
- CMN1627E: The command was unable to delete offer {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the offer for the given catalog entry object due to a system error. Ensure that the catalog entry object has previously been created and that the specified offer exists.
Action: Check the command parameters including the reference numbers of the catalog entry and the offer.
- CMN1636E: The command was unable to add a relationship between catalog {0}, catalog group {1}, and catalog entry {2}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not create the relationship between the given catalog, catalog group, and catalog entry due to a system error. Ensure that the given objects exist.
Action: If the specified objects do not exist, use one or more of the following commands to create the missing objects: CatalogAdd, CatalogGroupAdd, or CatalogEntryAdd.
- CMN1637E: The command was unable to delete the relationship between catalog {0}, catalog group {1}, and catalog entry {2}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the relationship between the given catalog, catalog group and catalog entry due to a system error. Ensure that the relationship exists.
Action: Check the command parameters including the reference numbers of the catalog, catalog group and the catalog entry.
- CMN1638E: The command was unable to add a relationship between catalog {0}, parent catalog group {1}, and child catalog group {2}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was unable to create a subcategory relationship between the specified catalog groups in the given catalog. One or more of the specified objects may not exist.
Action: Check the reference numbers for both catalog groups, and ensure that the specified catalog reference number refers to a valid catalog object.
- CMN1639E: The command was unable to delete the relationship between catalog {0}, parent catalog group {1}, and child catalog group {2}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was unable to delete the subcategory relationship between the specified catalog groups in the given catalog.
Action: Check the reference numbers for both catalog groups, ensure that the specified catalog reference number refers to a valid catalog object, and validate that this subcategory relationship exists.
- CMN1641E: The command was unable to delete the relationship between store entity {0}, catalog entry {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Either the relationship between the given catalog entry and store does not exist, or the reference numbers provided for the catalog entry or store objects are not valid.
Action: Validate the reference numbers for the catalog entry and store objects and ensure that the relationship exists in the STORECENT table.
- CMN1642E: The command was unable to add a relationship between store entity {0} and a catalog {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Either the relationship between the given catalog and store already exists, or the reference numbers provided for the catalog or store objects are not valid.
Action: Validate the reference numbers for the catalog and store and ensure that the relationship does not exist in the STORECAT table.
- CMN1643E: The command was unable to delete the relationship between store entity {0} and a catalog {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Either the relationship between the given catalog and store does not exist, or the reference numbers provided for the catalog or store objects are not valid.
Action: Validate the reference numbers for the catalog and store objects and ensure that the relationship exists in the STORECAT table.
- CMN1644E: The command was unable to add a relationship between store entity {0}, catalog group {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Either the relationship between the given catalog group and store already exists, or the reference numbers provided for the catalog group or store objects are not valid.
Action: Validate the reference numbers for the catalog group and store and ensure that the relationship does not exist in the STORECGRP table.
- CMN1645E: The command was unable to delete the relationship between store entity {0}, catalog group {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Either the relationship between the given catalog group and store does not exist, or the reference numbers provided for the catalog group or store objects are not valid.
Action: Validate the reference numbers for the catalog group and store objects and ensure that the relationship exists in the STORECGRP table.
- CMN1646E: The command was unable to add a relationship between catalog {0} and catalog group {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was unable to create a root category relationship to the given catalog. One or more of the specified objects may not exist.
Action: Check the reference numbers for the catalog group and ensure that the specified catalog reference number refers to a valid catalog object.
- CMN1647E: The command was unable to delete the relationship between catalog {0} and catalog group {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was unable to delete the root category relationship between the catalog group and the given catalog.
Action: Check the reference numbers for the catalog group and catalog object. Also, validate that this root category relationship exists.
- CMN1648E: The parent catalog entry cannot be an item. CMN3101E The system is unavailable due to {0}.
- Explanation: The parent type of a catalog entry cannot be a catalog item. Catalog items (or SKUs) are a base unit of merchandise and cannot abstract other types of catalog entries.
Action: Select another catalog entry, such as a valid product, as the parent of the specified catalog entry.
- CMN1653E: There is a type problem with {0}{1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The given types are not compatible with each other.
Action: Select an alternate type for the assignment.
- CMN1654E: There is a problem with the input {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The input is not valid.
Action: Check the input that shows in the error message and make sure it conforms to the requirements.
- CMN1655E: The following Instantiation Exception occurred during processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The class you are accessing is not consistent with the expected class definition.
Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.
- CMN1656E: The following Illegal Access Exception occurred during processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The class you are accessing is not consistent with the expected class definition.
Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.
- CMN1657E: The following Illegal Argument Exception occurred during processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The class you are accessing is not consistent with the expected class definition.
Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.
- CMN1658E: The following Invocation Target Exception occurred during processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The class you are accessing is not consistent with the expected class definition.
Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.
- CMN1659E: The following No Such Method Exception occurred during processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The class you are accessing is not consistent with the expected class definition.
Action: If you replaced the implementation of this class, ensure that the class definition and signatures match the orginal class definition.
- CMN1660E: Stored procedure {0} failed with error code {1}, SQL state {2}. Stored procedure {0} failed with error code {1}, SQL state {2}.
- Explanation: The specified stored procedure failed.
Action: Refer to the online documentation for "Stored procedure error codes".
- CMN1661E: The command was unable to delete catalog entry {0} because it is referenced in at least one order or has inventory. CMN3101E The system is unavailable due to {0}.
- Explanation: The command could not delete the catalog entry object due to a data integrity error. Ensure that the catalog entry object has not been previously purchased in an order item.
Action: To remove catalog entries that exist in previously completed orders, run the Database Cleanup (DBClean) utility to remove the orders that reference the catalog entry. When there are no more orders that reference the catalog entry, run the CatalogEntryDelete command or the DBClean utility to perform the deletion.
- CMN1662E: The command was unable to delete offer {0} because it is referenced in at least one order or has inventory. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was not able to delete the pricing information for the specified catalog entry. Offers cannot be deleted if they are being used in an order.
Action: Use the Database Cleanup utility (DBClean) to delete outdated orders before attempting to delete the catalog entries prices. Alternatively, set the PUBLISHED field in the OFFER table to indicate that this OFFER should not be used. See the OFFER table schema definition reference to view a list of available values for the PUBLISHED field.
- CMN1675E: The caller of the command did not supply the correct number of quantities and prices for the dynamic kit with configuration ID {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command was called to create a list of components for a configuration in the OICOMPLIST table, but the command caller did not supply enough quantities or prices.
When a list of components is created, a quantity amount must be specified for each component. If the component list is to include prices, then a price must be specified for each component.Action: Check that the caller of the DynamicKitConfigurationAdd command specified a quantity amount for each component, and, if prices are specified, a price for each component.
- CMN1676E: The caller of the command specified prices but no currency for the dynamic kit with configuration ID {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: A command was asked to create components for a configuration, and prices were specified, but no currency was specified for for the prices.
Action: Check the caller of the DynamicKitConfigurationAdd command to make sure that the currency parameter is specified.
- CMN1678E: The component list for the dynamic kit with configuration ID {0} is invalid. CMN3101E The system is unavailable due to {0}.
- Explanation: Each dynamic kit must contain at least one OrderItemComponent.
This error message indicates that no OrderItemComponent can be found with the specified configuration ID.Action: Check if any rows can be located from table OICOMPLIST with the configuration ID. Reconfigure the dynamic kit by issuing the DynamicKitConfigurationAdd command. For more information about this command, refer to the online help.
- CMN1700E: The upload file type {0} is not supported. CMN3101E The system is unavailable due to {0}.
- Explanation: The upload file type is not supported by the current implementation.
Action: Refer to the WebSphere Commerce online help to learn about the upload file tpyes that are supported, or contact your Site Administrator.
- CMN1701E: There was an error when attempting to create the directory {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is usually caused by the file system setup.
Action: Contact your Site Administrator to troubleshoot the possible file system setup errors.
- CMN1702E: The file {0} is not a valid zip file. CMN3101E The system is unavailable due to {0}.
- Explanation: The uploaded file has .zip file extension but it is not a valid ZIP file.
Action: Ensure that your ZIP file is not corrupted. Try to use a ZIP utility to check whether or not the ZIP file is valid.
- CMN1703E: The system could not upload the file because another catalog file is in publising status. CMN3101E The system is unavailable due to {0}.
- Explanation: When a catalog file is being publishing for a store, you cannot publish another catalog file.
Action: Check if there is another catalog file in publishing status. If one catalog file is in publishing status, wait until the publishing process is completed before publishing the next file.
- CMN1704E: An uploaded file with a status of {0} cannot be published. CMN3101E The system is unavailable due to {0}.
- Explanation: An uploaded catalog file can only be published if its status is 'New'.
Action: Typically, a JSP file only allows a catalog file with the status 'New' to be published. Contact your Site Administrator.
- CMN1706E: When extracting the .csv files, the following errors occured: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: This error can be caused by errors in the uploaded catalog file or can be caused by file system errors.
Action: If the error is caused by the errors in the uploaded catalog file, check the catalog file and fix the errors. If the error is caused by file system errors, contact your Site Administrator.
- CMN1707E: When creating the file {0}, the following errors occured: {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is usually caused by the file system setup.
Action: Contact your Site Administrator to troubleshoot possible file system setup errors.
- CMN1708E: The catalog publishing process cannot find the master catalog for store {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The master catalog is not defined for the store. This is a store setup problem.
Action: Contact your Site Administrator. The Site Administrator can check the STORECAT table to see if a master catalog is defined for the store. If not, check the STOREREL table to see if this store uses a master catalog from another catalog profile store.
- CMN1709E: The catalog publishing process cannot find any trading position container for store {0}. Contact the Site Administrator. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is caused by the store setup.
Action: Contact your Site Administrator to troubleshoot store setup errors.
- CMN1710E: The catalog import process failed to resolve and generate IDs. This error occurs when the catalog file contains some data errors and the catalog manager tool: ResolveId failed to resolve IDs. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is due to the error in the uploaded catalog file.
Action: Refer to the CSV catalog file format user's guide to determine the possible errors. After fixing the error, upload the catalog file and publish the catalog again.
- CMN1711E: The uploaded file {0} is not a valid catalog file. CMN3101E The system is unavailable due to {0}.
- Explanation: The uploaded file is not a valid catalog file.
Action: Refer to the WebSphere Commerce online help for the supported catalog file formats.
- CMN1952E: Product Advisor could not find the sort feature. CMN3101E The system is unavailable due to {0}.
- Explanation: When displaying Product Comparison results, Product Advisor needs to sort the results. This error message indicates that the sort feature is not defined for the metaphor.
Action: Define a sort feature for the Product Comparison metaphor.
- CMN1953E: The metaphor retrieval failed. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not retrieve the metaphor. All metaphors must be created in both the ICMETAPHOR and the ICMETAPROP tables, and registered in the ICMETAREG table.
Action: Verify that the metaphor exists and that it is registered. If the metaphor does not exist, you must create one.
- CMN1954E: Product Advisor could not find the MetaphorLink for the answer with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the MetaphorLink for the specified answer. The MetaphorLink either does not exist in the ICCNCPTLNK table, or it is not valid.
Action: Assign a valid MetaphorLink to the answer.
- CMN1955E: Product Advisor could not find the ProductFamily for the category with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the ProductFamily for the specified category. The search space for the category does not exist.
Action: Create a search space for the category.
- CMN1956E: Product Advisor could not find the product links. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the product links for a Product Comparison metaphor.
Action: Assign valid product links to the Product Comparison metaphor.
- CMN1957E: Product Advisor could not find the first question, and cannot complete the request. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find a question defined as the root question for a Guided Sell question and answer tree.
Action: Verify that a root question exists for the tree. If no root question exists, create a root question, or assign an existing question to the tree as its root.
- CMN1958E: Product Advisor could not find the parent question for the answer with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the parent question for the specified answer. The parent question does not exist in the ICKNOWLEDG and the ICKNOWDESC tables.
Action: Verify that both the question, and the answer, have been created successfully.
- CMN1959E: Product Advisor could not find the question with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the specified question in the database.
Action: Verify that the question has been created successfully. All questions should be created in both the ICKNOWLEDG and the ICKNOWDESC tables.
- CMN1960E: Product Advisor could not find the answer with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the specified answer in the database.
Action: Verify that the answer exists. If it does not, create it. All answers must be created in both the ICKNOWLEDG and the ICKNOWDESC tables.
- CMN1961E: Product Advisor could not find the answers for the question with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find the answers for the specified question in the database.
Action: Verify that the answers for the question have been created. All answers must be created in both the ICKNOWLEDG and the ICKNOWDESC tables.
- CMN1962E: Product Advisor could not find the widget for [{0}]. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor failed to load the widgets required for rendering Product Explorer pages.
Action: Verify that the widget registry has been correctly installed and updated. All of the widgets must be registered in the ICDEWIDREG table.
- CMN1963E: The metaphor does not match with the database. CMN3101E The system is unavailable due to {0}.
- Explanation: The database has been updated since the metaphor was created, and the metaphor is not synchronized with the updates. As a result, the metaphor is invalid.
Action: Re-create the metaphor to capture the database updates.
- CMN1964E: There is an invalid template usage {0} CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor supports the following template usages:
TO_METAPHOR(0): Use the template from the metaphor you're linking to
FROM_METAPHOR(1): Use the template from the metaphor you're linking from
OVERRIDE(2): Override the metaphor template
NO_METAPHOR(3): Do not use a metaphor, and link to an HTML page
This problem is typically caused by using the NO_METAPHOR usage, and specifying a metaphor link.
Action: Check the ICCNCPTLNK table, and assign a valid usage value to the template.
- CMN1966E: Product Advisor cannot find the parent table. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor failed to obtain the table object when sorting the results for display.
Action: No user action required.
- CMN1970E: There is no default link specified for the answer with reference number {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find a default link for the answer in the database.
Action: Assign a default link to the answer. All links must be created in the ICCNCPTLNK table.
- CMN1971E: Product Advisor cannot find any features to display. CMN3101E The system is unavailable due to {0}.
- Explanation: There are no features defined for a metaphor. As a result, Product Advisor fails to display the results page.
Action: Define features for the metaphor.
- CMN1972E: There are no feature values exist. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor could not find any values for a feature. This messages indicates that a category does not contain any values for one or more features.
Action: Define values for all of the features used in Product Advisor.
- CMN1973E: The search returned no results. CMN3101E The system is unavailable due to {0}.
- Explanation: Product Advisor did not find any products matching certain constraints.
Action: No user action required.
- CMN1992E: The command failed to get the root categories for category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command did not find any root categories for the given cateogy in the specified catalog.
Action: Use the WebSphere Commerce Accelerator to create the root category relationships in the given catalog, or alternatively add the relationships to the CATTOGRP table.
- CMN1993E: The command failed to get the attributes for product {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: There are no attribues for the specified product in the given language.
Action: Use the WebSphere Commerce Accelerator to create new product attributes, or alternatively add the attributes and their values to the ATTRIBUTE and ATTRVALUE tables.
- CMN1995E: The command failed to get the child categories for category {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command did not find any subcategories for the given cateogy in the specified catalog.
Action: Use the WebSphere Commerce Accelerator to create subcategory relationships, or alternatively add the relationships to the CATGPENREL table.
- CMN2003S: The command was unable to find interest item lists in which to copy data.
- Explanation: The command did not find any destination interest item lists in which to copy data. Valid destination interest item lists are not required for successful completion of the list copy command. If no destination lists are found, a new list for the user will be created.
Action: No action required.
- CMN2007E: There is insufficient inventory to purchase {1} units of the product for catalog entry {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: This message is issued by the default implementations of inventory related task commands (such as CheckInventoryCmdImpl, UpdateInventoryCmdImpl, and CheckInventoryAvailabilityCmdImpl) when there is insufficient inventory for the quantity of a product required to fulfill an Order.
When STORE.ALLOCATIONGOODFOR is zero, the CheckInventoryCmdImpl and UpdateInventoryCmdImpl default task command implementations check the INVENTORY table. Otherwise, the CheckInventoryAvailabilityCmdImpl default task command implementation checks the RECEIPT and ITEMFFMCTR tables.
Action: No action required.
- CMN2008D: The credit card number specified by the shopper is invalid. The card number is invalid.
- Explanation: The wrong credit card number may have been entered, or the credit card is invalid.
Action: Ensure that the credit card number is correct and that the credit card has not expired.
- CMN2009D: The card expiry date (year: {0}, month: {1}) is invalid. The card expiry date is invalid.
- Explanation: The card expiry month must be an integer value between 1 and 12. The card expiry year must be a 4-digit integer value equal to or greater than the current year. The card expiry date must be equal to or greater than the current date but less than the current date plus 10 years.
Action: Enter the correct card expiry date and resubmit the request. If the card has expired, use a different card with the corresponding card expiry date.
- CMN2012D: The card brand {0} is not defined in the CCCHECK table. The system is using the LUHN formula to verify the card number.
- Explanation: The CCCHECK table specifies the task commands to verify the card numbers of different card brands. If a card brand is not defined in the CCCHECK table, the system uses the standard LUHN formula to verify the card number.
Action: No action required.
- CMN2013D: The length or prefix of the card number is invalid for card brand {0}. The card number is invalid.
- Explanation: Most card issuers use card numbers with a fixed length and prefix. The specified card number does not match the length or prefix rules for the specified brand. The length and prefix rules are specified by entries in the CCCHECK table.
Action: Enter the correct card number and verify the card brand or make sure a correct entry is included in the CCCHECK table, then resubmit the request.
- CMN2022E: The command is unable to determine an appropriate fufillment center for an OrderItem. CMN3101E The system is unavailable due to {0}.
- Explanation: To be appropriate for an OrderItem, a FulfillmentCenter must have an active ShippingArrangement for the Store, ShipMode, and Address indicated by the OrderItem. Additionally, If the TradingAgreement for the OrderItem specifies a FulfillmentTC, then the FulfillmentCenter must be specified by the FulfillmentTC.
If ATP functionality is not enabled (STORE.ALLOCATIONGOODFOR is zero) then a FulfillmentCenter also must have sufficient inventory to fulfill the OrderItem.
Action: Examine previous messages in the log to determine the CatalogEntry, TradingAgreement, ShipMode, and shipping Address for the OrderItem. Check the ShipMode, StartDate and EndDate values for the ShippingArrangements defined in the SHPARRANG table. If the ShippingArrangements specify a ShippingJurisdictionGroup, check that the shipping Address matches one of the ShippingJurisdictions in the ShippingJurisdictionGroup. Check any applicable FulfillmentTC objects in the TERMCOND table. If ATP inventory is not enabled, then check the amount of inventory available in the INVENTORY table.
- CMN3204E: The store identifier associated to the command was not provided. CMN3101E The system is unavailable due to {0}.
- Explanation: Cannot find the store in the store registry. The store identifier associated to the command may be invalid or is not in the store table.
Action: Ensure the store identifier exists in the store table. Review the WebSphere Commerce log file to check if the servlet has been started successfully.
- CMN4501I: table {0} to be cleaned, this will imact the following child tables:
- Explanation: The specified table is ready to be cleaned, the child tables of this table are listed below. The child tables will be put in by _INF_TABLE in the following logs
Action: No action required.
- CMN4502I: The following tables have deletion restrictions.
- Explanation: The "restrict" delete rule applies to the following tables when parent tables are to be deleted
Action: No action required.
- CMN4507I:
- Explanation: DBClean will modify table "{0}"
Action: No action required.
- CMN4508I:
- Explanation: The SQL statement "{0}" has been executed.
Action: No action required.
- CMN4509E: A properly formatted name argument value is required
- Explanation: A properly formatted name argument value is required
Action: Check if name argument is provided or the format is correct
- CMN4509I: The staging table and production table are not synchronized. Each table contains a different number of rows.
- Explanation: The table has different number of rows on the staging server and the production server.
Action: No action required.
- CMN4510E: A properly formatted days argument value is required
- Explanation: DBClean needs days argument to execute
Action: Check if days argument is provided or the format is correct
- CMN4510I: The staging table and production table are synchronized.
- Explanation: The tables contain the same data on the staging server and the production server.
Action: No action required.
- CMN4511E: The staging server cannot read the source database password.
- Explanation: The source database password cannot be retrieved due to a system error.
Action: Type the database password and try again.
- CMN4511I: The staging table and production table are not synchronized.
- Explanation: The table contains different data on the staging server and the production server.
Action: No action required.
- CMN4512E: The staging server cannot read the destination database password.
- Explanation: The destination database password cannot be retrieved due to a system error.
Action: Type the database password and try again.
- CMN4512I:
- Explanation: Status message only.
Action: No action required.
- CMN4513E: Invalid database password entered
- Explanation: The database password provided is incorrect.
Action: Rerun DBClean using the correct database password
- CMN4513I: Table {0} ready to be updated.
- Explanation: The specified table is ready to be updated.
Action: No action required.
- CMN4514I: There is a primary key or unique index conflict between the staging table and the production table.
- Explanation: One of the tables has the same primary key or unique index value on the staging server and the production server. This will cause a key collision problem during staging propagation.
Action: Change the KEY column data on either the staging server or the production server to avoid the key value conflict.
- CMN4515I: There is a key conflict in table {0}.
- Explanation: The table has the same primary key value or unique index value on the staging server and the production server, which will cause key collision problems during the staging propagation.
Action: Compare the tables on the staging server and the production server, and correct the conflicting data on either the staging server or the production server.
- CMN4515S: An error occured when checking delete restrict rules for table {0}
- Explanation: Status message only.
Action: No action required.
- CMN4516E: The staging server command scope is not set to all merchants.
- Explanation: The staging server can only process all merchants at the same time, instead of an individual merchant.
Action: Change the command scope parameter to _merchant_, which will include all merchants.
- CMN4516I: The Database Cleanup utility retrieves column {0} from table {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4516S: Delete failed because of deletion restrictions between {0}
- Explanation: Status message only.
Action: Please check Database Cleanup utility log file, make sure there is no delete restriction and run DBClean again.
- CMN4517E:
- Explanation: The current command scope does not cover the table.
Action: Change the command scope parameter to _merchant_, which will process the table.
- CMN4518E:
- Explanation: The current command scope does not cover the table.
Action: Change the command scope parameter to _site_, which will process the table.
- CMN4518S: The Database Cleanup utility has started to clean.
- Explanation: Status message only.
Action: No action required.
- CMN4519E: The compression hash table index for the Stage Propagate utility is out of bounds.
- Explanation: The index is either negative or bigger than the size of compression hash table.
Action: Correct the index size to match the compression hash table.
- CMN4519S: The Database Cleanup utility is cleaning table {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4520E: An unexpected operation occurred in the STAGLOG table.
- Explanation: The operation can only be "I" (insert), "U" (update), or "D" (delete) in the STAGLOG table.
Action: Check the STAGLOG table and make sure the operations are correct.
- CMN4520S: The Database Cleanup utility failed to clean table {0}
- Explanation: Status message only.
Action: No action required.
- CMN4521E: The Stage Copy utility cannot open the script file{0}.
- Explanation: The Stage Copy utility cannot open or create the database script file due to a system error.
Action: Ensure that you have enough disk space and that your script directory is correct.
- CMN4521S: The staging server cleaned the table {0} successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4522E: SQL statement {0} is not permitted in cleanconf
- Explanation: The sql statement in cleanconf must start with either "DELETE" or "UPDATE"
Action: Check if the specified sql statement starts with "DELETE" or "UPDATE"
- CMN4523E: The staging server was unable to get the SQL statement from file {0}.
- Explanation: The staging server cannot read the database SQL from the script file.
Action: Verify that the input script file exists and can be accessed by the staging server.
- CMN4524E: The Database Cleanup utility could not resolve the statement type {0}.
- Explanation: The Database Cleanup utility only accepts "SELECT", "UPDATE" and "DELETE" SQL statements.
Action: Check the column STATEMENT in the CLEANCONF table to ensure that only "SELECT", "UPDATE" and "DELETE" SQL statements are in the column.
- CMN4525E: The customizer file {0} could not be found.
- Explanation: The JDBC driver file name provided by the command parameter could not be found.
Action: Check the path and file name, and run the database cleanup utlitily again.
- CMN4525S: The Database Cleanup utility successfully completed the assigned task.
- Explanation: Status message only.
Action: No action required.
- CMN4526E: The system could not open the customizer file {0}.
- Explanation: The JDBC driver file could be found and could not be opened.
Action: Check that the JDBC driver file can be opened and run the database cleanup utility again.
- CMN4526S: The Database Cleanup utility failed to construct set clause
- Explanation: Status message only.
Action: Please check Database Cleanup utility log file and run again.
- CMN4527E: The jdbcDriver and jdbcUrlPrefix are not provided correctly in {0}.
- Explanation: The JDBC customizer file was provided correctly, but the jdbcDriver and jdbcUrlPrefix parameters are not provided correctly in "{0}".
Action: Check the JDBC parameters provided in the customizer file
- CMN4527S: The Database Cleanup utility failed to construct where clause
- Explanation: Status message only.
Action: Please check Database Cleanup utility log file and run again.
- CMN4528S: The Database Cleanup utility failed to update child table{0} set null
- Explanation: Database Cleanup utility could not execute the set null update SQL statement.
Action: Please check Database Cleanup utility log file, identifiy the problem and run again.
- CMN4529S: Starting the Stage Propagate utility.
- Explanation: Status message only.
Action: No action required.
- CMN4530S: The Stage Propagate utility propagated the data successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4531S: The Stage Propagate utility failed.
- Explanation: The Stage Propagate utility failed due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4532S: The Stage Copy utility is copying the data for the site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4533S: The Stage Copy utility copied the site tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4534S: The Stage Copy utility failed to copy the data for the site tables.
- Explanation: The Stage Copy utility failed to copy the data for the site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4535S: The Stage Copy utility is copying the merchant table data.
- Explanation: Status message only.
Action: No action required.
- CMN4536S: The Stage Copy utility copied the merchant tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4537S: The Stage Copy utility failed to copy the merchant tables.
- Explanation: The Stage Copy utility failed to copy the merchant tables from the production database to the staging database.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4545S: The staging server failed to get all active site tables.
- Explanation: The staging server failed to get all active site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4547S: The Stage Copy utility copied table {0} successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4548S: The Stage Copy utility failed to copy table {0}.
- Explanation: The Stage Copy utility failed to copy the table from the production database to the staging database.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4550S: Starting the Stage Copy utility.
- Explanation: Status message only.
Action: No action required.
- CMN4553S: The staging server was unable to update the KEYS table.
- Explanation: The staging server was unable to update the KEYS table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4554S: The Stage Copy utility failed to copy the data.
- Explanation: The Stage Copy utility failed to copy data from the production database to the staging database.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4555S: The Stage Copy utility copied the data successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4567S: The staging server failed to get all merchant tables.
- Explanation: The staging server failed to get all merchant tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4571S: The staging server failed to get all site tables.
- Explanation: The staging server failed to get all site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4573S: The staging server got all merchant and site tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4574S: The staging server failed to get all merchant and site tables.
- Explanation: The staging server failed to get all merchant and site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4578S: Cleaning the merchant tables.
- Explanation: Status message only.
Action: No action required.
- CMN4579S: The staging server failed to clean the merchant tables.
- Explanation: The staging server failed to clean the merchant tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4580S: The staging server is cleaning the site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4581S: The staging server cleaned the site tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4582S: The staging server was unable to clean the site tables.
- Explanation: The staging server was unable to clean the site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4583S: The staging server is cleaning the STAGLOG table.
- Explanation: Status message only.
Action: No action required.
- CMN4584S: The staging server cleaned the STAGLOG table successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4585S: The staging server failed to clean the STAGLOG table.
- Explanation: The staging server failed to clean the STAGLOG table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4586S: The Database Cleanup utility failed to get child table for {0}
- Explanation: Database Cleanup utility could not get the child table according to the referential constraints.
Action: Please check Database Cleanup utility log file to identifiy the problem.
- CMN4587S: The Stage Propagate utility is propagating the site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4588S: The Stage Propagate utility propagated the site tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4589S: The Stage Propagate utility failed to propagate the site tables.
- Explanation: The Stage Propagate utility failed to propagate the site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4590S: Propagating merchant tables for merchant {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4591S: The Stage Propagate utility propagated the merchant tables for merchant {0} successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4592S: The Stage Propagate utility failed to propagate the merchant tables for merchant {0}.
- Explanation: The Stage Propagate utility failed to propagate data for the merchant due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4599S: The Stage Propagate utility is propagating table {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4600S: The Stage Propagate utility propagated the data for table {0} successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4601S: The Stage Propagate utility failed for table {0}.
- Explanation: The Stage Propagate utility failed to propagate the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4603S: The Stage Propagate utility failed to propagate all changed rows.
- Explanation: The Stage Propagate utility failed to propagate all changed rows due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4606S: The staging server was unable to update the STAGLOG table.
- Explanation: The staging server was unable to update the STAGLOG table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4608S: The Stage Propagate utility failed to propagate all merchant data.
- Explanation: The Stage Propagate utility failed to propagate the merchant data due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4609S: The Stage Propagate utility propagated all merchant data successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4613S: The staging server failed to get all active merchant tables.
- Explanation: The staging server failed to get all active merchant tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4615S: The Stage Check utility has completed successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4616S: The Stage Check utility failed.
- Explanation: The Stage Check utility failed due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4617S: The Stage Check utility is verifying the site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4618S: The Stage Check utility verified the site tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4619S: The Stage Check utility failed to verify the site tables.
- Explanation: The Stage Check utility failed to verify the site tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4620S: The Stage Check utility is verifying the merchant tables.
- Explanation: Status message only.
Action: No action required.
- CMN4621S: The Stage Check utility verified the merchant tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4622S: The Stage Check utility failed to verify the merchant tables.
- Explanation: The Stage Check utility failed to verify the merchant tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4624S: The Stage Check utility verified all merchant tables successfully.
- Explanation: All merchant tables contain the same data on both the staging server and the production server.
Action: No action required.
- CMN4626S: The Stage Check utility failed to verify table {0}.
- Explanation: The Stage Check utility failed to verify the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4627S: The Stage Check utility failed to verify all merchant tables.
- Explanation: The Stage Check utility failed to verify all merchant tables due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4630S: The staging server failed to get the primary key.
- Explanation: The staging server failed to get the primary key due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4631S: Starting the Stage Check utility.
- Explanation: Status message only.
Action: No action required.
- CMN4633S: The Stage Check utility is verifying table {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4669S: The staging server cleaned the merchant tables successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4670S: The Database Cleanup utility could not finish the assigned task.
- Explanation: Status message only.
Action: Please check Database Cleanup utility log file, and run again.
- CMN4671S: The Database Cleanup utility has started to clean object {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4672S: The Database Cleanup utility cleaned object {0} successfully
- Explanation: Status message only.
Action: No action required.
- CMN4673S: The Database Cleanup utility failed to clean object {0}
- Explanation: Status message only.
Action: No action required.
- CMN4674S: The Database Cleanup utility checking object {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4675S: The Database Cleanup utility finished checking object {0} successfully
- Explanation: Status message only.
Action: No action required.
- CMN4676S: The Database Cleanup utility failed to check object {0}
- Explanation: Status message only.
Action: Please check Database Cleanup utility log file.
- CMN4679S: The Database Cleanup utility failed to get SQL statements for object {0}
- Explanation: Database Cleanup utility could not get SQL statements from the CLEANCONF table for the specified object.
Action: Check the CLEANCONF table and ensure that the SQL statements for the specified object exist.
- CMN4680S: Generating the script to clean site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4681S: Generating the script to clean the merchant tables.
- Explanation: Status message only.
Action: No action required.
- CMN4682S: The script to clean merchant tables was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4683S: The script to clean merchant tables failed to generate.
- Explanation: The script to clean the merchant tables failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4684S: The script to clean the site tables was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4685S: The script to clean the site tables failed to generate.
- Explanation: The script to clean the site tables failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4686S: The Stage Copy utility script was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4687S: The Stage Copy utility script failed to generate.
- Explanation: The Stage Copy utility script generation failed due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4688S: Generating the Stage Copy utility script.
- Explanation: Status message only.
Action: No action required.
- CMN4689S: The script to copy the site tables was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4690S: The script to copy the site tables failed to generate.
- Explanation: The script to copy the site tables failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4691S: The script to copy the merchant tables was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4692S: The script to copy the merchant tables failed to generate.
- Explanation: The script to copy the merchant tables failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4693S: Generating the script to copy merchant tables.
- Explanation: Status message only.
Action: No action required.
- CMN4694S: Generating the script to copy site tables.
- Explanation: Status message only.
Action: No action required.
- CMN4700S: The Database Cleanup utility is updating table {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4702S: The Database Cleanup utility failed to update table {0}
- Explanation: Status message only.
Action: No action required.
- CMN4703S: The staging server failed to get all tables which require unique index verification.
- Explanation: The staging server failed to get all tables which require unique index verification due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4704S: The Stage Check utility has completed verifying the unique indexes.
- Explanation: Status message only.
Action: No action required.
- CMN4705S: The Stage Check utility is verifying the unique indexes.
- Explanation: Status message only.
Action: No action required.
- CMN4706S: The Stage Check utility failed to verify the unique indexes.
- Explanation: The Stage Check utility failed to verify the unique indexes due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4707S: The Stage Check utility failed to verify the unique indexes for table {0}.
- Explanation: The Stage Check utility failed to verify the unique indexes for the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4708S: The Stage Check utility is verifying the unique indexes for table {0}.
- Explanation: The Stage Check utility is comparing the unique index data between the staging table and the production table.
Action: No action required.
- CMN4709S: The staging server failed to get the number of unique indexes for table {0}.
- Explanation: The staging server failed to get the number of unique indexes for the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4710S: The staging server failed to get the unique index key for table {0}.
- Explanation: The staging server failed to get the unique index key for the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4711S: The Stage Check utility is verifying the unique index on table {0}.
- Explanation: The Stage Check utility is comparing the unique index data between the staging table and the production table.
Action: No action required.
- CMN4712S: The staging server failed to get the SQL for delta changes on table {0}.
- Explanation: The staging server failed to get the SQL for delta changes on the table due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4713S: Creating the trigger on the staging database.
- Explanation: Status message only.
Action: No action required.
- CMN4714S: The trigger failed to create on the staging database.
- Explanation: The staging trigger creation failed due to a syntax error in the trigger file.
Action: Go through the screen output to identify which trigger creation failed. Check the trigger syntax in the wcs.stage.triggers.sql file.
- CMN4715S: The trigger was created on the staging database successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4716S: The staging server is dropping the trigger from the staging database.
- Explanation: Status message only.
Action: No action required.
- CMN4717S: The trigger was dropped from the database successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4718S: The staging server was unable to drop the trigger from the staging database.
- Explanation: The staging server cannot drop the staging trigger due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4719S: Generating script to drop the trigger.
- Explanation: Status message only.
Action: No action required.
- CMN4720S: The script to drop the trigger failed to generate.
- Explanation: The script to drop the trigger failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4721S: The script to drop the trigger was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4722S: Generating script to create the trigger.
- Explanation: Status message only.
Action: No action required.
- CMN4723S: The script to create the trigger failed to generate.
- Explanation: The script to create the trigger failed to generate due to a system error.
Action: Refer to the staging server log file for detailed information on the cause of the error.
- CMN4724S: The script to create the trigger was generated successfully.
- Explanation: Status message only.
Action: No action required.
- CMN4726S: The Database Cleanup utility could not get store path prefix.
- Explanation: The Database Cleanup utility could not get the store path prefix located in the file whose name is passed by the parameter "-instance"
Action: Check the file name passed by the parameter "-instance"
- CMN4728S: The Database Cleanup utility failed to generate asset deletion script for table {0}.
- Explanation: The Database Cleanup utility could not generate a deletion script.
Action: No action required
- CMN4729S: The Database Cleanup utility failed to get asset path from database.
- Explanation: The Database Cleanup utility could not get the required filenames or directories from the database
Action: No action required
- CMN4730S: The Database Cleanup utility saved the asset path: {0}.
- Explanation: The filenames or directories were retrieved from the database.
Action: No action required
- CMN4732S: WebSphere Commerce instance file name : {0}.
- Explanation: Status message only.
Action: No action required.
- CMN4733S: Get JDBC configuration from {0}.
- Explanation: The Database Cleanup utility is getting the JDBC drivers from the configuration file.
Action: No action is required
- CMN4734S: The Database Cleanup utility will use the JDBC driver: {0}.
- Explanation: The Database Cleanup utility will use the JDBC driver "{0}" to connect to the database.
Action: No action required.
- CMN4735S: The Database Cleanup utility will use the JDBCUrlPrefix: {0}.
- Explanation: The JDBCUrlPrefix "{0}" is to be used to connect to the database.
Action: No action required.
- CMN4736S: The Database Cleanup utility will use the database type: {0}.
- Explanation: The database type to which the Database Cleanup utility will connect.
Action: No action required
- CMN4737S: The system failed to load the JDBC configuration data.
- Explanation: The Database Cleanup utility could not load the JDBC drivers from the customizer file.
Action: Check the parameters in the cutomizer file.
- CMN5105W: File {0} cannot be found.
- Explanation: The specified file cannot be found.
Action: Check to see if there are any messages that follow this one and give more detailed information.
- CMN5500D:
- Explanation:
Action: No action required.
- CMN5500E:
- Explanation: The instance can not be added from the command line. It may be caused by the Configuration Manager server process being stopped during processing or there are problems with the input instance XML file.
Action: Check the Configuration Manager server to make sure it is running properly, and that the input instance XML file contains no syntax errors and all the attributes values are correct.
- CMN5500I:
- Explanation:
Action: No action required.
- CMN5500S:
- Explanation: The activity and status of creating the database are logged in the log file.
Action: Refer to the log file for the status of creating the database.
- CMN5500W:
- Explanation: The WebSphere Commerce Configuration Manager encountered a problem while running the API. The instance user profile may not be set up correctly. The instance may not have enough authority to be started successfully.
Action: Make sure the instance user profile has access to function QIBM_EJB_SERVER_FUNC in product QIBM_EJB_PRODUCT. This can be manually set up through the Application Administration dialog from the iSeries Navigator tool.
- CMN5501D:
- Explanation:
Action: No action required.
- CMN5501E:
- Explanation: There was a problem removing an instance from the command line configuration tool. It may be caused by the instance file resources being used by running processes or the instance does not exist.
Action: Check to make sure the instance exists and that there are no running process reading from the instance's directory.
- CMN5501I:
- Explanation:
Action: No action required.
- CMN5501S:
- Explanation: The status and activities of populating database with Blaze repository are logged in the log file.
Action: Refer to the log file for details of populating database with Blaze repository.
- CMN5502D:
- Explanation:
Action: No action required.
- CMN5502E:
- Explanation: An invalid input instance XML file was entered or the file does not exist when using the command line configuration tool.
Action: Check to make sure the input instance XML file exists and it is well-formed.
- CMN5502I:
- Explanation:
Action: No action required.
- CMN5502S:
- Explanation: The activity and status of populating the instance database are logged in the log file.
Action: Refer to the log file for the status of populating the instance database.
- CMN5503D:
- Explanation:
Action: No action required.
- CMN5503E:
- Explanation: An invalid command was entered when using the command line configuration tool.
Action: Check the syntax of the input command. The following is the syntax of the valid commands. addInstance [instance xml file location] deleteInstance [instance name] updateInstance [modified xml file location] getInstances getInstanceInfo [instance name] getInstanceConfig [instance name] [[filename to print the instance xml file to]] help exit
- CMN5503I:
- Explanation:
Action: No action required.
- CMN5503S:
- Explanation: The activity and status of populating the instance database with multi-language support are logged in the log file.
Action: Refer to the log file for the status of populating the instance database.
- CMN5504D: Configuring HTTP Server.
- Explanation:
Action: No action required.
- CMN5504E:
- Explanation: There was a missing parameter when using the command line configuration tool.
Action: Check the syntax of the input command. The following is the syntax of the valid commands. addInstance [instance xml file location] deleteInstance [instance name] updateInstance [modified xml file location] getInstances getInstanceInfo [instance name] getInstanceConfig [instance name] [[filename to print the instance xml file to]] help exit
- CMN5504I:
- Explanation:
Action: No action required.
- CMN5505D: Configuring Netscape Enterprise Server.
- Explanation:
Action: No action required.
- CMN5505E:
- Explanation: An attempt was made to update an instance but the the input instance name can not be found in the instance list.
Action: Check to make sure the specified instance name exists on the system.
- CMN5505I:
- Explanation:
Action: No action required.
- CMN5505S:
- Explanation:
Action: No action required.
- CMN5506D: Configuring Lotus Domino Web Server.
- Explanation:
Action: No action required.
- CMN5506E:
- Explanation: An invalid input was entered for the instance default language in the input instance XML file during command line instance creation.
Action: Check the instance default language in the input instance XML file. Valid input are: -1, -2, -3, -4, -5, -6, -7, -8, -9 and -10 with the corresponding language listed below: -1 English -2 French -3 German -4 Italian -5 Spanish -6 Brazilian -7 Simplified Chinese -8 Traditional Chinese -9 Korean -10 Japanese
- CMN5506I:
- Explanation:
Action: No action required.
- CMN5506S:
- Explanation:
Action: No action required.
- CMN5507D: Configuring Microsoft Internet Information Services.
- Explanation:
Action: No action required.
- CMN5507E:
- Explanation: An invalid value in the input instance XML was specified for the use WebSphere Commerce Payments option.
Action: Check to make sure the input instance XML file contains valid values for the use WebSphere Commerce Payments option. Valid input is: yes, no.
- CMN5507I:
- Explanation:
Action: No action required.
- CMN5507S:
- Explanation:
Action: No action required.
- CMN5508D: Writing configuration file out to: {0}
- Explanation:
Action: No action required.
- CMN5508I:
- Explanation:
Action: No action required.
- CMN5508S:
- Explanation:
Action: No action required.
- CMN5509D: Entry.
- Explanation:
Action: No action required.
- CMN5509E:
- Explanation: While deleting the instance, the Commerce Server Web aliases for the instance could not be deleted from the IBM HTTP Server configuration file (httpd.conf).
Action: Remove the instance specific blocks manually from the httpd.conf file.
The instance specific blocks start with ########## IBM WebSphere Commerce (Do not edit this section) ################# and end with ########## End of IBM WebSphere Commerce (Do not edit this section) ##########. - CMN5509I:
- Explanation:
Action: No action required.
- CMN5509S:
- Explanation:
Action: No action required.
- CMN5510D: Exit.
- Explanation:
Action: No action required.
- CMN5510I:
- Explanation:
Action: No action required.
- CMN5510S:
- Explanation:
Action: No action required.
- CMN5511D: Setting component name to {0}
- Explanation:
Action: No action required.
- CMN5511E:
- Explanation: The content of the Configuration Manager initialization file (WC_install_directory/instances/wcs_instances) might be corrupted.
Action: The instance can be removed manually. /n1. Under the [instance] tag in the wcs_instances file, locate a line that starts with the instance name to be deleted. /n2. If the line exists, remove the line. /n3. Remove the instance directory from the WC_install_directory/instances directory.
- CMN5511I:
- Explanation:
Action: No action required.
- CMN5511S:
- Explanation:
Action: No action required.
- CMN5512D:
- Explanation:
Action: No action required.
- CMN5512E:
- Explanation: File I/O was not successful in the FTP session.
Action: Check if the directory and the file name are correct.
- CMN5512I:
- Explanation:
Action: No action required.
- CMN5512S: Importing the tools.
- Explanation:
Action: No action required.
- CMN5513D: Creating iSeries instance folders.
- Explanation:
Action: No action required.
- CMN5513E: There was a problem in the FTP session
- Explanation: There was a problem in the FTP session between Configuration Manager and the remote machine.
Action: Check the FTP hostname, port number, user ID, and password. Also, check if the FTP server and client are started.
- CMN5513I: The Oracle database does not exist yet. Please create one before attempting to populate it
- Explanation:
Action: No action required.
- CMN5513S: Importing the WebSphere Catalog Manager.
- Explanation:
Action: No action required.
- CMN5514D: Toolbox JDBC driver customizer file is used.
- Explanation: The WebSphere Commerce instance being created will use the iSeries Toolbox JDBC driver during store deployment.
Action: No action required.
- CMN5514I: The database was successfully created.
- Explanation:
Action: No action required.
- CMN5514S: Finished importing.
- Explanation:
Action: No action required.
- CMN5515D: Calling QSYCHFUI API.
- Explanation:
Action: No action required.
- CMN5515E: Instance was not created. Please correct the error before retrying.
- Explanation: The WebSphere Commerce instance was not created.
Action: One or more errors have occured in configuring components such as the database, WebSphere Appplication Server, and Web server.
Refer to the extended messages for the errors for more information. - CMN5515I: The currently active database type has changed. Please change your WebSphere settings accordingly to reflect this
- Explanation:
Action: No action required.
- CMN5515S: Starting WebSphere Commerce Application Server. Please check the log file for more details: {0}
- Explanation:
Action: No action required.
- CMN5516D: QSYCHFUI API completed successfully.
- Explanation:
Action: No action required.
- CMN5516E: Instance was not modified. Please correct the error before retrying.
- Explanation: The WebSphere Commerce instance was not created.
Action: One or more errors have occured in configuring components such as the database, WebSphere Appplication Server, and Web server.
Refer to the extended messages for the errors for more information. - CMN5516I: Successfully configured the External Server section.
- Explanation:
Action: No action required.
- CMN5516S: Finished starting the WebSphere Commerce Enterprise Application server. Please check the log for more information: {0}
- Explanation:
Action: No action required.
- CMN5517D: Toolbox JDBC driver is used.
- Explanation: The WebSphere Commerce instance being created will use the iSeries Toolbox JDBC driver to connect to the database.
Action: No action required.
- CMN5517E: Cannot find XML file {0}
- Explanation: The specified file was not found on the file system.
Action: Check whether the file exists. If the file exists, check if the file has the correct file permissions. If the file does not exist and no backup file is available, try to reinstall the product.
- CMN5517I: Instance was successfully modified.
- Explanation:
Action: No action required.
- CMN5518D: Native JDBC driver is used.
- Explanation: The WebSphere Commerce instance being created will use the native iSeries JDBC driver to conntect to the database.
Action: No action required.
- CMN5518E: The instance name, {0}, is already in use. Please pick another instance name.
- Explanation: The specified instance name is in use and each instance must have a unique instance name.
Action: Specify an unique instance name when creating an instance.
- CMN5518I: Instance was successfully created.
- Explanation:
Action: No action required.
- CMN5519D: Successfully updated the instance user profile.
- Explanation:
Action: No action required.
- CMN5519I: Successfully configured the Listener section.
- Explanation:
Action: No action required.
- CMN5520D: Logging into the FTP server.
- Explanation:
Action: No action required.
- CMN5520E: WebSphere Commerce Payments not installed.
- Explanation: WebSphere Commerce Payments needs to be installed before it can be configured.
Action: Check to make sure that WebSphere Commerce Payments is installed. If not, run the WebSphere Commerce setup program and select to install the WebSphere Commerce Payments component.
- CMN5520I: Successfully configured the Login Timeout section.
- Explanation:
Action: No action required.
- CMN5521D: FTP: Setting the file type to {0}
- Explanation:
Action: No action required.
- CMN5521I: Successfully configured Logging for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5522D: FTP: Changing the directory to {0}
- Explanation:
Action: No action required.
- CMN5522E: Failed to find an active WebSphere Commerce Payments database.
- Explanation: There was a problem finding the active WebSphere Commerce Payments database.
Action: Check to make sure the database server is running properly and that the WebSphere Commerce Payments database contains all the required tables.
- CMN5522I: Successfully configured LUM for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5523D: FTP: Get {0}
- Explanation:
Action: No action required.
- CMN5523E: Failed to create or configure WebSphere Commerce Payments instance for WebSphere Commerce.
- Explanation: There was a problem creating or configuring a WebSphere Commerce Payments instance.
Action: Check to make sure all the required services are running properly and there is enough temporary space.
- CMN5523I: Successfully configured MemberSubSystem for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5524D: FTP: Put {0}
- Explanation:
Action: No action required.
- CMN5524E: The WebSphere Commerce Payments profile path is invalid.
- Explanation: The entered WebSphere Commerce Payments profile path is invalid.
Action: Check to make sure the entered WebSphere Commerce Payments profile path is valid.
- CMN5524I: Successfully configured Messaging for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5525D: Quitting the FTP connection.
- Explanation:
Action: No action required.
- CMN5525E: The IP address of the host name could not be determined.
- Explanation: There was a problem determining the IP address of the host name.
Action: Check to make sure the WebSphere Commerce Payments machine is on the same network as the WebSphere Commerce machine.
- CMN5525I: Enabling Password Invalidation.
- Explanation:
Action: No action required.
- CMN5526E: The Web server port is out of bounds.
- Explanation: The Web server port is out of bounds.
Action: Check to make sure the port number is between 0 and 65535.
- CMN5526I: Disabling Password Invalidation.
- Explanation:
Action: No action required.
- CMN5527E: The IP address of the SOCKS host name could not be determined.
- Explanation: The entered WebSphere Commerce Payments SOCKS host name is invalid.
Action: Please make sure the entered WebSphere Commerce Payments SOCKS host name is valid and that the machine is the same network.
- CMN5527I: Successfully configured the Password Invalidation component.
- Explanation:
Action: No action required.
- CMN5528E: The SOCKS port number is out of bounds.
- Explanation: The entered WebSphere Commerce Payments SOCKS port number is out of bounds.
Action: Check to make sure the port number is between 0 and 65535.
- CMN5528I: Successfully configured the Password Protected Commands section.
- Explanation:
Action: No action required.
- CMN5529E: Failed to export WebSphere Application Server configuration.
- Explanation: There was a problem exporting current configuration from the WebSphere Application Server.
Action: Check to make sure the WebSphere Application Server information is correct for the instance and that the WebSphere Application Server is running properly.
- CMN5529I: Successfully configured WebSphere Commerce Payments for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5530E: There was an error configuring the WebSphere Commerce transports section.
- Explanation: There was a problem configuring the WebSphere Commerce transports section. It may be caused by invalid manual updates to the instance XML file.
Action: Check to make sure that there are no invalid manual updates to the instance XML file.
- CMN5530I: Successfully configured the Protected Parameters section.
- Explanation:
Action: No action required.
- CMN5531E: Failed to connect to WebSphere Application Server. Ensure that the port number is correct.
- Explanation: There was a problem connecting to the WebSphere Application Server.
Action: Check to make sure the WebSphere Application Server is started on the port specified in the WebSphere node of your WebSphere Commerce instance XML file.
- CMN5531I: Sucessfully configured the WebSphere Commerce registry.
- Explanation:
Action: No action required.
- CMN5532E: WAS is not started.
- Explanation: The WebSphere Application Server is not started during the configuration of WebSphere Commerce.
Action: Check to make sure the WebSphere Application Server is started before attempting to configure WebSphere Commerce.
- CMN5532I: Successfully configured the search parameters for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5533E: Domino supports only one SSL port. Please enter 443 for the tools port number.
- Explanation: When using WebSphere Commerce with the Lotus Domino Web server, all internal tools port numbers must be set to 443 due to a limitation of Domino.
Action: Please specify to use port 443 for all internal tools ports when using Lotus Domino Web server.
- CMN5533I: Successfully configured the WebSphere Commerce session management module.
- Explanation:
Action: No action required.
- CMN5534E: There was an error importing the main portion of the EJBs.
- Explanation: There was a problem importing the WebSphere Commerce Enterprise Java Beans. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5534I: Successfully configured QuickPlace for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5535E: There was an error importing the WebSphere Commerce application server.
- Explanation: There was a problem importing the WebSphere Commerce application server. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly.
- CMN5535I: Successfully configured Sametime for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5536E: There was an error importing the WebSphere Commerce enterprise application.
- Explanation: There was a problem importing the WebSphere Commerce Enterprise Application. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5536I: Successfully configured Security for WebSphere Commerce. You must restart your WebSphere Application Server administration server before the changes will take effect.
- Explanation:
Action: No action required.
- CMN5537E: There was an error importing the virtual hosts.
- Explanation: There was a problem importing the WebSphere Commerce virtual hosts. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly.
- CMN5537I: Successfully configured Trading for WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5538E: There was an error importing the data sources.
- Explanation: There was a problem importing the WebSphere Commerce datasources. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly.
- CMN5538I: Restart your Web server to apply the changes to your Web server configuration file.
- Explanation:
Action: No action required.
- CMN5539E: There was an error importing the EJBs.
- Explanation: There was a problem importing the WebSphere Commerce Enterprise Java Beans. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there are enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5539I: Successfully restarted IBM HTTP Server.
- Explanation:
Action: No action required.
- CMN5540E: There was an error importing the demo stores.
- Explanation: There was a problem importing the WebSphere Commerce Stores web module. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5540I: Please make sure that your remote Web server is properly configured for operation with WebSphere Commerce.
- Explanation:
Action: No action required.
- CMN5541E: There was an error importing the tools.
- Explanation: There was a problem importing the WebSphere Commerce Tools web module. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5541I: Successfully configured the Web server.
- Explanation:
Action: No action required.
- CMN5542E: There was an error importing the WebSphere Catalog Manager.
- Explanation: There was a problem importing the WebSphere Commerce Catalog Manager Web Editor Web module. The WebSphere Application Server information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information for the instance is correct and the WebSphere Application Server is running properly. Also make sure there is enough temporary space in your system temp directory. Please refer to the install guide for the amount of free space required.
- CMN5542I: Successfully configured the secure server.
- Explanation:
Action: No action required.
- CMN5543E: There was an error starting the application servers.
- Explanation: There was a problem starting the WebSphere Commerce application server. The WebSphere Application Server information or the database information for the instance may not be accurate.
Action: Check to make sure the WebSphere Application Server information and the database information for the instance is correct and the WebSphere Application Server and the database server are running properly.
- CMN5543I: Successfully configured the non-secure server.
- Explanation:
Action: No action required.
- CMN5544E: There was an error starting the WC application server. Check log file:
- Explanation: There was a problem starting the WebSphere Commerce Application Server.
Action: Please check the wcs.log file located under the instance logs directory. Possible causes could be incorrect database logon information for the WebSphere Commerce datasource or invalid entries in the instance XML file.
- CMN5544I: Successfully configured the secure tools server.
- Explanation:
Action: No action required.
- CMN5545I: Please apply the configuration changes from the iPlanet admin server and restart your servers.
- Explanation:
Action: No action required.
- CMN5546E: Cannot configure the Web server.
- Explanation: The Web server could not be configured.
Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.
- CMN5546I: Please configure your Domino WebServer to enable X.509 certificates
- Explanation:
Action: No action required.
- CMN5547E: Cannot configure the secure server.
- Explanation: The secure server could not be configured.
Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.
- CMN5547I: Successfully modified the WebSphere Application Server properties
- Explanation:
Action: No action required.
- CMN5548E: Cannot configure the non-secure server.
- Explanation: The non-secure server could not be configured.
Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.
- CMN5548I: Successfully configured the Cross Site Scripting Protection section.
- Explanation:
Action: No action required.
- CMN5549E: Cannot configure the secure tools server.
- Explanation: The tools server could not be configured.
Action: One or more Web server configuration related errors have occured. Please refer to the extended messages for the related errors.
- CMN5549I: Successfully changed authorities on the instance folders.
- Explanation:
Action: No action required.
- CMN5550E: There was a problem restarting IBM HTTP Server.
- Explanation: Configuration Manager could not restart HTTP Server.
Action: Start the Web server manually. In addition, check: whether the value of "ServerRoot" in the httpd.conf file is correct, and whether any other application is hold up the port HTTP Server is trying to use.
- CMN5550I: Successfully created instance user profile.
- Explanation: A user profile with the instance name should now exist on the iSeries system.
Action: No action required.
- CMN5551E: SSL is not enabled.
- Explanation: The sample SSL configuration block in the HTTP Server's configuration file (httpd.conf) is not found.
Action: Check whether "Listen 443" statement exists before the instance Web aliases configuration block in the httpd.conf file. If it does not, add "Listen 443" in the httpd.conf file. Note: Listen 443 should not be commented out. Refer to the httpd.conf.sample file for the right location of "Listen 443" statement location.
- CMN5551I: Successfully created the instance schema.
- Explanation: If a local database is used, a database library with the instance name should now exist on the iSeries system where WebSphere Commerce is installed. If a remote database is used, the database library should exist on the remote iSeries system.
Action: No action required.
- CMN5552I: The database does not exist yet.
- Explanation:
Action: No action required.
- CMN5555E: Cannot find remote Configuration Manager server.
- Explanation: There was a problem connecting to the Configuration Manager server.
Action: Check to make sure the Configuration Manager server is running on the port specified. The default port for the Configuration Manager is 1099. If it is started on a non-default port, please use the -port option when running the Configuration Manager client.
- CMN5556E: Could not load the class to configure this component.
- Explanation: There was a problem loading a class for the Configuration Manager.
Action: Check to make sure the wcsconfig.jar file is in the classpath. If you are using a non-root user to run the Configuration Manager on UNIX, please make sure the non-root user has read and execute permission on the file.
- CMN5558E: Cannot initialize logging system.
- Explanation: The logging initialization file (WC_install_directory/instances/CM_log.xml) might be missing or contain invalid XML.
Action: Check if the XML in this file is valid. If the file does not exist and you do not have a backup file, you should reinstall WebSphere Commerce.
- CMN5559E: Failed to connect to the database using the Oracle SID.
- Explanation: There was a problem connecting to the Oracle database using the specified information.
Action: Check to make sure the Oracle database is running properly on the specified host/port. Also check to make sure the specified logon information including the Oracle SID is correct.
- CMN5560E: Failed to connect to the database using the database name.
- Explanation: There was a problem connecting to the Oracle database using the specified information.
Action: Check to make sure the Oracle database is running properly on the specified host/port. Also check to make sure the specified logon information including the Oracle SID is correct.
- CMN5561E: There was a problem creating the database
- Explanation: Configuration Manager could not create the database for the instance.
Action: Make sure the system classpath and JDBC level are correct for the database . Also, check the createdb.log file in the instance's logs directory.
- CMN5562E: There was a problem populating the database
- Explanation: Configuration Manager could not populate the database for the instance.
Action: Make sure the system classpath and JDBC level are correct for the database . Also, check the createdb.log file in the instance's logs directory.
- CMN5564E: This database name is reserved. Please choose another one.
- Explanation: The database name, VAJ_demo, is reserved for WebSphere Commerce.
Action: Choose another database name.
- CMN5565E: There was a problem configuring the External Server section.
- Explanation: There was a problem configuring the External Server section. It may be due to a problem connecting to the WebSphere Commerce database or invalid manual updates to the instance XML file.
Action: Check to make sure the specified WebSphere Commerce database logon information is correct and the database server is running properly. Also make sure there are no invalid manual updates to the instance XML file.
- CMN5566E: DB2 not installed
- Explanation: Configuration Manager detected that DB2 is not installed on the database machine.
Action: Install DB2 and make sure it is functioning correctly.
- CMN5567E: Oracle not installed
- Explanation: Configuration Manager detected that Oracle is not installed in the database machine.
Action: Install Oracle database and make sure it functions correctly.
- CMN5570E: Copying files from {0} to {1}
- Explanation:
Action: No action required.
- CMN5571E: {0} and {1} are already in the configuration file.
- Explanation: The CGI block in the configuration file has already been configured.
Action: No action required.
- CMN5572E: Cannot read file {0}
- Explanation: Configuration Manager cannot read the file.
Action: Check if the permissions on the file are correct. Also, check if the file is corrupted.
- CMN5573E: Cannot create file {0}
- Explanation: The file could not be created in the specified directory.
Action: Check the access permissions of the directory.
- CMN5574E: Cannot copy file {0}
- Explanation: Configuration Manager could not copy the file.
Action: Check if the permissions on the file are correct. Also, check if the file system has enough storage space.
- CMN5575E: Cannot open file {0}
- Explanation: The file was found but could not be opened by Configuration Manager.
Action: Check the permissions of the file.
- CMN5576E: Cannot find file {0}
- Explanation: The file does not exist.
Action: If the file has been backed up, use the back-up file. Also check the file permissions and ownership of the file.
- CMN5577E: There was an error creating the database.
- Explanation: The WebSphere Commerce Configuration Manager cannot create the schema for the instance.
Action: Check the schema.err log file in the instance log folder for more details. Also check if the instance user profile is created.
- CMN5578E: Failed to create instance user profile.
- Explanation: The WebSphere Commerce Configuration Manager encountered a problem while creating the instance user profile. The instance creation cannot continue until this is resovled.
Action: Check the user profile used to launch the Configuration Manager server to ensure it has the authority to create user profiles.
- CMN5579E: Failed to update the instance user profile.
- Explanation: The WebSphere Commerce Configuration Manager encountered a problem while setting the current library of the instance user profile to be the instance schema.
Action: Before starting the WebSphere Commerce instance, change the instance user profile manually to set the current library to be the instance schema.
- CMN5580E: The language selected, {0}, is not a supported language.
- Explanation: The language selected is not supported by WebSphere Commerce.
Action: Refer to the WebSphere Commerce documentation for a list of supported languages.
- CMN5581E: There was an error getting the installation path.
- Explanation: There was a problem getting the WebSphere Commerce installation path.
Action: Make sure the product is installed correctly and try the task again.
- CMN5957E: A failure occurred while executing the Payments Configurator function.
- Explanation: An unknown failure has occurred while trying to execute the Payments operation.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on failure.
- CMN5958E: The Payments Configurator could not be initialized.
- Explanation: The Payments Configurator failed to initialize for unknown reasons.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the failure occurred.
- CMN5959E: The password specified for Payments instance {0} is not valid.
- Explanation:
Action: Specify the correct password for this Payments instance.
- CMN5960E: The value for the {0} parameter is null.
- Explanation: The value for the parameter was passed as null or an empty string and is not valid for this API.
Action: Specify a value other than null or empty string for the parameter.
- CMN5961E: Payments instance {0} appears to already exist.
- Explanation: The Payments instance specified appears to already exist on the system.
Action: If a Payments instance with this name appears to exist, choose a different name for the new Payments instance. If the instance does not appear to exist, verify the following: 1. The database specified is not being used by another Payments instance. 2. The PaymentsInstance.properties file in the Payments instance directory does not exist. Rename the file to PaymentsInstance.properties.old if it does exist. 3. The Payments tables do not exist in the database. If the tables do exist, verify again that the tables do not belong to another Payments instance. If they do not belong to another Payments instance, the tables can be deleted. Back up the tables before they are deleted.
- CMN5962E: Payments instance {0} does not exist on the system.
- Explanation: The Payments instance specified does not appear to exist on this system. If the instance should exist, it may be corrupted.
Action: No action is needed if the instance should not exist. Verify the Payments instance name was correctly specified. Verify that the PaymentsInstance.properties file exists in the Payments instance directory. If this file is missing, the Payments instance is corrupted. Contact your IBM support representative for assistance.
- CMN5963E: The following properties do not have valid values: {0}.
- Explanation: The properties listed contain values that are not valid for the Payments instance.
Action: See the Configuration Manager documentation for valid properties and property values for Payments instance configuration.
- CMN5964E: This function cannot be completed while the Payments instance {1} is started. Stop the instance and try the request again.
- Explanation:
Action: Stop the Payments instance and try the request again. The Payments instance can be stopped through the Configuration Manager, through the WebSphere Administration Console, or with the StopIBMPayServer script.
- CMN5965E: A failure occurred while initializing the database connection.
- Explanation: A connection to the database could not be established for unknown reasons.
Action:
See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the database connection failed. - CMN5966E: A failure occurred while initializing the database connection. Verify the database user name and password are set correctly.
- Explanation: The connection to the database could not be established because the user ID or password appear to be incorrect.
Action: Update the database password for this Payments instance through the Configuration Manager.
- CMN5967E: A failure occurred while initializing the database connection. Verify the JDBC URL is set correctly.
- Explanation: A connection to the database specified in the JDBC URL could not be established. This may indicate a problem with the JDBC URL.
Action: Verify that the database product is running on the system specified in the URL and that the JDBC URL is set correctly.
- CMN5968E: A failure occurred while initializing the database connection. Verify the database name in the JDBC URL is set correctly.
- Explanation: The database specified in the JDBC URL does not appear to exist on the system.
Action: Verify that the database specified in the JDBC URL exists on the system. The database specified must exist for a Payments instance to be created. Use the Database Configuration Manager to create a database for a Payments instance.
- CMN5969E: A failure occurred while initializing the database connection. The JDBC driver failed to load. Verify the JDBC driver is set correctly.
- Explanation: The JDBC driver could not be loaded. This may indicate that the JDBC driver is set incorrectly or that the JDBC driver is not found in the classpath of this program.
Action: Verify that the database product that you are using for this instance is correctly installed and configured. Contact your IBM support representative for further assistance.
- CMN5970E: Payments instance {0} failed to create.
- Explanation: The Payments instance could not be created. The failure most likely occurred while trying to create or configure the Payments database tables.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the instance creation failed.
- CMN5971E: The Payments instance {0} failed to delete properly. The following objects may need to be deleted manually: {1}.
- Explanation: The Payments instance was not successfully deleted because parts of the instance could not be deleted at this time.
Action: Manually remove the objects listed to ensure the instance is properly deleted. Running the delete command against this instance again may fail because parts of the instance have been deleted. If the instance is not properly deleted, running the create command for an instance with the same name may fail because parts of the original instance have not been deleted.
- CMN5972E: Payments instance {0} still has cassettes added. Remove the cassettes before deleting the instance.
- Explanation: A Payments instance cannot be deleted while cassettes are still added to the instance.
Action: Remove the cassettes before deleting the instance. Note that if a cassette is removed, all cassette order data will be lost.
- CMN5973E: Payments instance {0} could not be enabled. Payments return codes are {1}, {2}.
- Explanation: Starting the Payments instance is a two step process. First the WebSphere Application Server for the instance is started and then the Payment Servlet is contacted and given a password so that it can be initialized. The WebSphere Application Server started successfully, the Payment Servlet was contacted, but the Payment instance was not enabled because the Payments Servlet could not be initialized. The return codes indicate the error that occurred in the Payments Servlet.
Action: Look up the return codes in the WebSphere Commerce Payments Programmer's Guide and Reference to determine the cause of the error.
- CMN5974E: Payments instance {0} could not be started. An exception occurred while trying to connect to the Payments Servlet.
- Explanation: A communication error occurred while trying to connect to the Payment Servlet for this Payments instance. This error could result from the following:
1. The Web Server is not started.
2. The Web Server is not configured properly and is not listening on the port specified for the Payments instance.
3. The Payment Servlet failed to start.
4. The WebSphere virtual host list is not correct.
Action: Verify the following: 1. The Web Server is started and listening on the port specified for this Payments instance. 2. The WebSphere Application Server and Payment Servlet started correctly. See the WebSphere logs in the Application Server logs directory for this instance. 3. The WebSphere Application Server plugin-cfg.xml file has the correct entries for the Application Server for this instance. Regenerate the plugin-cfg.xml file if it does not.
- CMN5975E: The Payments instance {0} failed during update.
- Explanation: A failure occurred while trying to update the Payments instance. The failure most likely occurred while trying to access or update the PaymentsInstance.properties file.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the update failed.
- CMN5976E: The following properties cannot be updated in a Payments instance: {0}.
- Explanation: The properties listed are not allowed to be updated for the Payments instance.
Action: Do not attempt to update these properties of a Payments instance.
- CMN5977E: The password change failed for Payments instance {0}.
- Explanation: The password was not changed for the Payments instance. The failure most likely occurred while trying to reinitialize the Payments instance framework tables with the new password.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the password change failed.
- CMN5978E: Cassette {0} does not appear to be installed properly. The following objects are missing: {1}.
- Explanation: The cassette operation could not be executed because the cassette does not appear to be installed properly. The items listed could not be found.
Action: Contact the cassette vendor and report this error.
- CMN5979E: Cassette {0} could not be added to Payments instance {1}. The enterprise application could not be redeployed.
- Explanation: This cassette could not be added to the Payments instance because the WebSphere enterprise application could not be redeployed in the WebSphere Application Server.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.
- CMN5980E: The Add Cassette {0} function failed for Payments instance {1}.
- Explanation: The specified cassette could not be added to the Payments instance.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the cassette failed to add.
- CMN5981E: Cassette {0} already exists for Payments instance {1}.
- Explanation: This cassette could not be added to the Payments instance because it already exists for this instance. The cassette is configured in the Payments tables or has cassette tables in the Payments database. The cassette must be removed from this instance before it can be added again.
Action: No action is needed if the cassette status appears to be added and loadable. If the cassette does not have a loadable status, try the Repair Cassette command. Note that if the cassette is removed, all cassette order data will be lost.
- CMN5982E: The Remove Cassette {0} function failed for Payments instance {1}.
- Explanation: The specified cassette could not be removed from the Payments instance.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the cassette remove failed.
- CMN5983E: Cassette {0} does not exist for Payments instance {1}.
- Explanation: This cassette could not be removed from the Payments instance because it does not exist for this instance. The cassette is not configured in the Payments tables . The cassette must be added to this instance before it can be removed.
Action: No action is needed if the cassette should not exist for this instance. If the cassette does appear to be partially configured for this instance, try the Repair Cassette command and then try to remove the cassette again. Note that if a cassette is removed, all cassette order data will be lost.
- CMN5984E: WebSphere Application Server configuration objects could not be initialized.
- Explanation: The Payments instance could not be configured in WebSphere Application Server because configuration objects for WebSphere could not be initialized.
Action: Verify the WebSphere Application Server product is installed and functioning properly.
- CMN5985E: An exception occurred while trying to configure the WebSphere Application Server.
- Explanation: An exception occured for unknown reasons while trying to configure the WebSphere Application Server.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on the failure.
- CMN5986E: Creation failed for Payments instance {0}. A failure occurred while creating the WebSphere Application Server configuration for the instance.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebSphere configuration failed.
- CMN5987E: The WebSphere enterprise application failed to install for Payments instance {0}.
- Explanation: The Payments instance failed to created because the WebSphere enterprise application could not be installed.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the create failed.
- CMN5988E: The WebSphere enterprise application failed to uninstall for Payments instance {0}.
- Explanation: The Payments instance was not properly deleted. The WebSphere enterprise application could not be uninstalled from WebSphere for this instance.
Action: Manually uninstall the WebSphere enterprise application for this instance from the WebSphere Application Server product to complete the deletion of the Payments instance.
- CMN5989E: The WebSphere enterprise application failed during redeploy for Payments instance {0}.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebSphere configuration failed.
- CMN5989I: Payments instance {0} was redeployed successfully.
- Explanation:
Action: No action required.
- CMN5990E: Update failed for Payments instance {0}. A failure occurred while updating the WebSphere Application Server configuration.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebSphere configuration failed.
- CMN5990I: All Payments instances were redeployed successfully.
- Explanation:
Action: No action required.
- CMN5991E: The WebSphere Application Server for Payments instance {0} failed to start.
- Explanation:
Action: The Payments instance can be manually started with the WebSphere Application Server startServer script. See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the start failed.
- CMN5991I: The {0} cassette was successfully removed from Payments instance {1}.
- Explanation:
Action: No action required.
- CMN5992E: The WebSphere Application Server for Payments instance {0} failed while trying to stop.
- Explanation:
Action: The Payments instance can be manually stopped with the WebSphere Application Server stopServer script. See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the stop failed.
- CMN5992I: The {0} cassette was successfully added to Payments instance {1}.
- Explanation:
Action: No action required.
- CMN5993E: Update failed for Payments instance {0}. The {1} component of the WebSphere configuration failed to update.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebSphere configuration failed.
- CMN5993I: Payments instance {0} was updated successfully.
- Explanation:
Action: No action required.
- CMN5994E: Create failed for Payments instance {0}. The {1} component of the WebSphere configuration failed to create.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebSphere configuration failed.
- CMN5994I: Payments instance {0} was queried successfully.
- Explanation:
Action: No action required.
- CMN5995E: The Payments instance {0} failed to redeploy properly in the WebSphere Application Server.
- Explanation:
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.
- CMN5995I: Payments instance {0} was started successfully.
- Explanation:
Action: No action required.
- CMN5996E: The following Payments instances failed to redeploy properly in the WebSphere Application Server: {0}.
- Explanation: The instances listed failed when the redeploy function was attempted. The failures may have occurred because the Payments instances were still started. The WCSconfig_<timestamp>.log file will show the reason that each Payments instance failed.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.
- CMN5996I: Payments instance {0} was stopped successfully.
- Explanation:
Action: No action required.
- CMN5997E: The WebServer configuration could not be created.
- Explanation: The creation failed for the Payments instance. The WebServer configuration could not be created for unknown reasons.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebServer configuration failed.
- CMN5997I: Payments instance {0} was created successfully.
- Explanation:
Action: No action required.
- CMN5998E: The WebServer configuration could not be updated.
- Explanation: The WebSever configuration could not be updated for unknown reasons. Other applications will not be able to contact the Payment Servlet until the WebServer is properly updated with the current Payments instance configuration.
Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the WebServer configuration failed.
- CMN5998I: Payments instance {0} was deleted successfully.
- Explanation:
Action: No action required.
- CMN5999E: The WebServer configuration could not be deleted.
- Explanation: The Payments instance was not properly deleted. Parts of the WebServer configuration could not be deleted for unknown reasons.
Action: This error should not effect the future creation or deletion of Payments instances. Manually delete the WebServer configuration for this Payments instance if desired. See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the delete failed.
- CMN5999W: Unattended restart could not be enabled because the WebSphere Application Server for Payments instance {0} could not be updated.
- Explanation: The password change for the Payments instance was successful, but the WebSphere Application Server configuration for this instance could not be updated. The Unattended Restart feature has been disabled for this Payments instance.
Action: Go to the Configuration Manager and re-enable the Unattended Restart feature for this instance.
- CMN6222E:
- Explanation: The application tried to create an instance of a class using the method Class.newInstance(), but the current method does not have access to the zero-argument constructor. Another possibility is that the application tried to load a class, but the current method does not have access to the other class because it is in a different package, and it is not declared as 'public'.
Action: Check to ensure the zero-argument constructor exists in the class that the current method tries to instantiate. Also ensure that the class that the current method tried to access is declared 'public' if it is in another package.
- CMN7501E:
- Explanation: A file, %1, required by the WebSphere Commerce problem determination tool cannot be located on your file system.
Action: Ensure that the file %1 exists in your file system, or contact WebSphere Commerce support, quoting the error code and providing the file name.
- CMN7502E:
- Explanation: A JDBC connection cannot be established to the database. The possible causes are:
o There is no JDBC driver available.
o The database name, user ID, or password is incorrect.
Action: o Ensure that the required JDBC driver is loaded and that the CLASSPATH environment variable includes the full path to the JDBC driver. o Verify that the correct database name, user ID, or password have been entered.
- CMN7503E:
- Explanation: The WebSphere Commerce problem determination tool cannot connect to the %1 Web server. Possible reasons are:
o A firewall is preventing the HTTP request to successfully access the Web server.
o The host name of the Web server is incorrect.
Action: o Disable the firewall o Ensure that the host name is entered correctly. If this does not work, try using the fully qualified host name (for example, myhost.mydomain.myorg.com)
- CMN7504E:
- Explanation: The WebSphere Commerce problem determination tool is attempting to access a file which is currently locked.
Action: Ensure that the file is not locked by another process when you run the WebSphere Commerce problem determination tool.
- CMN7505E:
- Explanation: The WebSphere Commerce problem determination tool component cannot check Windows services at this time.
Action: This is an internal program error. Contact WebSphere Commerce support, quoting the error code, and providing exact details of the circumstances under which the error occurs.
- CMN7506E:
- Explanation: The WebSphere Commerce problem determination tool cannot parse the XMLfile.
Action: This is an internal program error. Contact WebSphere Commerce support, providing the XML file that cannot be parsed.
- CMN7507E:
- Explanation: The WebSphere Commerce problem determination tool cannot detect where WebSphere Commerce is installed in your system.
Action: Ensure that the problem determination tool is running on the WebSphere Commerce Server machine.
- CMN7508E: An error has ocurred while attemping the connection to the Web Server.
- Explanation: The WebSphere Commerce problem determination tool cannot establish a connection to the Web server. The possible causes are:
o The hostname entered is invalid
o A firewall is preventing the WebSphere Commerce problem determination tool to establish a connection
Action: To resolve the problem: o Ensure that the correct hostname is specified. If the short name does not work, try using the fully qualified name instead (for example, myhost.mydomain.com). o Disable the firewall.
- CMN7509E: WebSphere Commerce Problem Determination Tool is unable to resolve the local host name in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in resolving the the local host name. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7510E: WebSphere Commerce Problem Determination Tool internal generic catch error caught in: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contect IBM Support.
Action: Contact your IBM Support representative.
- CMN7511E: The value for the {0} parameter is null.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call due to a NullPointerException. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7512E: A remote exception has been caught in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7513E: A runtime exception has been caught when setting the nextStack during the WebSphere Commerce Problem Determination Tool client GUI initialization.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in a GUI initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7514E: ArrayIndexOutOfBoundsException in {0} can be safely ignored.
- Explanation: Status message only.
Action: No action required.
- CMN7515E: The WebSphere Commerce Problem Determination Tool server exits when the WebSphere Commerce Problem Determination Tool client exits.
- Explanation: Status message only.
Action: No action required.
- CMN7516E: An error has ocurred while registering the client callback.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7517E:
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool client was unable to establish a connection to the IBM WebSphere Commerce Problem Determination Tool sever.
Action: The user should check the following: 1) The network between the IBM WebSphere Commerce Problem Determination Tool sever and the IBM WebSphere Commerce Problem Determination Tool client is up and running. 2) The correct host name was specified as the input parameter for the IBM WebSphere Commerce Problem Determination Tool client. If the problem persists, contact your IBM Support representative.
- CMN7518E: An I/O error has occurred while creating the WebSphere Commerce Problem Determination Tool logs.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unable to create the log files due to an I/O exception.
Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access the directory. 3)Ensure that the drive has sufficient space. If the problem persists, contact your IBM Support representative.
- CMN7519E: An I/O error has occurred while clearing the WebSphere Commerce Problem Determination Tool logs.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unable to clear the content of the log files due to an I/O exception.
Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.
- CMN7520E:
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call to update the screen. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7521E: A remote exception has been caught while checking node in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool server was unsuccessful in checking a particular node. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7522E: A remote exception has been caught while getting instance vector in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in parsing the wcs_instance file.
Action: The user should check the following: 1)Check that the CommerceServer55/instances directory exists. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.
- CMN7523E: A remote exception has been caught while setting property in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7524E: A remote exception has been caught while setting the selected options in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7525E: A remote exception has been caught while setting the selected database type in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7526E:
- Explanation: The IBM WebSphere Commerce Problem Determination Tool client was unsuccessful in updating the screen. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM Support representative.
- CMN7527E: A remote exception has been caught while recreating the WebSphere Commerce Problem Determination Tool logs in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unable to recreate the log files during a service reset.
Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access the directory. 3)Ensure that the drive has sufficient space. If the problem persists, contact your IBM Support representative.
- CMN7528E: A remote exception has been caught while setting the selected Web server type in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7529E: There was an error getting the instance of GuiProperties in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in a GUI initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7530E: There was an error invoking DepChecker methods.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7531E: There was an error initializing DepChecker properties.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in a internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7532E: The format of input parameter to {0}: {1} is incorrect.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in parsing the requiredVersions.xml file. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7533E: An I/O error has occurred while scanning {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in scanning the log file due to an I/O exception.
Action: The user should check the following: 1)Check that the full path including the directories of the file exist. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.
- CMN7534E:
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call to write to log files. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7535E: There was an error while initializing the vector for nodeCheckers.
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7536E: An I/O error has occurred while initializing logs in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7537E: An error has occurred while initializing the required software stack table in {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal initialization call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7538E: An I/O error has occurred while parsing {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in parsing the wcs_instance file due to an I/O exception.
Action: The user should check the following: 1)Check that the CommerceServer55/instances directory exists. 2)Ensure that the user has authority to access and edit the file. 3)Ensure that the file exists and that it is not locked by another process. If the problem persists, contact your IBM Support representative.
- CMN7539E: An I/O error has occurred while parsing {0}
- Explanation: This message indicates that the IBM WebSphere Commerce Problem Determination Tool was unsuccessful in an internal service call. This is an internal error and no user action can be performed to correct this. Make note of the entire message and contact IBM Support.
Action: Contact your IBM support representative.
- CMN7700E: IBM WebSphere Commerce Installer error setting the {0} properties in BeanID: {1}
- Explanation:
This message indicates that the internal mapping of the user-selected languages for the documentation has failed in the
Documentation Selection panel.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7701E: IBM WebSphere Commerce Installer File Service Exception caught while checking file: {0}
- Explanation: The installation has attempted to a query to determine whether the specified file exists and the service request failed.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7702E: IBM WebSphere Commerce Installer failed to copy file from {0} to {1}
- Explanation:
The installation has attempted to copy the specified file to the user system and was unsuccessful.Action: The user should check that the follow are true: 1) Check that the full path including the directories of the destination exists. 2) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to write to the specified destination. 4) Ensure that if the destination file exists, that it is not locked by another process. 5) Ensure that the drive exists and is not a CD-ROM drive. 6) Ensure that the destination drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7703E: IBM WebSphere Commerce Installer failed to move file from {0} to {1}
- Explanation: The installation has attempted to move the specified file from one location to another on the user system and was unsuccessful.
Action: The user should check that the follow are true: 1) Check that the full path including the directories of the source and destination exist. 2) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to read the source file and write to the specified destination. 5) Ensure that the source file exists and that it is not locked by another process. 6) Ensure that if the destination file exists, that it is not locked by another process. 7) Ensure that the destination drive exists and is not a CD-ROM drive. 8) Ensure that the source and destination drives are active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7704S: IBM WebSphere Commerce Installer has successfully copied file from {0} to {1}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that a file copy of the indicated file was successful.
Action: No action required.
- CMN7705S: IBM WebSphere Commerce Installer has successfully moved file from {0} to {1}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that a file move of the indicated file to the destination path was successful.
Action: No action required.
- CMN7706E: IBM WebSphere Commerce Installer internal FileService Error caught: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in an internal file service call, most likely a request for a File Service in a getService call.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7707S: IBM WebSphere Commerce Installer adding the {0} file to the install archive <{1}>
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to track the progress of
files in the installation archive.Action: No action required.
- CMN7708E: IBM WebSphere Commerce Installer internal IOException Error caught: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in an I/O service. There are some user actions that may correct this. If all measures have passed without resolving this exception, make note of the entire error message and contact IBM support.
Action: The user should check that the follow are true: 1) Ensure that the destination drive has sufficient space. 3) Ensure that the user has authority to read and write to the specified destination. 5) Ensure that the any displayed files exists and are not locked by another process. 6) Ensure that the destination drive exists and is not a CD-ROM drive. 7) Ensure that the destination drive is active in the case of mapped drives or networked drives. If none of the measures correct this issue, contact your IBM support representative.
- CMN7709S: IBM WebSphere Commerce Installer adding the external resource {0} to the main archive.
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to track the progress of
external resouces in the installation archive.Action: No action required.
- CMN7710E: IBM WebSphere Commerce Installer internal IOException adding external jar files to the main archive.
- Explanation: This message indicates that the addition of external resource jars into the main IBM WebSphere Commerce installer has failed.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.Action: Contact your IBM support representative.
- CMN7711E: IBM WebSphere Commerce Installer error reading the XML input parameters: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in parsing the WebSphere Commerce product.xml file.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7712E: IBM WebSphere Commerce Installer internal parameter newTree is null. Cannot initialize ConfigXMLFile. {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in instantiating the ConfigXML node.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.Action: Contact your IBM support representative.
- CMN7713S: IBM WebSphere Commerce Installer has found W32 Registry Key: {0} \\\\ {1} text= {2}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that a search in the W32 Registry was successful.
Action: No action required.
- CMN7714S: IBM WebSphere Commerce Installer could not find W32 Registry Key: {0} \\\\ {1}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in finding the particular W32 registry entry on the destination node. This is an internal error and there are some user actions that can be performed to correct this. Make note of the entire error message and contact IBM support if this fails.
Action: The user should check that the follow are true: 1) Ensure that the product indicated is installed properly on the destination node. 2) Ensure that the product is of a supported level for WebSphere Commerce. If this does not solve your problem, contact your IBM support representative.
- CMN7715E: IBM WebSphere Commerce Installer has caught an internal javax.swing.UIManager.setLookAndFeel Exception: {0}
- Explanation:
This message indicates that the IBM WebSphere Commerce installer was unsuccessful in a GUI initialization call.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7716E: IBM WebSphere Commerce Installer internal ProductService Error caught: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in an internal product service call.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7717E: IBM WebSphere Commerce Installer internal Generic Catch Error caught: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in an internal service call.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM support representative.
- CMN7718S: IBM WebSphere Commerce Installer user input directory exists but it is read-only: {0}
- Explanation: This is a warning message indicating that the directory the user entered is read-only. The installer will not be able to write
to the specified directory.
Common causes for this are:
1) The directory specified is a CD-ROM drive or path.
2) The directory specified has been set to read-only.
3) The user does not have the authority to write to this directory.
Action: Enter a directory which has write-permissions for your user ID.
- CMN7719E: IBM WebSphere Commerce Installer internal Service Error caught: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in an internal service request call.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.Action: Contact your IBM support representative.
- CMN7720S: IBM WebSphere Commerce Installer internal Generic Catch Warning caught: {0}
- Explanation:
This message is a warning indicating that the IBM WebSphere Commerce installer has exited a wait prematurely. This is a warning message and most likely the user has selected to cancel the install at some point.
This is an internal warning and no user action can be performed to correct this. If the installation has failed, make note of the entire warning message and contact IBM support.
Action: No action required.
- CMN7721E: IBM WebSphere Commerce Installer could not load Strings resource bundle for locale: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in finding the resource file that contains messages specific to the user locale.
This is an internal error and there are some user actions that can be performed to possibly correct this. Make note of the entire error message and contact IBM support if this fails.
Action: The user should check that the follow are true: 1) Ensure that your operating system locale settings are supported by WebSphere Commerce. 2) Ensure that the destination drive has sufficient space to unpack the resource files. 3) Ensure that the user has access to the default temp directory as assigned by the system. If the problem persists, contact your IBM support representative.
- CMN7722E: IBM WebSphere Commerce Installer could not find String Value Key {0} in resource bundle for locale: {1}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in finding the particular string within the resource bundle specific to the user locale.
This is an internal error and there are some user actions that can be performed to possibly correct this. Make note of the entire error message and contact IBM support if this fails.
Action: The user should check that the follow are true: 1) Ensure that your operating system locale settings are supported by WebSphere Commerce. 2) Ensure that the destination drive has sufficient space to unpack the resource files. 3) Ensure that the user has access to the default temp directory as assigned by the system. If this does not solve your problem, contact your IBM support representative.
- CMN7723E: IBM WebSphere Commerce Installer internal error running command string: {0} in method {1}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in the displayed AS400 command execution.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.Action: Contact your IBM support representative.
- CMN7724E: IBM WebSphere Commerce Installer File Not Found Exception Error for files: {0}
- Explanation: The installation has attempted to access the specified files on the user system and was unsuccessful as the file was not found.
Action: The user should check that the follow are true: 1) Check that the full path including the directories exist. 2) Ensure that the user has authority to read the source file. 3) Ensure that the source file exists and that it is not locked by another process. 4) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7725E: IBM WebSphere Commerce Installer utility class InstallUtils Search and Replace Error: Filetext={0} Searchtext={1} Replacetext={2} Input Buffertext={3} Output Buffertext={4}
- Explanation:
This message indicates that the IBM WebSphere Commerce installer was unsuccessful in performing a search and replace on the specified file. There are some user actions that may correct this. If all measures have passed without resolution of this exception, make note of the entire error message and contact IBM support.
Action: The user should check the following: 1) Check that the full path including the directories of the source file exists. 2) Ensure that the source drive has sufficient space as a copy will be made. 3) Ensure that the user has authority to read the source file and write to the specified destination. 5) Ensure that the source file exists and that it is not locked by another process. 6) Ensure that the source drive exists and is not a CD-ROM drive. 7) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7726E: IBM WebSphere Commerce Installer encountered a WIN32 Registry Service Error: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in performing an action on the W32 registry. This is an internal error and there are no user actions that can be performed to correct this. Make note of the entire error message and contact IBM support if this fails.
Action: Contact your IBM support representative.
- CMN7727E: IBM WebSphere Commerce Installer XML file not found while attempting parsing: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful reading an XML file. There are some user actions that may correct this. If all measures have passed without resolving this exception, make note of the entire error message and contact IBM support.
Action: The user should check the following: 1) Ensure that the user has authority the specified file. 2) Ensure that the the XML file exists and are not locked by another process. 3) Ensure that the source drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7728E: IBM WebSphere Commerce Installer file parsing encountered missing resource: {0}
- Explanation: This message indicates that the IBM WebSphere Commerce installer was unsuccessful in scanning and retrieving data from an XML file.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.Action: Contact your IBM support representative.
- CMN7729S: IBM WebSphere Commerce Installer has successfully deleted file: {0}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified file was successfully deleted.
Action: No action required.
- CMN7730E: IBM WebSphere Commerce Installer failed to delete file: {0}
- Explanation:
The installation has attempted to delete the specified file from specified location on the user system and was unsuccessful.
Action: The user should check that the follow are true: 1) Check that the full path including the directories of the file exist. 2) Ensure that the user has authority to access the file. 3) Ensure that the file exists and that it is not locked by another process. 4) Ensure that the drive exists and is not a CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7731S: IBM WebSphere Commerce Installer successfully edited file: {0} with changes: {1}
- Explanation:
This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified file was successfully edited with the displayed changes.
Action: No action required.
- CMN7732E: IBM WebSphere Commerce Installer failed to edit file: {0} with changes: {1}
- Explanation:
The installation has attempted to edit the specified file at the specified location on the user system and was unsuccessful.
Action: The user should check the following: 1) Check that the full path including the directories of the file exist. 2) Ensure that the user has authority to access and edit the file. 3) Ensure that the file exists and that it is not locked by another process. 4) Ensure that the drive exists and is not a CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. If the problem persists, contact your IBM support representative.
- CMN7733W: IBM WebSphere Commerce Installer warning, an active or running service was detected: {0}
- Explanation: The installation has detected that the indicated service or process was active at install time. The service should be shut down before continuing with the installation as it may lock assets the installation will need to access.
Action: The user should shut down the specified process before continuing with the installation.
- CMN7734S: IBM WebSphere Commerce Installer has successfully stopped the service: {0}
- Explanation:
This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified process was successfully stopped. This is to ensure that any related file or system assets are available for the installer to use.
Action: No action required.
- CMN7735E: IBM WebSphere Commerce Installer encountered an unexpected error stopping service: {0}
- Explanation:
The installation has attempted to stop the specified process on the user system and was unsuccessful.
The process may prevent access to assets the installer will need to use.
Action: The user can: 1) Manually stop the process from the operating system services or command line and retry the installation again. 2) Manually stop any related processes that may prevent the specified process from being stopped and retry the installation again. If the problem persists, contact your IBM support representative.
- CMN7736S: IBM WebSphere Commerce Installer has created the User ID of: {0}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified system user ID was created successfully.
Action: No action required.
- CMN7737E: IBM WebSphere Commerce Installer encountered an error creating the User ID of: {0}
- Explanation: The installation has attempted to create the specified system user ID on the user system and was unsuccessful.
Action: The user should check that the follow are true: 1) The user ID does not contain any special characters or restricted characters. 2) The user ID is not an operating system reserved value. 3) The installation is run as the root user or equivalent to allow access to system services to create a user. 4) The default home directory for this user is a valid path. If the problem persists, contact your IBM support representative.
- CMN7738S: IBM WebSphere Commerce Installer has created the Group ID of: {0}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified group ID was created successfully.
Action: No action required.
- CMN7739E: IBM WebSphere Commerce Installer encountered an error creating the Group ID of: {0}
- Explanation:
The installation has attempted to create the specified group ID on the user system and was unsuccessful.Action: The user should check that the follow are true: 1) The group ID does not contain any special characters. 2) The group ID is not an operating system reserved value. 3) The installation is run as the root user or equivalent to allow access to system services to create a group. If the problem persists, contact your IBM support representative.
- CMN7740S: IBM WebSphere Commerce Installer has successfully installed the software package: {0}
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the specified software product was successfully installed.
Action: No action required.
- CMN7741E: IBM WebSphere Commerce Installer has failed to install the software package: {0}
- Explanation: The installation has attempted to install the specified software package onto the user system and was unsuccessful.
Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. If the problem persists, contact your IBM support representative.
- CMN7742E: IBM WebSphere Commerce Installer has failed to detect the following: {0}
- Explanation:
This message indicates that the IBM WebSphere Commerce installer was unsuccessful in detecting the required information from the system.
This is an internal error and no user action can be performed to correct this. Make note of the entire error message and contact IBM support.
Action: Contact your IBM Support representative.
- CMN7743E: IBM WebSphere Commerce Installer has failed to verify that the logon user has administrative rights.
- Explanation:
This message indicates that the IBM WebSphere Commerce installer could not verify that the logon user has administrative rights. There are some user actions that may correct this. If all measures have passed without resolving this exception, make note of the entire error message and contact IBM support.
Action: Ensure the logon account you use has administrative rights. If the problem persists, contact your IBM Support representative.
- CMN7744E: IBM WebSphere Commerce Installer has detected an error while silently installing WebSphere Application Server and cannot continue. Check log {0} for details.
- Explanation:
The installation has attempted to install the specified software package onto the user system and was unsuccessful.
Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log
- CMN7745E: IBM WebSphere Commerce Installer has detected an error while silently installing DB2 Universal Database and cannot continue. Check log {0} for details.
- Explanation:
The installation has attempted to install the specified software package onto the user system and was unsuccessful.
Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the <Commerce Install Dir>/logs and would include: - db2setup.log - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log
- CMN7746E: IBM WebSphere Commerce Installer has detected an error while silently installing IBM HTTP Server and cannot continue. Check log {0} for details.
- Explanation:
The installation has attempted to install the specified software package onto the user system and was unsuccessful.
Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log
- CMN7747E:
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the installation of WebSphere Application Server was successful.
Action: No action is required.
- CMN7748E:
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the installation of IBM DB2 Universal Database was successful.
Action: No action is required.
- CMN7749E:
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the installation of IBM HTTP Server was successful.
Action: No action is required.
- CMN7750E: IBM WebSphere Commerce Installer has detected an error while silently installing Web Server plug-ins. Check log {0} for details.
- Explanation:
The installation has attempted to install the specified software package onto the user system and was unsuccessful.
Action: The user should check the following: 1) Ensure the software package does not have any outstanding prerequisites. 2) Ensure that the destination path has sufficient disk space, including the system temp directory. 3) Ensure that the user has access to the destination path for the software package. 4) Ensure that the correct CD is in the CD-ROM drive. 5) Ensure that the drive is active in the case of mapped drives or networked drives. 6) Check that any related processes are not active or locking assets the software package needs to access. 7) Ensure the user running the IBM WebSphere Commerce installer is root. 8) Ensure the that the system registry does not contain any residual information from a previous installation of the product. 9) Ensure that if this product existed previously, that it was cleanly uninstalled. and then attempt another installation of the product upon removal of the failed installed product. If the problem persists, the user may attempt a manual installation from the product CD after exiting the Commerce installer and removing the failed installation. Contact your IBM support representative with all available log information in any event. Logs would be located in the User/System TEMP directory as well as the "<Commerce Install Dir>/logs" directory and the "<WebSphere Application Server Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log
- CMN7751S: IBM WebSphere Commerce Installer successfully installed Web Server plug-ins.
- Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the installation of WebSphere Application Server Web server plug-ins was successful.
Action: No action is required.
- CMN7752S: Applying WebSphere Application Server eFixes. Please check the log file for more detail: {0}
- Explanation:
Status message only
Action: No action required
- CMN7753S: WebSphere Commerce installation complete.
- Explanation:
Status message only
Action: No action required
- CMN7754S:
- Explanation:
Status message only
Action: No action required
- CMN8000E: Messaging system cannot create the JMS BytesMessage to send {0} to JMS queue {1}. Error: {2}
- Explanation: The messaging system encountered an error when trying to create a JMS message to send. The QueueSession may have a problem creating the JMS Message and setting its properties, for example, JMSReplyTo and JMSCorrelationID.
Action: Make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and the JMS Server.
- CMN8001E: Messaging system cannot send the JMS BytesMessage containing {0} to JMS queue {1}. Error: {2}
- Explanation: The messaging system encountered an error when it is trying to send a JMS message. The queue specified in the error message may not be available.
Action: Make sure the JMS Server is available and active, and, as well, the connection between WebSphere Commerce and JMS Server.
- CMN8002E: Messaging system cannot receive JMS BytesMessage from JMS queue {0}. Error: {1}
- Explanation: There is a problem connecting to the JMS Server. This exception can be thrown if the type of inbound JMS message is not supported. With the current release, only javax.jms.TextMessage and javax.jms.BytesMessage are supported.
Action:
In the first case, make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and the JMS Server. In the second case, use either java.jms.TextMessage or java.jms.BytesMessage for the inbound message. - CMN8003E: Messaging system cannot look up QueueConnectionFactory {0} in the naming context.
- Explanation: The messaging system cannot retrieve information about QueueConnectionFactory from the WebSphere Application Server's JNDI naming context.
Action: The JNDI naming context settings should be checked and users should make sure QueueConnectionFactory is defined as outlined in the product documentation. Re-connection to the JMS Server will happen within 10 minutes by default. This value can be changed under inbound connector configuration using WebSphere Commerce Configuration manager.
- CMN8004E: Messaging system cannot look up JMS queue {0} in the naming context.
- Explanation: Information about the JMS Queue specified in the error message cannot be retrieved from the WebSphere Application Server's JNDI naming context.
Action: The JNDI naming context settings should be checked and users should make sure the JMS Queue specified is defined as outlined in the product documentation. Re-connection to the JMS Server will happen within 10 minutes by default. This value can be changed under inbound connector configuration using WebSphere Commerce Configuration manager.
- CMN8005E: Messaging system cannot establish a JMS Session for QueueConnectionFactory {0}. Error: {1}
- Explanation: A new session cannot be created based on the QueueConnection created.
Action: Make sure the JMS Server is available and active, as well as the connection between WebSphere Commerce and JMS Server is available.
- CMN8006E: Messaging system cannot start a JMS QueueConnection for QueueConnectionFactory {0}.Error: {1}
- Explanation: The QueueConnection cannot be started with the JMS provider. The queue connection factory defined in the JNDI naming context may not match with the actual setup on the JMS provider. The areas of problem include the queue manager name (qmanager), transport, hostname(remote JMS server name), and listener port.
This problem may also happen when there is access problem with a remote JMS server.Action: Check the JNDI naming context settings to make sure QueueConnectionFactory is defined as outlined in the product documentation. The JMS provider settings (e.g. a MQ Server) should match the requirements of the naming context settings mentioned above. If the JMS Server is a remote server, make sure that the user ID running WebSphere Application Server and WebSphere Commerce is part of the user group of (or has access to) the JMS provider on the remote machine.
- CMN8007E: Messaigng system cannot close down the JMS session or the JMS queue {0}. Error: {1}
- Explanation: The JMS session or the queue cannot be closed properly. One session of a connection between WebSphere Commerce and the JMS provider may be lost after messaging operation is completed. This problem is likely to happen when using a remote JMS Server, with which networking condition is unstable.
Action: If the problem persists, the networking condition between WebSphere Commerce and the JMS Server should be improved.
- CMN8008E: Messaging system cannot start the reciever for queue {0}. Error: {1}
- Explanation: The messaging system cannot create a JMS receiver out of the current session being used, and as a result, cannot receive a JMS message with the specified queue.
Action: Make sure that the JMS Server used by WebSphere Commerce is running and that the connection between JMS Server and WebSphere Commerce is active. If not, restart the JMS server.
WebSphere Commerce should re-connect to the JMS Server in 10 minutes by default. If a reply JMS message is expected after sending out a message to a remote system, the sent message will need to be re-sent. - CMN8009E: Messaging system cannot receive the inbound message as there is no inbound queue defined.
- Explanation: The JMS inbound queue definition has not been defined. There is a problem with the command using the receive or send/receive operation.
Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the WebSphere Commerce Administration Console. Update the WebSphere Application Server namespace definition of the inbound queue with the correct queue information.
- CMN8010E: Messaging system cannot send the message because there is no outbound queue defined.
- Explanation: The JMS outbound queue definition has not been defined. There is a problem with the command using the send or send/receive operation.
Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the WebSphere Commerce Administration Console. Update the WebSphere Application Server namespace definition of the outbound queue with the correct queue information.
- CMN8013E: Error occurred when JSP processing for ViewName {0}.
- Explanation: The error may occur if the jsp file being composed has syntax error or there is a missing parameter needed by composing the file.
Action: Update the jsp file according to the exception information listed in the error message.
- CMN8014E: The URL constructed during composition using ViewName {0} is invalid {1}.
- Explanation: The constructed URL during message composition is invalid. This can happen if the PROPERTIES column in the VIEWREG table is pointing to an incorrect JSP, or the JSP is missing.
Action: Using the ViewName listed in the ecmsg log, do a query on the ViewName against the VIEWREG table.
Ensure the PROPERTIES column points to a valid JSP file on the server. - CMN8016E: The logonId {0} was not found in USERREG table.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the user_ID command parameter. The command is unable to proceed.
Action: Verify the logonId parameter in the inbound message is a valid user ID.
- CMN8017E: UserID {0} was not created from the XML message.
- Explanation: User with ID as shown was not created.
Action: Refer to other related exception information on the same thread for details.
- CMN8018E: An EJB Naming Exception occurred when accessing UserID {0}.
- Explanation: This error occurs when the system tries to use an EJB to look up the user ID for a member. Naming exceptions normally occur when the system tries to look up the EJB using a predefined name, but the name does not exist in the JNDI namespace. This can occur if the customer has changed the JNDI name of that particular EJB.
Action: Open the Administrator's Console from WebSphere Application Server and correct the JNDI name of the user registry EJB according to the information found in the ecmsg log file. Restart the WebSphere Commerce instance
- CMN8019E: An EJB Remote Exception occurred when accessing UserID {0}.
- Explanation: Messaging system encountered the remote exception as shown.
Action: Fix the problem shown in the exception information. There may also be related exception information shown on the same thread.
- CMN8020E: Exception occurred while loading the inbound listeners: {0}
- Explanation: The JMS/MQ transport adapter failed to initialize. The section defining the inbound connector(s) in <instance>.xml may be missing.
Action: Correct the situation according to the exception information and re-start WebSphere Commerce if necessary.
- CMN8021E: Exception {1} occurred when the listener for WebSphere MQ (transport adapter) started up: {0}
- Explanation: An exception occurred when starting up either the serial or parallel transport adapter. Most likely, there was problem configuring the JNDI namespace for the JMS queue connection factory and/or queue name(s).
Action: Correct the situation according to the error information provided. Verify that the JMS configuration has been correctly set up under the WAS JNDI namespace, and ensure that the queue and queue manager information are set according to the JMS provider (e.g. MQSeries Server). You can use IVTRun.bat to verify this configuration if you are using MQSeries.
- CMN8022E: Listener for Websphere MQ has been stopped.
- Explanation: The serial/parallel transport adapter (as indicated in the class name) encountered an exception while shutting down. This may be a result of an improper shutdown procedure.
Action: Shut down WebSphere Commerce before shutting down the JMS Server.
- CMN8023E: Exception occurred when receiving JMS message from the listener for WebSphere MQ: {0}
- Explanation: The serial/parallel transport adapter (as indicated in the class name) encountered an exception while listening to a queue.
Action: Correct the situation according to the exception information and restart WebSphere Commerce if necessary.
- CMN8025E: The request {0} failed with error {1}
- Explanation: A WebSphere Commerce component (e.g. Serial or Parallel Transport Adapter) encountered the error as shown.
Action: Fix the problem according to the exception information and restart WebSphere Commerce if necessary.
- CMN8026E: The pool of worker threads for parallel listeners for WebSphere MQ (transport adapters) cannot be created.
- Explanation: Messaging system cannot create worker thread(s) for JMS/MQ Transport Adapter.
Action: Make sure the number of threads defined under Parallel Connectors of the <instance>.xml is larger than 0 but less than the maximum allowable threads created under WebSphere Commerce.
- CMN8027E: Exception occurred when sending to transport: {0}
- Explanation: The serial/parallel transport adapter (as indicated in the class name) encountered an exception while writing to an error queue.
Action: Correct the situation according to the exception information and restart WebSphere Commerce if necessary.
- CMN8028E: The interface name must be of type MessagingViewCommand for ViewName {0}.
- Explanation: The composer throws an error because interface name in the VEIWREG.INTERFACENAME is not com.ibm.commerce.messaging.viewcommands.MessagingViewCommand for the specified ViewName.
Action: Correct the interfacename and re-execute the command.
- CMN8101E: The command failed to run the doPreProcess method.
- Explanation: The command failed to perform the additional processing at the begining of its execution.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8101S: An error occurred when parsing XML file {0}: {1}
- Explanation: The XML parser has identified a recoverable error (according to the XML v1.0 recommendations) in the XML file indicated. The error reports a violation of a validity constraint. Parsing stops at this point.
Action: Users will need to fix the XML file according to the error message (as shown) and restart WebSphere Commerce.
- CMN8102E: The command failed to run the doProcess method.
- Explanation: The command failed to execute.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8102S: A fatal error occurred when parsing XML file {0}: {1}
- Explanation: XML parser has identified a non-recoverable error (according to XML v1.0 recommendation) in the XML file indicated. The error reports that the XML file/message is not well-formed. Parsing stops at this point.
Action:
If the reported error is against an XML file, users will need to fix it according to the fatal error message as shown and restart WebSphere Commerce. If the reported error is against an inbound XML message, fix the message according to the fatal error message and resend it. - CMN8103E: The command failed to run the doPostProcess method.
- Explanation: The command failed to perform the additional processing at the begining of its execution.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8103S: A warning occurred when parsing XML message {0}: {1}
- Explanation: XML parser has identified a warning condition that is neither an error nor a fatal error (according to XML v1.0) in the XML file indicated. Parsing continues.
Action: Need to fix the XML file if necessary according to the warning message as shown and restart WebSphere Commerce.
- CMN8104E: The command failed to run. The order number and merchant order number are null.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the order number and merchant order number command parameters. The command is unable to proceed.
Action: Verify the order number and merchant order number parameters in the inbound message is a valid merchant order number.
- CMN8104S: ISO Date Format Error: Unexpected delimiter {0} in the date string {1}
- Explanation: The xml message/file does not have the correct ISO Date Format in the required field.
Action: Correct the content with proper ISO Date Format.
- CMN8105E: The order ID {0} found in the inbound message cannot be found in previous order status update record(s).
- Explanation: The order ID found in the inbound message cannot be found in the previous order status update record.
Action: Correct the order ID in the inbound message and re-send the message to WebSphere Commerce.
- CMN8105S: ISO Date Format Error: Data type error. There was an unexpected character {0} in the date string {1}
- Explanation: The xml message/file does not have the correct ISO Date Format in the required field.
Action: Correct the content with proper ISO Date Format.
- CMN8106E: The merchant order number {0} does not match the merchant order number {1} in the ORDSTAT table.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the merchant order number command parameter. The command is unable to proceed.
Action: Verify and correct the DTD file corresponding to the command ensuring it contains a mandatory order number and merchant order number elements.
- CMN8106S: ISO Date Format Error: The mandatory field is missing in the date string {0}
- Explanation: The xml message/file does not have the correct ISO Date Format in the required field.
Action: Correct the content with proper ISO Date Format.
- CMN8107S: ISO Date Format Error: There are unexpected tailing characters {0} in the date string {1}
- Explanation: The xml message/file does not have the correct ISO Date Format in the required field.
Action: Correct the content with proper ISO Date Format.
- CMN8108S: Messaging system cannot determine the command name to be invoked by the inbound message. No command condition is satisfied by this message.
- Explanation: The message system cannot determine the correct command name to be invoked for the inbound message.
Action: Make sure there is a unique condition in the system/user message template file for the inbound message to satisfy, in order to invoke a controller command.
- CMN8110E: No order was found for the merchant order number {0} in ORDSTAT table.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the merchant order number command parameter. The command is unable to proceed.
Action: Verify the merchant order number parameter in the inbound message has a valid order number.
- CMN8111E: The message is incorrectly sequenced. Either the sequence number or the last update timestamp is obsolete.
- Explanation: The order status update message was incorrectly sequenced. There may be a previously received message with a later timestamp or larger sequence number than this newly received inbound message.
Action: Correct the sequence number and/or the timestamp and re-send the message to WebSphere Commerce.
- CMN8112E: There is an invalid value {0} for numeric field {1}
- Explanation: The error can occur in the ProductOfferPriceUpdateCmd, OrderItemStatusCmd, and OrderStatusCmd commands. An input parameter cannot be converted to the corresponding numeric value because the format is invalid.
Action: Check the appropriate format for the numeric field indicated in the ecmsg log. Make modifications or appropriate type checking in the files that invoke the command (normally either a JSP or a Java class).
- CMN8113E: There is an invalid value {0} for timestamp field {1}. The correct format is yyyy-mm-dd hh:mm:ss.ssssss.
- Explanation: The inbound message does not have the correct date format in the required field.
Action: Correct the inbound message with proper date format as indicated.
- CMN8114E: Messaging system failed to verify the mandatory parameters. At least one of the ItemNumbers of the order is missing in the inbound message.
- Explanation: At least one of the ItemNumber(s) of the order is missing in the inbound order status update message. The inbound message cannot be processed by the messaging system.
Action: Ensure each order item has the ItemNumber in the inbound message, and resend it.
- CMN8115E: The command failed to run.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the command parameters. The command is unable to proceed.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8116E: The message for catalog entry ID {0} in the OFFER table does not have the correct precedence.
- Explanation: The precedence value and/or offer ID found in the inbound message does not match with catalog entry ID found in the OFFER table.
Action: Modify the precedence value and/or offer ID in the inbound message and re-send the message to WebSphere Commerce.
- CMN8117E: Could not find OFFERPRICE with offer ID {0} and currency {1}.
- Explanation: The OFFERPRICE and/or offer ID found in the inbound message cannot be found under the specified offer ID and currency in the OFFER table.
Action: Modify the offer price and/or offer ID with the correct values and re-send the message to WebSphere Commerce.
- CMN8118E: The catalog entry (row) with MEMBER_ID and PARTNUMBER cannot be found in the CATENTRY table.
- Explanation: The messaging system cannot find the product by the provided MEMBER_ID and PARTNUMBER from the CATENTRY table, using CatalogEntryAccessBean finder method.
Action: Make sure the inbound message has the correct MEMBER_ID and PARTNUMBER combination, in order to identify a catalog entry in CATENTRY table.
- CMN8119E: The Member ID attribute of the command must be set.
- Explanation: The Member ID field in the command is not set. As a result, the command cannot be executed.
Action: Check the invocation sequence in the ecmsg log. Make modifications to the files that invoke the command (normally either a JSP or a Java class).
- CMN8121E: The specified Trading Position Containter ID cannot be found.
- Explanation: The command cannot find the TradingPositionContainerID (specified in the inbound message) from the TRADPOSCN table.
Action: Make sure the TradingPositionContainerID provided in the inbound message is correct and the corresponding row in the TRADPOSCN table has been created.
- CMN8123E: The command failed to run.
- Explanation: This error is normally due to a failure in the input validation logic of the inbound message that supplies the value for the message command parameter. The command is unable to proceed.
Action: Correct the DTD file corresponding to the command ensuring it contains a mandatory message element.
- CMN8124E: No command matches the inbound message {0}.
- Explanation: This error is normally due to a failure in the parsing logic of the inbound message. The command is unable to proceed.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8125E: A new offer cannot be created because the precedence for catalog entry ID {0} will exceed the maximum value for the precedence of {1}.
- Explanation: The precedence value of the inbound product offer price update message is larger than the maximum value allowed, 999999999999999D.
Action: Decrease the precedence value of the offer and re-send the message to WebSphere Commerce.
- CMN8126E: Messaging system failed to find the order item status. OrderItemId {0} for order {1} in the inbound message does not match the existing record(s) in the ORDISTAT table.
- Explanation: OrderItemId "{0}" for order "{1}" in the inbound order status update message does not match with the existing record(s) in the ORDISTAT table.
The new inbound order status update messages has the wrong order item id(s). This message cannot be processed by WebSphere Commerce.
Action: Correct the order item ID and resend the message.
- CMN8151E: The system/user message template file of the message mapper cannot be parsed.
- Explanation: This error occurs when there is a syntax error in one of the message template files of a message mapper. The file name and failure reason will be indicated in the ecmsg log file.
This problem is likely due to modifications to the default/customized template files, for example, <WC>/xml/messaging/user_template.xml. These files may be defined for a customized message mapper as indicated in instance.xml file.Action: Fix the file according to the failure message indicated in the ecmsg log file and restart the WebSphere Commerce instance.
- CMN8152E: SAX Parser cannot be initialized. Error: {0}.
- Explanation: An internal error has occured.
Action: Contact your IBM support representative.
- CMN8153E: The file {0} cannot be found.
- Explanation: This file not found exception is normally due to an incorrect name or location of the specified file.
Action: Verify the specified file exists on the file system.
- CMN8154E: The file {0} cannot be read.
- Explanation: This I/O exception is normally due to an incorrect name or location of the specified file.
Action: Verify the content of the specified file.
- CMN8156E: Template Error: TemplateTagName {0} for command {1} is not defined.
- Explanation: No "TemplateTag" with the specified name is defined for a "TemplateDocument" node.
Action: Add "TemplateTag" node with "Tag" node(s) for the "TemplateDocument" to the message template file and restart WebSphere Commerce.
- CMN8157E: Template Error: TemplateTagName {0} could not be found in the message template file.
- Explanation: No "Tag" node was defined for the specified "TemplateTag". At least 1 "Tag" must be defined for each "TemplateTag".
Action: Add 1 or more "Tag" node(s) to the specified "TemplateTag" node and restart WebSphere Commerce.
- CMN8158E: Template Error: Unsupported XPath Type {0} for XPath {1}.
- Explanation: The XPath Type found in the system/user message template file for the specified XPath is not supported.
Action: Correct the XPath Type to "EMPTY", "PCDATA" or "USERDATA" and restart WebSphere Commerce.
- CMN8159E: Template Error: Unsupported XPath Type {0} for an attribute in XPath {1}.
- Explanation: The XPath Type for the XPath must be "EMPTY".
Action: Correct the XPath Type in system/user message file and restart WebSphere Commerce.
- CMN8160E: Template Error: FieldName is empty for XPath {0}.
- Explanation: The system/user message template file has error(s). The field name for the XPath as shown is empty.
Action: Add the field name to XPath in the system/user message template file.
- CMN8161E: Template Error: USERDATA type element {0} has no name attribute.
- Explanation: This error occurs in the default/customized template files where the name attribute in the USERDATA element is missing. These template files may define a customized message mapper as indicated in the <instance_name>.xml file.
Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.
- CMN8162E: Template Error: name attribute for USERDATA type element {0} has empty value.
- Explanation: The message template contains an empty value in the USERDATA element.
Action: Add a value to the USERDATA element in the template, and restart the WebSphere Commerce instance.
- CMN8163E: Template Error: Unknown XPathType {0}.
- Explanation: The XPathType is unknown to the messaging system parser.
Action: Correct the XPathType and restart WebSphere Commerce.
- CMN8164E: Template Error: Expecting {0} at the end of Condition ({1}) for Command {2}.
- Explanation: The error occurs when the condition string in one of the message template files is not correct. The expected expression and the original condition string are indicated in ecmsg log file. This problem is likely due to modifications to the default/customized template files, for example, <WC>/xml/messaging/user_template.xml. These files may be defined for a customized message mapper as indicated in the <instance_name>.xml file.
Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.
- CMN8165E: Template Error: {0} is not expected at the end of Condition ({1}) for Command {2}.
- Explanation: The error occurs when the condition string in one of the message template files is not correct. The unexpected expression and the original condition string are indicated in ecmsg log file.
This problem is likely due to modifications to the default/customized template files, for example, <WC>/xml/messaging/user_template.xml. These files may be defined for a customized message mapper as indicated in the <instance_name>.xml file.Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.
- CMN8166E: Template Error: {0} is not recognized in Condition ({1}) for Command {2}.
- Explanation: The error occurs when the condition string in one of the message template files is not correct. The problematic expression and the original condition string are indicated in ecmsg log file.
This problem is likely due to modifications to the default/customized template files, for example, <WC>/xml/messaging/user_template.xml. These files may be defined for a customized message mapper as indicated in the <instance.xml> file.Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.
- CMN8167E: Template Error: FieldInfo attribute value {0} is not recognized.
- Explanation: The FieldInfo of Tag nodes in the message template files (for example, sys_template.xml or user_template.xml) in the <WC>/xml/messaging directory will only support CDATA. FieldInfo of any other type cannot be recognized.
Action: Change the FieldInfo as shown in the error message to CDATA in the message template file and restart WebSphere Commerce.
- CMN8168E: Template Error: FieldType attribute value {0} in the message template file is not recognized.
- Explanation: FieldType of Tag nodes in message template files (e.g. sys_template.xml or user_template.xml) in directory <WC>/xml/messaging will only support either STRING or DATA. FieldType of any others cannot be recognized.
Action: Change the FieldType as shown in the error message to either STRING or DATA in message template file and restart WebSphere Commerce.
- CMN8169E: Template Error: XPathType attribute value {0} in the message template file is not recognized.
- Explanation: XPathType of Tag nodes in message template files (e.g. sys_template.xml or user_template.xml) in directory <WC>/xml/messaging will only support one of these: PCDATA, EMPTY, REPEAT, VECTOR, ATTRIBUTE and USERDATA. XPathType of any other type cannot be recognized.
Action: Change the XPathType as shown in the error message to one of the supported types in message template file and restart WebSphere Commerce.
- CMN8201E: Tag: {0} is missing.
- Explanation: The required tag as shown is missing from the inbound legacy message.
Action: Correct the inbound legacy message and re-send it to WebSphere Commerce.
- CMN8202E: Messaging system parser cannot retrieve MsgType and/or MsgVersion from the legacy message.
- Explanation: The message type ID and/or message version of the legacy message being processed cannot be read properly. The inbound legacy message may be corrupted.
Action: Check the type ID and version fields of the inbound legacy message and make sure the PROLOG_DATA section of the inbound message is correctly formatted.
- CMN8203E: Invalid date format: {0}. Date should be in YYYYMMDD format
- Explanation: The data format in the inbound message is not valid.
Action: Please edit the inbound message with the data format specified in the error message and re-send the message to WebSphere Commerce.
- CMN8204E: Messaging system parser cannot retrieve field name: {0} with field size: {1}
- Explanation: The format of the inbound legacy message is incorrect.
Action: Check the field size of the message format and make sure the correct number of bytes is used for the field.
- CMN8205E: Messaging system parser cannot find the item template for this message.
- Explanation: Messaging system cannot find the corresponding ECETMPT record for the inbound legacy message, with message type, message version, record type, and record version.
Action: Ensure there is a matching legacy message defined in the ECETMPT table. Resend the inbound message with the correct message type, message version, record type, and record version if necessary.
- CMN8206E: Invalid <DATUSR> segment format found in the inbound message.
- Explanation: Messaging system identified an invalid DATUSR_DATA segment while parsing the inbound legacy message. This inbound message cannot be processed.
Action: Ensure the field names and corresponding field types are formatted according to WebSphere Commerce online documentation and resend the message.
- CMN8207E: The product inventory/quantity update message cannot be processed. The message may be corrupted.
- Explanation: The inbound message may be corrupted. Some required parameters for the command may be missing. One reason is that ProductSKU or ProductNumberByMerchant are missing. The other reason can be that the mapping of inbound message to required parameters is not done correctly.
Action: Check the requirement set by the corresponding DTD and verify that the mapping between the message and the parameters (used by the command) is correctly done by the message template files.
- CMN8208E: An EJB error {1} occurred when accessing ADDRESS table for NICKNAME {0} and MEMBER_ID {1}.
- Explanation: This error is normally due to a failure in finding a record in the ADDRESS table due do invalid parameters passed in by the calling command.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8209E: An EJB error {1} occurred when accessing ADDRESS table for Address_Id {0}.
- Explanation: This error is normally due to a failure in updating the ADDRESS table due do an invalid BillToRefNumber parameter passed in by the calling command.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8210E: The class specified cannot get the store/supplier information from the database.
- Explanation: The command cannot get some store/supplier related information from STADDRESS, STOREENTDS and STOREDEF tables.
Action: Please make sure the store has all the above tables configured properly.
- CMN8211E: The class specified failed to format the content of the order message.
- Explanation: The command failed to set the content of the outbound order message.
Action: Make sure the jsp (by default, OrderCreateXML.jsp) generating the order create message is using UTF-8 encoding.
- CMN8212E: The class specified failed to send the order message.
- Explanation: The command failed to send the order message. There could be problem setting the content of the order message, saving the message to the database or other related problems.
Action: Please look up other related errors reported with the same thread id in EC message log file.
- CMN8213E: Error {0} occurred when using the File adapter to open the file.
- Explanation: The File Connector fails to open the output file. The error can be caused by an invalid path or file name, file already in use, or not enough privileges to write to the file.
Action: Check whether the path and file name are valid for that particular platform (OS), and that no other process is using that particular file.
- CMN8214E: Error {0} occurred when using the File adapter to close the file.
- Explanation: The File Connector fails to close the file.
Action: Check whether another process has the output file locked (still writing to this file).
- CMN8215E: Error {0} occurred when using the File adapter to write to the file.
- Explanation: The File Connector fails to write to the output file. This error may occur when the connector fails to open the file, or there is not enough disk space.
Action: Check in the ecmsg log file, and verify that the file opened without any problems. Run a disk space check to see whether you have enough free space.
- CMN8216E: An error {1} occurred while sending the message.
- Explanation: Status message only.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8301E: ERROR ClassNotFound occurred when trying to find the Class named {0}.
- Explanation: The classe used by the e-mail connector cannot be found. This is a JVM runtime problem. When the JVM tries to load a required class, no class definition is found.
Action: Ensure that the class listed in the ecmsg log is included in a jar file (wcsruntime.jar by default), and is inside <WebSphere Application Server directory>/installedApps/WC_Enterprise_App_<instance name>.ear/lib.
- CMN8302E: The class {1} does not declare the method {0}.
- Explanation: Status message only.
Action: No action required.
- CMN8303E: The input byte[] parameter is null.
- Explanation: The CCF2JMContentData constructor failed because the content of the message to be sent out is null.
Action: Check the WebSphere Commerce log and the trace file for additional information.
- CMN8305E: ERROR ClassNotFound occurred when trying to find the Address class.
- Explanation: Messaging system cannot find the class with name property being "Address" (by default, javax.mail.internet.InternetAddress, speicified under TransportConfig section) in the <instance>.xml file.
Action: Make sure that the class speicified is loaded for WebSphere Commerce within the WebSphere Application Server.
- CMN8308E: InstantiationException occurred when instantiating the Message class. Error: {0}
- Explanation: Messaging system cannot instantiate the class with name property being "Message" (by default, javax.mail.internet.MimeMessage, speicified under TransportConfig section) in the <instance>.xml file.
Action: Make sure that the class speicified is properly loaded for WebSphere Commerce within the WebSphere Application Server.
- CMN8309E: MessagingException occurred when messaging system was setting message attributes: {0}
- Explanation: The message system encountered an exception when it set the message (i.e. email) attributes of an outbound message. The exception is likely due to missing mandatory message attributes for the sending operation.
Action: Please check the message attributes of the message type under WebSphere Commerce Administration Console (under the page assigning the message type to a transport) and make sure attributes are filled with valid data format (e.g. valid email address).
- CMN8313E: An error {0} occurred while building the message.
- Explanation: The message was not sent out.
Action: Check the WebSphere Commerce log and the trace file for additional information.
- CMN8314E: An illegal access exception occurred while building the message.
- Explanation: The error occurs when the message body is constructed, the runtime is calling a non public set method.
Action: Ensure the BodyPart class has the following public methods: setDataHandler, setDisposition, and setFileName.
- CMN8315E: A messaging exception occurred while building the message.
- Explanation: This error occurs when a muli-part message is constructed in the e-mail connector. The setDataHandler, setDisposition, or the setFileName methods, make changes against an underlying implementation (Java Mail package) that does not support the modification of existing values.
Action: Ensure the underlying implemenation (Java Mail package) supports changes for these headers.
- CMN8316E: An instantiation exception occurred while building the message.
- Explanation: This error can occur when creating an instance of a class using the newInstance method, but the specified class object cannot be instantiated because it is an interface or is an abstract class. In the e-mail adapter, a newInstance method is invoked against the BodyPart and MultiPart class.
Action: Make sure that the BodyPart or MultiPart class is not an interface or an abstract class.
- CMN8317E: An invocation exception occured while building the message.
- Explanation: This error occurs when an exception is thrown by an invoked method or constructor. In the e-mail connector, methods that can cause this error are the constructors of BodyPart and MultiPart, plus the setDataHandler, setDisposition, and setFileName.
Action: Ensure that the input parameters match the signatures of the methods.
- CMN8318E: Exception occurred when using the Message class constructor. Error: {0}
- Explanation: Messaging system cannot invoke the class with name property being "Message" (by default, javax.mail.internet.MimeMessage, speicified under TransportConfig section) in the <instance>.xml file.
Action: Make sure that the class speicified is properly loaded for WebSphere Commerce within the WebSphere Application Server.
- CMN8319E: Exception occurred when the messaging system sent the message: {0}
- Explanation: An exception occurred when the messaging system sent the message. The exception is likely due to missing mandatory attributes set for the sending operation.
Action: Please see the related exception information in the same thread for reference.
- CMN8321E: The Message class does not contain a constructor taking a parameter of type Object.
- Explanation: The signature of the constructor is invalid because it contains a parameter of type Object.
Action: Check the customized code that set the contents of the message, and make sure it is not passing in a whole object as parameter.
- CMN8322E: A recipient must be specified.
- Explanation: When an e-mail message was constructed, there was no recipient specified. There are two ways a recipient can be specified. Statically, a recipient can be added in the Administration Console during message type configuration. Dynamically, the recipient can be set using the API in the SendMsgCmd or Messaging class in a JSP or command.
Action: Ensure that an e-mail address is added in the Administration Console by selecting Message Types under the Configuration menu. Set up the recipient using the API in the SendMsgCmd, or the Messaging class in a JSP.
- CMN8323E: The setAddress method cannot be found.
- Explanation: Messaging system cannot find the method with name, "setAddress", in the message class defined under property name, "Address" (by default, javax.mail.internet.InternetAddress, speicified under TransportConfig section) in the <instance>.xml file.
Action: Make sure that the method with name "setAddress" is provided by the class specified under property name "Address" in the TransportConfig section of the <instance>.xml file.
- CMN8324E: The connection spec properties have not been specified.
- Explanation: The "host" or "protocol" properties for the e-mail connector have not been set up. These two properties are required for the e-mail connector. They can be assigned in the Administration Console or by creating an override in a JSP/Java class that generates the send command.
Action: Ensure that the "host" and the "protocol" properties are either set up in the Administration Console by selecting the Transport and Message Type options under the Configuration menu.
Create an override in the JSP/Java class. - CMN8325E:
- Explanation: This is a generic exception used by many classes in the Messaging sub-system.
Action: Check the WebSphere Commerce ecmsg log for additional information and fix the problem accordingly. For further information, contact your IBM support representative.
- CMN8326E: There is no connection to disconnect.
- Explanation: There is no available active connection to the SMTP server to be disconnected. Apparently, an active connection to the SMTP server is lost.
Action: Check the connection between the SMTP server and WebSphere Commerce.
- CMN8327E: The message class is not in the cache.
- Explanation: Messaging system cannot find the property with name, "Message", (by default, javax.mail.internet.MimeMessage, speicified under TransportConfig section) in the <instance>.xml file. The property section is missing from the <instance>.xml file.
Action: Make sure that the property with name "Message" is defined in the TransportConfig section in the <instance>.xml file.
- CMN8328E: An I/O Exception {0} occurred.
- Explanation: Failed to create an InputStream of bytes.
Action: No action required.
- CMN8330E: An EJB CreateException occurred for {0} {2} when accessing {1} table.
- Explanation: Status message only.
Action: Use the Administration Console to properly configure the message type for the specific transport.
- CMN8331E: An EJB FinderException occurred for {0} {2} when accessing {1} table.
- Explanation: Status message only.
Action: Use the Administration Console to properly configure the message type for the specific transport.
- CMN8332E: An EJB NamingException occurred for {0} {2} while accessing {1} table.
- Explanation: Status message only.
Action: Use the Administration Console to properly configure the message type for the specific transport.
- CMN8333E: An EJB RemoteException occurred for {0} {2} while accessing {1} table.
- Explanation: Status message only.
Action: Use the Administration Console to properly configure the message type for the specific transport.
- CMN8345E: No data returned by {0}.
- Explanation: This error can occur when performing update on the Connection/Interaction Properties on a Message type or updating the status of a transport.
Action: If the error occurs in Connection/Interaction Properties update, ensure that the foreign key (PROFILE_ID) in either the CSEDITATT or the ISEDITATT database table maps to the primary key (PROFILE_ID) in the PROFILE table.
If the error occurs in Transport Status update, open the TRANSPORT database table and check whether there is a valid transport associated with the given STORE_ID and TRANSPORT_ID. - CMN8401E: The adapters (for outbound messages) have not been initialized.
- Explanation: This error is normally due to an exception that occurred while initializing the connector based on the content of the <instance>.xml file.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8402E: The runtime profile object cannot be instantiated.
- Explanation: Status message only.
Action: No action required.
- CMN8403E: The node: {0} does not exist in the serverConfiguration file.
- Explanation: The <instance>.xml file does not contain the specified node.
Action: Open the <instance>.xml file and verify its content.
- CMN8404E: The methods of the Member Address Access Bean Object cannot be accessed. Invalid Class Name is {0}.
- Explanation: Class com.ibm.commerce.user.objects.AddressAccessBean cannot be loaded. It could not be loaded by the WebSphere Application Server class loader.
Action: Please check whether the class path for WebSphere Commerce is properly configured under WebSphere Application Server. If the problem persists, contact your IBM support representative.
- CMN8405E: The structure: {0} does not exist or does not conform to the DTD.
- Explanation: The XML parser has identified a non-recoverable error (according to XML v1.0 recommendation) in the <instance>.xml file. The error reports the violation of a well-formedness constraint. Parsing stops at this point.
Action: Verify the <instance>.xml file, fix the error and restart WebSphere Commerce.
- CMN8406E: A required attribute was missing from an XML Node. Attribute: {0}.
- Explanation: During the initialization of a Connector, an XML attribute was mssing in the <instance_name>.xml file.
Action: Based on the attribute name in the ecmsg log, re-insert the XML attribute into <instance_name>.xml and restart the WebSphere Commerce instance.
- CMN8407E: A class identified in the Messaging System XML does not correspond to a java class. Class: {0}.
- Explanation: The ClassName attribute in <instance_name>.xml for a connector does not correspond to a valid Java class or the Java class is missing from the WebSphere Commerce instance classpath.
Action: Ensure the ClassName for the class listed in ecmsg log is valid. If not, correct the problem in <instance_name.xml>. If the ClassName is valid, check whether this class (either packaged as a jar or directory structure) is included in the WebSphere Commerce classpath.
- CMN8408E: The following internal messaging system error occurred: {0}.
- Explanation: This error can occur when a connector is being initialized and the set methods being used are not public, so that the runtime cannot invoke the methods directly.
This error can also occur during send transacted message, the Messaging runtime cannot serialize the Message object into a byte stream, resulting in it not being able to send the message.Action: If the error occurs in ConnectorsInfo.java, ensure that the Editable Properties are mapped to public set methods in the Connector. If the error occurs in Messaging, contact your IBM support representatives.
- CMN8409E: The Method {0} extracted from the XML does not correspond to a valid method for the class.
- Explanation: The specified method (name of a property) cannot be found in the class indicated in the connection or interaction specification.
Action: Correct the method name and restart WebSphere Commerce.
- CMN8410E: The setter method indicated in the Messaging System XML configuration is not the appropriate type. The method accepts only one parameter of type Integer, String, Float, Long, or Boolean. Method {0}
- Explanation: The set method for the Connection/Interaction properties only accepts zero or one parameter and must be of type of Integer, String, Float, Long, or Boolean. If any of these requirements are violated, the system generates the error message.
Action: Check whether the set method (in the Connection/Interaction Spec) indicated in the ecmsg log conforms to the following: 1 There is not more than one parameter in the method. 2 The parameter is of type Integer, String, Float, Long, or Boolean.
- CMN8411E: An error {0} occurred when accessing {1} table.
- Explanation: The message was not saved in the specified table due to an EJB exception.
Action: Check to ensure the correct msgtype_ID and store_ID are specified in the calling command.
- CMN8412E: An error {1} occured. No message could be found for MSGTYPE_ID {0} in table MSGTYPES.
- Explanation: The specified message does not have any corresponding records in the MSGTYPES table. An incorrect msgtype_id argument may have been specified.
Action: Check to ensure the correct msgtype_id is specified in the calling command.
- CMN8413E: No profiles could be found for MSGTYPE_ID {0} and STORE_ID {1} in table PROFILE.
- Explanation: The specified profile does not have any corresponding records in the PROFILE table. Incorrect msgtype_id and store_id arguments may have been specified.
Action: Check to ensure the correct msgtype_id and store_id are specified in the calling command.
- CMN8415E: No transport configuration can be found for MSGTYPE_ID {0} and STORE_ID {1} in table PROFILE.
- Explanation: One of the profiles does not have any corresponding transport information in the PROFILE table. Incorrect msgtype_id and store_id arguments may have been specified, or the transport configuration is incomplete.
Action: Use the Admin Console to properly configure the message type for the specific transport.
- CMN8416E: ClassCastException occurred when casting transport ID from table {0}.
- Explanation: After the Transport ID is retrieved from the PROFILE table and put in a Property class, the runtime cannot cast the Transport ID back to Integer.
Action: Make sure the TRANSPORT_ID column in the TRANSPORT table is of type Integer and that Transport_ID value in the Property class has not been modified.
- CMN8417E: Transport_ID specified in the PROFILE table is not valid.
- Explanation: The TRANSPORT_ID specified in the PROFILE table is not valid.
Action: Examine the tranport_ID column in the PROFILE tables and make sure that all the TRANSPORT_IDs have the corresponding entries in the TRANSPORT table.
- CMN8418E: Error {1} occurred in the messaging system. The ADDRESS ENTRY object for Member {0} was not found.
- Explanation: This error occurs when there is no e-mail address associated with the member. In this case, there will be no row in the ADDRESS database table associated with that member.
Action: Make sure that there is at least one e-mail address associated with each member during the registration process. Verify this in the ADDRESS database table.
- CMN8420E: Messaging system cannot find the profile entry object for user's view preference. Error: {0}
- Explanation: Messaging system cannot find users view preference specified in PROFILE.USERSVIEW for a member.
Action: Make sure that MBRBIEWPRF table has a entry with correct PREFERENCE and VIEWNAME for the member with the MEMBER_ID. All the other corresponding tables, for examples USERPVCDEV and DEVICEFMT, should be configured properly.
- CMN8421E: Messaging system cannot find an initialized MessageTransport.
- Explanation: The messaging system cannot find the required initialized MessageTransport. The transport may not have the necessary connection and interaction specification defined.
Action: Ensure that both the transport and the message type have the required connection and interaction specification defined.
- CMN8423E: Messaging system. The composer encountered the following error: {0}.
- Explanation: The location or name of the JSP file indicated in the VIEWNAME.DOCNAME (in VIEWREG table) being used may be missing or may not match the actual file location.
The viewname is identified using the STOREENT_ID id. If the viewname record for the STOREENT_ID used in the command cannot be found, viewname with STOREENT_ID=0 will be used. However, before the system can look up the JSP file for compilation, the store name will be appended to the front of the JSP file name, if "&storeDir=no" is not appended to the end of the JSP file in the VIEWNAME.DOCNAME column.
The correct location of the JSP file depends on whether the calling command belongs to the Tools or Stores Web module. The full path of the JSP file should be located under the document root location of the Web module appended with the path described in the previous paragraph.
Action: Either correct the file path/name in VIEWNAME.DOCNAME column or put the JSP file to the desired location according to VIEWNAME.DOCNAME.
- CMN8424E: An exception {1} occurred when accessing the item at the index {0}.
- Explanation: Status message only.
Action: No action required.
- CMN8425E: The adapter for the transport was not initialized. Error: {0}
- Explanation: This error is normally due to an exception that occurred while parsing the <instance>.xml file.
Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.
- CMN8426E: Messaging system cannot find a MessageTransport object for transport {0}.
- Explanation: The messaging system cannot find a MessageTransport object for the specified Transport_ID. The transport specified by the outbound message cannot be found and, therefore, the message cannot be sent.
Action: Ensure the message type has been properly assigned to an active and well-defined TRANSPORT by WebSphere Commerce Administration Console. Details on assigning a message type to a transport can be found in the online documentation.
- CMN8427E: Messaging system cannot recognize the specification properties.
- Explanation: An unrecognized specification section (neither connection nor interaction specification) was identified for the transport. The outbound message being processed cannot be sent.
Action: Ensure that only connection and interaction specification properties can be stated for a transport in an <instance>.xml file.
- CMN8428E: Messaging system cannot instantiate either the connection or interaction specification class.
- Explanation: The messaging system cannot instantiate an instance object of either connection or interaction specification class.
Action: Make sure that the <instance>.xml has the correct connection and interaction specification class name specified and they only contain the valid connection or interaction specification attributes.
- CMN8429E: The ConnectionSpec class or InteractionSpec class is not accessible{0}.
- Explanation: This error occurs when the specification class does not have a public zero-argument constructor. As a result, the Messaging system cannot create a new instance (using newInstance( ) ).
Action: Ensure the specification class has a public zero-argument constructor. This class can be found in the <WebSphere Application Server directory>/installedConnectors.
- CMN8430E: The property {1} has no value {0}.
- Explanation: The property specified in the <instance>.xml file contains no value.
Action: Open the <instance>.xml file and check the specified property and its value.
- CMN8431E: The class named java.lang.String cannot be found.
- Explanation: The Java String class (java.lang.String) cannot be found. As the class is inside the Java Language library (java.lang), this error should not occur unless there is a critical error in the Java Runtime.
Action: Contact your IBM support representative.
- CMN8432E: An error {1} occurred. An instance of the class {0} cannot be created.
- Explanation: The package name or class name are incorrect or the class can not be found in the classpath of the WebSphere Commerce.
Action: Open the <instance>.xml file and search for the occurence of the class shown in the error message. Verify the correctness of the package and class name. Verify the class is in the classpath of the WebSphere Commerce log.
- CMN8433E: An exception {3} occurred when running {0} with {1}.
- Explanation: Status message only.
Action: No action required.
- CMN8434E: The node: {0} does not exist in the serverConfiguration file.
- Explanation: The <instance>.xml file does not contain the specified node.
Action: Open the <instance>.xml file and verify its content.
- CMN8435E: An error {1} occurred when accessing the serverConfiguration file {0}.
- Explanation: This error occured while testing in a non-WebSphre Application Server environment, because the serverConfiguration file can not be accessed.
Action: No action required.
- CMN8436E: Messaging system cannot invoke the method {1} with the specification object {0}. Error: {2}
- Explanation: The method of the specification (either connection or interaction) class cannot be invoked. An instance of the specification cannot be created.
Action: Ensure that the method names specified in properties of the connection or interaction specification of the transport (in instance.xml) have the correct spelling.
- CMN8437E: Messaging System. An error occurred. No such class is found {0}.
- Explanation: The class specified is not found.
Action: Check and verify the specified class is in the classpath setting.
- CMN8438E: Messaging System encountered a NullPointerException. A required variable was null. Class {0} Variable {1}
- Explanation: This error occurs when a connector's connection/interaction specification is initialized, and either the class name or the list of property fields is missing.
Action: Ensure that the class name and the list of property fields of the Specification Class are both present in the <instance_name>.xml file.
- CMN8439E: Messaging system error. The messaging configuration data must be initialized. The configuration parameter {0} is null.
- Explanation: The messaging system detected that the mandatory configuration data was not properly set by the calling command.
Action: Correct the command to provide the mandatory parameters before calling the message command/system. Consult the WebSphere Commerce Programing Guide for further information.
- CMN8440E: Messaging system error. The specified message {0} using type {1} must have an address.
- Explanation: When the Messaging system tries to look up the e-mail address for a particular member, there is no associated e-mail address.
Action: Make sure that there is at least one e-mail address associated to a member during the registration process. Verify this in the ADDRESS table.
- CMN8441E: The Member_ID was not set for an outbound message.
- Explanation: No MEMBER_ID has been set for a message (usually an email) to be sent. The caller command to the messaging system must set at least one MEMBER_ID for sending the message.
Action: Make sure that the command has set at least 1 MEMBER_ID when calling the messaging system.
- CMN8444E: Messaging System. The store entered is invalid. It does not exist in the database {0}.
- Explanation: Messaging system cannot find the store ID (provided by the caller command) in the database used by WebSphere Commerce.
Action: Correct the store ID and re-send the message.
- CMN8445E: Messaging System. A message is set to work with user preference, but no user preference exists. {0}
- Explanation: The specified user preference does not have any corresponding records in the USERPVCDEV table. An incorrect member_id and viewname arguments may have been specified.
Action: Check to ensure the correct member_id and viewname are specified in the calling command.
- CMN8446E: Messaging system error. This version does not accomodate non-HTTP requests via sendImmediate or sendReceiveImmediate. Use the sendTransacted method for composing non-HTTP requests.
- Explanation: Obsolete. Reason same as _ERR_MSG_CFG_NOT_INIT
Action: Obsolete. Action same as _ERR_MSG_CFG_NOT_INIT
- CMN8447E: No correlation ID available to identify the reply message.
- Explanation: An outbound JMS message has been sent out and the controller/task command is waiting for a reply. However, the correlation ID required to identify the reply message is missing.
Action: Check whether the JMS provider supports setting a correlation ID or not.
- CMN8448E: Messaging system cannot send or receive the message because the mandatory queue(s) is not defined.
- Explanation: The required JMS queue definition has not been defined.
Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the WebSphere Commerce Administration Console. Update the WebSphere Application Server namespace definition(s) of required queue(s) with the correct queue information.
- CMN8449E: Messaging system cannot send or receive the message because there is no error queue defined.
- Explanation: The JMS error queue definition has not been defined. There is a problem with the command using the receive, send, or send/receive operation.
Action: Ensure that the message type used by the command has been properly assigned to the JMS/MQ transport in the WebSphere Commerce Administration Console. Update the WebSphere Application Server namespace definition of the error queue with the correct queue information.
- CMN8450E: Messaging system cannot create a JMS QueueConnection for QueueConnectionFactory {0}. Error: {1}
- Explanation: The QueueConnection cannot be created with the JMS provider. The queue connection factory defined in the JNDI naming context may not match with the actual setup on the JMS provider. The areas of problem include the queue manager name (qmanager), transport, hostname(remote JMS server name), and listener port.
This problem may also happen when there is an access problem with a remote JMS server. It could also due to JMS provider's internal error or client authentication failure because of invalid user name or password.Action: Check the JNDI naming context settings to make sure QueueConnectionFactory is defined as outlined in the product documentation. The JMS provider settings (e.g. a MQ Server) should match the requirements of the naming context settings mentioned above. If the JMS Server is a remote server, users need to make sure the user ID running WebSphere Application Server and WebSphere Commerce is part of the user group of (or has access to) the JMS provider on the remote machine.
- CMN8451E: Messaging system cannot stop a JMS QueueConnection for QueueConnectionFactory {0}. Error: {1}
- Explanation: The QueueConnection cannot be stopped with the JMS provider. It could be due to an internal error of the JMS provider.
Action: If connection pooling on the JMS connector is enabled, check the connection timeout and enlarge it if necessary.
- CMN8452E: Messaging system cannot commit a JMS Session for QueueConnectionFactory {0}. Error: {1}
- Explanation: A JMS session cannot be committed. There could be a lock on the queue or the queue connection has been stopped.
Action: Investigate whether there is another thread working on the same queue. This problem can be avoided by synchronizing the command execution. This problem could also be a result of an internal error of the JMS provider. If this is the case, investigate the trace/log file of the JMS provider.
- CMN8453E: Messaging system cannot close a JMS Session for QueueConnectionFactory {0}. Error: {1}
- Explanation: A JMS session cannot be closed. This could be the result of an internal error of the JMS provider.
Action: Investigate the trace/log file of the JMS provider.
- CMN8454E: Messaging system cannot create sender object for queue {0}. Error: {1}
- Explanation: A sender object cannot be created under an active session. A JMS provider internal error or an invalid queue was specified for creating the sender.
Action: Check the JMS definition of either the outbound or the error queue. Investigate the trace/log file of the JMS provider.
- CMN8455E: The e-mail content is empty.
- Explanation: The input record of the e-mail adapter is empty.
Action: Check the JSP file or command that sets the input record appropriately.
- CMN8456E: A recipient must be specified.
- Explanation: When an e-mail message was constructed, there was no recipient specified. There are two ways a recipient can be specified. Statically, a recipient can be added in the Administration Console during message type configuration. Dynamically, the recipient can be set using the API in the SendMsgCmd or Messaging class in a Java Server Page or command.
Action: Ensure that an e-mail address is added in the Administration Console by selecting Message Types under the Configuration menu. Set up the recipient using the API in the SendMsgCmd, or the Messaging class in a Java Server Page.
- CMN8457E: There is no connection to disconnect.
- Explanation: There is no available active connetion to the SMTP server to be disconnected. Apparently, an active connection to the SMTP server is lost.
Action: Check the connection between the SMTP server and WebSphere Commerce.
- CMN8458E: Exception occurred when the messaging system sent the message: {0}
- Explanation: An exception occured when the messaging system sent the message. The exception is likely due to missing mandatory attributes set for the sending operation.
Action: See the related exception information in the same thread for reference.
- CMN8459D: The message was sent (partially) to the following e-mail address(es): {0}
- Explanation: Status message only.
Action: No action required.
- CMN8460E: Error {0} occurred when using the File adatper to open the file.
- Explanation: The File Connector fails to open the output file. The error can be caused by an invalid path or file name, file already in use, or not enough privileges to write to the file.
Action: Check whether the path and file name are valid for that particular platform (operating system), and that no other process is using that particular file.
- CMN8461E: Error {0} occurred when using the File adapter to close the file.
- Explanation: The File Connector fails to close the file.
Action: Check whether another process has the output file locked (still writing to this file).
- CMN8462E: Error {0} occurred when using the File adapter to write to the file.
- Explanation: The File Connector fails to write to the output file. This error may occur when the connector fails to open the file, or there is not enough disk space.
Action: Check in the WebSphere Commerce log file, and verify that the file opened without any problems. Run a disk space check to see whether you have enough disk space.
- CMN8463D: Configurable adapter property {0} is set to {1}.
- Explanation: Status message only.
Action: No action required.
- CMN8466E: Invalid connection type: The connection type is not {0}.
- Explanation: This error occurs when the connection passed into the SampleManagedConnection class is not of type SampleConnection. As a result, the SampleManagedConnection cannot process the unknown type of connection, and an exception will be thrown.
Action: Pass in the SampleConnection type into SampleManagedConnection class.
- CMN8467E: Illegal state: The connection is closed.
- Explanation: This error occurs when the connection should be available, but has been closed. As a result, the Connector cannot process any messages since the connection is in an illegal state - closed.
Action: Ensure that the connection is still available.
- CMN8468E: The connection auto commit failed.
- Explanation: This error occurs when the connection auto commit failed.
Action: Set the value of the input parameter to true when invoking the setAutoCommit(boolean param) method.
- CMN8470E: Messaging system encountered an IOException: {0}.
- Explanation: Failed to create an input stream of bytes.
Action: No action required.
- CMN8471E: The replyToQueueName {0} specifies a reply queue with an invalid queue type.
- Explanation: The reply queue in the inbound message is not of type "local" or "remote".
Action: There is no reply message generated from the inbound message. No action needed if the inbound message originator does not expect a reply message. Otherwise, correct the inbound message and re-send to WebSphere Commerce.
- CMN8472E: The replyToQueueManagerName {0} specifies a remote queue manager that is not defined in the local queue manager {1}.
- Explanation: There is a problem identifying the remote queue manager for the reply mesage.
Action: Correct either the remote queue manger of the remote queue definition (specified by the inbound message) or the inbound message with the correct queue manager name.
- CMN8473E: The replyToQueueManagerName {0} does not match the name of the local queue manager {1}.
- Explanation: The queue manager of the reply queue, specified in the inbound message, does not match the local queue manager, manager name.
Action: Correct either the local queue manger of the local queue definition (specified by the inbound message), or the inbound message with the correct queue manager name.
- CMN9003E: The value of the command parameter {0} is not valid. CMN3101E The system is unavailable due to {0}.
- Explanation: This error is normally due to a failure in the input validation logic or a failure in the value retrieval logic of the JSP file that supplies the value for the command parameter. The command is unable to proceed.
Action: Correct the JSP file or data bean that supplies the value for the command parameter.
- CMN9018E: The user identified in the configuration file does not have the correct authorization to perform this action. CMN3101E The system is unavailable due to {0}.
- Explanation: Indicates that an attempt to configure the payment information for a store failed while trying to authorize a user. The Payment Manager returned the Primary Return Code PRC_AUTHORIZATION_ERROR, "An error occurred during the user authorization."
Action: Refer to the Payment Manager documentation for details on providing users with the correct authority to configure payments.
- CMN9019E: The order must be in I or M state and it is currently in state {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The command expects the order status to be either 'I' or 'M' in order to proceed. This verification guards against the user inadvertently running the command by clicking the reload button or by clicking an action button more than once.
Action: Typically, no action required.
- CMN9032E: The value of the configuration file variable {0} must be numeric. CMN3101E The system is unavailable due to {0}.
- Explanation: The specified configuration variable can only take a numeric value.
Action: Change the value of the configuration file variable to a numeric, and restart the WebSphere Commerce Server.
- CMN9032S: Payment status not found for order {0} in store {1}.
- Explanation: There are no payment records for the order in the WebSphere Commerce Payments database. This is an informational message for the System Administrator.
Action: No action required.
- CMN9035E: The card number is invalid. The card number is invalid.
- Explanation: Some card number digits may be missing or incorrectly entered.
Action: Enter the card number correctly and in the same sequence as provided by the card issuer, then resubmit the request.
- CMN9036E: The card expiry date is invalid. The card expiry date is invalid.
- Explanation: The card expiry date is invalid. The card expiry date is usually specified by an expiry year and an expiry month, both of which are integer values.
The following checks are performed on the card expiry date. Failing any one of these checks results in this error:
- The expiry month must be an integer value that is between 1 and 12 inclusive.
- The expiry year must be an integer value that is equal to or greater than the current year.
- The expiry year and expiry month must be equal to or greater than the current year and month but less than the current date plus 10 years.
Action: The customer must enter the correct card expiry date and resubmit the request. If the card has expired, use a different card with the corresponding card expiry date.
- CMN9037E: The card number is missing. The card number is missing.
- Explanation: The card number must be provided to complete the operation.
Action: Enter the card number and resubmit the request.
- CMN9038E: The card brand is missing. The card brand is missing.
- Explanation: The card brand must be provided to complete the operation.
Action: Specify the card brand and resubmit the request.
- CMN9039E: The card expiry month is missing. The card expiry month is missing.
- Explanation: The command expects the card expiry month parameter. This parameter is expected for one of the following reasons:
1) The command has explicitly made it a mandatory parameter.
2) The expiry year was provided and the command dictates that the expiry year must always be accompanied by the expiry month.
Action: Supply the missing parameter. The card expiry month is usually expressed as an integer from 1 to 12 inclusive, with the value 1 representing the month of January.
- CMN9040E: The card expiry year is missing. The card expiry year is missing.
- Explanation: The command expects the card expiry year parameter. This parameter is expected for one of the following reasons:
1) The command has explicitly made it a mandatory parameter.
2) The expiry month was provided and the command dictates that the expiry month must always be accompanied by the expiry year.
Action: Supply the missing parameter. A four-digit year value is expected.
- CMN9041E: The payment method used for order {0} does not support this function. The payment policyId is {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The payment operation requested by the command is not a supported operation for the payment method used by the order. The payment method used by the order is specified by the payment business policy with the referenced policy ID.
Action: Avoid using this particular payment method if you expect to use this command to invoke the payment operation for the order.
- CMN9142E: Currency conversion for order {0} failed. Currency conversion for order failed.
- Explanation: Unable to convert from the order's currency to the store's default currency or another currency. An ECApplicationException is thrown with error code 1961. The order's currency and the target currency are included as exception fields "fromCurrency" and "toCurrency" respectively.
Action: Add an entry to the CURCONVERT table that leads from the order's currency to the target currency and retry the operation.
- CMN9143E: The purchase amount for order {0} exceeds the remaining spending limit of the trading agreement {1}. Purchase amount exceeds the spending limit of the Trading Agreement
- Explanation: The trading agreement used by the order items in this order has a specified spending limit. The total value of the order items exceeds this spending limit in one of the following ways:
1) The total value of the order items using this trading agreement exceeds the spending limit of the trading agreement.
2) The total value of the order items using this trading agreement exceeds the spending limit remaining for this trading agreement, when other orders and order items under this trading agreement are considered.
Action: There are two possible corrective actions: 1) Use a different trading agreement that has a sufficient remaining spending limit. 2) Reduce the total value of the order items (for example, by reducing the quantity of each item purchased) until the value is within the remaining spending limit.
- CMN9144E: The purchase amount for order {0} exceeds the remaining spending limit of the limited purchase order number {1}. Purchase amount exceeded the spending limit of the Limited Purchase order
- Explanation: The specified purchase order has a specified spending limit. The total value of the order exceeds this spending limit in one of the following ways:
1) The value of this order alone exceeds the spending limit of the purchase order.
2) The value of this order exceeds the spending limit remaining for this purchase order, when other orders that specify this purchase order number are considered.
Action: There are two possible corrective actions: 1) Use a different purchase order number that has a sufficient remaining spending limit. 2) Reduce the total value of the order (for example, by reducing the quantity of each item purchased) until the expenditure is within the remaining spending limit.
- CMN9145E: The purchase order number {0} is invalid. Purchase order is not a predefined Purchase Order and Account does not specify that Individual Purchase Order is allowed.
- Explanation: The specified purchase order is not a predefined purchase order and the account to which it is being applied does not permit the use of individual purchase orders.
Action: If the account requires that a purchase order number be specified, resubmit the order and specify the number of a predefined purchase order. Otherwise, resubmit the order without specifying a purchase order number.
- CMN9146E: The purchase order number {0} has already been used with another order. Purchase order is not a predefined Purchase Order number and the Account requires Individual Purchase Order to be unique but this purchase order number is already in use within the Account.
- Explanation: The purchase order number has already been used for a previous purchase and the account is configured to accept single-use individual purchase order numbers.
Action: Specify a different purchase order number and resubmit the order for processing.
- CMN9147E: The predefined purchase order number {0} is no longer active. Purchase order is a predefined purchase order but the purchase order is not active.
- Explanation: The purchase order number specified is no longer active.
Action: Resubmit the order for processing using an active purchase order.
- CMN9148E: Credit line {0} is not available for purchases. Credit Line is not available or not active for purchases.
- Explanation: The specified credit line is not available for purchases.
Action: Contact the Seller's Account Representative to determine which credit lines are available for purchases, or select a different payment method.
- CMN9149E: Account {0} is not unique for order {1}. Order processing failed. Account is not unique for current order.
- Explanation: The specified order has order items that use contracts associated with different business accounts. All contracts used by order items in the same order must be associated with the same business account except for contracts that have no specific account association. An example of a contract that has no specific account association is the store's default contract.
Action: Do not add order items that use contracts with business accounts different from the ones that are associated with existing contracts. The existing contracts are those used by existing order items in the specified order.
- CMN9150E: Account {0} is not active for purchases. Account is not available or not active for purchases.
- Explanation: The specified account is no longer active for purchases.
Action: Contact the Seller's Account Representative to determine which accounts are active or select a different contract that references a different account.
- CMN9520E: ApproveReversal request failed for order {1} in store {0}. Primary and secondary return codes are {2} and {3}.
- Explanation: WebSphere Commerce Payments detected an error while processing an ApproveReversal request for the order. The primary and secondary return codes from the failed operation are included with the logged message.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9523E: CancelOrder request failed for order {1} in store {0}. Primary and secondary return codes are {2} and {3}.
- Explanation: WebSphere Commerce Payments detected an error while processing a CancelOrder request for the order. The primary and secondary return codes from the failed operation are included with the message.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9526E: The Payment Cassette ''{0}'' is not active for the Store {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: Indicates that an attempt to configure the specified cassette for the specified store failed. The Payment Manager returned the Primary Return Code PRC_CASSETTE_NOTRUNNING, "The cassette is not running."
This is a general exception that is produced when a Payment Manager command fails while attempting to configure the payment cassette for a store.Action: Refer to the Payment Manager documentation for details on running and configuring cassettes.
- CMN9527E: The connection to the payment server failed. CMN3101E The system is unavailable due to {0}.
- Explanation: The WebSphere Commerce Server is unable to communicate with the payment server because the connection could not be established, or the connection was lost.
The payment component is not running on the machine as specified on the payment configuration settings page.
Or, the host name of the machine where the payment component is installed is incorrectly entered on the payment configuration settings page.
Or, SSL is incorrectly configured on the machine where the payment component is installed.
Action: Install and run the payment component on the machine specified on the payment configuration settings page. If SSL is specified as the method of communication between the WebSphere Commerce Server and the payment server, follow the instructions in the WebSphere Commerce Installation Guide about enabling SSL for the Web server and the WebSphere Application Server. This is especially important if the payment component is installed on a different machine than the WebSphere Commerce Server.
- CMN9528E: The ''{0}'' request failed. Primary and secondary return codes are {1} and {2}. The returned message is ''{3}''. CMN3101E The system is unavailable due to {0}.
- Explanation: WebSphere Commerce Payments detected an error while processing the specified request. The primary and secondary return codes from the failed operation are included with the logged message. A returned message may also be included if one is returned from the failed operation.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9529E: The ''{0}'' request failed for the store {1}. Primary and secondary return codes are {2} and {3}. The returned message is ''{4}''. CMN3101E The system is unavailable due to {0}.
- Explanation: WebSphere Commerce Payments detected an error while processing the specified request for the store. The primary and secondary return codes from the failed operation are included with the message. A returned message may be included if one is returned from the failed operation.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9530E: The ''{0}'' request failed for the order {2} in store {1}. Primary and secondary return codes are {3} and {4}. The returned message is ''{5}''. CMN3101E The system is unavailable due to {0}.
- Explanation: WebSphere Commerce Payments detected an error while processing the specified request for the order. The primary and secondary return codes from the failed operation are included with the logged message. A returned message may also be included if one is returned from the failed operation.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9531E: The CollectPayment directive of the cashier function failed for order {1} in store {0}. Primary and secondary return codes are {2} and {3}. The returned message is ''{4}''. CMN3101E The system is unavailable due to {0}.
- Explanation: The return codes are explained in the payment component documentation. A returned message may be included if one is returned by the cashier function.
Action: Consult the "IBM WebSphere Commerce Payments for Multiplatforms Programmer's Guide and Reference" or the appropriate Cassette Supplement for the corrective action that corresponds to the primary and secondary return codes.
- CMN9532E: The cashier function returned the following error during payment processing: {0}. CMN3101E The system is unavailable due to {0}.
- Explanation: The specific payment processing error is returned in the message. Normally, this error is caused when the payment cassette is incorrectly configured, or there are invalid Parameter statements in the cashier profile.
Action: Consult the payment cassette and payment component documentation. Correct the error and resubmit the request.
- CMN9533E: Store {0} is not authorized to use the cashier profile identified by payMethodId parameter {1}. CMN3101E The system is unavailable due to {0}.
- Explanation: The payMethodId parameter identifies the row in the PAYMTHD table that contains the cashier profile for payment processing. The PAYMTHDSUP table specifies which store is allowed to use which profile. Out of the box, all of the supplied cashier profiles from WebSphere Commerce Suite version 5.1 can be used by all of the stores belonging to the default store group (storeEntityId -1). However, If you have added entries to the PAYMTHDSUP table that are specific to a store, then only those payment methods identified by the entries can be used by the store.
Action: Add an entry to the PAYMTHDSUP table for the specified store with the specified payMethodId parameter. Or use the new policyId parameter to identify a payment business policy to use. The policyId parameter identifies the payment business policy to use for payment processing.
- CMN9534E: Store {0} and store group {1} are not authorized to use the cashier profile identified by payMethodld parameter {2}. CMN3101E The system is unavailable due to {0}.
- Explanation: The payMethodId parameter identifies the row in the PAYMTHD table that contains the cashier profile for payment processing. The PAYMTHDSUP table specifies which store is allowed to use which profile. Out of the box, all of the supplied cashier profiles from WebSphere Commerce Suite version 5.1 can be used by all of the stores belonging to the default store group (storeEntityId -1). However, If you have added entries to the PAYMTHDSUP table that are specific to a store, then only those payment methods identified by the entries can be used by the store.
Action: Add an entry to the PAYMTHDSUP table for the specified store with the specified payMethodId parameter. Or use the new policyId parameter to identify a payment business policy to use. The policyId parameter identifies the payment business policy to use for payment processing.
- CMN9536E: Administrator ''{0}'' is not authorized to administer store {1} in WebSphere Commerce Payments. CMN3101E The system is unavailable due to {0}.
- Explanation: The WebSphere Commerce Server uses a configuration-defined administrator ID when sending payment administrative commands or operation commands to the WebSphere Commerce Payments server. The specified ID must be authorized to send these commands to the WebSphere Commerce Payments server. In this case, the ID does not have the required authorization.
Action: By default, the configuration-defined administrator ID used when sending these commands is "wcsadmin". This ID is pre-assigned to have the Payment Manager Administrator role in WebSphere Commerce Payments database and this error should not occur. Normally, there is no need to change this configuration-defined administrator ID. If, however, your WebSphere Commerce configuration uses a WebSphere Commerce Payments server that is owned by an outside service provider, you may have to change the configuration-defined ID to an ID specified by the service provider. This change is done by manually editing the WebSphere Commerce configuration file. For instructions on how to make this change, refer to the "Enabling shared use of WebSphere Commerce Payments" section of the WebSphere Commerce online help. Note that this configuration-defined ID is used for WebSphere Commerce Server to WebSphere Commerce Payments server communications. This is different from administrator to WebSphere Commerce Payments server interactions. All administrator to WebSphere Commerce Payments server interactions are done using the administrator's logon ID.
- CMN9537E: Administrator ID ''{0}'' is not an active WebSphere Commerce administrator ID. CMN3101E The system is unavailable due to {0}.
- Explanation: The WebSphere Commerce Server uses an administrator ID when sending payment administrative commands or operation commands to the WebSphere Commerce Payments server.
This error message indicates that the ID is no longer active.Action: Ensure the administrator ID specified is active by attempting to log on to the WebSphere Commerce Administration Console using the ID. If the ID is inactive or disabled, log on using an alternate ID with the Site Administrator priviledges and reactivate the ID that is used when sending these payment related commands. Retry the payment operation.
- CMN9538E: A password is required for administrator ''{0}''. CMN3101E The system is unavailable due to {0}.
- Explanation: The administrator with the specified logon ID does not have a registered password. The administrator ID is unable to log on to the system as the user cannot be authenticated.
Action: Supply a password when creating a logon ID for an administrator. If the logon ID has already been created, add a password. Do not allow the client tool to create an administrator ID without an associated password.
- CMN9539E: Order number {0} for store {1} already exists in the WebSphere Commerce Payments database. CMN3101E The system is unavailable due to {0}.
- Explanation: In WebSphere Commerce Payments, an order record is identified by an order number ID that is owned by a merchant object. The merchant object is identified by a unique merchant number ID and all order numbers under each merchant object must be unique. Order number IDs can be reused, as long as they are under different merchant objects.
This error message indicates that the order (with the specified order number ID and where the merchant number ID is equal to the WebSphere Commerce store ID) cannot be created in the WebSphere Commerce Payments database because this order already exists in the database. This can be caused when multiple commerce systems have the same merchant number IDs and use the same WebSphere Commerce Payments server.
This error can also be caused if the WebSphere Commerce database rolls back after the order has been created in the WebSphere Commerce Payments database. This is extremely rare.
Action: If multiple commerce systems use the same WebSphere Commerce Payments server, ensure that each commerce system uses a unique merchant number ID. This ensures that the orders from one commerce system will not be mixed with the orders from other commerce systems.
- CMN9540E: Order number {0} for store {1} does not exist in the WebSphere Commerce Payments database. CMN3101E The system is unavailable due to {0}.
- Explanation: The order identified in the message does not exist in the WebSphere Commerce Payments database. The order may have inadvertently been deleted from the database by an outside function.
Action: Check the WebSphere Commerce Payments log to ensure that the order has not been deleted by an administrative action.
- CMN9541E: Order number {0} for store {1} is not in a refundable state. CMN3101E The system is unavailable due to {0}.
- Explanation: The DoRefund task command is unable to proceed with the refund request because the specified order is not in a refundable state.
The point at which an order enters a refundable state depends on the payment type (or in the case of WebSphere Commerce Payments, it depends on the payment cassette used). For some payment types, an order is refundable only after payment for the order has been captured. There are, however, payment types that allow a refund to occur before any payment is captured. For this second group of payment types, the payment cassette moves the order to a refundable state as soon as the order is submitted to WebSphere Commerce Payments.
Action: Ensure that the order is in a refundable state before calling the DoRefund task command.
- CMN9600D: The file {0} is not available.
- Explanation: The BIShowReport command is not able to retrieve the specified file. The file does not exist in the specified directory. This is caused by one of the following:
- The Reports document root field on the Commerce Accelerator page of the WebSphere Commerce Configuration Manager contains incorrect path information.
- WebSphere Commerce Analyzer is not installed or is configured incorrectly.
- WebSphere Commerce Analyzer has not generated the requested report.
Action: Depending on the source of the error, perform one of the following solutions: - Ensure that the Reports document root field contains the correct path information. - Ensure that WebSphere Commerce Analyzer is installed and configured correctly. - Ensure that WebSphere Commerce Analyzer has generated the requested report at least once.
- CMN9601D: The specified file, {0} has an unsupported file type.
- Explanation: The BIShowReport command is supplied with a file that has an unsupported file name extension. The file name extensions supported by the command are: css, gif, htm, html, and jpg.
Action: - Ensure the file has a supported file name extension.
- CMN9650E: The price cannot be retrieved from the price policy. CMN3101E The system is unavailable due to {0}.
- Explanation: Each store and contract must contain at least one price policy. The price list ID will be retrieved from price policy. Either the business policy does not exist or the Properties field content is not correct.
Action: Verify that there is at least one price policy which belongs to the specified store and the specified contract. Use the ecmsg.log file to obtain the store ID and contract ID.
- CMN9651E: Publishing custom price list failed. CMN3101E The system is unavailable due to {0}.
- Explanation: A custom price list is generated when you create a contract using the WebSphere Commerce Accelerator . An XML string is generated and stored in the XMLDEFINITION row of the TRDPSCNXML table. The error indicates that either the XML string is not available or there are enterprise bean errors.
Action: This is a system error. Check the WebSphere Application Server EJB error log to find the source of the problem. Follow the recovery action suggested for the problem and retry.
- CMN9652E: WebSphere Commerce encountered errors when exporting the contract. The contract was not successfully exported. CMN3101E The system is unavailable due to {0}.
- Explanation: This exception is thrown if the provided encoding is unsupported or the file name is incorrect and cannot be created.
Action: Check the encoding and the file name. If you think both of those are right, please contact your system administrator.
- CMN9655E: Trading object cannot be null in constructor of ProductSetSelection. CMN3101E The system is unavailable due to {0}.
- Explanation: The constructor of ProductSetSelection needs trading objects. If the trading object is null when calling the ProductSetSelection, this error will occurs.
Action: Please make sure a user has at least one entitled contract.
- CMN9800E: You do not have authority to make transitions for the {0} event. CMN3101E The system is unavailable due to {0}.
- Explanation: The user does not have the authority to run the action command for the transition.
Action: Check the access control policy for the command to make sure the user has authority to run the command.
- CMN9801E: All business logic guards fail for the event:{0}. CMN3101E The system is unavailable due to {0}.
- Explanation: All business logic guards checking failed for the event.
Action: Enusre that the command implementing the business logic guards is working appropriately.
- CMN9802E: The transition:{0} requires an action command. CMN3101E The system is unavailable due to {0}.
- Explanation: The transition action cannot be null.
Action: Make sure the transition action is not null. Check the database by running the following SQL query: "select actioninterface from fltransitn where flow_id=? and eventidentifier=? and sourcestate_id=? and targetstate_id=?" You need to replace the ? in the above sql statement with the actual values.
- CMN9803E: The action command:{0} does not implement the BusinessFlowCmd interface. CMN3101E The system is unavailable due to {0}.
- Explanation: The action command for the transaction requires to implement the BusinessFlowCmd interface.
Action: Check the java class for the action command to see if it implements the BusinessFlowCmd interface. If not, modify the class to implement the BusinessFlowCmd interface.
- CMN9804E: The data bean class {0} does not implement the BusinessFlowEntityBean interface. CMN3101E The system is unavailable due to {0}.
- Explanation: The resource data bean class must implement the BusinessFlowEntityBean interface.
Action: Check the Java class for the resource data bean to see if it implements the BusinessFlowEntityBean interface. If not, modify the data bean class to implement it.
- CMN9851E: A request needs to be approved, but there are no users assigned to the approval member group named {0} (owned by org id {1}). The request needs to be approved, but there are no approvers assigned to do the approval.
- Explanation: There no users assigned to the approval member group.
Action: Make sure you have users assigned in the approval member group. Check database by running the following SQL query: "select m.member_id from mbrgrp g, mbrgrpmbr m where g.mbrgrp_id = m.mbrgrp_id and m.exclude = '0' and mbrgrpname = '?' and owner_id = ?" You need to replace the ? with the actual values.
- CMN9852E: The system detected an error while prefiltering for access control within the system. CMN3101E The system is unavailable due to {0}.
- Explanation: The access control policies are not set up properly.
Action: Check the access control policies in the database to see if the user has the access control policy to execute the action with the resources.
- CMN9907E: A resource exception occured during processing: {0}.
- Explanation: This error occurs when a generic J2EE resource exception is thrown.
Action: Check the WebSphere Commerce log for additional information and fix the problem accordingly. For further information, contact your IBM support representative.
- CMN9908E: The JNDI name is either null or empty.
- Explanation: This error occurs when the messaging framework is trying to do a JNDI lookup, and the JNDI name cannot be found. As a result, the messaging framework cannot create the ConnectionFactory instance.
Action: Ensure that the JNDI name which is specified in the outbound connector section of <instance_name>.xml is the same as the "JNDI binding path" that is used to deploy a resource adapter in WebSphere Application Server.
- CMN9910E: Failed initializing license API: {0}. Failed initializing license API: {0}.
- Explanation: Could not initialize the APIs to verify the license information.
Action: Contact your IBM support representative.
- CMN9911E:
- Explanation: The usage limit for product WebSphere Commerce (5724A18), has been exceeded. The system operator has been notified.
Action: Use the Work with License Information (WRKLICINF) command and select option 2 (Change) to increase the usage limit. The usage limit should be increased only if it will match the limit authorized by the software provider. If the software provider authorized limit has been exceeded, the software provider must be notified immediately to update the authorized limit and start the appropriate order and billing processes.
- CMN9912E:
- Explanation: License information for WebSphere Commerce (5724A18), release V5R5M0 could not be retrieved. Refer to previously listed messages. If no previous messages are found, the product is not correctly installed on the system.
Action: Ensure that the QWEBCOMM55 library exists. If the library does not exit, the product was not installed correctly.