CyberSource Payment Manager 6.5 SP2

CyberSource Payment Manager 6.5 SP2 Messages and Processor Codes November 2012 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095

CyberSource Contact Information For general information about our company, products, and services, go to http://www.cybersource.com. For sales questions about any CyberSource Service, email sales@cybersource.com or call 650-432-7350 or 888-330-2300 (toll free in the United States). For support information about any CyberSource Service, visit the Support Center at http://www.cybersource.com/support. Copyright 2012 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 be 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 252.227-7013 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 52.227-19 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 Power of Payment, CyberSource Payment Manager, CyberSource Risk Manager, CyberSource Decision Manager, CyberSource Connect, Authorize.Net, and ECheck.net are trademarks and/or service marks of CyberSource Corporation. All other brands and product names are trademarks or registered trademarks of their respective owners. 2

Contents CONTENTS Documentation Changes and Enhancements 8 Chapter 1 Introduction 9 Introducing CPM 9 CPM Components 10 CPM Architecture 11 CPM Errors 12 CPM API Errors 12 CPM Server Errors 12 Chapter 2 Batch Status Values 13 Chapter 3 CPM Server Error Messages 15 CPM Error Message Severity 15 CPM Server Errors 16 (NULL) 16 1001 MSG_DATABASE_SIZE_WARNING 17 1002 MSG_START_DBUTIL_FAILED_WARNING 17 1003 MSG_INVALID_MERCHANT_STORE_WARNING 18 1004 MSG_NO_SEND_WARNING 19 1005 MSG_NOT_CREATE_WARNING 20 1006 MSG_WRITING_WARNING 20 1007 MSG_READING_WARNING 21 1008 MSG_FIVE_ACK_WARNING 22 1009 MSG_FIVE_NACK_WARNING 23 1010 MSG_LOST_DATABASE_CONNECTION 24 1011 CHANNEL_MGR_RECEIVED_A_BAD_IP_ADDRESS 25 1012 NO_CONNECTION_DEVICE_DLLS_AVAILABLE 26 1013 FAILED_TO_UNLOAD_DLL 26 1014 MSG_PARTIAL_MESSAGE_RECEIVED 27 1015 MSG_TX_NOT_UNIFIED_WARNING 27 1016 MSG_ACK_NOT_UNIFIED_WARNING 28 CPM Messages and Processor Codes November 2012 3

Contents 1017 MSG_MERCHANT_COUNTER_NOT_FOUND_WARNING 28 1018 MSG_TX_NOT_SETTLED_NOT_IN_DB_WARNING 29 1019 MSG_TX_NOT_SETTLED_MULTIPLE_SEQ_NUMBER 29 1020 MSG_PAYMENTECH_NO_DATA 30 1021 MSG_BATCH_NOT_SETTLED_NO_LPC 30 1022 MSG_SERVER_SETTLEMENT_WARNING 31 2000 MSG_TX_INITIALIZATION_FAILED 31 2001 MSG_NO_LPCS_ENABLED 32 2002 MSG_COULD_NOT_INITIATE_SIGNON 33 2003 MSG_COULD_NOT_INITIATE_SIGNOFF 34 2004 MSG_CURRENT_PAYMENT_PROCESSOR_HOST 34 2005 MSG_PARTIAL_MSG_AND_NAK_COUNT_EXCEEDED 35 5001 MSG_UNABLE_TO_OPEN_CWND_FOR_SCHEDULER 36 5002 MSG_STARTSERVICECTRLDISPATCHER_FAILED 36 5003 MSG_SETSERVICESTATUS_FAILED 37 5004 MSG_CREATE_EVENT_FAILED 37 5005 MSG_LOGIN_FAILED 38 5006 MSG_STORE_FAILED_SQL_STMT_FAILED 38 5007 MSG_INSERT_FAILED_SQL_STMT_FAILED 39 5008 MSG_UNABLE_TO_OPEN_COM_PORT 39 5009 MSG_BATCH_TX_ERROR 40 5010 MSG_SQL_EXECUTE_ERROR 40 5011 MSG_SIZE_PARAMETER_ERROR 41 5012 MSG_WINSOCK_ERROR 41 5013 MSG_CREATE_SOCKET_ERROR 42 5015 MSG_LOST_DATABASE_CONNECTION_ERROR 42 5016 MSG_CANT_INSERT_FAILED_SQLSTMT_FILE_ERROR 43 5017 MSG_INVALID_OR_EXPIRED_LICENSE_ERROR 43 5018 MSG_EXCEEDED_MERCHANT_LIMIT_ERROR 44 5019 MSG_OUT_OF_MEMORY 44 5020 MSG_SQL_ERROR 45 5021 MSG_DATABASE_CONNECT_FAILURE_ERROR 45 5022 MSG_UNKNOWN_MESSAGE_RECEIVED 46 5023 MSG_CANT_READ_BATCH_ERROR 46 5024 MSG_BATCH_HEADER_TRAILER_ERROR 47 5025 MSG_UNABLE_TO_CONNECT_TO_PROCESSOR 47 5026 MSG_BATCH_FAILED_DUE_TO_CONNECTION_CLOSE 48 5027 MSG_BATCH_PROCESSING_ERROR 48 5028 MSG_CHANNEL_DEVICE_CONFIG_ERROR 49 5029 MSG_CREATE_SOCKET_WND_ERROR 49 5030 MSG_SSL_INIT_ERROR 50 5031 MSG_SSL_NEG_ERROR 50 5032 MSG_TXBCONV_ERROR 51 5033 MSG_NBTXCONV_ERROR 51 5034 MSG_DATABASE_TABLES_NOT_EXIST_ERROR 52 CPM Messages and Processor Codes November 2012 4

Contents 5035 MSG_BATCH_DISK_FILE_OPEN_ERROR 52 5036 MSG_BATCH_DISK_FILE_WRITE_ERROR 53 5037 MSG_BATCH_DISK_FILE_FTP_ERROR 53 5038 MSG_BATCH_DISK_FILE_CLOSE_ERROR 54 5039 MSG_BATCH_JOB_CARDS_FILE_OPEN_ERROR 54 5040 MSG_BATCH_JOB_CARDS_FILE_CLOSE_ERROR 55 5041 MSG_PIPELINE_COMPONENT_FAILED_TO_START 55 5042 MSG_FRAUD_CONNECT_INFO_MISSING 56 5043 MSG_FRAUD_CHANNEL_START_FAIL 56 5044 MSG_FRAUD_CONNECTION_FAIL 57 5045 MSG_FRAUD_CONNECTION_LOST 57 5046 MSG_FRAUD_DEVICE_FAIL 58 5047 MSG_DATABASE_TABLES_INCORRECT_VERSION_ERROR 58 5048 MSG_BATCH_SETTLEMENT_ERROR 59 5049 MSG_BATCH_SETTLMENT_TIMEOUT 59 5050 MSG_BATCH_SETTLMENT_UKNOWN_STATE 60 5051 MSG_SETTLE_RESPONSE_ERR 60 5052 MSG_FAILED_TO_SEND 61 5053 MSG_CLEAR_ERROR_TO_CONTINUE_SETTLEMENT 61 5054 MSG_BATCH_OUT_OF_BALANCE 62 5055 MSG_BATCH_REJECTED_BY_HOST 62 5056 MSG_DB_ENCRYPTION_KEY_FILE_MISSING 63 5057 MSG_HTTP_SSL_COMMUNICATIONS_ERROR 63 5058 MSG_MERCHANT_CONFIGURATION_ERROR 64 5059 MSG_NULL_POINTER_TO_BATCH_STRUCTURE 64 5060 MSG_BATCH_NUMBER_OUT_OF_SEQUENCE 65 5061 MSG_SERVER_SETTLEMENT_ERROR 66 5062 MSG_MERCHANT_SETTLEMENT_ERROR 67 5063 MSG_COULD_NOT_UPDATE_MERCHANT_STATE 68 5064 MSG_SETTLEMENT_GATEWAY 68 Chapter 4 CPM API Error Messages 69 Negative Numbered CPM API Errors 70-114 ERR_MISSING_CONNECTION_INFO 70-113 ERR_MERCHANT_NOT_SPECIFIED 71-112 ERR_CONFIG_BAD_ENTRY 71-111 ERR_CONFIG_LOOKUP_FAILED 72-110 ERR_CONFIG_OPEN_FAILED 73-105 ERR_OPEN_DEBUG_FILE 74-104 ERR_VALUE_TOO_LARGE 75-103 ERR_VALUE_NOT_FOUND 75-102 ERR_CONNECTION_INVALID 76-101 ERR_INVALID_HANDLE 76 CPM Messages and Processor Codes November 2012 5

Contents -100 ERR_NOT_INITIALIZED 77-20 ERR_SSL_GENERAL 78-19 ERR_SSL_NEG 79-18 ERR_SSL_LIB_INIT 80-17 ERR_ENCRYPTION_FAILED 81-16 ERR_SOCK_READ 82-15 ERR_SOCK_WRITE 83-14 ERR_SOCK_CONN_REFUSED 84-13 ERR_SOCK_CONNECT 85-12 ERR_SOCK_CREATE 86-10 ERR_SOCK_LIB_INIT 87 Positive Numbered CPM API Errors 88 0 Success 88 11 ERR_NOT_ACCEPTING_TX 89 13 ERR_INVALID_FIELD_25_NO_MAP 90 30 ERR_TRANSACTION_TYPE 90 101 ERR_INVALID_FIELD 91 102 ERR_FIELD_TOO_LONG 91 107 ERR_BATCH_GROUP_DRAFT_ID_EXISTS 92 109 ERR_OUT_OF_MEMORY_BUFFERS 92 110 ERR_OUT_OF_MEMORY_HEAP 93 135 ERR_COULD_NOT_CONNECT_PROCESSOR 93 136 ERR_TIME_OUT 94 137 ERR_UNIDENTIFIABLE 94 138 ERR_INVALID_FIELD_VALUE 95 139 ERR_INVALID_DATA_TYPE 95 141 ERR_INVALID_RECORD_SEQUENCE 96 142 ERR_INVALID_MERCHANT_CONFIGURATION 96 143 ERR_CC_MOP_MISMATCH 97 144 ERR_INVALID_MOP_FOR_DIVISION 98 145 ERR_INVALID_TRANSACTION_TYPE 98 146 ERR_DUPLICATE_PURCHASE_IDENTIFIER 99 200 ERR_UNKNOWN 99 230 ERR_LOOKUP_NO_RECORDS_FOUND 100 231 ERR_MULTIPLE_RECORDS_FOUND 100 232 ERR_VOID_FAILED_TX_SETTLED 101 233 ERR_VOID_FAILED_TX_NOT_FOUND 101 234 ERR_SEQUENCE_NUMBER_LOOKUP_TIMEOUT 102 235 ERR_HTTP_SSL_COMMUNICATIONS_FAILURE 103 236 ERR_LOOKUP_FIELD_NOT_SET 103 237 ERR_LOOKUP_ENCYRPTED_ACCOUNT_NUMBER 104 1000 ERR_SERVICE_NEED_TCB_PRIV 104 1001 ERR_INVALID_USERNAME_PASSWORD 105 1002 ERR_SESSION_INVALID 105 1003 ERR_SESSION_TIMEOUT 106 CPM Messages and Processor Codes November 2012 6

Contents 1004 ERR_SESSION_SOURCE_INVALID 106 1005 ERR_INVALID_MERCHANT_ID 107 1006 ERR_SESSION_ACCESS_DENIED 107 1007 ERR_CREATE_SESSION_FAILURE 108 1008 ERR_SESSION_AMOUNT_LIMIT_REACHED 108 1009 ERR_SESSION_RETURN_AMOUNT_LIMIT_REACHED 109 1010 ERR_LICENSE_KEY_VIOLATION 109 1011 ERR_DATABASE_LOG_FAILURE 110 1012 ERR_DUPLICATE_TRANSACTION_CHECK 110 1013 ERR_FRAUD_CHECK 111 1014 ERR_FRAUD_TIMEOUT 111 1015 ERR_VOID_TX_FAILURE 112 1016 ERR_NO_GATEWAY_AVAILABLE 112 1017 ERR_GATEWAY_NOT_ENABLED 113 1018 ERR_TX_NOT_VOIDABLE 113 1019 ERR_INVALID_MERCHANT_STATE_AUTH 114 Invalid Field Messages for FDMS South Debit 115 Messages Received for Authorization and Capture 115 Messages Received for Reversal 116 Chapter 5 Financial Processor Return Codes 117 Authorization Response Codes 117 AVS Response Codes 122 Visa RED Regulations for AVS 122 AVS Response Codes: Address 123 AVS Response Codes: Postal Code 124 AVS Response Codes: Name, Phone, and Email Match 126 CVV Result Codes 126 CPM Messages and Processor Codes November 2012 7

Documentation Changes and Enhancements REVISIONS The following table lists changes made in recent releases of this document: Release Changes 6.5.2 Update version to 6.5.2. 6.5.1 Update version to 6.5.1. 6.4.7 Updated to CPM 6.4 SP7. Added new authorization response codes to American Express gateway. See Table 8, page 118. 6.4.6 Updated to CPM 6.4 SP6. Added new authorization response codes to FTPS gateway. See Table 8, page 118. 6.4 Added the RBS WorldPay, Inc.Gateway Added new authorization response codes for Paymentech New Hampshire and Global Payments. See Table 8, page 118. 6.3.3 Updated the CPM version number to 6.3.3. Added new authorization response codes for Paymentech New Hampshire. See Table 8, page 118. 6.3 Updated the CPM version to 6.3. For Paymentech New Hampshire: Added new AVS response codes. See "AVS Response Codes: Address," page 123 and "AVS Response Codes: Postal Code," page 124. Added new authorization response codes. See "Authorization Response Codes," page 117. 6.2.5 Updated the CPM version to 6.2.5. 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, page 118. Updated the AVS response codes for FTPS. See Table 10, page 123 and Table 12, page 125. 6.2.4 Updated the CPM version number to 6.2.4. 6.2.3 Updated the CPM version number to 6.2.3. Updated the AVS response codes for American Express Phoenix and Vital. See Table 10, page 123 and Table 11, page 124. CPM Messages and Processor Codes November 2012 8

Introduction CHAPTER 1 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, RBS Worldpay SSL, 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 November 2012 9

Chapter 1 Introduction 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 November 2012 10

Chapter 1 Introduction 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 November 2012 11

Chapter 1 Introduction 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 November 2012 12

Batch Status Values CHAPTER 2 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, RBS Worldpay SSL, 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 November 2012 13

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 05. 06 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 November 2012 14

CPM Server Error Messages CHAPTER 3 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 November 2012 15

Chapter 3 CPM Server Error Messages CPM Server Errors (NULL) 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. Message. This message is informational only and can only be viewed in the CC_ TRANSACTION table of the CPM database. 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. CPM Messages and Processor Codes November 2012 16

Chapter 3 CPM Server Error Messages 1001 MSG_DATABASE_SIZE_WARNING The CPM database has reached the age/volume warning levels you have set. Runtime. 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. Generate a transaction activity report before purging the CPM database. Note 1002 MSG_START_DBUTIL_FAILED_WARNING Could not cmsg_vital_http_ssl_communications_error reate database utility. Reason: <reason> Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 17

Chapter 3 CPM Server Error Messages 1003 MSG_INVALID_MERCHANT_STORE_WARNING The CPM Server received an invalid merchant/store number combination. Runtime. 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. CPM Messages and Processor Codes November 2012 18

Chapter 3 CPM Server Error Messages 1004 MSG_NO_SEND_WARNING 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. Runtime. 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 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. CPM Messages and Processor Codes November 2012 19

Chapter 3 CPM Server Error Messages 1005 MSG_NOT_CREATE_WARNING CPM is unable to establish a connection to the CPM API client. Catastrophic. CPM cannot operate until this problem is solved. 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. 1006 MSG_WRITING_WARNING The CPM Server could not write to the TCP/IP socket. Catastrophic. CPM cannot operate until this problem is solved. The CPM Server cannot write data to the TCP/IP port used to communicate with 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. CPM Messages and Processor Codes November 2012 20

Chapter 3 CPM Server Error Messages 1007 MSG_READING_WARNING The CPM Server could not read from the TCP/IP socket. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 21

Chapter 3 CPM Server Error Messages 1008 MSG_FIVE_ACK_WARNING The CPM Server received five acknowledgements when trying to communicate with the financial processor. Runtime. If the error persists, the error is catastrophic and the CPM cannot operate until this problem is solved. 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. 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. CPM Messages and Processor Codes November 2012 22

Chapter 3 CPM Server Error Messages 1009 MSG_FIVE_NACK_WARNING The CPM Server received five negative acknowledgements when trying to communicate with the financial processor. Runtime. If the error persists, the error is catastrophic and the CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 23

Chapter 3 CPM Server Error Messages 1010 MSG_LOST_DATABASE_CONNECTION CPM lost its connection to the database. Catastrophic. CPM cannot operate until this problem is solved. 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. 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. CPM Messages and Processor Codes November 2012 24

Chapter 3 CPM Server Error Messages 1011 CHANNEL_MGR_RECEIVED_A_BAD_IP_ ADDRESS The CPM Server channel manager received a bad IP address. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 25

Chapter 3 CPM Server Error Messages 1012 NO_CONNECTION_DEVICE_DLLS_AVAILABLE No connection device DLLs available or connection device DLLs failed to load. Catastrophic. CPM cannot operate until this problem is solved. 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. 1013 FAILED_TO_UNLOAD_DLL The CPM Server failed to unload DLL (#). Runtime. When the CPM Server was shut down, it could not unload a communication DLL. If the errors continue, contact CyberSource Customer Support. CPM Messages and Processor Codes November 2012 26

Chapter 3 CPM Server Error Messages 1014 MSG_PARTIAL_MESSAGE_RECEIVED A partial message was received from your financial processor. Runtime. 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. 1015 MSG_TX_NOT_UNIFIED_WARNING The CPM Server received a transaction response that couldn't be connected to a particular transaction request. Runtime. 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. CPM Messages and Processor Codes November 2012 27

Chapter 3 CPM Server Error Messages 1016 MSG_ACK_NOT_UNIFIED_WARNING An unknown transaction was acknowledged. Runtime. 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. 1017 MSG_MERCHANT_COUNTER_NOT_FOUND_ WARNING Transaction returned that could not be unified with a merchant counter. Runtime. 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. CPM Messages and Processor Codes November 2012 28

Chapter 3 CPM Server Error Messages 1018 MSG_TX_NOT_SETTLED_NOT_IN_DB_WARNING Transaction not settled because it could not be found in the database. Runtime. 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. 1019 MSG_TX_NOT_SETTLED_MULTIPLE_SEQ_ NUMBER A transaction did not settle because multiple transactions with the same sequence number were found. Runtime. 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. 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. CPM Messages and Processor Codes November 2012 29

Chapter 3 CPM Server Error Messages 1020 MSG_PAYMENTECH_NO_DATA Paymentech sent a No Data response. Batch Number: <batch number> Runtime. 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. 1021 MSG_BATCH_NOT_SETTLED_NO_LPC A settlement batch was not settled for the merchant because no Gateway was found or enabled. Runtime. 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 November 2012 30

Chapter 3 CPM Server Error Messages 1022 MSG_SERVER_SETTLEMENT_WARNING Settlement could not proceed for a CPM Server. Runtime. 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. 2000 MSG_TX_INITIALIZATION_FAILED CPM was unable to read from the Windows registry at startup. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 31

Chapter 3 CPM Server Error Messages 2001 MSG_NO_LPCS_ENABLED No Gateways are enabled. Catastrophic. CPM cannot operate until this problem is solved. This error occurs when a transaction is attempted by a merchant without an enabled Gateway. 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. CPM Messages and Processor Codes November 2012 32

Chapter 3 CPM Server Error Messages 2002 MSG_COULD_NOT_INITIATE_SIGNON No sign on response from processor. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 33

Chapter 3 CPM Server Error Messages 2003 MSG_COULD_NOT_INITIATE_SIGNOFF No sign off response from processor. Runtime. 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. 2004 MSG_CURRENT_PAYMENT_PROCESSOR_HOST The connection to financial processor switched to back-up connection. Runtime. 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. CPM Messages and Processor Codes November 2012 34

Chapter 3 CPM Server Error Messages 2005 MSG_PARTIAL_MSG_AND_NAK_COUNT_ EXCEEDED A message less than the required size has been received and the NAK (negative acknowledgement) count is exceeded. Runtime. 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 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. CPM Messages and Processor Codes November 2012 35

Chapter 3 CPM Server Error Messages 5001 MSG_UNABLE_TO_OPEN_CWND_FOR_ SCHEDULER Unable to open the Windows scheduler. Catastrophic. CPM cannot operate until this problem is solved. CPM cannot allocate the necessary resources needed to run. Restart the CPM Server. If you receive the same message at restart, reinstall CPM. 5002 MSG_STARTSERVICECTRLDISPATCHER_FAILED The Start Server Control Dispatcher failed to initialize. Catastrophic. CPM cannot operate until this problem is solved. CPM could not initialize the CPM Service Control Manager. Restart the CPM Server. If you receive the same message at restart, reinstall CPM. CPM Messages and Processor Codes November 2012 36

Chapter 3 CPM Server Error Messages 5003 MSG_SETSERVICESTATUS_FAILED The Set Service Status failed to initialize. Catastrophic. CPM cannot operate until this problem is solved. 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. 5004 MSG_CREATE_EVENT_FAILED The Create Event failed to initialize. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 37

Chapter 3 CPM Server Error Messages 5005 MSG_LOGIN_FAILED Unable to login to the database. Catastrophic. CPM cannot operate until this problem is solved. 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. When you have determined the cause of the problem, restart the CPM Server. 5006 MSG_STORE_FAILED_SQL_STMT_FAILED Unable to store failed SQL statements. Runtime. 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. CPM Messages and Processor Codes November 2012 38

Chapter 3 CPM Server Error Messages 5007 MSG_INSERT_FAILED_SQL_STMT_FAILED Unable to restore failed SQL statements. Runtime. 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. 5008 MSG_UNABLE_TO_OPEN_COM_PORT Unable to open a port for serial communications. Catastrophic. CPM cannot operate until this problem is solved. CPM was unable to reserve the specified COM port for its use. Verify the COM port is not reserved by another application. Restart the CPM Server. CPM Messages and Processor Codes November 2012 39

Chapter 3 CPM Server Error Messages 5009 MSG_BATCH_TX_ERROR 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. Runtime. 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. 5010 MSG_SQL_EXECUTE_ERROR Database SQL execute error. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 40

Chapter 3 CPM Server Error Messages 5011 MSG_SIZE_PARAMETER_ERROR Cannot read the database size parameter. Catastrophic. CPM cannot operate until this problem is solved. 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. 5012 MSG_WINSOCK_ERROR Failure to start the WinSock subsystem. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 41

Chapter 3 CPM Server Error Messages 5013 MSG_CREATE_SOCKET_ERROR Failure to create server socket. Catastrophic. CPM cannot operate until this problem is solved. 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. 5015 MSG_LOST_DATABASE_CONNECTION_ERROR CPM lost connection to the database. Catastrophic. CPM cannot operate until this problem is solved. 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. CPM Messages and Processor Codes November 2012 42

Chapter 3 CPM Server Error Messages 5016 MSG_CANT_INSERT_FAILED_SQLSTMT_FILE_ ERROR The database could not store a failed SQL statement or statements. Runtime. 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 5016. Refer to your database server documentation to determine how to correct the error. After correcting the error, restart the CPM Server. 5017 MSG_INVALID_OR_EXPIRED_LICENSE_ERROR The CPM license key is invalid or expired. Catastrophic. CPM cannot operate until this problem is solved. The license key for this Gateway has expired. The CPM Server will not process any new transactions without a valid license key. Contact your CPM sales representative to acquire a new key. CPM Messages and Processor Codes November 2012 43

Chapter 3 CPM Server Error Messages 5018 MSG_EXCEEDED_MERCHANT_LIMIT_ERROR CPM licensed merchant limit is exceeded. Only the first merchants will be activated. Runtime. More merchants were configured than are supported in the current CPM license key. Contact your CPM sales representative to purchase a CPM license key that allows additional merchants to be set up on the CPM Server. 5019 MSG_OUT_OF_MEMORY The CPM Server is out of memory. Runtime. CPM Server could not initialize because there are not enough system resources. Make sure that your system meets the CPM minimum operating requirements. Use the Windows Task Manager and Performance Monitor to track system usage and remove any running programs that are taking up CPU resources. CPM Messages and Processor Codes November 2012 44