Messages and Processor Codes March 2008

Transcription

1 CyberSource Payment Manager 6.3 Messages and Processor Codes March 2008

2 CyberSource Contact Information For questions about CyberSource Payment Manager, For general information about our company, products, and services, go to For sales questions about any CyberSource Service, or call or (toll-free in the United States). For support information about any CyberSource service, visit the Support Center at Copyright 2008 CyberSource Corporation. All rights reserved. CyberSource Corporation ("CyberSource") furnishes this document and the software described in this document under the applicable agreement between the reader of this document ("You") and CyberSource ("Agreement"). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the information contained in this document is subject to change without notice and therefore should not interpreted in any way as a guarantee or warranty by CyberSource. CyberSource assumes no responsibility or liability for any errors that may appear in this document. The copyrighted software that accompanies this document is licensed to You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using the software. Except as permitted by the Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of CyberSource. Restricted Rights Legends For Government or defense agencies. Use, duplication, or disclosure by the Government or defense agencies is subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS and in similar clauses in the FAR and NASA FAR Supplement. For civilian agencies. Use, reproduction, or disclosure is subject to restrictions set forth in subparagraphs (a) through (d) of the Commercial Computer Software Restricted Rights clause at and the limitations set forth in CyberSource Corporation's standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States. Trademarks CyberSource, the CyberSource logo, SmartCert, and PaylinX are registered trademarks of CyberSource Corporation in the U.S. and other countries. The Power of Payment, CyberSource Payment Manager, CyberSource Risk Manager, CyberSource Decision Manager, and CyberSource Connect are trademarks and/or service marks of CyberSource Corporation. All other brands and product names are trademarks or registered trademarks of their respective owners. CPM Messages and Processor Codes CyberSource Corporation March 2008 ii

3 Contents Documentation Changes and Enhancements... viii Chapter 1 Introduction...1 Introducing CPM...1 CPM Components...2 CPM Architecture...3 CPM Errors...4 CPM API Errors...4 CPM Server Errors...4 Chapter 2 Batch Status Values...5 Chapter 3 CPM Server Error Messages...7 CPM Error Message Severity...7 CPM Server Errors...8 (NULL) MSG_DATABASE_SIZE_WARNING MSG_START_DBUTIL_FAILED_WARNING MSG_INVALID_MERCHANT_STORE_WARNING MSG_NO_SEND_WARNING MSG_NOT_CREATE_WARNING MSG_WRITING_WARNING MSG_READING_WARNING MSG_FIVE_ACK_WARNING MSG_FIVE_NACK_WARNING MSG_LOST_DATABASE_CONNECTION CHANNEL_MGR_RECEIVED_A_BAD_IP_ADDRESS NO_CONNECTION_DEVICE_DLLS_AVAILABLE FAILED_TO_UNLOAD_DLL MSG_PARTIAL_MESSAGE_RECEIVED MSG_TX_NOT_UNIFIED_WARNING MSG_ACK_NOT_UNIFIED_WARNING MSG_MERCHANT_COUNTER_NOT_FOUND_WARNING MSG_TX_NOT_SETTLED_NOT_IN_DB_WARNING MSG_TX_NOT_SETTLED_MULTIPLE_SEQ_NUMBER...15 CPM Messages and Processor Codes CyberSource Corporation March 2008 iii

4 Contents 1020 MSG_PAYMENTECH_NO_DATA MSG_BATCH_NOT_SETTLED_NO_LPC MSG_SERVER_SETTLEMENT_WARNING MSG_TX_INITIALIZATION_FAILED MSG_NO_LPCS_ENABLED MSG_COULD_NOT_INITIATE_SIGNON MSG_COULD_NOT_INITIATE_SIGNOFF MSG_CURRENT_PAYMENT_PROCESSOR_HOST MSG_PARTIAL_MSG_AND_NAK_COUNT_EXCEEDED MSG_UNABLE_TO_OPEN_CWND_FOR_SCHEDULER MSG_STARTSERVICECTRLDISPATCHER_FAILED MSG_SETSERVICESTATUS_FAILED MSG_CREATE_EVENT_FAILED MSG_LOGIN_FAILED MSG_STORE_FAILED_SQL_STMT_FAILED MSG_INSERT_FAILED_SQL_STMT_FAILED MSG_UNABLE_TO_OPEN_COM_PORT MSG_BATCH_TX_ERROR MSG_SQL_EXECUTE_ERROR MSG_SIZE_PARAMETER_ERROR MSG_WINSOCK_ERROR MSG_CREATE_SOCKET_ERROR MSG_LOST_DATABASE_CONNECTION_ERROR MSG_CANT_INSERT_FAILED_SQLSTMT_FILE_ERROR MSG_INVALID_OR_EXPIRED_LICENSE_ERROR MSG_EXCEEDED_MERCHANT_LIMIT_ERROR MSG_OUT_OF_MEMORY MSG_SQL_ERROR MSG_DATABASE_CONNECT_FAILURE_ERROR MSG_UNKNOWN_MESSAGE_RECEIVED MSG_CANT_READ_BATCH_ERROR MSG_BATCH_HEADER_TRAILER_ERROR MSG_UNABLE_TO_CONNECT_TO_PROCESSOR MSG_BATCH_FAILED_DUE_TO_CONNECTION_CLOSE MSG_BATCH_PROCESSING_ERROR MSG_CHANNEL_DEVICE_CONFIG_ERROR MSG_CREATE_SOCKET_WND_ERROR MSG_SSL_INIT_ERROR MSG_SSL_NEG_ERROR MSG_TXBCONV_ERROR MSG_NBTXCONV_ERROR MSG_DATABASE_TABLES_NOT_EXIST_ERROR MSG_BATCH_DISK_FILE_OPEN_ERROR MSG_BATCH_DISK_FILE_WRITE_ERROR MSG_BATCH_DISK_FILE_FTP_ERROR MSG_BATCH_DISK_FILE_CLOSE_ERROR MSG_BATCH_JOB_CARDS_FILE_OPEN_ERROR MSG_BATCH_JOB_CARDS_FILE_CLOSE_ERROR...34 CPM Messages and Processor Codes CyberSource Corporation March 2008 iv

5 Contents 5041 MSG_PIPELINE_COMPONENT_FAILED_TO_START MSG_FRAUD_CONNECT_INFO_MISSING MSG_FRAUD_CHANNEL_START_FAIL MSG_FRAUD_CONNECTION_FAIL MSG_FRAUD_CONNECTION_LOST MSG_FRAUD_DEVICE_FAIL MSG_DATABASE_TABLES_INCORRECT_VERSION_ERROR MSG_BATCH_SETTLEMENT_ERROR MSG_BATCH_SETTLMENT_TIMEOUT MSG_BATCH_SETTLMENT_UKNOWN_STATE MSG_SETTLE_RESPONSE_ERR MSG_FAILED_TO_SEND MSG_CLEAR_ERROR_TO_CONTINUE_SETTLEMENT MSG_BATCH_OUT_OF_BALANCE MSG_BATCH_REJECTED_BY_HOST MSG_DB_ENCRYPTION_KEY_FILE_MISSING MSG_VITAL_HTTP_SSL_COMMUNICATIONS_ERROR MSG_VITAL_MERCHANT_CONFIGURATION_ERROR MSG_NULL_POINTER_TO_BATCH_STRUCTURE MSG_BATCH_NUMBER_OUT_OF_SEQUENCE MSG_SERVER_SETTLEMENT_ERROR MSG_MERCHANT_SETTLEMENT_ERROR MSG_COULD_NOT_UPDATE_MERCHANT_STATE MSG_SETTLEMENT_GATEWAY...43 Chapter 4 CPM API Error Messages...44 Negative Numbered CPM API Errors ERR_MISSING_CONNECTION_INFO ERR_MERCHANT_NOT_SPECIFIED ERR_CONFIG_BAD_ENTRY ERR_CONFIG_LOOKUP_FAILED ERR_CONFIG_OPEN_FAILED ERR_OPEN_DEBUG_FILE ERR_VALUE_TOO_LARGE ERR_VALUE_NOT_FOUND ERR_CONNECTION_INVALID ERR_INVALID_HANDLE ERR_NOT_INITIALIZED ERR_SSL_GENERAL ERR_SSL_NEG ERR_SSL_LIB_INIT ERR_ENCRYPTION_FAILED ERR_SOCK_READ ERR_SOCK_WRITE ERR_SOCK_CONN_REFUSED ERR_SOCK_CONNECT...55 CPM Messages and Processor Codes CyberSource Corporation March 2008 v

6 Contents -12 ERR_SOCK_CREATE ERR_SOCK_LIB_INIT...56 Positive Numbered CPM API Errors Success ERR_NOT_ACCEPTING_TX ERR_INVALID_FIELD_25_NO_MAP ERR_TRANSACTION_TYPE ERR_INVALID_FIELD ERR_FIELD_TOO_LONG ERR_BATCH_GROUP_DRAFT_ID_EXISTS ERR_OUT_OF_MEMORY_BUFFERS ERR_OUT_OF_MEMORY_HEAP ERR_COULD_NOT_CONNECT_PROCESSOR ERR_TIME_OUT ERR_UNIDENTIFIABLE ERR_INVALID_FIELD_VALUE ERR_INVALID_DATA_TYPE ERR_INVALID_RECORD_SEQUENCE ERR_INVALID_MERCHANT_CONFIGURATION ERR_CC_MOP_MISMATCH ERR_INVALID_MOP_FOR_DIVISION ERR_INVALID_TRANSACTION_TYPE ERR_DUPLICATE_PURCHASE_IDENTIFIER ERR_UNKNOWN ERR_LOOKUP_NO_RECORDS_FOUND ERR_MULTIPLE_RECORDS_FOUND ERR_VOID_FAILED_TX_SETTLED ERR_VOID_FAILED_TX_NOT_FOUND ERR_SEQUENCE_NUMBER_LOOKUP_TIMEOUT ERR_HTTP_SSL_COMMUNICATIONS_FAILURE ERR_LOOKUP_FIELD_NOT_SET ERR_LOOKUP_ENCYRPTED_ACCOUNT_NUMBER ERR_SERVICE_NEED_TCB_PRIV ERR_INVALID_USERNAME_PASSWORD ERR_SESSION_INVALID ERR_SESSION_TIMEOUT ERR_SESSION_SOURCE_INVALID ERR_INVALID_MERCHANT_ID ERR_SESSION_ACCESS_DENIED ERR_CREATE_SESSION_FAILURE ERR_SESSION_AMOUNT_LIMIT_REACHED ERR_SESSION_RETURN_AMOUNT_LIMIT_REACHED ERR_LICENSE_KEY_VIOLATION ERR_DATABASE_LOG_FAILURE ERR_DUPLICATE_TRANSACTION_CHECK ERR_FRAUD_CHECK ERR_FRAUD_TIMEOUT ERR_VOID_TX_FAILURE...73 CPM Messages and Processor Codes CyberSource Corporation March 2008 vi

7 Contents 1016 ERR_NO_GATEWAY_AVAILABLE ERR_GATEWAY_NOT_ENABLED ERR_TX_NOT_VOIDABLE ERR_INVALID_MERCHANT_STATE_AUTH...74 Invalid Field Messages for FDMS South Debit...75 Messages Received for Authorization and Capture...75 Messages Received for Reversal...76 Chapter 5 Financial Processor Return Codes...77 Authorization Response Codes...77 AVS Response Codes...82 Visa RED Regulations for AVS...82 AVS Response Codes: Address...83 AVS Response Codes: Postal Code...84 CVV Result Codes...86 CPM Messages and Processor Codes CyberSource Corporation March 2008 vii

8 Documentation Changes and Enhancements The following table lists changes made in recent releases of this document: Release Changes 6.3 Updated the CPM version to 6.3. For Paymentech New Hampshire: - Added new AVS response codes. See AVS Response Codes: Address on page 83 and AVS Response Codes: Postal Code on page Added new authorization response codes. See Authorization Response Codes on page Updated the CPM version to Updated gateway processor name: changed Midwest Payment Systems (MPS) to Fifth Third Processing s (FTPS). Updated the authorization response codes for FTPS. See Table 8 on page 78. Updated the AVS response codes for FTPS. See Table 10 on page 83 and Table 12 on page Updated the CPM version number to Updated the CPM version number to Updated the AVS response codes for American Express Phoenix and Vital. See Table 10 on page 83 and Table 11 on page Updated the CPM version number to Updated the CPM version number to 6.2. Added information about the processor codes returned for the new BA Merchant Services gateway. See the tables in Chapter 5, Financial Processor Return Codes, on page 77. CPM Messages and Processor Codes CyberSource Corporation March 2008 viii

9 Chapter 1 Introduction This guide contains CPM Server error messages, CPM API error messages and warnings, batch status codes, and financial processor return codes. Financial processor codes currently supported by CPM include First Data Merchant Services, Fifth Third Processing s, Paymentech, American Express, NOVA, and Vital. As new processors are added to the CyberSource payment options, their return codes will be included in future updates to this guide. The CPM Messages and Processor Codes is intended for IT engineers, software programmers, database administrators, and the CPM Server administrator. Use this guide in conjunction with the CPM API Reference Guide. CPM utilizes the CPM Error Log to display any errors or warnings that can occur during operation of the CPM Server. You can access that viewer with the CPM Administration Client. You can also view these errors and warnings with the Windows Event Viewer. Access this application from within the Administrative Tools for Windows. Introducing CPM CyberSource Payment Manager Server (CPM) is a client-server credit card solution that provides high-speed payment processing of multiple simultaneous transactions. The CPM Server connects, as needed, to various credit card and other financial networks such as First Data Merchant Services (FDMS), Fifth Third Processing s (FTPS), Paymentech, and Visa. CPM is ODBC compliant so that integration with an existing database is readily accomplished. CPM integrates with Microsoft SQL Server, Oracle, and other well known ODBC-compliant databases. CPM comes with a full-featured reporting application, CPM Reports, for reporting and analysis of transaction information. With the CPM Server, you can choose from a rich set of CPM Client APIs including a Unix daemon for IVR systems, and DLLs for Windows application integration. In addition to these clients, CPM offers an ActiveX Control, CPM Client APIs for UNIX, and the CPM Java API. These make CPM easy to fit into many business environments. CPM Messages and Processor Codes CyberSource Corporation March

10 Chapter 1 Introduction Introducing CPM CPM Components The CPM provides all traditional credit card processing operations including the management of authorizations, settlements, and reporting. CPM is comprised of the following components: CPM Server The CPM Server is the core of the CPM system and provides all traditional credit card processing operations including the management of authorizations, settlements, and reporting. The CPM Server takes advantage of the Windows and Sun Solaris client-server environment to establish username and password security for setting up permission levels to the CPM Server. The CPM Server runs as a Windows or Sun Solaris service and is the core of the CPM system. The CPM Server provides high-speed payment processing with the ability to handle multiple transactions simultaneously. CPM Administration Server The CPM Administration Server runs on the same machines as the CPM server and provides an administrative interface to remotely start and stop the CPM server, as well as to query the CPM Error/Status log. CPM Administration Client The CPM Administration Client runs on any Windows Server 2000 or 2003 machine with TCP/IP connectivity to the CPM server machine. There is also a command-line-only version for Sun platforms. The CPM Administration Client is a graphical administration tool that is used to configure, monitor, and control the CPM server. The CPM Administration Client communicates with the CPM server and with the CPM Administration Server via TCP/IP. It can be used to remotely administer CPM over a local LAN or the Internet. CPM Reports Provides full reporting capabilities of transaction information contained in the CPM database for a wide range of business needs. CPM Windows Client The CPM Windows Client is a graphical client application for the CPM Server that runs on Windows workstations. This optional component enables organizations to test the CPM installation without having to write a program that uses the CPM API. CPM Client APIs The CPM Client APIs supply the resources to develop custom client applications to interact with the CPM Server. These APIs include ActiveX in VB, Windows DLLs, Java SDKs, and Sun shared objects. CPM Messages and Processor Codes CyberSource Corporation March

11 Chapter 1 Introduction Introducing CPM CPM Architecture The CPM architecture allows for a wide variety of configurations, from a very simple single server with one processor connection to multiple servers with multiple processor connections. Multiple servers and processors enable increased throughput and reliability through redundancy. The following figure illustrates the most basic recommended CPM configuration. Client Application LAN CPM Admin Client Router Frame to Processor Database Server CPM Server CPM Admin Server Firewall Internet SSL to Processor Client Application CPM Admin Client The client applications in the diagram include point of sale (POS) terminals or applications, Web store fronts, or IVR systems. All communications between client applications and the CPM server use the CPM API libraries and are encrypted with the Blowfish encryption algorithm. For additional security, client applications may optionally use SSL to communicate with the CPM server. The database server in the diagram may be any of those listed in the requirements section of the CPM Setup Guide. The CPM Server communicates with the financial processor through a frame connection, or, in some cases, through a SSL connection involving the Internet. The CPM Server is configured and controlled using the CPM Administration Client. A single CPM Administration Client can control multiple CPM servers. Multiple CPM Servers can be included to build redundant or higher throughput systems. When multiple CPM Servers are used in a configuration it is recommended that only one of the servers be configured to settle. For example, configure all but one server as Auth- Only servers. CPM Messages and Processor Codes CyberSource Corporation March

12 Chapter 1 Introduction CPM Errors CPM Errors The CPM can use many interfaces to pass transaction data from one point of the CPM API integration to the CPM system and then along to the financial processor. If errors occur, the errors can be reported in two places of the CPM: CPM API Errors CPM Server Errors CPM API Errors CPM API errors are generated any time the CPM API encounters a malfunction when receiving transaction requests from the integrating point of purchase (card swipe, web site, call center) and submitting transaction requests to the CPM Server. CPM Server Errors The CPM Server generates errors any time the CPM Server encounters a problem during operation. CPM Messages and Processor Codes CyberSource Corporation March

13 Chapter 2 Batch Status Values This chapter lists the batch status values that are assigned to transactions during the settlement batching process. You can see the batch status value in the Batch Status window in the Administration Client, or in the CC_SETTLEMENT table in the database. Normally, if a settlement batch fails and results in a batch status other than 00, subsequent settlement batches are not processed until you fix the error with the failed batch. However, CPM has a system-wide switch that lets subsequent batches continue to be settled even when a batch status error occurs. The behavior is controlled by a parameter in the cpm.cfg file called OverrideBatchError. If you set the parameter to false, the system behaves as normal. If you set the parameter to true, settlement continues even though a previous batch failed. This ability mainly benefits merchants using FDMS Nashville, Paymentech New Hampshire, and Vital, which use online settlement and not FTP file settlement. Table 1 Batch Status Values Batch Status Value Description 00 Settlement batch processing complete. 01 Settlement batch is sending or delayed. If batch settlement is delayed, the batch will be sent at the next settlement interval. 02 Settlement batch file is built and is waiting to be communicated to the financial processor using file transfer protocol (FTP). 03 Batch failed in sending to processor. For the Global Payments and Paymentech New Hampshire gateways, 03 means that the settlement batch is still sending. CPM Messages and Processor Codes CyberSource Corporation March

14 Chapter 2 Batch Status Values Table 1 Batch Status Values (Continued) Batch Status Value Description 04 Error creating batch file. For the FDMS North gateway, 04 indicates that there was no batch to settle. All other errors related to the batch for FDMS North use status 05. For the Global Payments and Paymentech New Hampshire gateways, 04 indicates that at least one of the transactions in the batch is bad (TRANSACTION_STATE=B). Determine the problem with the transaction and fix it. If necessary, call the processor. In the database, set the BATCH_STATUS to 00 and null out the BATCH_ID and the DRAFT_ID for the bad transaction. The transaction will then get picked up for settlement the next time CPM settles. 05 Used for special batch situations that are specific to a particular gateway. See the BATCH_RESPONSE_MSG field in the CC_SETTLEMENT table for a description. For the Paymentech New Hampshire gateway, 05 means that the settlement batch was sent and CPM is now waiting for the request for response (RFR) file to be available from the processor. The RFR file indicates whether the processor received the settlement file correctly. When CPM receives the file, the status changes to 00 if the file indicates success or 04 if the file indicates an error. If the RFR is never produced, the Batch Status value remains at FTP file is being transmitted to the processor. This value is returned only for the FDMS North, FTPS, and NOVA gateways. 07 FTP error. This value is returned only for the FDMS North, FTPS, and NOVA gateways. 08 Error occurred while building the batch list from the database. Might occur, for example, if your database server crashes in the middle of settlement, or if the resulting batch list came back empty. CPM Messages and Processor Codes CyberSource Corporation March

15 Chapter 3 CPM Server Error Messages This chapter covers the error codes and corresponding error messages that can be issued by the CPM Server. Each error description includes a brief statement and recommends a solution for the error. CPM Error Message Severity Each CPM Server error message consists of an identifier, definition, and error description. The listing includes a brief problem statement and suggested solution. The severity of the problem that generated the CPM Server error message is categorized into two types: Table 2 CPM Error Message Severity Severity Runtime Catastrophic Description The CPM Server can continue to function and transmit data while the error is resolved. In a few instances, runtime errors are informational only and do not require immediate attention. Persistent runtime errors could indicate a chronic problem affecting CPM operation. If the error persists, correct the problem before the error becomes more serious. The CPM Server cannot function or transmit data until this error is resolved. Because each CPM installation is different, the solutions presented below may not work for every situation. However, most solutions should provide insight for possible remedies. CPM Messages and Processor Codes CyberSource Corporation March

16 Chapter 3 CPM Server Error Messages CPM Server Errors CPM Server Errors (NULL) Definition The CPM API submitted a transaction request to the CPM Server. The CPM Server creates a new row in the CC_TRANSACTION table to contain the transaction request s information of the CPM database. Certain fields in the new row are populated with (NULL). This (NULL) value is removed and the LCC_RETURN_CODE and LCC_ RETURN_MESSAGE fields are written with the appropriate API return code for the transaction at processor response. The (NULL) message is written for authorization, authorization and capture, and reversal transactions. Type of error Message. This message is informational only and can only be viewed in the CC_TRANSACTION table of the CPM database. Problem If the CPM Server is disconnected from the database, new transaction requests in CC_TRANSACTION contain the (NULL) value until the database connection is reestablished and the responses for those transactions are received from the financial processor and the (NULL) value removed. None. Transactions in the CC_TRANSACTION database are not being updated and the (NULL) value removed. This may indicate an error is occurring during processor response. This could be a network error or other communication problem with the financial processor MSG_DATABASE_SIZE_WARNING Definition The CPM database has reached the age/volume warning levels you have set. Problem The CPM Database Utility has detected that the database is larger than the size/date limit established in the CPM Administration Client. Either increase the database warning thresholds in the CPM Administration Client or reduce the number of transactions in the database by using the purge feature of the CPM Database Utility. Note Generate a transaction activity report before purging the CPM database. CPM Messages and Processor Codes CyberSource Corporation March

17 Chapter 3 CPM Server Error Messages CPM Server Errors 1002 MSG_START_DBUTIL_FAILED_WARNING Definition Could not create database utility. Reason: <reason> Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server was unable to start the CPM Database Utility. The CPM Server attempts to start the CPM Database Utility every hour. Verify that both the CPM Database Utility and the CPM Server are located in the same directory on the hard drive hosting CPM Server. If they are not, call CyberSource Customer Support for assistance MSG_INVALID_MERCHANT_STORE_WARNING Definition The CPM Server received an invalid merchant/store number combination. Problem A transaction was successfully sent and the CPM Server received a response but the merchant no longer exists in the CPM database. Use the CPM Administration Client to make sure that the Merchant Number field on the CPM API client side and the CPM Server side are identical. If the fields are not identical, call your financial processor to determine your Merchant Number. If the Merchant Number is correct, call CyberSource Customer Support for assistance MSG_NO_SEND_WARNING Definition The connection between the CPM API client and the CPM Server was severed. The transaction may have been processed by the CPM Server but not returned to the CPM API client. Problem The CPM Server processed the last transaction, but the CPM API client computer was not notified. This problem can be caused by a failed network connection, a CPM Messages and Processor Codes CyberSource Corporation March

18 Chapter 3 CPM Server Error Messages CPM Server Errors delay in network communication, or because the CPM API client was terminated before receiving a response from the CPM Server. Check the network connection between the CPM API client and the CPM Server by using the netstat -a command to verify port usage. Another application may have reserved the port. Restart the server hosting CPM and contact CyberSource Customer Support to report any problems. Note The condition causing error message ID 1004 can allow a transaction to be charged twice to the same credit card. To determine if the transaction was added to the database before the error occurred, run CPM transaction report. If the transaction has been added to the database, do not resubmit it MSG_NOT_CREATE_WARNING Definition CPM is unable to establish a connection to the CPM API client. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM Server cannot communicate with the CPM API client because the CPM Server cannot open a TCP/IP port. Check network connections at both the CPM Server and CPM API client terminals by using the netstat -a command to verify port usage. Another application may have reserved the port. If another application is using the port, resolve the conflict and try to reconnect. Restart the CPM Server and contact CyberSource Customer Support to report any problems MSG_WRITING_WARNING Definition The CPM Server could not write to the TCP/IP socket. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server cannot write data to the TCP/IP port used to communicate with the CPM API client. CPM Messages and Processor Codes CyberSource Corporation March

19 Chapter 3 CPM Server Error Messages CPM Server Errors Check the network connection between the CPM API client and the CPM Server by using the netstat -a command to verify port usage. Another application may have reserved the port. If another application is using the port, resolve the conflict and try to reconnect. Restart the CPM Server and contact CyberSource Customer Support to report any problems MSG_READING_WARNING Definition The CPM Server could not read from the TCP/IP socket. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server cannot read data from the TCP/IP listening port used to capture transaction requests from the CPM API client. Check the network connection between the CPM API client and the CPM Server by using the netstat -a command to verify port usage. Another application may have reserved the port. If another application is using the port, resolve the conflict and try to reconnect. Restart the CPM Server and contact CyberSource Customer Support to report any problems MSG_FIVE_ACK_WARNING Definition The CPM Server received five acknowledgements when trying to communicate with the financial processor. If the error persists, the error is catastrophic and the CPM cannot operate until this problem is solved. Problem The CPM Server received five or more acknowledgements (ACKs) when communicating with the financial processor. Line noise, improperly configured or malfunctioning communications hardware, or improperly connected cabling can cause this error. Verify the following: The communications hardware is properly configured. CPM Messages and Processor Codes CyberSource Corporation March

20 Chapter 3 CPM Server Error Messages CPM Server Errors The communications lines for the type of network are reliable. Correct any network configuration problems in the CPM Server and on the server hosting the CPM Server. If the errors continue, contact CyberSource Customer Support and your financial processor MSG_FIVE_NACK_WARNING Definition The CPM Server received five negative acknowledgements when trying to communicate with the financial processor. If the error persists, the error is catastrophic and the CPM cannot operate until this problem is solved. Problem The CPM Server received five or more negative acknowledgements (NAKs) when communicating with the financial processor. Line noise, improperly configured or malfunctioning communications hardware, or improperly connected cabling can cause this error. Verify the following: The communications hardware is properly configured. The communication lines for the type of network are reliable. Correct any network configuration problems in the CPM Server and on the server hosting the CPM Server. If the errors continue, contact CyberSource Customer Support and your financial processor MSG_LOST_DATABASE_CONNECTION Definition CPM lost its connection to the database. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM lost its connection to the database. Check the connection to the database using the CPM Database Utility. If the connection is successful, restart the CPM Server. If CPM Database Utility cannot connect to the database and the CPM cannot reconnect to the database after restart, check the connection to the database. CPM Messages and Processor Codes CyberSource Corporation March

21 Chapter 3 CPM Server Error Messages CPM Server Errors If the connection cannot be established, verify that the network is operating properly. If the network is operating properly, verify your database server is operation properly CHANNEL_MGR_RECEIVED_A_BAD_IP_ADDRESS Definition The CPM Server channel manager received a bad IP address. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server cannot connect to your processor over a network TCP/IP connection. This problem could occur for the following reasons: Either your network or the financial processor s network is down. The TCP/IP address you used to configure the CPM Server is not valid. Restart the CPM Server. Obtain the correct TCP/IP address and port number from your financial processor and enter this information into the CPM Server in the CPM Administration Client if necessary NO_CONNECTION_DEVICE_DLLS_AVAILABLE Definition No connection device DLLs available or connection device DLLs failed to load. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server failed to load a communication library. Check the CPM Error Log. If many of these messages were written during a short period of time, check your database to see if transactions were being submitted to the financial processor at the same time. If not, contact CyberSource Customer Support FAILED_TO_UNLOAD_DLL Definition The CPM Server failed to unload DLL (#). CPM Messages and Processor Codes CyberSource Corporation March

22 Chapter 3 CPM Server Error Messages CPM Server Errors Problem When the CPM Server was shut down, it could not unload a communication DLL. If the errors continue, contact CyberSource Customer Support MSG_PARTIAL_MESSAGE_RECEIVED Definition A partial message was received from your financial processor. Problem CPM received an incomplete response from the financial processor for a transaction in the waiting queue. Resend the transaction. If the errors continue, contact CyberSource Customer Support and your financial processor MSG_TX_NOT_UNIFIED_WARNING Definition The CPM Server received a transaction response that couldn't be connected to a particular transaction request. Problem The CPM Server received a response from the financial processor that failed to correspond to any transactions in the waiting queue. If the errors continue, contact CyberSource Customer Support MSG_ACK_NOT_UNIFIED_WARNING Definition An unknown transaction was acknowledged. Problem The financial processor returned an acknowledgement that failed to correspond to any transactions in the waiting queue. If the errors continue, contact CyberSource Customer Support. CPM Messages and Processor Codes CyberSource Corporation March

23 Chapter 3 CPM Server Error Messages CPM Server Errors 1017 MSG_MERCHANT_COUNTER_NOT_FOUND_WARNING Definition Transaction returned that could not be unified with a merchant counter. Problem The CPM Server received a response from the financial processor that failed to correspond to a merchant on the CPM Server. Check the merchant information in the CPM Error Log against the merchant information configured on the CPM Server. Contact CyberSource Customer Support if you find any problems MSG_TX_NOT_SETTLED_NOT_IN_DB_WARNING Definition Transaction not settled because it could not be found in the database. Problem The CPM Server could not settle a captured transaction in the queue because the database record corresponding to that sequence number was not found. Make sure the CPM Server is running. Verify that a transaction with that sequence number actually exists using the lookup function through the CPM API or a database SQL query. Contact CyberSource Customer Support if you find any problems MSG_TX_NOT_SETTLED_MULTIPLE_SEQ_NUMBER Definition A transaction did not settle because multiple transactions with the same sequence number were found. Problem The CPM Server could not settle a captured transaction in the queue because multiple database records corresponding to that same sequence number exist in the database. Check the database for transactions sharing the same sequence number. CPM Messages and Processor Codes CyberSource Corporation March

24 Chapter 3 CPM Server Error Messages CPM Server Errors If you have multiple CPM Servers accessing the same database, make sure that each server has a unique Server ID. Contact CyberSource Customer Support if you find multiple transactions in the CPM Server database or have other problems MSG_PAYMENTECH_NO_DATA Definition Paymentech sent a No Data response. Batch Number: <batch number> Problem Paymentech did not receive a settlement batch for processing. A network error or other interruption may have caused Paymentech to be receive the settlement batch in part or not at all. The CPM Server will resend the settlement batch at the next settlement event. If problems persist, verify that the network is operating properly. If you have multiple CPM Servers accessing the same database, make sure that each server has a unique Server ID. Contact Paymentech and CyberSource Customer Support if you have problems MSG_BATCH_NOT_SETTLED_NO_LPC Definition A settlement batch was not settled for the merchant because no Gateway was found or enabled. Problem The CPM Server could not settle a settlement batch because it either could not find the correct Gateway or the Gateway was not enabled on the CPM Server. Open the CPM Administration Client and make sure that the Gateway exists or make sure it is enabled. If the Gateway was enabled when authorizations and captures were performed but the Gateway is now disabled or does not exist, this will generate orphaned transactions. Contact CyberSource Customer Support. CPM Messages and Processor Codes CyberSource Corporation March

25 Chapter 3 CPM Server Error Messages CPM Server Errors 1022 MSG_SERVER_SETTLEMENT_WARNING Definition Settlement could not proceed for a CPM Server. Problem The CPM Server was unable to initiate or complete a settlement event. The CPM Server was unable to process a settlement batch. The CPM Server will try to process the settlement batch at the next settlement event. If errors persist, verify the following: If the merchant and network connection information are set up properly, contact your financial processor and verify you have the correct merchant and network connection information MSG_TX_INITIALIZATION_FAILED Definition CPM was unable to read from the Windows registry at startup. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server was unable to read from the Windows registry. Restart Windows. Uninstall, then reinstall CPM. If the errors continue, there may be a fault with the installation instance of Windows. Either verify the reliability of the Windows installation and the hard disk on which Windows is running or install CPM on another Windows server MSG_NO_LPCS_ENABLED Definition No Gateways are enabled. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem This error occurs when a transaction is attempted by a merchant without an enabled Gateway. CPM Messages and Processor Codes CyberSource Corporation March

26 Chapter 3 CPM Server Error Messages CPM Server Errors Verify that the appropriate Gateway is enabled and properly configured in the Gateway Instances tab in the CPM Administration Client. If the Gateway is enabled and configured, restart the CPM Server. If the Gateway name does not appear in the Gateway Instances tab in the Administration Client, your CPM license key may be missing or incorrectly configured. Re-enter the license key and restart the CPM Server. The Gateway you purchased with CPM should then appear in the Gateway Instances tab in the CPM Administration Client. Contact CyberSource Customer Support for a new license key with the correct options for your CPM Server. If the errors continue, there may be a problem with the installation instance of the operating system. Either verify the reliability of the operating system installation and hard disk on which the operating system is running or use another server MSG_COULD_NOT_INITIATE_SIGNON Definition No sign on response from processor. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem When the Gateway was attempting to connect to the financial processor, no signon response was received from the financial processor and a connection was not established. Verify that merchant and network connection information is set up correctly in the CPM Administration Client. If the merchant and network connection information are set up properly, contact your financial processor and verify you have the correct merchant and network connection information. Verify that the server network configuration and your network infrastructure are operating properly MSG_COULD_NOT_INITIATE_SIGNOFF Definition No sign off response from processor. CPM Messages and Processor Codes CyberSource Corporation March

27 Chapter 3 CPM Server Error Messages CPM Server Errors Problem When the Gateway was disconnecting from the financial processor, no response was received from the financial processor and the connection could not be closed. Verify that merchant and network connection information is set up correctly in the CPM Administration Client. If the merchant and network connection information are set up properly, contact your financial processor and verify you have the correct merchant and network connection information. Verify that the server network configuration and your network infrastructure are operating properly MSG_CURRENT_PAYMENT_PROCESSOR_HOST Definition The connection to financial processor switched to back-up connection. Problem For Gateways that offer a back up connection to the financial processor, this error is generated when ever the Gateway must switch to the alternate connection. This message is informational only and does not require any action. If the errors continue and the CPM Server switches network connection frequently, verify the proper operation of your network infrastructure and the connection to the financial processor. You may want to consult with your network provider and your financial processor to clear any network problems. For further assistance, contact CyberSource Customer Support MSG_PARTIAL_MSG_AND_NAK_COUNT_EXCEEDED Definition A message less than the required size has been received and the NAK (negative acknowledgement) count is exceeded. Problem Two errors are occurring. At settlement batch response, the CPM Server received a message and a negative acknowledgement. If the CPM receives this error three or more times in a settlement response, the error is written to the CPM Error Log. A corresponding settlement batch error is also written to the event viewer indicating the settlement batch state. CPM Messages and Processor Codes CyberSource Corporation March

28 Chapter 3 CPM Server Error Messages CPM Server Errors CPM continues to try and settle the settlement batch every five minutes after the error is recorded. If the error persists for more than 24 hours, verify that the network is operating properly. Consult with your network provider and your financial processor to clear any network problems. If the same error is written to the CPM Error Log for more than 48 hours, contact CyberSource Customer Support MSG_UNABLE_TO_OPEN_CWND_FOR_SCHEDULER Definition Unable to open the Windows scheduler. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM cannot allocate the necessary resources needed to run. Restart the CPM Server. If you receive the same message at restart, reinstall CPM MSG_STARTSERVICECTRLDISPATCHER_FAILED Definition The Start Server Control Dispatcher failed to initialize. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM could not initialize the CPM Service Control Manager. Restart the CPM Server. If you receive the same message at restart, reinstall CPM MSG_SETSERVICESTATUS_FAILED Definition The Set Service Status failed to initialize. Type of error Catastrophic. CPM cannot operate until this problem is solved. CPM Messages and Processor Codes CyberSource Corporation March

29 Chapter 3 CPM Server Error Messages CPM Server Errors Problem The CPM Server and CPM Service Control Manager cannot communicate with each other. Restart the CPM Server. If you receive the same message at startup, reinstall CPM MSG_CREATE_EVENT_FAILED Definition The Create Event failed to initialize. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The CPM Server service cannot run because it cannot allocate an event through the operating system. Restart the CPM Server. If you receive the same message at startup, reinstall CPM MSG_LOGIN_FAILED Definition Unable to login to the database. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM is unable to login to the database through the specified ODBC datasource. There can be several causes for this problem. Check your login configuration in the CPM Administration Client s Server Properties. Verify that the ODBC data source points to the correct database and that the database contains current CPM tables using database tables. Verify proper network operation. Check the state of the database through a separate SQL database client application. CPM Messages and Processor Codes CyberSource Corporation March

30 Chapter 3 CPM Server Error Messages CPM Server Errors When you have determined the cause of the problem, restart the CPM Server MSG_STORE_FAILED_SQL_STMT_FAILED Definition Unable to store failed SQL statements. Problem CPM was unable to store a transaction in the save queue during a runtime database connection drop. None required. If CPM detects a dropped database connection, it will queue transactions in a flat file while at the same time attempting to restore the database connection. Resolution to this problem depends on the message entered into the CPM Error Log. If the errors continue, verify that the database connection is set up properly between the CPM and the CPM database MSG_INSERT_FAILED_SQL_STMT_FAILED Definition Unable to restore failed SQL statements. Problem CPM was unable to update the database with queued transactions stored in the flat file after the database connection was lost. When CPM restores the database connection, it will attempt to flush the transaction queue held in the flat file. The error may indicate either an embedded syntax error in one of the transaction statements being flushed from the flat file or an environmental or ODBC management issue. Resolution of this problem depends on the message entered in the CPM Error Log associated with this error MSG_UNABLE_TO_OPEN_COM_PORT Definition Unable to open a port for serial communications. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM was unable to reserve the specified COM port for its use. CPM Messages and Processor Codes CyberSource Corporation March

31 Chapter 3 CPM Server Error Messages CPM Server Errors Verify the COM port is not reserved by another application. Restart the CPM Server MSG_BATCH_TX_ERROR Definition CPM was unable to send a settlement batch to the financial processor because the settlement batch resource limit was reached. This can occur when the financial processor is experiencing a peak in transaction volume. It may not be possible to successfully settle any settlement batches during this period. Problem The settlement batch was not sent completely or returned completely in echo. Call your financial processor for instructions on recovering a failed settlement batch. Use the Recover Settlement Errors function in the CPM Administration Client. Consider changing your settlement times to avoid peak periods MSG_SQL_EXECUTE_ERROR Definition Database SQL execute error. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM attempted to write a transaction to the database but failed due to a SQL error. Check the CPM Error Log and write down the error message exactly as it appears. Contact CyberSource Customer Support MSG_SIZE_PARAMETER_ERROR Definition Cannot read the database size parameter. Type of error Catastrophic. CPM cannot operate until this problem is solved. CPM Messages and Processor Codes CyberSource Corporation March

32 Chapter 3 CPM Server Error Messages CPM Server Errors Problem CPM cannot read a database size parameter. Without this parameter, CPM cannot read any information stored in the database. Because each database is different, there is no set solution. Contact CyberSource Customer Support MSG_WINSOCK_ERROR Definition Failure to start the WinSock subsystem. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem CPM was unable to initialize the Windows Sockets layer of the operating system. This occurs when the TCP/IP protocol stack on the Windows server hosting the CPM Server is configured incorrectly, corrupt, or missing. Restart the CPM Server. Restart the Windows server. Contact your network administrator to diagnose the problem TCP/IP configuration in Windows MSG_CREATE_SOCKET_ERROR Definition Failure to create server socket. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem During initialization, the CPM Server was unable to create the socket for client use. Check the proper installation of WinSock components. If they are correct, restart the CPM Server MSG_LOST_DATABASE_CONNECTION_ERROR Definition CPM lost connection to the database. CPM Messages and Processor Codes CyberSource Corporation March

33 Chapter 3 CPM Server Error Messages CPM Server Errors Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The ODBC datasource reported an error that corresponds to a dropped connection. Wait several minutes, then try to reconnect to the database. Verify that the network is operating properly. Verify that the computer hosting the database is operating properly. Verify that the database server is operating properly MSG_CANT_INSERT_FAILED_SQLSTMT_FILE_ERROR Definition The database could not store a failed SQL statement or statements. Problem As the CPM Server began the process of restoring failed SQL statements to the database, an error occurred. One potential cause for this error is a full database. When the CPM Server loses the connection to the database, it caches the data in transit between the database and the server. As the database began the process of restoring the SQL statements, an error occurred. Look at the error code generated in the Windows Event Log and the CPM Error Log. Write down the specific error message, not just the code Refer to your database server documentation to determine how to correct the error. After correcting the error, restart the CPM Server MSG_INVALID_OR_EXPIRED_LICENSE_ERROR Definition The CPM license key is invalid or expired. Type of error Catastrophic. CPM cannot operate until this problem is solved. Problem The license key for this Gateway has expired. The CPM Server will not process any new transactions without a valid license key. CPM Messages and Processor Codes CyberSource Corporation March