WebSphere Commerce messages

+

Search Tips   |   Advanced Search

 

CEPBankServACH0606

Explanation: An internal error occurred in the cassette. The exception text will help IBM support identify the location of the problem.

Action: If some required operation or service is not functioning properly, contact your IBM support representative.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH2001

Explanation: The specified merchant already has an account for the specified account number.

Action: Try to create the account again, but specify an account number that does not already exist.

CEPBankServACH2002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH2003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH2004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH2005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH2006

Explanation: A bad return code ("RB") was returned in the batch settlement response. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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 defined per merchant.

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 database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH3002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH3003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH3004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH4003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH4004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH4005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 the order.

CEPBankServACH5001

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH5003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH5004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH5005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7001

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7002

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7003

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7004

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7005

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH7006

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH8000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH8001

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH9000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH9001

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH9002

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPBankServACH9003

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 a need for it or use a different method.

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 could be due to an error connecting to or accessing the database, or due to an error in the content of the data.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPCustomOffline2001

Explanation: An SQL exception occurred while closing CUSTOMACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline2003

Explanation: This insertion is only supposed to insert one row, but more than one row was inserted. This condition should not happen but if it does, contact support.

Action: None

CEPCustomOffline2004

Explanation: An SQL exception occurred while inserting a row into the CUSTOMACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server. Also make sure that the database user is authorized to access the WebSphere Commerce Payments database.

CEPCustomOffline2005

Explanation: The update should have changed only one row but more than one row were affected.

Action: None

CEPCustomOffline2006

Explanation: SQL exception occurred while reading a WebSphere Commerce Payments database table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline2007

Explanation: The deletion is only supposed to delete one row, but more than one row was deleted. This condition should not happen but if it does, contact support.

Action: Contact your IBM support representative.

CEPCustomOffline2008

Explanation: An SQL exception occurred while inserting a row into the CUSTOMACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server. Also make sure that the database user is authorized to access the WebSphere Commerce Payments database.

CEPCustomOffline2009

Explanation: The socket connection that performs the communication between the cassette and the CustomOffline CashRegister failed to close successfully.

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 to happen on a production system.

Action: Contact your IBM support representative.

CEPCustomOffline3000

Explanation: An SQL query of CUSTOMBATCH table should have returned only one row but multiple rows were returned. The merchant number is merchant_number and batch number is number.

Action: Contact your IBM support representative.

CEPCustomOffline3001

Explanation: An SQL query of CUSTOMBATCH table should have returned only one row but multiple rows were returned. The merchant number is merchant_number and batch number is number.

Action: Contact your IBM support representative.

CEPCustomOffline3002

Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline3003

Explanation: An SQL exception occurred while closing the CUSTOMBATCH table query. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline3004

Explanation: This insertion is only supposed to insert one row, but more than one row was inserted. This condition should not happen but if it does, contact support.

Action: Contact your IBM support representative.

CEPCustomOffline3005

Explanation: SQL exception occurred while inserting into the CUSTOMBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline3006

Explanation: The update is only supposed to affect one row, but more than one row was updated. This condition should not happen but if it does, contact support.

Action: Contact your IBM support representative.

CEPCustomOffline3007

Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline3008

Explanation: An SQL delete of CUSTOMBATCH table should have returned only one row but multiple rows were returned.

Action: Contact your IBM support representative.

CEPCustomOffline3009

Explanation: An SQL exception occurred while reading the CUSTOMBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline3010

Explanation: This is a sanity check in the processing of request. A user may not see this.

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 but multiple rows were returned.

Action: Contact your IBM support representative.

CEPCustomOffline4001

Explanation: An SQL query of the CUSTOMORDER table should have returned one row but nothing was returned.

Action: Contact your IBM support representative.

CEPCustomOffline4002

Explanation: An SQL exception occurred while querying the CUSTOMORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline4003

Explanation: An SQL exception occurred while closing the CUSTOMORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline4004

Explanation: An SQL insertion into the CUSTOMORDER table should have inserted one row but multiple rows were affected.

Action: Contact your IBM support representative.

CEPCustomOffline4005

Explanation: An SQL exception occurred while inserting into the CUSTOMORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline4006

Explanation: An SQL update of the CUSTOMORDER table should have updated one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPCustomOffline4007

Explanation: An SQL exception occurred while updating the CUSTOMORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline4008

Explanation: An SQL delete of the CUSTOMORDER table should have deleted one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPCustomOffline4009

Explanation: An SQL exception occurred while deleting an order from the CUSTOMORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline4010

Explanation: While closing a batch, it was discovered that the batch contained a payment whose order is in the wrong state.

Action: Contact your IBM support representative.

CEPCustomOffline4011

Explanation: While closing a batch, it was discovered that the batch contained a credit whose order is in the wrong state.

Action: Correct the state and close the batch again.

CEPCustomOffline5000

Explanation: While querying for a payment, it returned multiple entries. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPCustomOffline5001

Explanation: While querying for a payment that should have returned one row, nothing was returned. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPCustomOffline5002

Explanation: An SQL exception occurred while querying from the CUSTOMPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline5003

Explanation: An SQL exception occurred while closing from the CUSTOMPAYMENT table query. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline5004

Explanation: An SQL insertion into the CUSTOMPAYMENT table should have inserted one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPCustomOffline5005

Explanation: An SQL exception occurred while inserting a new payment into from the CUSTOMPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline5006

Explanation: While updating a payment that should have affected one row, multiple rows were returned. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPCustomOffline5007

Explanation: An SQL exception occurred while updating the CUSTOMPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline5008

Explanation: While deleting a payment that should have affected one row, multiple rows were returned. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPCustomOffline5009

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline5010

Explanation: While closing a batch, it was discovered that the batch contained a payment in the wrong state.

Action: Contact your IBM support representative.

CEPCustomOffline6000

Explanation: While querying the CUSTOMCREDIT table, it was supposed to return one row but it returned multiple entries.

Action: Contact your IBM support representative.

CEPCustomOffline6001

Explanation: While querying the CUSTOMCREDIT table, it should have returned one row but nothing was returned.

Action: Contact your IBM support representative.

CEPCustomOffline6002

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline6003

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline6004

Explanation: While querying the CUSTOMCREDIT table, it should have returned one row but multiple rows are returned.

Action: Contact your IBM support representative.

CEPCustomOffline6005

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline6006

Explanation: While updating the CUSTOMCREDIT table, it should have updated one row but multiple rows are affected.

Action: Contact your IBM support representative.

CEPCustomOffline6007

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline6008

Explanation: While deleting a row from the CUSTOMCREDIT table, it should have deleted one row but multiple rows were affected.

Action: Contact your IBM support representative.

CEPCustomOffline6009

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline6010

Explanation: While closing a batch, it was discovered that the batch contained a credit in the wrong state.

Action: Contact your IBM support representative.

CEPCustomOffline7000

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline7001

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline7002

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline7003

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPCustomOffline7004

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

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 a need for it, or use a different method.

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. This could be due to an error connecting to or accessing the database, or due to an error in the content of the data.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPOfflineCard2001

Explanation: An SQL exception occurred while closing OFFLINECARDACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard2003

Explanation: This insertion is only supposed to insert one row, but more than one row was inserted.

Action: Contact your IBM support representative.

CEPOfflineCard2004

Explanation: An SQL exception occurred while inserting a row into the OFFLINECARDACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server. Also make sure that the database user is authorized to access the WebSphere Commerce Payments database.

CEPOfflineCard2005

Explanation: The update should have changed only one row but more than one row were affected.

Action: Contact your IBM support representative.

CEPOfflineCard2006

Explanation: SQL exception occurred while reading a WebSphere Commerce Payments database table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard2007

Explanation: The deletion is only supposed to delete one row, but more than one row was deleted. This condition should not happen but if it does, contact your IBM support representative.

Action: Contact your IBM support representative.

CEPOfflineCard2008

Explanation: An SQL exception occurred while inserting a row into the OFFLINECARDACCOUNT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server. Also make sure that the database user is authorized to access the WebSphere Commerce Payments database.

CEPOfflineCard2009

Explanation: The socket connection that performs the communication between the cassette and the OfflineCard CashRegister failed to close successfully.

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 to happen on a production system.

Action: Contact your IBM support representative.

CEPOfflineCard3000

Explanation: An SQL query of OFFLINECARDBATCH table should have returned only one row but multiple rows were returned. The merchant number is merchant_number and batch number is number.

Action: Contact your IBM support representative.

CEPOfflineCard3001

Explanation: An SQL query of OFFLINECARDBATCH table should have returned only one row but multiple rows were returned. The merchant number is merchant_number and batch number is number.

Action: Contact your IBM support representative.

CEPOfflineCard3002

Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard3003

Explanation: An SQL exception occurred while closing the OFFLINECARDBATCH table query. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard3004

Explanation: This insertion is only supposed to insert one row, but more than one row was inserted.

Action: Contact your IBM support representative.

CEPOfflineCard3005

Explanation: SQL exception occurred while inserting into the OFFLINECARDBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard3006

Explanation: The update is only supposed to affect one row, but more than one row was updated.

Action: Contact your IBM support representative.

CEPOfflineCard3007

Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard3008

Explanation: An SQL delete of OFFLINECARDBATCH table should have returned only one row but multiple rows were returned.

Action: Contact your IBM support representative.

CEPOfflineCard3009

Explanation: An SQL exception occurred while reading the OFFLINECARDBATCH table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard3010

Explanation: This is really a sanity check in the processing of request. A user may not see this.

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 row but multiple rows were returned.

Action: Contact your IBM support representative.

CEPOfflineCard4001

Explanation: An SQL query of the OFFLINECARDORDER table should have returned one row but nothing was returned.

Action: Contact your IBM support representative.

CEPOfflineCard4002

Explanation: An SQL exception occurred while querying the OFFLINECARDORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard4003

Explanation: An SQL exception occurred while closing the OFFLINECARDORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard4004

Explanation: An SQL insertion into the OFFLINECARDORDER table should have inserted one row but multiple rows were affected.

Action: Contact your IBM support representative.

CEPOfflineCard4005

Explanation: An SQL exception occurred while inserting into the OFFLINECARDORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard4006

Explanation: An SQL update of the OFFLINECARDORDER table should have updated one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPOfflineCard4007

Explanation: An SQL exception occurred while updating the OFFLINECARDORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard4008

Explanation: An SQL delete of the OFFLINECARDORDER table should have deleted one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPOfflineCard4009

Explanation: An SQL exception occurred while deleting an order from the OFFLINECARDORDER table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard4010

Explanation: While closing a batch, it was discovered that the batch contained a payment whose order is in the wrong state.

Action: Contact your IBM support representative.

CEPOfflineCard4011

Explanation: While closing a batch, it was discovered that the batch contained a credit whose order is in the wrong state.

Action: Contact your IBM support representative.

CEPOfflineCard5000

Explanation: While querying for a payment, it returned multiple entries. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPOfflineCard5001

Explanation: While querying for a payment that should have returned one row, nothing was returned. This condition should not have occurred.

Action: Report the problem to your IBM support representative.

CEPOfflineCard5002

Explanation: An SQL exception occurred while querying from the OFFLINECARDPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard5003

Explanation: An SQL exception occurred while closing from the OFFLINECARDPAYMENT table query. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard5004

Explanation: An SQL insertion into the OFFLINECARDPAYMENT table should have inserted one row but affected multiple rows.

Action: Contact your IBM support representative.

CEPOfflineCard5005

Explanation: An SQL exception occurred while inserting a new payment into from the OFFLINECARDPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard5006

Explanation: While updating a payment that should have affected one row, multiple rows were returned. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPOfflineCard5007

Explanation: An SQL exception occurred while updating the OFFLINECARDPAYMENT table. The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard5008

Explanation: While deleting a payment that should have affected one row, multiple rows were returned. This condition should not have occurred.

Action: Contact your IBM support representative.

CEPOfflineCard5009

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard5010

Explanation: While closing a batch, it was discovered that the batch contained a payment in the wrong state.

Action: Change the payment state and close the batch again.

CEPOfflineCard6000

Explanation: While querying the OFFLINECARDCREDIT table, it was supposed to return one row but it returned multiple entries.

Action: Contact your IBM support representative.

CEPOfflineCard6001

Explanation: While querying the OFFLINECARDCREDIT table, it should have returned one row but nothing was returned.

Action: Contact your IBM support representative.

CEPOfflineCard6002

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6003

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6004

Explanation: While querying the OFFLINECARDCREDIT table, it should have returned one row but multiple rows are returned.

Action: Contact your IBM support representative.

CEPOfflineCard6005

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6006

Explanation: While updating the OFFLINECARDCREDIT table, it should have updated one row but multiple rows are affected.

Action: Contact your IBM support representative.

CEPOfflineCard6007

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6008

Explanation: While deleting a row from the OFFLINECARDCREDIT table, it should have deleted one row but multiple rows were affected.

Action: Contact your IBM support representative.

CEPOfflineCard6009

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6010

Explanation: While closing a batch, it was discovered that the batch contained a credit in the wrong state.

Action: Change the credit state and close the batch again.

CEPOfflineCard6100

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6101

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6102

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard6103

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard7000

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard7001

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard7002

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard7003

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPOfflineCard7004

Explanation: The SQL exception text describes the exception and provides SQL state information that can be looked up in the XOPEN SQL specification. This could be the result of a disruption in communication between WebSphere Commerce Payments and the database server, or a discrepancy between the table definition and the definition expected by WebSphere Commerce Payments.

Action: Refer to the SQL state information to get specific details about the nature of the problem. Test the database server connection and verify that the table definition matches the definition expected by WebSphere Commerce Payments.

CEPPaymentech0606

Explanation: An internal error occurred in the cassette. The exception text will help IBM support to identify the location of the problem.

Action: If some required operation or service is not functioning properly, contact your IBM support representative.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech2001

Explanation: The specified merchant already has an account defined. Each merchant can have only one account associated with it.

Action: Try to create the account again but specify a different merchant number, or delete the existing merchant's account and re-create it.

CEPPaymentech2002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech2003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech2004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech2005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech2006

Explanation: A bad return code ("RB") was returned in the batch settlement response. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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 number.

Action: Try the request again, but specify a division number that does not already exist.

CEPPaymentech2012

Explanation: The specified merchant already has a division defined for the specified currency code.

Action: Re-attempt the request, specifying a currency code that does not already exist.

CEPPaymentech3000

Explanation: The specified batch for the specified merchant was not found in the WebSphere Commerce Payments database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech3002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech3003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech3004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech4003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech4004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech4005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 the order.

CEPPaymentech5001

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech5003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech5004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech5005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 while depositing the indicated payment.

Action: Contact your Paymentech representative to determine why the deposit was not successful.

CEPPaymentech6000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech6001

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech6002

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech6003

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 the specified order.

CEPPaymentech6006

Explanation: The Request For Response (RFR) response returned from Paymentech indicated that an error occurred while refunding the specified credit.

Action: Contact your Paymentech representative to determine why the refund was not successful.

CEPPaymentech7000

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7001

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7002

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7003

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7004

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7005

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech7006

Explanation: An SQL exception occurred while processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech8000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech8001

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech9000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech9001

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech9002

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPPaymentech9003

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 IBM service identify the location of the problem.

Action: If some required operation or service is not functioning properly, contact IBM Service.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet2001

Explanation: The specified merchant already has an account for the specified account number.

Action: Re-attempt the CreateAccount request, specifying an account number that does not already exist.

CEPVisaNet2002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet2003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet2004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet2005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet2006

Explanation: A bad return code ("RB") was returned in the batch settlement response. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in a Detail record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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. The error occurred in the Header, Parameter, or Trailer record. Batch reconciliation must occur in order to settle the batch.

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 Terminal Number.

Action: Re-attempt the CreateAccount request, specifying an account that has a different Store Number and a different Terminal Number.

CEPVisaNet3000

Explanation: The specified batch for the specified merchant was not found in the WebSphere Commerce Payments database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet3002

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet3003

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet3004

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 database.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet4003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet4004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet4005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 the specified order.

CEPVisaNet5001

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet5003

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet5004

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet5005

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet6001

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet6002

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet6003

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

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 the specified order.

CEPVisaNet7000

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7001

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7002

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7003

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7004

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7005

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet7006

Explanation: An SQL exception occurred processing a result set that was obtained by querying a database view. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet8000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet8001

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet9000

Explanation: An SQL exception occurred while retrieving a record from the WebSphere Commerce Payments database. This could be due to an error connecting to or reading from the database, or due to an error in the content of the data that was read from the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet9001

Explanation: An SQL exception occurred while creating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet9002

Explanation: An SQL exception occurred while updating a record in the WebSphere Commerce Payments database. This could be due to an error connecting to or writing to the database, or due to an error in the content of the data that is being written to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet9003

Explanation: An SQL exception occurred while deleting a record in the WebSphere Commerce Payments database. This could be due to an error connecting to the database.

Action: Check the connection to the database to make sure that there is not a problem with the communication between the WebSphere Commerce Payments machine and the database server.

CEPVisaNet9005

Explanation: Unable to encrypt/decrypt the PAN or expiration date.

Action: Contact your service representative.

CMN0001E

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.

CMN0007S

Explanation: Status message only.

Action: No action required.

CMN0008S

Explanation: Status message only.

Action: No action required.

CMN0009S

Explanation: This is a status message to indicate the component is enabled.

Action: No action required.

CMN0009W

Explanation: This message warns the administrator that the specified SQL query has reached or exceeded the limit on the number of values that can be returned (and that any values in excess of the limit have been suppressed).

Action: If this error becomes frequent, add a new JVM system property to the WebSphere Commerce Server instance to increase the maximum number of results.

CMN0010S

Explanation: This is a status message to indicate the component is disabled.

Action: No action required.

CMN0103E

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

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

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.

CMN0110E

Explanation: The command factory cannot create a new instance of {0} for a command interface {1}. Possible problem : (1) Either command implementation class name {0} is incorrect or it does not implement the interface {1}. (2) The class is not loaded properly

Action: Verify that the class name {0} is correct and it implements the interface {1} and that it is included in the classpath.

CMN0111E

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.

CMN0112E

Explanation: The WebSphere Commerce Server has caught the specified exception during the specified initialization step.

Action: React accordingly to the wrapped exception and the associated error log.

CMN0201E

Explanation: The path provided may contain an error or invalid information.

Action: Verify that the path you have specified is correct or specify a new path.

CMN0203E

Explanation: The name of the command specified cannot be resolved to an implementation. The WebSphere Commerce server attempted to resolve a URL request to a command implementation or the command interface specified cannot be resolved to an implementation.

Action: Ensure that the specified command has been defined in the appropriate configuration files.

If the command is a URL request, ensure the struts configuration files contains the action configuration between the URL and the command interface name that represents that URL.

If the command cannot be resolved based on the command interface name, update the CMDREG table to contain a mapping between the interface name and the command implementation.

If the changes were made to the configuration files while the server is running, the registries may need to be refreshed. Refreshing the registries can be done using the WebSphere Commerce Administration Console by navigating to the Configuration > Registry menu and updating either the struts or command registry.

CMN0205E

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

Explanation: Exception occurred when the command was executed.

Action: Fix the problem according to the exception information as shown.

CMN0211E

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.

CMN0214E

Explanation: A non-recoverable database has error occurred.

Action: Contact your sytem administrator.

CMN0215E

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

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

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

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.

CMN0304S

Explanation: This is a status message to indicate that OrderItems are being inserted in the database.

Action: No action required.

CMN0306S

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

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

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.

CMN0409E

Explanation: This generic exception wraps another unexpected exception thrown during processing.

Action: Contact WebSphere Commerce support.

CMN0410E

Explanation: The WebSphere Commerce logging facility could not find the property file message for the key within the specified property file. This message only affects the logging of system errors but does not necessarily mean there is a problem with the operation of the WebSphere Commerce server.

Action: Contact WebSphere Commerce support to check for any updated messages.

CMN0411E

Explanation: This generic exception wraps another exception thrown when a record cannot be found in the WebSphere Commerce database. The specified primary key for the record may not exist.

Action: Ensure the primary key used for the lookup exists.

CMN0412E

Explanation: This generic exception wraps another exception thrown during communication with a remote object such as an enterprise bean.

Action: React accordingly to the wrapped exception. If the problem persists, contact WebSphere Commerce support.

CMN0413E

Explanation: This generic exception wraps another exception thrown during an unsuccessful attempt to create a database record using an enterprise bean. A record with the same unique index may already exist or the record may have relationships to other tables that are not valid for the particular values specified.

Action: Ensure that the values specified for the create operation do not violate database constraints.

CMN0414E

Explanation: An unexpected null value was encountered, indicating the system state may be invalid.

Action: System Administrators should review the WebSphere Commerce log files and take action to correct any previous errors. Contact WebSphere Commerce Support if the problem is not resolved.

CMN0415E

Explanation: This generic exception wraps another exception thrown during an attempt to remove an enterprise bean.

Action: If this problem persists, contact WebSphere Commerce support.

CMN0416E

Explanation: The specified data could not be converted into a number.

Action: Ensure the specified data is a number.

CMN0417E

Explanation: This generic exception wraps an SQL exception.

Action: React accordingly to the wrapped exception.

CMN0419E

Explanation: This exception is thrown by the data bean manager when the WebSphere Commerce Server detects a double-click or multi-click condition and needs to cancel execution of the current request.

Action: Contact WebSphere Commerce support.

CMN0420E

Explanation: The data bean manager or the WebSphere Commerce server has detected an unexpected exception when populating a data bean or invoking a command.

Action: React accordingly to the wrapped exception and the accompanying exception stack.

CMN0422E

Explanation: The WebSphere Commerce Server has detected an enterprise bean naming exception during an attempt to access an enterprise bean.

Action: React accordingly to the wrapped exception.

CMN0423E

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.

CMN0424E

Explanation: The current transaction has been rolled back. The reason for the rollback is included in the wrapped system exception.

Action: React accordingly to the wrapped exception. If the problem persists, contact WebSphere Commerce support.

CMN0450E

Explanation: The WebSphere Commerce Server has detected an unexpected exception during the execution of a request.

Action: React accordingly to the wrapped exception and the exception stack.

CMN0493E

Explanation: The WebSphere Commerce Server has detected an exception during server configuration.

Action: React accordingly to the wrapped exception and the exception stack.

CMN0499E

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.

CMN0515E

Explanation: This is caused by a missing configuration parameter in the XML configuration file for promotion engine. This is a rare error. If this does occur, please check the content of this file: <i>WC_installDir</i>instances<i>instance</i>xmlPromotionEngineConfigurationWCSPromotionEngineConfig.xml. If this XML file is corrupted or does not contain the required parameter (as reported by this message), this error will be raised.

Action: Check the content of the above mentioned file. If need further assistance, contact WC support with the configuration file.

CMN0518E

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

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

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

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

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

Explanation: To plug in the directory, 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

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

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

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

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.

CMN0615E

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.

CMN0902E

Explanation: The server attempted to retrieve the current time stamp value from the WebSphere Commerce database and the result of executing the statement has failed. This can either happen if the database server is not responding or the database type is set incorrectly, so the wrong syntax is used to retrieve the time stamp from the database.

Action: Check first to ensure that the database server is responding. If the database server is responding, ensure that the database type is set correctly. The database type is configured at deployment time and can be verified by checking the value of the WCDBType environment variable on the Configurator enterprise bean (in the Enablement-BaseComponentsData module). The correct values are "DB2" for IBM DB2, "DBJ" for IBM Cloudscape, and "Oracle" for Oracle. The default if the attribute is not found is "DB2".

CMN0924E

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

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

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.

CMN1008E

Explanation: An unhandled exception was thrown from the DataCryptCmd command when the system was retrieving payment information.

Action: Check the logic of the DataCrytCmd command and ensure it does not throw invalid exceptions.

CMN1009E

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

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.

CMN1011E

Explanation: The system was unable to find a valid offer with which to price the catalog entry.

Action: There are multiple causes for this problem. Contact IBM support for assitance with problem determination.

CMN1011S

Explanation: The specified stored procedure is about to be invoked.

Action: No action required.

CMN1012S

Explanation: The specified stored procedure has returned.

Action: No action required.

CMN1013E

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

Explanation: The AllocateInventory task command is attempting to allocate inventory for the specified OrderItems.

Action: No action required.

CMN1014S

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

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

Explanation: The AllocateInventory task command is merging the specified OrderItem objects.

Action: No action required.

CMN1017S

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

Explanation: The AllocateInventory task command is abut to call the CheckInventoryAvailability task command for the specified OrderItem objects.

Action: No action required.

CMN1019E

Explanation: An incorrect password has been entered for this user and therefore the WebSphere Commerce authentication has failed.

Action: Enter the correct password for this WebSphere Commerce user.

CMN1019S

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.

CMN1021E

Explanation: Your order is in the wrong status for the function being executed.

Action: The order needs to be in the appropriate state prior to issuing this command.

CMN1022E

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.

CMN1023E

Explanation: This error is issued because the field is not defined properly.

Action: The field needs to be defined as Integer or BigDecimal.

CMN1023S

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.

CMN1024E

Explanation: An invalid orderId was passed into ProcessOrderCmd.

Action:

CMN1024S

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.

CMN1029E

Explanation: The specified category id could not be found. When this error occurs in the CategoryDisplay command, it may indicate that the command can not find an appropriate display template for this category in the DISPCGPREL table.

Action: Ensure that the category id that is specified refers to a valid category. When this error occurs in the CategoryDisplay command, also check the DISPCGPREL table to ensure that a valid display page has been defined.

CMN1030E

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 WebSphere 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

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.

CMN1032E

Explanation: The specified catalog entry id could not be found. When this error occurs in the ProductDisplay command, it may indicate that the command can not find an appropriate display template for this catalog entry (or catalog entry type) in the DISPENTREL table.

Action: Ensure that the catalog entry id that is specified refers to a valid catalog entry. When this error occurs in the ProductDisplay command, also check the DISPENTREL table to ensure that valid display pages have been defined for all catalog entry types.

CMN1033E

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

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.

CMN1037E

Explanation: WebSphere Commerce Server or a WebSphere Commerce command has detected an invalid parameter value.

Action: Ensure that the value of the specified input parameter is valid.

CMN1038E

Explanation: Web controller cannot find the acceptance cookie.

Action: No action required.

CMN1039E

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 logon ID. Also check if there are any logon violations. Close all browser windows and retry the action.

CMN1044E

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.

CMN1047E

Explanation: On OrderCopyCmd the value of the parameter 'shippingAddressFromOrderProfile' is set to '1', and if the toOrder is not null, the code will try to copy the default shipping address of the order profile to all the order items of the order specified in the 'toOrderId'. This error is thrown if any of these conditions exist: 1. There are no orderitems for the order profile 2. There is no shipping address in the order profile 3. An order profile doesn't exist and shippingAddressFromOrderProfile is set to '1'

Action: Don't use this parameter if these conditions could exist or check for these conditions and resolve them prior to calling OrderCopyCmd.

CMN1048E

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.

CMN1050E

Explanation: A problem occurred while updating an order item.

Action: Ask the administrator for assistance.

CMN1052E

Explanation: The orderId was not set or was not a valid orderId.

Action:

CMN1057E

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

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.

CMN1060E

Explanation: This exception wraps another exception thrown in the course of parsing a single sign-on token.

Action: Contact WebSphere Commerce support.

CMN1062E

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.

CMN1072E

Explanation: A user that does not have the proper authority has attempted to access a store that has been closed or locked.

Action: If the user requires access to a store in the closed or locked state, ensure that the proper authority is granted.

CMN1076E

Explanation: The specified logon ID could not be found in the user registry. If the WebSphere Commerce database user registry is used, then this error means that the logon ID could not be resolved against any of the records in the USERREG table. If an LDAP user registry is used, it means that a search of the LDAP tree using the short name specified failed to resolve a user.

Action: If the WebSphere Commerce database user registry is used, check the database to ensure that the specified logon ID is valid. If an LDAP user registry is used, check to ensure that the user exists on your LDAP server. If the user does exist, check the LDAP configuration to ensure that the searchbase and mapping attributes are defined correctly in the LDAPEntry.xml file and that the LDAP bind ID has authority to view the subtree.

CMN1082E

Explanation: There is currently a scheduler job with the exact information that already exists. This attempt will create a second instance of the same job which may lead into some concurrency problems.

Action: Check to see if there should be an instance of that job by using the job scheduleer in the Administration Conole or by manually inspecting the SCHCONFIG table.

CMN1083E

Explanation: The messaging system cannot find any order items associated with the specified order ID.

Action: Ensure that the order ID used is correct and that there is at least 1 item associated with the order.

CMN1086E

Explanation: The command expects a reference or part number parameter to uniquely identify the catalog entry. The command was not able retrieve an identifier for the catalog entry.

Action: Ensure that all the required parameters are specified, particularly those that identify a catalog entry (such as partnumber, catEntryId, or productId).

CMN1087E

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

Explanation: The WebSphere Commerce runtime did not set the user ID in the command context.

Action: Contact your IBM support representative.

CMN1090E

Explanation: A user cannot have two addresses with the same nickname.

Action: Change the nickname, and run the command again.

CMN1091E

Explanation: The customer attempted to update their user registration information without logging on to the system or site.

Action: Log on to WebSphere Commerce and try the update request again.

CMN1108E

Explanation: The quantity of for this bid is null and the bidQuantity parameter has not been set correctly.

Action: Ensure that you invoke the setBidQuantity() method in the CheckBidControlCmdImpl command to set the value of the bid quantity before calling it.

CMN1109E

Explanation: The order reference number was not available in the request properties.

Action: Ensure that the request properties included the order reference number.

CMN1110E

Explanation: The inbound xml message, named Update_WCS_ProductPrice, did not set the product price.

Action: Ensure the inbound xml message did set the product price, ItemUnitPrice of ListPriceInfo or OfferPriceInfo tag in the xml message.

CMN1111E

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

Explanation: A javax.ejb.CreateException error occurred while creating an ORDPAYMETHOD record for the order.

Action: Check the WAS EJB error log to find the source of the problem.

CMN1113E

Explanation: The system could not locate the SKU specified. The attribute and value combination may be invalid.

Action: Verify that your attribute and value combination is correct and try again.

CMN1117E

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

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.

CMN1120E

Explanation: An error occurred while attempting to process the order.

Action: Check the trace to see what failed.

CMN1122E

Explanation: The command requires a category reference number.

Action: Run the command again with the appropriate category reference number.

CMN1123E

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

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

Explanation: The command requires a catalog reference number.

Action: Run the command again with the appropriate catalog reference number.

CMN1129E

Explanation: The specified catalog could not be found in the database.

Action: Ensure that the paramters of the command have been set correctly, particularly the catalogID and catalogIdentifier.

CMN1130E

Explanation: The request properties object was null.

Action: Ensure that the request properties object is not null.

CMN1200E

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.

CMN1201E

Explanation: The year portion of the time value specifed is invalid as the value entered is not numeric.

Action: Enter a value for the year that is numeric, for example, 1961.

CMN1202E

Explanation: The month portion of the time value specified is invalid as the value entered does not faill between 1 and 12 months.

Action: Enter a value for the month portion of the time value that is between 1 and 12.

CMN1203E

Explanation: The day portion of the time value specified is invalid. The value must be a numeric number between 1 and the maximum days in the specified month.

Action: Enter a valid numeric day value for the month, for example, 15.

CMN1204E

Explanation: The hour portion of the time value specified is invalid as the value entered does not fall between 0 and 23 hours.

Action: Enter a value for the hour portion of the time value that is between 0 and 23.

CMN1205E

Explanation: The minute portion of the time value specified is invalid as the value entered does not fall between the values of 0 and 59 minutes.

Action: Enter a value for the second portion of the time value that is between 0 and 59.

CMN1206E

Explanation: The second portion of the time value specified is invalid as the value entered does not fall between 0 and 59 seconds.

Action: Enter a value for the second portion of the time value that is between 0 and 59.

CMN1207E

Explanation: The specified preferred start time contains an hour, minute, or second value that is not numeric. The elements of the preferred start time (for example, hours, minutes, seconds) must be numeric data.

Action: Enter a preferred start time that contains numeric elements.

CMN1214E

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.

CMN1216E

Explanation: The command or databean was not able to separate the generic list of catalog entries into its component list of specific catalog entry types. This error can occur, for example, if the CategoryDataBean can not process the list of catalog entries contained within the category to retrieve the specific list of ProductDataBeans, PackageDataBeans and ItemDataBeans. This error can occur if one or more of the catalog entries contained within the list does not have record in the CATENTDESC table.

Action: Ensure that all catalog entries in the CATENTRY table also have a record in the CATENTDESC table for each language that the store supports.

CMN1217E

Explanation: There are no attributes for the specified category in the given language.

Action: Add the attributes to the CATGRPATTR table.

CMN1218E

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

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

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.

CMN1222E

Explanation: The catalog entry must be associated to either the store where the current command is running, or it must be associated to a store that has a catalog store relationship to the current store. Store relationships are stored in the STOREREL table, and catalog entry to store relationships are stored in the STORECENT table.

Action: Ensure that the catalog entry exists in the CATENTRY table and that it is associated with the current store or a store that has a catalog relationship to the current store.

CMN1223E

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

Explanation: The command was passed two conflicting parameter values.

Action: Change the calling code to specify only one of the two parameter values.

CMN1225E

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

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

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.

CMN1228E

Explanation: An incorrect orderItem ID has been passed for processing.

Action: Ensure that the oderItem ID is correct for the order.

CMN1230E

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

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

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

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.

CMN1236E

Explanation: This error occurs when the system fails to convert from one conversion type to another.

Action: Evaluate your conversion configuration to ensure that it is set up properly.

CMN1238E

Explanation: This error is thrown when you call the OrderPrepare command to prepare an empty order.

Action: Add items to the shopping cart before you can call the OrderPrepare command.

CMN1239E

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.

CMN1242E

Explanation: An error occurred in the Calculation Framework. The error is in the specified CalculationUsage.

Action: Check the error code specified. This should be the cause of the problem. After you determine the source of the error, refer to the Calculation Framework documentation to correct your configuration.

CMN1244E

Explanation: The WebSphere Commerce Server has encountered an exception while forwarding execution to a JSP page.

Action: If the original exception is an ECException, examine its accompanying trace and react accordingly. Otherwise, add to the JSP page a catch block that dumps the stack trace.

CMN1245E

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

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.

CMN1247E

Explanation: This generic exception wraps another exception thrown in the process of relaying raw data provided by a command.

Action: React accordingly to the wrapped exception.

CMN1248E

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

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.

CMN1253E

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

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

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

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

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

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

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

Explanation: The orderId parameter passed to the OrderQuotationRequest specified an order that contained no items. No request was sent.

Action: No action required.

CMN1268E

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

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

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

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

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

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

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

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

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: Verify there is an entry in the database for store.rtnffmctr_id.

CMN1352E

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.

CMN1500E

Explanation: This message can occur if there is no inventory available for this product.

Action: Once inventory is available, this product will be orderable.

CMN1501E

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

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

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

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

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

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

Explanation: Either 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 interest item list that is available to the user.

CMN1514E

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

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.

CMN1517S

Explanation: Status message only.

Action: No action required.

CMN1519I

Explanation: Status message only.

Action: No action required.

CMN1520E

Explanation: The WebSphere Commerce Server has detected an invalid language ID provided for a request.

Action: Verify that the language ID is valid.

CMN1521E

Explanation: An invalid store ID has been detected.

Action: Ensure that the store ID is valid.

CMN1526E

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

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

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

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

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

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

Explanation: To run this command 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

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

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

Explanation: The command requires that the store identifies a default fulfillment center in the FFMCENTER_ID column of the STORE table.

Action: Verify the FFMCENTER_ID column of the STORE table specifies a default fulfillment center for the store.

CMN1537E

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

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.

CMN1539E

Explanation: This command does not support the value of "{0}" for parameter "{1}" combination.

Action: Verify the value of "{0}" and parameter "{1}" and try again.

CMN1540E

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

Explanation: The attribute for the specified language already exists.

Action: Use the AttributeUpdate command to modify the properties of the existing attribute.

CMN1602E

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

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

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

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

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.

CMN1607E

Explanation: The command was not able to create the catalog entry object with the specified parameters. There was an error that may have been caused by invalid parameters or by a system problem such as a database deadlock.

Action: Review the catalog entry parameters and ensure that each is valid for the context in which it is being used. If all parameters appear to be of the expected types, try executing the operation again.

CMN1608E

Explanation: The command was not able to update the catalog entry object with the specified parameters. There was an error that may have been caused by invalid parameters or by a system problem such as a database deadlock.

Action: Review the catalog entry update parameters and ensure that each is valid for the context in which it is being used. If all parameters appear to be of the expected types, try executing the operation again.

CMN1609E

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

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

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

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

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

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

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

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

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

Explanation: The specified catalog does not exist.

Action: Use the CatalogAdd command to create the specified catalog, then try the update again.

CMN1621E

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

CMN1649E

Explanation: The langauge id parameter is not correct. Either the langauge id is missing, or it does not represent a valid language supported by the store.

Action: Enusre that the language id parameter represents a valid langauge as defined in the LANGUAGE table.

CMN1653E

Explanation: The given types are not compatible with each other.

Action: Select an alternate type for the assignment.

CMN1654E

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

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

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

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

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

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

Explanation: The specified stored procedure failed.

Action: Refer to the online documentation for "Stored procedure error codes".

CMN1661E

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

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

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

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

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.

CMN1679E

Explanation: The system could not locate a component price or offer with which to price the component.

Action: There are multiple causes for this problem. Contact IBM support for assitance with problem determination.

CMN1700E

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

Explanation: This error is caused by the file system setup.

Action: Contact your Site Administrator to troubleshoot the possible file system setup errors.

CMN1702E

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. Use a ZIP utility to check whether or not the ZIP file is valid.

CMN1703E

Explanation: When one catalog file is being published for a store, you cannot publish another catalog file.

Action: Check if there is another catalog file in publishing status. If a catalog file is being published, wait until the process is complete before publishing the next catalog file.

CMN1704E

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

Explanation: This error can be caused by errors in the uploaded catalog file or 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

Explanation: When creating the file {0}, the following errors occured: {1}. This error is caused by the file system setup.

Action: Contact your Site Administrator to troubleshoot possible file system setup errors.

CMN1708E

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

Explanation: This error is caused by the store setup.

Action: Contact your Site Administrator to troubleshoot store setup errors.

CMN1710E

Explanation: This error is due to the error in the uploaded catalog file.

Action: Refer to the CSV catalog file documentation in the WebSphere Commerce information cetner to determine possible errors. After fixing the error, upload the catalog file and publish the catalog again.

CMN1711E

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

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

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, create one.

CMN1954E

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

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

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

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

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

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

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

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

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

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

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

Explanation: Product Advisor failed to obtain the table object when sorting the results for display.

Action: No user action required.

CMN1970E

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

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

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

Explanation: Product Advisor did not find any products matching certain constraints.

Action: No user action required.

CMN1992E

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

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

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

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.

CMN2006E

Explanation: The numeric data is incorrect.

Action: Correct the numeric data and try again.

CMN2007E

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

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

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

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

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.

CMN2020E

Explanation: This error occurs when the span of the calculation range for a calculation code contains a gap. Your calculation range moves from 1-2 and then covers 4-6 leaving the value three, outside the scope of the calculation range.

Action: Review your CALRANGE table and ensure that there are no gaps in the span.

CMN2022E

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.

CMN3102E

Explanation: The WebSphere Commerce scheduler could not recover the job as it could not create a failure record in the SCHACTIVE table.

Action: If this job has an interval of 0 (that is, a job that will only run once), create another WebSphere Commerce scheduler job for the same command to recover this missed run.

CMN3104E

Explanation: The WebSphere Commerce scheduler could not load the scheduled job with the specified instance reference number.

Action: Validate the instance by looking up the SCHACTIVE record and ensuring that the SCSINSTREFNUM value matches the specified reference number.

CMN3105E

Explanation: The WebSphere Commerce scheduler attempted to update the job state but could not complete the update because of a database problem. The job completed, but appears to be in running state because the record could not be updated.

Action: Manually clean up the SCHSTATUS record for the job by changing the state from "R" (running) to the value to which it should be updated in the database. For example, "C" for complete or "CF" for complete but failed.

CMN3204E

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.

CMN4501E

Explanation: Incorrect argument indicator "{0}".

Action: Edit the command line to correct or remove the incorrect argument.

CMN4501I

Explanation: The specified table is ready to be cleaned, and 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.

CMN4502E

Explanation: Missing argument "{0}".

Action: Edit the command line to include the missing argument.

CMN4502I

Explanation: The restrict delete rule applies to the following tables when the parent tables are to be deleted:

Action: No action required.

CMN4502S

Explanation: Connect to the database "{0}".

Action: No action is required.

CMN4503E

Explanation: The "{0}" argument is wrong.

Action: Correct the argument.

CMN4503I

Explanation: Type the source database password.

Action: Type the password for the source database of the staging server.

CMN4503S

Explanation: The connection to the "{0}" database is successful.

Action: No action is required.

CMN4504E

Explanation: Unknown argument "{0}".

Action: Correct or remove the specified argument.

CMN4504I

Explanation: Type the password for the destination database.

Action: Type the password for the destination database.

CMN4505E

Explanation: The mandatory arguments are missing.

Action: Edit the command line to provide the missing mandatory arguments.

CMN4505I

Explanation: The command input is "{0}".

Action: No action is required.

CMN4506E

Explanation: Cannot find the JDBC driver class "{0}".

Action: Check your java runtime classpath to see if the JDBC driver class specified is included.

CMN4506I

Explanation: The system requires a database password.

Action: Type your database password.

CMN4507E

Explanation: Cannot set the transaction isolation level for "{0}".

Action: Contact your database admininstrator to ensure the isolation level is allowed.

CMN4507I

Explanation: Status message only.

Action: No action required.

CMN4507S

Explanation: Disconnect from the database "{0}".

Action: No action is required.

CMN4508E

Explanation: Cannot turn off the transaction auto commit for "{0}".

Action: Contact your database administrator to ensure auto commit can be turned off before you try again.

CMN4508I

Explanation: Status message only.

Action: No action required.

CMN4508S

Explanation: You have successfully disconnected from the "{0}" database.

Action: No action is required.

CMN4509E

Explanation: The Database Cleanup utility requires a properly formatted name argument value to execute.

Action: Check if a name argument is provided or if the format provided is correct.

CMN4509I

Explanation: The table has different number of rows on the staging server and the production server.

Action: No action required.

CMN4510E

Explanation: The Database Cleanup utility requires a days argument to execute.

Action: Check if a days argument is provided or if the format is correct.

CMN4510I

Explanation: The tables contain the same data on the staging server and the production server.

Action: No action required.

CMN4510S

Explanation: Cannot connect to the database "{0}".

Action: Check if the db type, user name, password, and the schema (if applicable) is correct.

CMN4511E

Explanation: The source database password cannot be retrieved due to a system error.

Action: Type the database password and try again.

CMN4511I

Explanation: The table contains different data on the staging server and the production server.

Action: No action required.

CMN4512E

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.

CMN4512S

Explanation: Cannot commit the transaction on "{0}".

Action: Try again. If it continues to fail, then contact the administrator.

CMN4513E

Explanation: The database password provided is incorrect.

Action: Execute the Database Cleanup utility again, using the correct database password.

CMN4513I

Explanation: Status message only.

Action: No action required.

CMN4514E

Explanation: The SQL return code is "{0}".

Action: You might want to check the return code to determine if an error occurred.

CMN4514I

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.

CMN4514S

Explanation: Cannot rollback the transaction for "{0}".

Action: Determine why the failed transaction could not be rolled back. Restarting the database usually resolves the issue but should be used as the last resort.

CMN4515E

Explanation: The SQL is in "{0}" state.

Action: Check the cause if the state represents an error.

CMN4515I

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

Explanation: An error occured when the Database Cleanup utility was checking the delete restrict rules.

Action: No action required.

CMN4516E

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

Explanation: Status message only.

Action: No action required.

CMN4516S

Explanation: Status message only.

Action: Check the Database Cleanup utility log file for errors and ensure that there are no delete restrictions. Run the utility 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

Explanation: Status message only.

Action: No action required.

CMN4519E

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

Explanation: Status message only.

Action: No action required.

CMN4520E

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

Explanation: Status message only.

Action: No action required.

CMN4521E

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

Explanation: Status message only.

Action: No action required.

CMN4522E

Explanation: The SQL statement must start with either DELETE or UPDATE.

Action: Ensure that the specified SQL statement starts with DELETE or UPDATE.

CMN4523E

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.

CMN4523S

Explanation: The data in table {0} was not retrieved properly. Table {0} may be missing in the database. Or an incorrect user ID and password may have been provided. Or the database server may be down.

Action: Verify that the user ID and password specified to run the Database Cleanup utility are correct. Verify that the database server is running.

CMN4524E

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

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 utility again.

CMN4525S

Explanation: Status message only.

Action: No action required.

CMN4526E

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

Explanation: Status message only.

Action: Check the Database Cleanup utility log file for errors and run the utility again.

CMN4527E

Explanation: The JDBC customizer file was provided correctly, but the JDBC driver and JDBC URL prefix parameter values are not provided correctly in "{0}".

Action: Check the JDBC parameters provided in the customizer file.

CMN4527S

Explanation: Status message only.

Action: Check the Database Cleanup utility log file for errors and run the utility again.

CMN4528S

Explanation: The Database Cleanup utility could not execute the set null update SQL statement.

Action: Check the Database Cleanup utility log file to identifiy the problem and run the utility again.

CMN4529S

Explanation: Status message only.

Action: No action required.

CMN4530S

Explanation: Status message only.

Action: No action required.

CMN4531S

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

Explanation: Status message only.

Action: No action required.

CMN4533S

Explanation: Status message only.

Action: No action required.

CMN4534S

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

Explanation: Status message only.

Action: No action required.

CMN4536S

Explanation: Status message only.

Action: No action required.

CMN4537S

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.

CMN4543S

Explanation: Beginning to retrieve the active site table.

Action: No action is required.

CMN4545S

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.

CMN4546S

Explanation: Copy the table "{0}".

Action: No action is required.

CMN4547S

Explanation: Status message only.

Action: No action required.

CMN4548S

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

Explanation: Status message only.

Action: No action required.

CMN4551S

Explanation: The propagation utility updates the KEYS table.

Action: No action is required.

CMN4553S

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

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

Explanation: Status message only.

Action: No action required.

CMN4567S

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.

CMN4568S

Explanation: Beginning to retrieve the merchant tables.

Action: No action is required.

CMN4569S

Explanation: Beginning to retrieve the site tables.

Action: No action is required.

CMN4571S

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.

CMN4572S

Explanation: Retrieving the merchant and site tables.

Action: No action is required.

CMN4573S

Explanation: Status message only.

Action: No action required.

CMN4574S

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.

CMN4576S

Explanation: DBClean has failed to clean up the database.

Action: Correct the error and restart DBClean.

CMN4578S

Explanation: Status message only.

Action: No action required.

CMN4579S

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

Explanation: Status message only.

Action: No action required.

CMN4581S

Explanation: Status message only.

Action: No action required.

CMN4582S

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

Explanation: Status message only.

Action: No action required.

CMN4584S

Explanation: Status message only.

Action: No action required.

CMN4585S

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

Explanation: The Database Cleanup utility could not get the child table according to the referential constraints.

Action: Check the Database Cleanup utility log file for errors.

CMN4587S

Explanation: Status message only.

Action: No action required.

CMN4588S

Explanation: Status message only.

Action: No action required.

CMN4589S

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

Explanation: Status message only.

Action: No action required.

CMN4591S

Explanation: Status message only.

Action: No action required.

CMN4592S

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

Explanation: Status message only.

Action: No action required.

CMN4600S

Explanation: Status message only.

Action: No action required.

CMN4601S

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

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.

CMN4604S

Explanation: Propagating the rows.

Action: No action is required.

CMN4606S

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

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

Explanation: Status message only.

Action: No action required.

CMN4613S

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

Explanation: Status message only.

Action: No action required.

CMN4616S

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

Explanation: Status message only.

Action: No action required.

CMN4618S

Explanation: Status message only.

Action: No action required.

CMN4619S

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

Explanation: Status message only.

Action: No action required.

CMN4621S

Explanation: Status message only.

Action: No action required.

CMN4622S

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.

CMN4623S

Explanation: Check the merchant tables for all the merchants.

Action: No action is required.

CMN4624S

Explanation: All merchant tables contain the same data on both the staging server and the production server.

Action: No action required.

CMN4626S

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

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.

CMN4628S

Explanation: Get the primary key.

Action: No action is required.

CMN4630S

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

Explanation: Status message only.

Action: No action required.

CMN4633S

Explanation: Status message only.

Action: No action required.

CMN4669S

Explanation: Status message only.

Action: No action required.

CMN4670S

Explanation: Status message only.

Action: Check the Database Cleanup utility log file for any errors, and run the utility again.

CMN4671S

Explanation: Status message only.

Action: No action required.

CMN4672S

Explanation: Status message only.

Action: No action required.

CMN4673S

Explanation: Status message only.

Action: No action required.

CMN4674S

Explanation: Status message only.

Action: No action required.

CMN4675S

Explanation: Status message only.

Action: No action required.

CMN4676S

Explanation: Status message only.

Action: Check the Database Cleanup utility log file for any errors.

CMN4677S

Explanation: The Database Cleanup utility is trying to retrieve SQL statements for a given object.

Action: No action required.

CMN4679S

Explanation: The Database Cleanup utility could not retrieve 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

Explanation: Status message only.

Action: No action required.

CMN4681S

Explanation: Status message only.

Action: No action required.

CMN4682S

Explanation: Status message only.

Action: No action required.

CMN4683S

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

Explanation: Status message only.

Action: No action required.

CMN4685S

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

Explanation: Status message only.

Action: No action required.

CMN4687S

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

Explanation: Status message only.

Action: No action required.

CMN4689S

Explanation: Status message only.

Action: No action required.

CMN4690S

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

Explanation: Status message only.

Action: No action required.

CMN4692S

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

Explanation: Status message only.

Action: No action required.

CMN4694S

Explanation: Status message only.

Action: No action required.

CMN4700S

Explanation: Status message only.

Action: No action required.

CMN4702S

Explanation: Status message only.

Action: No action required.

CMN4703S

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

Explanation: Status message only.

Action: No action required.

CMN4705S

Explanation: Status message only.

Action: No action required.

CMN4706S

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

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

Explanation: The Stage Check utility is comparing the unique index data between the staging table and the production table.

Action: No action required.

CMN4709S

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

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

Explanation: The Stage Check utility is comparing the unique index data between the staging table and the production table.

Action: No action required.

CMN4712S

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

Explanation: Status message only.

Action: No action required.

CMN4714S

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

Explanation: Status message only.

Action: No action required.

CMN4716S

Explanation: Status message only.

Action: No action required.

CMN4717S

Explanation: Status message only.

Action: No action required.

CMN4718S

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

Explanation: Status message only.

Action: No action required.

CMN4720S

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

Explanation: Status message only.

Action: No action required.

CMN4722S

Explanation: Status message only.

Action: No action required.

CMN4723S

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

Explanation: Status message only.

Action: No action required.

CMN4726S

Explanation: The Database Cleanup utility could not retrieve the store path prefix located in the file whose name is passed by the parameter called -instance.

Action: Check the file name passed by the parameter -instance, and run the command again.

CMN4728S

Explanation: The Database Cleanup utility could not generate a deletion script.

Action: No action required.

CMN4729S

Explanation: The Database Cleanup utility could not get the required file names or directories from the database.

Action: Ensure that you have specified the appropriate file name or directory and run the utility again.

CMN4730S

Explanation: The file names or directories specified were retrieved from the database.

Action: No action required.

CMN4731S

Explanation: The script file {0} has been generated to delete file assets associated with the object being deleted in the database. You can keep the file assets by taking no action or delete the assets by running the generated script.

Action: No action required.

CMN4732S

Explanation: Status message only.

Action: No action required.

CMN4733S

Explanation: Status message only.

Action: No action is required.

CMN4734S

Explanation: The Database Cleanup utility will use the JDBC driver "{0}" to connect to the database.

Action: No action required.

CMN4735S

Explanation: Status message only.

Action: No action required.

CMN4737S

Explanation: The Database Cleanup utility could not load the JDBC drivers from the customizer file.

Action: Check the parameters in the cutomizer file.

CMN5105W

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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

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.

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) ##########.

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.

CMN5512E

Explanation: File I/O was not successful in the FTP session.

Action: Check if the directory and the file name are correct.

CMN5513E

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.

CMN5514D

Explanation: The WebSphere Commerce instance being created will use the iSeries Toolbox JDBC driver during store deployment.

Action: No action required.

CMN5515E

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.

CMN5516E

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.

CMN5517D

Explanation: The WebSphere Commerce instance being created will use the iSeries Toolbox JDBC driver to connect to the database.

Action: No action required.

CMN5517E

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.

CMN5518D

Explanation: The WebSphere Commerce instance being created will use the native iSeries JDBC driver to conntect to the database.

Action: No action required.

CMN5518E

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.

CMN5520E

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.

CMN5522E

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.

CMN5523E

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.

CMN5524E

Explanation: The entered WebSphere Commerce Payments profile path is invalid.

Action: Check to make sure the entered WebSphere Commerce Payments profile path is valid.

CMN5525E

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.

CMN5526E

Explanation: The Web server port is out of bounds.

Action: Check to make sure the port number is between 0 and 65535.

CMN5527E

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.

CMN5528E

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.

CMN5529E

Explanation: There was a problem exporting current configuration from the WAS.

Action: Check to make sure the WAS information is correct for the instance and that the WAS is running properly.

CMN5530E

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.

CMN5531E

Explanation: There was a problem connecting to the WAS.

Action: Check to make sure the WAS is started on the port specified in the WebSphere node of your WebSphere Commerce instance XML file.

CMN5532E

Explanation: The WAS is not started during the configuration of WebSphere Commerce.

Action: Check to make sure the WAS is started before attempting to configure WebSphere Commerce.

CMN5533E

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.

CMN5534E

Explanation: There was a problem importing the WebSphere Commerce Enterprise Java Beans. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5535E

Explanation: There was a problem importing the WebSphere Commerce application server. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS is running properly.

CMN5536E

Explanation: There was a problem importing the WebSphere Commerce Enterprise Application. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5537E

Explanation: There was a problem importing the WebSphere Commerce virtual hosts. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS is running properly.

CMN5538E

Explanation: There was a problem importing the WebSphere Commerce datasources. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS is running properly.

CMN5539E

Explanation: There was a problem importing the WebSphere Commerce Enterprise Java Beans. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5540E

Explanation: There was a problem importing the WebSphere Commerce Stores web module. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5541E

Explanation: There was a problem importing the WebSphere Commerce Tools web module. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5542E

Explanation: There was a problem importing the WebSphere Commerce Catalog Manager Web Editor Web module. The WAS information for the instance may not be accurate.

Action: Check to make sure the WAS information for the instance is correct and the WAS 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.

CMN5543E

Explanation: There was a problem starting the WebSphere Commerce application server. The WAS information or the database information for the instance may not be accurate.

Action: Check to make sure the WAS information and the database information for the instance is correct and the WAS and the database server are running properly.

CMN5544E

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.

CMN5546E

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.

CMN5547E

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.

CMN5548E

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.

CMN5549E

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.

CMN5550E

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

Explanation: A user profile with the instance name should now exist on the iSeries system.

Action: No action required.

CMN5551E

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.

Listen 443 should not be commented out. Refer to the httpd.conf.sample file for the right location of "Listen 443" statement location.

CMN5551I

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.

CMN5555E

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

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

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

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

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

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

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

Explanation: The database name, VAJ_demo, is reserved for WebSphere Commerce.

Action: Choose another database name.

CMN5565E

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

Explanation: Configuration Manager detected that DB2 is not installed on the database machine.

Action: Install DB2 and make sure it is functioning correctly.

CMN5567E

Explanation: Configuration Manager detected that Oracle is not installed in the database machine.

Action: Install Oracle database and make sure it functions correctly.

CMN5571E

Explanation: The CGI block in the configuration file has already been configured.

Action: No action required.

CMN5572E

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

Explanation: The file could not be created in the specified directory.

Action: Check the access permissions of the directory.

CMN5574E

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

Explanation: The file was found but could not be opened by Configuration Manager.

Action: Check the permissions of the file.

CMN5576E

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

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

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

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

Explanation: The language selected is not supported by WebSphere Commerce.

Action: Refer to the WebSphere Commerce documentation for a list of supported languages.

CMN5581E

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

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

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.

CMN5960E

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

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

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

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.

CMN5965E

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

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

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

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

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

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

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

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

Explanation: Starting the Payments instance is a two step process. First the WAS 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

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 WAS and Payment Servlet started correctly. See the WebSphere logs in the Application Server logs directory for this instance. 3. The WAS 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

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

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

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

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

Explanation: This cassette could not be added to the Payments instance because the WebSphere enterprise application could not be redeployed in the WAS.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on why the redeploy failed.

CMN5980E

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

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.

CMN5983E

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

Explanation: The Payments instance could not be configured in WAS because configuration objects for WebSphere could not be initialized.

Action: Verify the WAS product is installed and functioning properly.

CMN5985E

Explanation: An exception occured for unknown reasons while trying to configure the WAS.

Action: See the WCSconfig_<timestamp>.log file in the Commerce instance logs directory for details on the failure.

CMN5987E

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

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 WAS product to complete the deletion of the Payments instance.

CMN5996E

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.

CMN5997E

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.

CMN5998E

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.

CMN5999E

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

Explanation: The password change for the Payments instance was successful, but the WAS 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.

CMN6224E

Explanation: The specified class cannot be found.

Action: Ensure that the directory or JAR file that contains the class is in the class path of the WebSphere Commerce Server. The recommended procedure for adding JAR files is to place them in the Stores.war/WEB-INF/lib directory of the application (found, in turn, in the installedApps subdirectory of the WAS installation directory). The recommended procedure for adding classes is to place them in the Stores.war/WEB-INF/classes directory.

CMN7000E

Explanation: The record cannot be created because its values cause a duplicate key constraint error in the database table.

Action: Check the parameters of the record and ensure that its values will produce a unique record. Check the database constraint definition of the assocaited table and ensure that all unique indecies are not violated by the data from the new record.

CMN7001E

Explanation: The business logic requires that {0} be unique in the {1} table.

Action: Check the table and remove the duplicated rows.

CMN7003E

Explanation: A record with {0} = {1} does not exist in the {2} table.

Action:

CMN7004E

Explanation: The object specified in the XML document could not be located in the database.

Action: Enusre that the structure and contents of the XML document are correct.

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

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

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

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

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

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

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

Explanation: Status message only.

Action: No action required.

CMN7515E

Explanation: Status message only.

Action: No action required.

CMN7516E

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 "<WAS Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

CMN7745E

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

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 "<WAS Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

CMN7750E

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 "<WAS Dir>/logs" directory and would include: - log.txt - wctrace.log - wcinstall.log - trace files beginning with "depcheck" - install_<date stamp>.log

CMN7751S

Explanation: This message is a status message used within the IBM WebSphere Commerce installation to indicate that the installation of WAS Web server plug-ins was successful.

Action: No action is required.

CMN7752S

Explanation: Status message only

Action: No action required

CMN7753S

Explanation: Status message only

Action: No action required

CMN7754S

Explanation: Status message only

Action: No action required

CMN8000E

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

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

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

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

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

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

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 WAS and WebSphere Commerce is part of the user group of (or has access to) the JMS provider on the remote machine.

CMN8007E

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

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: Verify 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

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

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.

CMN8011E

Explanation: The trading agreement XML could not be parsed.

Action: Ensure the trading agreement XML follows the format as specified in the XSD or DTD files.

CMN8013E

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.

CMN8016E

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

Explanation: User with ID as shown was not created.

Action: Refer to other related exception information on the same thread for details.

CMN8018E

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 WAS 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

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

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

Explanation: An exception occurred when starting up either the serial or parallel transport adapter. Most likely, there was problem configuring the JNDI (Java Naming and Directory Interface) namespace for the JMS (Java Message Service) queue connection factory and/or queue name(s).

Action: Correct the situation according to the error information that has been provided. Verify that the JMS (Java Message Service) configuration has been correctly set up under the WAS JNDI (Java Naming and Directory Interface) namespace. Ensure that the queue and queue manager information are set according to the JMS provider (for example, WebSphere MQ Server). Use the IVTRun script to verify this configuration if you are using WebSphere MQ.

CMN8022E

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

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

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

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.

CMN8028E

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

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

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

Explanation: The command failed to execute.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

CMN8102S

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Explanation: An internal error has occured.

Action: Contact your IBM support representative.

CMN8153E

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

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

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

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

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

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

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

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>.xml file.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

CMN8162E

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

Explanation: The XPathType is unknown to the messaging system parser.

Action: Correct the XPathType and restart WebSphere Commerce.

CMN8164E

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>.xml file.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

CMN8165E

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>.xml file.

Action: Fix the file according to the failing message indicated in the ecmsg log file, and restart the WebSphere Commerce instance.

CMN8166E

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Explanation: Status message only.

Action: Check the WebSphere Commerce log and the trace file for additional information regarding this method.

CMN8301E

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 <WAS directory>/installedApps/WC_Enterprise_App_<instance name>.ear/lib.

CMN8302E

Explanation: Status message only.

Action: No action required.

CMN8303E

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

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: Verify the class speicified is loaded for WebSphere Commerce within the WAS.

CMN8308E

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: Verify the class speicified is properly loaded for WebSphere Commerce within the WAS.

CMN8309E

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).

CMN8311E

Explanation: WebSphere Commerce has no access rights to instantiate the Messaging class object (referenced in a deprecated class).

Action: Check the access rights of the user id running WebSphere Commerce and make sure it has access rights to the Messaging.class file.

CMN8313E

Explanation: The message was not sent out.

Action: Check the WebSphere Commerce log and the trace file for additional information.

CMN8314E

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

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

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: Verify the BodyPart or MultiPart class is not an interface or an abstract class.

CMN8317E

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

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: Verify the class speicified is properly loaded for WebSphere Commerce within the WAS.

CMN8319E

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

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

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

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: Verify 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

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 log for additional information and fix the problem accordingly. For further information, contact your IBM support representative.

CMN8326E

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

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: Verify the property with name "Message" is defined in the TransportConfig section in the <instance>.xml file.

CMN8328E

Explanation: Failed to create an InputStream of bytes.

Action: No action required.

CMN8330E

Explanation: Status message only.

Action: Use the Administration Console to properly configure the message type for the specific transport.

CMN8331E

Explanation: Status message only.

Action: Use the Administration Console to properly configure the message type for the specific transport.

CMN8332E

Explanation: Status message only.

Action: Use the Administration Console to properly configure the message type for the specific transport.

CMN8333E

Explanation: Status message only.

Action: Use the Administration Console to properly configure the message type for the specific transport.

CMN8340E

Explanation: A generic exception to indicate that there was an attempt to create a record using an Enterprise Java Bean and it failed. This usually happens if a record with the same unique index already exists or the record has relationships to other tables that are not valid for the particular values specified.

Action: Ensure the values specified for the create operation does not violate any database constraints.

CMN8341E

Explanation: This is a generic message when looking for a particular record and it could not be found in the database. In most cases when this exception is thrown it is because the primary key of the record has been specified and the operation assumes that the primary key must exists.

Action: Ensure the primary key used for the lookup exists.

CMN8342E

Explanation: The exception is throw when the runtime detects a ejb Naming exception error when accessing an EJB.

Action: Analyse {0} to determine the original error.

CMN8343E

Explanation: A generic exception for reporting remote exceptions when communication problems occur when talking with remote objects such as Enterprise Java Beans.

Action: If this problem continuously occurs, contact WebSphere Commerce support.

CMN8344E

Explanation: A generic exception for reporting remote exceptions when communication problems occur when talking with remote objects such as Enterprise Java Beans.

Action: If this problem continuously occurs, contact WebSphere Commerce support.

CMN8345E

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.

CMN8402E

Explanation: Status message only.

Action: No action required.

CMN8403E

Explanation: The <instance>.xml file does not contain the specified node.

Action: Open the <instance>.xml file and verify its content.

CMN8404E

Explanation: Class com.ibm.commerce.user.objects.AddressAccessBean cannot be loaded. It could not be loaded by the WAS class loader.

Action: Please check whether the class path for WebSphere Commerce is properly configured under WAS. If the problem persists, contact your IBM support representative.

CMN8405E

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

Explanation: During the initialization of a Connector, an XML attribute was mssing in the <instance>.xml file.

Action: Based on the attribute name in the ecmsg log, re-insert the XML attribute into <instance>.xml and restart the WebSphere Commerce instance.

CMN8407E

Explanation: The ClassName attribute in <instance>.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.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

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

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

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

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

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 the calling command to ensure that it specifies the correct MSGTYPE_ID.

CMN8413E

Explanation: The specified profile does not have an appropriate record in the PROFILE table. WebSphere Commerce cannot locate a MSGTYPE_ID and an active transport combination for the store.

Action: Check to ensure that the correct MSGTYPE_ID and STORE_ID are specified in the calling command. In addition, ensure that the message type has been assigned to the appropriate active transport of the store or site (STORE_ID = 0).

CMN8414E

Explanation: The messaging system cannot retrieve the required configuration for this message type from the PROFILE table.

Action: Ensure that the required message type has been assigned to the required transport (for example, email) under the site or store configuration, using WebSphere Commerce Adminstration Console.

CMN8415E

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

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

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

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: Verify there is at least one e-mail address associated with each member during the registration process. Verify this in the ADDRESS database table.

CMN8420E

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

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.

CMN8422E

Explanation: The messaging system cannot find the member ID in the MEMBER table.

Action: Ensure that the member ID is defined in the MEMBER table.

CMN8424E

Explanation: Status message only.

Action: No action required.

CMN8425E

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

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

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

Explanation: The messaging system cannot instantiate an instance object of either connection or interaction specification class.

Action: Verify 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

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 <WAS directory>/installedConnectors.

CMN8430E

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

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

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

Explanation: Status message only.

Action: No action required.

CMN8434E

Explanation: The <instance>.xml file does not contain the specified node.

Action: Open the <instance>.xml file and verify its content.

CMN8435E

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

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

Explanation: The class specified is not found.

Action: Check and verify the specified class is in the classpath setting.

CMN8438E

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>.xml file.

CMN8439E

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

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: Verify there is at least one e-mail address associated to a member during the registration process. Verify this in the ADDRESS table.

CMN8441E

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: Verify the command has set at least 1 MEMBER_ID when calling the messaging system.

CMN8442E

Explanation: The system could not retrieve the default language for the current store. The LANGUAGE_ID for the current store is null.

Action: Check the LANGUAGE_ID column of the STORE table for the current store and ensure that it is not null.

CMN8443E

Explanation: There was a problem accessing the STORE table through the StoreAccessBean. This happens under 2 conditions: 1) When trying to change the state of a store that is marked for delete. 2) When sending email or text messages, WepSphere Commerce cannot instantiate the StoreAccessBean for the specified storeId. The storeId may be incorrect or invalid.

Action: Check the STOREENT.MARKFORDELETE value of the storeId. If the value is 1, change it to 0. If you are sending email or text messages, make sure you are sending email messages through a valid store.

CMN8444E

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

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

Explanation: Obsolete. Reason same as _ERR_MSG_CFG_NOT_INIT

Action: Obsolete. Action same as _ERR_MSG_CFG_NOT_INIT

CMN9003E

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.

CMN9017E

Explanation: The transition cannot occur because the order is in an incorrect state.

Action: Ensure that the state of the current order is valid to make the requested transition.

CMN9018E

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

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

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

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.

CMN9041E

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.

CMN9042E

Explanation: The amount of the order is not valid.

Action: Verify that the order amount is valid and try again.

CMN9142E

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

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

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

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

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

Explanation: The purchase order number specified is no longer active.

Action: Resubmit the order for processing using an active purchase order.

CMN9148E

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

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

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

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

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

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

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 WAS. This is especially important if the payment component is installed on a different machine than the WebSphere Commerce Server.

CMN9528E

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

CMN9653E

Explanation: The access bean associated with the personalization attribute could not be retrieved.

Action: Correct the ACCESSBEAN column in the PATTRIBUTE table for the personalization attribute.

CMN9654E

Explanation: A relationship is missing between the personalization attribute and the catalog entry in the PATTRPROD table.

Action: Register a relationship between the personalization attribute and the catalog entry in the PATTRPROD table.

CMN9655E

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

Explanation: You do 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

Explanation: All checks for the business logic guards failed for the event.

Action: Ensure that the command implementing the business logic guards is working correctly.

CMN9802E

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 ? with the actual values.

CMN9803E

Explanation: The action command for the transaction must 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

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

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

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.

CMN9900E

Explanation: Obsolete

Action: Obsolete

CMN9901E

Explanation: Obsolete

Action: Obsolete

CMN9902E

Explanation: Obsolete

Action: Obsolate

CMN9903E

Explanation: Obsolete

Action: Obsolete

CMN9904E

Explanation: Obsolete

Action: Obsolete

CMN9905E

Explanation: Obsolete

Action: Obsolete

CMN9906E

Explanation: Obsolete

Action: Obsolete

CMN9907E

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

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>.xml is the same as the "JNDI binding path" that is used to deploy a resource adapter in WAS.

CMN9910E

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.

CWXAC0001D

Explanation: Status message only.

Action: No action required.

CWXAC0001E

Explanation: The system failed to get the configuration information for database {0}.

Action: Verify your configuration settings and try the command again.

CWXAC0001I

Explanation: Getting the configuration information for database {0}.

Action: No action required.

CWXAC0001S

Explanation: Status message only.

Action: No action required.

CWXAC0002E

Explanation: The code set for database {0} is not UTF-8 compliant.

Action: Ensure that the code set you specify is UTF-8 compliant.

CWXAC0002I

Explanation: The codeset for database {0} is set to {1}.

Action: No action required.

CWXAC0003E

Explanation: The user ID under which Configuration Manager is running does not have write permission for the specified file.

Action: Allow write permission for the file for the user ID under which Configuration Manager is running.

CWXAC5517S

Explanation: Status message only.

Action: No action required.

CWXAC5518S

Explanation: Status message only.

Action: No action required.

CWXAC5519S

Explanation: Status message only.

Action: No action required.

CWXAC5520S

Explanation: Status message only.

Action: No action required.

CWXAC5521S

Explanation: Status message only.

Action: No action required.

CWXAC5522S

Explanation: Status message only.

Action: No action required.

CWXAC5523S

Explanation: Status message only.

Action: No action required.

CWXAC5524S

Explanation: Status message only.

Action: No action required.

CWXAC5525S

Explanation: Status message only.

Action: No action required.

CWXAC5526D

Explanation: Status message only.

Action: No action required.

CWXAC5526S

Explanation: Status message only.

Action: No action required.

CWXAC5527D

Explanation: Status message only.

Action: No action required.

CWXAC5527S

Explanation: Status message only.

Action: No action required.

CWXAC5528D

Explanation: Status message only.

Action: No action required.

CWXAC5528S

Explanation: Status message only.

Action: No action required.

CWXAC5529D

Explanation: Status message only.

Action: No action required.

CWXAC5529S

Explanation: Status message only.

Action: No action required.

CWXAC5530S

Explanation: Status message only.

Action: No action required.

CWXAC5531D

Explanation: Status message only.

Action: No action required.

CWXAC5531S

Explanation: Status message only.

Action: No action required.

CWXAC5532D

Explanation: Status message only.

Action: No action required.

CWXAC5532S

Explanation: Status message only.

Action: No action required.

CWXAC5533D

Explanation: Debug message only.

Action: No action required.

CWXAC5533S

Explanation: Status message only.

Action: No action required.

CWXAC5534D

Explanation: Debug message only.

Action: No action required.

CWXAC5534S

Explanation: Status message only.

Action: No action required.

CWXAC5535S

Explanation: Status message only.

Action: No action required.

CWXAC5536S

Explanation: Status message only.

Action: No action required.

CWXAC5537S

Explanation: Status message only.

Action: No action required.

CWXAC5538S

Explanation: Status message only.

Action: No action required.

CWXAC5539S

Explanation: Status message only.

Action: No action required.

CWXAC5540S

Explanation: Status message only.

Action: No action required.

CWXAC5541S

Explanation: Status message only.

Action: No action required.

CWXAC5542S

Explanation: Status message only.

Action: No action required.

CWXAC5543S

Explanation: Status message only.

Action: No action required.

CWXAC5544S

Explanation: Status message only.

Action: No action required.

CWXAC5545S

Explanation: Status message only.

Action: No action required.

CWXAC5546S

Explanation: Status message only.

Action: No action required.

CWXAC5547S

Explanation: Status message only.

Action: No action required.

CWXAC5548S

Explanation: Status message only.

Action: No action required.

CWXAC5549S

Explanation: Status message only.

Action: No action required.

CWXAC5550S

Explanation: Status message only.

Action: No action required.

CWXAC5551S

Explanation: Status message only.

Action: No action required.

CWXAC5553I

Explanation: Status message only.

Action: No action required.

CWXAC5554I

Explanation: Status message only.

Action: No action required.

CWXAC5582E

Explanation: The specified WebSphere Commerce Web alias is not defined in the template instance configuration XML file. The file might have been corrupted.

Action: Reinstall WebSphere Commerce.

CWXAC5584E

Explanation: The mappedConfigPath Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedConfigPath property and re-run the configuration.

CWXAC5585E

Explanation: The mappedServerPath Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedServerPath property and re-run the configuration.

CWXAC5586E

Explanation: The webserverHostname Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the webserverHostname property and re-run the configuration.

CWXAC5587E

Explanation: The iisServerNumber Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the iisServerNumber property and re-run the configuration.

CWXAC5588E

Explanation: The documentRoot property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the documentRoot property and re-run the configuration.

CWXAC5589E

Explanation: The specified document root path is either does not exist or invalid.

Action: Make sure the document root path is correct and exists and re-run your cofiguration.

CWXAC5590E

Explanation: The webserverPort Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the webserverPort property and re-run the configuration.

CWXAC5591E

Explanation: The value of the webserverPort property must be between 1024 and 65535.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the webserverPort property and re-run the configuration.

CWXAC5592E

Explanation: The toolsPort property is required to configure the Web server

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the toolsPort property and re-run the configuration.

CWXAC5593E

Explanation: The value of the toolsPort property must be between 0 and 65535 and cannot be the same as the webserverPort property .

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the toolsPort property and re-run the configuration.

CWXAC5594E

Explanation: The sunoneSecurePortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneSecurePortConf property and re-run the configuration.

CWXAC5595E

Explanation: The sunoneNonSecurePortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneNonSecurePortConf property and re-run the configuration.

CWXAC5596E

Explanation: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneToolsPortConf property and re-run the configuration.

Action: The sunoneToolsPortConf Ant property is required to configure the Web server.

CWXAC5597E

Explanation: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneAdminPortConf property and re-run the configuration.

Action: The sunoneAdminPortConf Ant property is required to configure the Web server.

CWXAC5598E

Explanation: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneOrgAdminPortConf property and re-run the configuration.

Action: The sunoneOrgAdminPortConf Ant property is required to configure the Web server.

CWXAC5599E

Explanation: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneSecurePortConf property and re-run the configuration.

Action: The sunoneSecurePortConf Ant property is required to configure the Web server.

CWXAC5600E

Explanation: The file specified by the sunoneOrgAdminPortConf property must have read and write permissions.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneOrgAdminPortConf property

CWXAC5601E

Explanation: The sunoneNonSecurePortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneNonSecurePortConf property and re-run the configuration.

CWXAC5602E

Explanation: The file specified by the sunoneNonSecurePortConf property must have read and write permissions

Action: Change the file permissions to allow read and write access on the file specified by the sunoneNonSecurePortConf property

CWXAC5603E

Explanation: The sunoneToolsPortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the sunoneToolsPortConf property and re-run the configuration.

CWXAC5604E

Explanation: The file specified by the sunoneToolsPortConf property must have read and write permissions.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneToolsPortConf property.

CWXAC5605E

Explanation: The sunoneAdminPortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the sunoneAdminPortConf property and re-run the configuration.

CWXAC5606E

Explanation: The file specified by the sunoneAdminPortConf property must have read and write permissions.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneAdminPortConf property.

CWXAC5607E

Explanation: The sunoneOrgAdminPortConf Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the sunoneOrgAdminPortConf property and re-run the configuration.

CWXAC5608E

Explanation: The file specified by the sunoneOrgAdminPortConf property must have read and write permissions.

Action: Change the file permissions to allow read and write access on the file specified by the sunoneOrgAdminPortConf property.

CWXAC5609E

Explanation: The authenticationMode Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the authenticationMode property and re-run the configuration.

CWXAC5610E

Explanation: To configure a remote Web server, you can choose only one remote configuration option, either configuration using FTP or using NFS.

Action: In the< WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value of the isConfigViaFTP property and the isConfigViaNFS property and re-run your configuration.

CWXAC5611E

Explanation: The remoteInstallPath Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the remoteInstallPath property and re-run the configuration.

CWXAC5612E

Explanation: The ftpServerName Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerName property and re-run the configuration.

CWXAC5613E

Explanation: The ftpServerName Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerName property and re-run the configuration.

CWXAC5614E

Explanation: The ftpServerPort Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpServerPort property and re-run the configuration.

CWXAC5615E

Explanation: The ftpServerPort Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, correct the value for the ftpServerPort property and re-run the configuration.

CWXAC5616E

Explanation: The ftpUserId Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpUserId property and re-run the configuration.

CWXAC5617E

Explanation: The ftpUserPwd Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the ftpUserPwd property and re-run the configuration.

CWXAC5618E

Explanation: The mappedConfigPath Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedConfigPath property and re-run the configuration.

CWXAC5619E

Explanation: The mappedServerPath Ant property is required to configure the Web server.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, enter the value for the mappedServerPath property and re-run the configuration.

CWXAC5620E

Explanation: The specified object was not found in the WAS configuration.

Action: Re-run the previous configuration to make sure the object is created and re-run the current configuration.

CWXAC5621E

Explanation: While trying to create the datasource object, a datasource with the same name was detected.

Action: The datasource name assigned by Configuration Manager is WebSphere Commerce DB2 DataSource <instanceName> or WebSphere Commerce Oracle DataSource <instanceName>. If the datasource name assigned Configuration Manager is already in use, change the datasource name and re-create the instance using the instance creation wizard. You can also change the value of the datasourceName property in the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file and re-run the configuration.

CWXAC5623E

Explanation: The database type is invalid. The supported database type is DB2 and Oracle.

Action: Correct the database type.

CWXAC5624E

Explanation: While trying to create the JAAS Authentication Data Alias object, a JAAS Authentication Data Alias object with the same name already exists.

Action: The JAAS Authentication Data Alias name assigned by Configuration Manager is WC_<instanceName> - authDataAlias. If an existing JAAS Authentication Data Alias already used the name assigned by Configuration Manager, remove the instance, change the instance name and re-create the instance using the instance creation wizard. You can also change the value of the instanceName property in the WC_installdir/instances/<instanceName>/properties/createInstance.properties file and re-run the configuration.

CWXAC5625E

Explanation: Configuration Manager tried to create the specified JAAS Authentication Data for the specified application server and it failed.

Action: Try to re-run the configuration. If problem persists, contact your WebSphere Commerce support representative.

CWXAC5626E

Explanation: Configuration Manager tried to create a JDBC provider for the specified application server but it failed because the application server could not be found

Action: Ensure the application server exists or create the application server and re-run the configuration.

CWXAC5627E

Explanation: While trying to create the JDBC provider object, a JDBC provider object with the same name already exists.

Action: Assign a unique JDBC provider name or delete the existing one and re-run the configuration.

CWXAC5628E

Explanation: Configuration Manager falied to create a JDBC provider.

Action: Try to re-run the configuration or manually create the JDBC provider using the WAS. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5629E

Explanation: Configuration Manager falied to remove the specified datasource.

Action: Try to re-run the configuration or manually remove the datasource using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5630E

Explanation: Configuration Manager falied to remove the specified JAAS authentication data.

Action: Try to re-run the configuration or manually remove the JAAS authentication data using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5631E

Explanation: Configuration Manager falied to remove the specified JDBC provider.

Action: Try to re-run the configuration or manually remove the JDBC provider using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5632E

Explanation: Configuration Manager falied to remove the specified application server.

Action: Try to re-run the configuration or manually remove the application server using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5633E

Explanation: Configuration Manager tried to install the specified EAR file but it failed.

Action: If the EAR file is partially installed, clean up and re-run the configuration. Also, try to install the EAR file using the WebSphere Aoolication Server Administrative Console. The EAR file to be installed is located in <WC_installdir>/instances/<instanceName>/<instanceName>.ear. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5634E

Explanation: Configuration Manager falied to create the specified virtual host.

Action: Try to re-run the configuration or manually create the specified virtual host using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5635E

Explanation: Configuration Manager could not find the WAS node on which to configure WebSphere Commerce.

Action: Ensure that the WAS configuration is not corrupted. Also, ensure the <WAS_installdir>/<profileName>/bin/setupCmdLine utility has the correct value for the WAS_NODE variable and re-run the configuration.

CWXAC5636E

Explanation: Configuration manager attempted to create an application server that already exists. Configuration Manager will skip to the next configuration step and will use this existing application server.

Action: No action required.

CWXAC5637E

Explanation: Configuration Manager falied to create an application server on the specified node.

Action: Try to re-run the configuration or manually create the application server using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5638E

Explanation: Configuration Manager could not find the specified WAS object when configuring WebSphere Commerce.

Action: Ensure the the WAS configuration is not corrupted. Also, ensure the object exists and re-run the configuration.

CWXAC5639E

Explanation: Configuration Manager could not find the specified application server during configuration.

Action: Ensure that the specified application server exists or create the application server and re-run the configuration.

CWXAC5640E

Explanation: Configuration Manager falied to remove the application server on the specified node.

Action: Try to re-run the configuration or manually remove the application server on the specified noder using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5641E

Explanation: The host alias that Configuration Manager was trying to create in the specifed vritual host already exists. Configuration Manager will skip creating the host alias.

Action: No action required.

CWXAC5642E

Explanation: Configuration Manager falied to create the host alias for the virtual host.

Action: Try to re-run the configuration or manually create the host alias for the virtual host using the WebSphere Application Server Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5643E

Explanation: Configuration Manager attempted to create a virtual host that already exists. Configuration Manager will skip creating a virtual host.T

Action: No action required.

CWXAC5644E

Explanation: Configuration Manager falied to remove the host alias from the virtual host.

Action: Try to re-run the configuration or manually remove the host alias using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5645E

Explanation: Configuration Manager falied to remove the WAS object.

Action: Try to re-run the configuration or manually remove the object using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5646E

Explanation: More than one application server with the same name is found when Configuration Manager tried to configure the application server.

Action: Remove the duplicate application servers using the WAS Administrative Console and re-run the configuration.

CWXAC5647E

Explanation: The object could not be modified or created by Configuration Manager.

Action: Try to re-run the configuration or manually modify or create the object using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5648E

Explanation: The Ant property is missing from the createInstance.properties file.

Action: Add the <propertyName>=<propertyValue> at the end of the createInstance.properties file and re-run the configuration. The file is located in the WC_installdir/instances/<instanceName>/properties/createInstance.properties.

CWXAC5649E

Explanation: During instance configuration, Configuration Manager copies some template configuration files into instance specific directories. The file copy failed.

Action: Ensure the following directories exist and re-run the configuration: <WC_installdir>/instances/default/xml <WC_installdir>/instances/default/trading Also, ensure that the user running Configuration Manager has write access to the <WC_installdir>/instances/<instanceName> directory.

CWXAC5650E

Explanation: Configuration Manager unregisters the WebSphere Commerce instance by removing the instance specific line in the <WC_installdir>/instances/wcs_instances file.

Action: Examine the <WC_installdir>/instance/<instanceName>/logs/createInstanceANT.log file and correct the problem describe the error messages in the log file. Then, re-run the configuration or remove the instance specific line in the <WC_installdir>/instances/wcs_instances file manually.

CWXAC5651E

Explanation: The Commerce instance directory located in the <WC_installdir>/instances directory could not be deleted during the instance removal.

Action: Ensure that no application is using any file in the instance's directory. Back up any necessary files and delete the <WC_installdir>/instances/<instanceName> directory manually.

CWXAC5652E

Explanation: The specified file was not found.

Action: Ensure the file exists and the permissions are set correctly. If you cannot recover from this, re-install the product.

CWXAC5653E

Explanation: The specified Ant property is missing in the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file.

Action: In the <WC_installdir>/instances/<instanceName>/properties/createInstance.properties file, add a line anywhere that reads <property_name>=<property_value>.

CWXAC5654E

Explanation: Configuration Manager falied to remove the specified WAS object.

Action: Try to re-run the configuration or manually remove the object using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAC5655E

Explanation: Configuration Manager failed to create the shared library because it already exists. No library reference is assigned to the WebSphere Commerce enterprise application.

Action: Try to remove the existing shared library using the WAS Administrative Console. If the problem persists, contact your WebSphere Commerce support representative.

CWXAI7755E

Explanation: The instance creation has attempted to create a user profile on iSeries for WebSphere Commerce Payments and this action failed.

Action: The user should contact their iSeries System Administrator to see creation of the user profile failed. Logs will be located in the /tmp/installshield/wctrace.log

CWXBB1000E

Explanation: A required parameter, such as activity token or activity ID, is not specified.

Action: Ensure the parameter is specified so that it is properly passed to the method.

CWXBB1001E

Explanation: The business context configuration file has failed to load.

Action: Ensure the business context configuration XML file is well-formed and is in the class path of the WebSphere Commerce Server.

CWXBB1002E

Explanation: The referenced business context factory class, defined in the business context configuration file, cannot be loaded.

Action: Ensure that the name of the factory class is specified correctly in the busines context configuration file and is in the class path of the WebSphere Commerce Server.

CWXBB1010E

Explanation: The referenced activity token has failed validation test. The activity token may have become corrupted.

Action: User must log in to WebSphere Commerce Server again in order to obtain a new activity token.

CWXBB1011E

Explanation: The referenced activity token has expired.

Action: User must log in again in order to retrieve a new activity token.

CWXBB1012E

Explanation: The referenced activity token has been terminated due to user inactivity or logoff. The user has logged off or remained inactive.

Action: User must log on again in order to retrieve a new activity token.

CWXBB1100E

Explanation: Referenced business context could not be found for referenced activity due to one of the following reasons: the activity could not be initialized properly, the activity cache has been flushed (generic-user activity only), or the business context server could not communicate with the database (guest-user or registered-user activity only).

Action: If this is a generic-user activity, ensure that the activity exists in the activity cache. If this is a guest-user or registered-user activity, ensure that its business context exists in the CTXDATA database table.

CWXBB1101E

Explanation: One or more attributes of the business context are invalid.

Action: Ensure the attributes of the business context are specified correctly.

CWXBE0400E

Explanation: There has been an attempt to update a managed resource that is currently locked by another process. This lock could have been obtained by a user, workspace, task group, or task.

Action: If the resource should be locked, then no action is required. To manually unlock the managed resource, delete the record in the CMMETADATA table that has the matching resource container, resource manager, and managed resource keys.

CWXBE1000I

Explanation: This is a status message to indicate that the preview Web application did not find any plug-ins that may intercept the request.

Action: No action necessary.

CWXBE1001I

Explanation: Status message specifying the preview request plug-in that is being loaded by the preview Web application.

Action: No action required.

CWXBE1400E

Explanation: The preview Web application cannot find the Stores Web application and therefore cannot forward the requests for processing.

Action: Ensure that the Stores Web application has been started.

CWXBE1500E

Explanation: The site's deployment policy prevents this URL from being invoked in the preview environment.

Action: No action required.

CWXBR0000W

Explanation: The verification check of the business audit record with a session ID of {0} and a sequence of {1} has failed. This might be the result of altered data within the audit record.

Action: A status message is available in the audit log to indicate which record might be altered. Examine the audit record to see the current values and to see what data might have been altered.

CWXBR0100W

Explanation: There was a problem retrieving the properties of the attachment asset.

Action: Ensure the input properties for the attachment asset are valid.

CWXBR0101W

Explanation: There was a problem retrieving the properties of the attachment relation.

Action: Ensure the input properties for the attachment relation are valid.

CWXBR0102W

Explanation: There was a problem creating the attachment asset. The attachment asset and attachment target might not be owned by the same store entity, or the attachment asset path, together with the store entity and the attachment target, might not be unique in the database.

Action: Check the attachment asset in the database. The table containing the information is ATCHAST. Ensure that the attachment asset is owned by an attachment target in the same store entity. Ensure that the attachment asset path, together with the store entity and the attachment target, is unique in the database.

CWXBR0103W

Explanation: There was an error updating the attachment asset. The store entity must own both the attachment target and attachment asset and the path and filename of the attachment asset might not be valid.

Action: Check that the store entity owns both the attachment target and the attachment asset. Check that the path and filename of the attachment asset is valid and is not used by another attachment asset.

CWXBR0104W

Explanation: There was an error deleting the attachment asset.

Action: Ensure that the row in the database table ATCHAST that contains attachment asset is not locked.

CWXBR0105W

Explanation: There was an error assigning a language to the attachment asset. This error can result when the attachment target that owns the attachment asset is language-independent, disallowing any language to be assigned to the asset. This error can also result when the attachment asset is already assigned that language. A third possibility is that one of the assets of the same attachment target is already assigned to that language; two assets cannot be assigned to the same language in the same attachment target.

Action: Check that the attachment target is not language-independent, ensure the attachment asset is not already assigned to the language, and do not assign more than one attachment asset in the same attachment target to the same language.

CWXBR0106W

Explanation: There was a problem unassigning the language for the attachment asset.

Action: Check the ATCHASTLG database table for the assigned languages for the attachment asset. Ensure the row is not locked.

CWXBR0107W

Explanation: There was a problem creating the attachment relation. The WebSphere Commerce object can be attached to the attachment target with a specific usage only once.

Action: Check the ATCHREL database table for the attachment relation. Ensure the sure the unique index of the table is not violated. To attach the WebSphere Commerce object to the same target again, use a different usage.

CWXBR0108W

Explanation: There was a problem updating the attachment relation.

Action: Check the ATCHREL database table for the attachment relation. Ensure that the combination of the object ID, the attachment object type ID, the attachment target ID in the attachment relation and the attachment relation usage ID is unique. Also ensure that the row is not locked.

CWXBR0109W

Explanation: There was a problem deleting the attachment relation.

Action: Check the ATCHREL table in the database for the attachment relation. Ensure the row is not locked.

CWXBR0110W

Explanation: There was an error creating the description for the attachment relation. The description for the attachment relation in the specified language might already exist.

Action: Check the database table ATCHRELDSC for the description of the attachment relation in the specified language.

CWXBR0111W

Explanation: There was a problem updating the description of the attachment relation.

Action: Check the ATCHRELDSC database table for the description of the attachment relation. Ensure the row is not locked.

CWXBR0112W

Explanation: There was a problem deleting the description of the attachment relation.

Action: Check the ATCHRELDSC table for the description of the attachment relation in the specified language in the database.

CWXBR0113W

Explanation: There was a problem creating the attachment relation usage.

Action: Check the attachment relation usage in the database table ATCHRLUS. Ensure that the unique index is not violated.

CWXBR0114W

Explanation: There was a problem updating the attachment relation usage.

Action: Check the ATCHRLUS database table for the attachment relation usage. Ensure the identifier for the attachment relation usage is unique.

CWXBR0115W

Explanation: There was a problem deleting the attachment relation usage. An attachment relation usage cannot be deleted if it is being used by in an attachment relation.

Action: Check the ATCHREL database table for the attachment relation. Ensure that no attachment relation is using the attachment relation usage by checking the ATCHRLUS_ID column. If this usage is being used by another attachment relation, assign the attachment realation to a different attachment relation usage and try deletion again.

CWXBR0116W

Explanation: There was an error creating a description for the attachment relation usage. The description for the attachment relation usage in the specified language might already exist.

Action: Check the databaes table ATCHRLUSDS for the description of the attachment relation usage in the specified language.

CWXBR0117W

Explanation: There was an error updating the description of the attachment relation usage.

Action: Check ATCHRLUSDS database table for the description of the attachment relation usage in the specified language.

CWXBR0118W

Explanation: There was an error deleting the description of the attachment relation usage.

Action: Check the ATCHRLUSDS database table for the description of the attachment relation usage in the specified language. Ensure the row is not locked.

CWXBR0119W

Explanation: There was a problem creating the attachment target. Ensure the target identifier, the store entity that the in which the attachment target exists, and the owner of the attachment target are unique.

Action: Check the ATCHTGT database table Ensure that the unique index of the table is not violated.

CWXBR0120W

Explanation: There was an error updating the attachment target. The combination of the identifier of the attachment target, the store entity that owns the attachment target, and the owner of the attachment target must be unique.

Action: Check the ATCHTGT databae table. Ensure the combination of the identifier of the attachment target, the store entity that owns the attachment target, and the owner of the attachment target is unique.

CWXBR0121W

Explanation: There was a problem deleting the attachment target. An attachment target associated with an object cannot be deleted.

Action: Ensure the attachment target is not associatied with any objects before deletion.

CWXBR0122W

Explanation: There was an error creating the description for the attachment target. The attachment target description in the specified language might already exist.

Action: Check the ATCHTGTDSC database table for the description of the attachment target in the specified language.

CWXBR0123W

Explanation: There was an error updating the description of an attachment target

Action: Check database table ATCHTGTDSC for the description of the attachment target in the specified language.

CWXBR0124W

Explanation: There was a problem deleting the description of the attachment target.

Action: Check the ATCHTGTDSC table in the database for the description of the attachment target. Ensure the row is not locked.

CWXBR0128W

Explanation: There was a generic problem when updating the attachment.

Action: Turn on tracing for attachments and examine the trace file.

CWXBR0900E

Explanation: An exception has been thrown while processing the com.ibm.commerce.security.commands.MigrateGuestUserCmd command. This means that the information of the previous guest user has not been properly copied over to the new guest user. By default, this command copies the active shopping cart of the previous guest user to the current user.

Action: If this happens consistently, contact WebSphere Commerce support for assistance.

CWXBR1000E

Explanation: This is the error message that will be send by server when SSO Activity token has expired.

Action: Relogon to Multichannel Sales Center. If problem persists, contact your system administrator.

CWXBR1001E

Explanation: This is error message that will be send by server if SSO activity token is no longer valid.

Action: Relogon to Multichannel Sales Center. If proble persists, contact your system administrator.

CWXBR1002E

Explanation: ActivityToken Based Single Sign-On service in wesphere commerce is not enabled.

Action: Contact your system administrator to provide this service by enabling ActivityTokenBased SSO flag in webshpere commerce.

CWXCM001E

Explanation: The system failed to communicate with WebSphere Member Manager.

Action: Check the WAS Admininstrative console to ensure that the WebSphere Member Manager application is running. Check to ensure that your LDAP server is running and accessible.

CWXCP3000E

Explanation: Invalid reservation amount or release IDs have been passed down to EDP.reservePayment(). This can happen if order task commands have been customized.

Action: Correct the customized code so that it passes valid reservation amounts and release IDs to EDP.reservePayment().

CWXCP3001E

Explanation: An invalid release ID has been specified in a finalize payment request. This can occur if order task commands have been customized.

Action: Correct the customized code and ensure that the correct invalid ID is being passed down to finalize payment.

CWXCP3002E

Explanation: The order {0} is submitted successfully, but the payment is pending.

Action: Check the payment status later. If the payment status is still pending, then call the administrator.

CWXCP3003E

Explanation: The details of a payment instruction could not be retrieved from the payment subsystem. This can occur if an invalid payment instruction or order ID was specified. This can also occur if a payment instruction could not be created previously.

Action: Ensure that the correct payment instruction has been successfully created and the correct order ID and payment instruction ID are being specified.

CWXCP3004E

Explanation: A payment instruction could not be added or modified because invalid attributes have been specified in the protocol data. This can occur if the processing payment plug-in requires more or different fields from those specified in the protocol data.

Action: Ensure that the correct payment details are passed as the protocol data for a payment instruction.

CWXCP3005E

Explanation: Payment instruction attributes are invalid. This can occur if invalid payment instruction details are collected during order capture in the storefront JSP buy page. This can also happen if a JSP file was developed for a payment method and has been reused for a different method or a different payment plug-in, with different requirements being used.

Action: Ensure that the required payment plug-in attributes are specified in the storefront JSP buy page.

CWXCP3006E

Explanation: The finalization amount has not been specified accordingly. This can occur if order task commands have been customized and the finalization amount is not calculated.

Action: Correct the task commands code and pass the finalization amount down to the EDP.finalizePayment request accordingly.

CWXCP3007E

Explanation: No release ID has been passed down to EDP.reservePayment() or EDP.finalizePayment(). This can happen if the order's task commands have been customized.

Action: Ensure that the customized code is passing a valid (non-empty) set of release IDs on EDP.reservePayment and a valid release ID on EDP.finalizePayment().

CWXCP3008E

Explanation: The total order amount has not been specified to event-driven payments during an order creation or order edit. This can happen when order task commands have been customized and invalid logic has been added. Event-driven payments validates every request and ensures that proper parameters are passed down.

Action: Correct the customized code so that the total order amount is always specified in event-driven payment requests.

CWXCP3009E

Explanation: An invalid reservation amount has been specified in EDP.reservePayment(). This can occur if order task commands have been customized.

Action: Correct the customized code so that it passes a valid reservation amount to EDP.reservePayment().

CWXCP3010E

Explanation: The order subsystem could not add a payment instruction to an order. This can happen if invalid parameters have been specified in the order, if there is incorrect payment configuration for the referred payment method, or if the processing payment plug-in is missing or misconfigured.

Action: Ensure that correct parameters are passed for the payment instruction being created and the complete end-to-end configuration of order and payments is correct for available payment methods, payment method configurations, payment system mappings, and plug-in deployment descriptors.

CWXCP3011E

Explanation: The order subsystem could not find any payment activity for an specified order. This can happen if no payment instruction has been added to an order or the specified order does not exist.

Action: Add a payment instruction to a specified order or modify the order ID to refer to an existing order.

CWXCP3012E

Explanation: The order system could not find any payment activity for a specified order. This can happen if no payment instruction has been added to an order or the specified order does not exist.

Action: Add a payment instruction to a specified order or modify the order ID to refer to an existing order.

CWXCP3013E

Explanation: The order subsystem could not retrieve valid payment methods for a store. This can happen if there is a misconfiguration or an invalid store ID has been provided to event-driven payments.

Action: Correct the end-to-end payment method configuration and specify a valid store ID.

CWXCP3014E

Explanation: The overall status of a payment object could not be retrieved from the payment subsystem. This can occur if an invalid payment ID is used or the payment back-end system cannot be reached (online queries only).

Action: Ensure that a valid payment ID is specified and that the payment back-end system is available and can be reached through the network.

CWXCP3015E

Explanation: The return system could not retrieve valid refund methods for a store. This can happen if there is a misconfiguration or an invalid store ID has been provided to the event-driven payments subcomponent.

Action: Correct the end-to-end refund method configuration and specify a valid store ID.

CWXCP3016E

Explanation: The overall status of a refund object could not be retrieved from the payment subsystem. This can occur if an invalid refund (RMA) ID is used or the payment back-end system cannot be reached (online queries only).

Action: Ensure that a valid refund (RMA) ID is specified and that the payment back-end system is available and can be reached through the network.

CWXCP3017E

Explanation: A payment instruction could not be found in the payment subsystem. This can occur if an invalid payment instruction ID has been specified.

Action: Ensure that a valid payment instruction ID is specified in the task command.

CWXCP3018E

Explanation: A payment instruction could not be added or modified because invalid attributes have been specified in the protocol data. This can occur if the processing payment plug-in requires more fields or different fields from those specified in the protocol data.

Action: Ensure that the correct payment details are passed as the protocol data for a payment instruction.