Error Code Reference

TM
Error Code Reference
Error Codes -1 Through -10
Error numbers -1 through -10 typically do not usually occur after Payment Gateway is
configured and operating properly.
-1 Unable to open file
-2 Can occur when attempting to read an already open file
-3 Error when attempting to seek to a position within an open file
-4 Error when attempting to allocate memory
-5 Invalid tag found in data (audio files, image files, HTTP response, SSL response, etc...)
-7 Requested item not found (executable, config entry...)
-8 Required input or output data is missing
-9 Required parameter missing or invalid parameter specified
-10 Unable to write to a file. Usually low disk space
-11 Error creating subprocess
-12 Response was not received before timeout expired
-13 Invalid data was returned from a remote client
-14 Internal error code indicating that invalid file information was sent to a read or write call
-15 Disk drive hardware failure
-16 Error usually caused by an unexpected error returned by an OS specific API
-17 Invalid Request attempted
-22 Table contains no key entries
-23 No server is connected to transmgr to process the specified transaction
-24 The requested operation is not allowed. Check the trxattrs.txt and clientid.txt files.
-25 A request was made to add a new entry to a table that already contains the requested key.
-26 The client request would exceed the maximum allowed number of requests.
-1300 Series Errors
For users with IP connectivity, reports will display any -1300 series socket-related errors.
Typically, these errors are related to IP or SSL processes. If one of these errors occurs, contact
your network administrator for assistance with the cause of the error.
-1300 General network communications error
-1301 Unable to create a socket resource
-1302 Unable to resolve host name to IP address. Check DNS configuration
-1303 Socket connection not established due to socket not available
-1304 Error writing to socket after established connection
-1305 Error reading from socket after established connection
-1306 Error during socket close. Internal error, usually ignored
-1309 Attempt to listen on a socket already in use. Perform a “netstat –a” to find out
TouchNet Confidential

Error Code Reference
-1310 Socket has not been setup correctly or there are not enough resources available
-1311 Internal error indicating an invalid socket request has been made
-1312 Error occurred during socket read request
-1313 Internal error (not returned to applications)
-1314 Operation attempted on a socket no longer open
-1315 Internal error indicating that a socket operation cannot be completed immediately
-1316 Request made on a connection where other side has closed the connection
-1317 Request was not completed before the maximum time allowed
-1318 A socket setup as a server did not receive a valid connection
-1319 Occurs when waiting for a read or write to occur on a socket and the other side of the
connection is closed
-1351 Internal error caused by fatal ssl error
-1352 Internal error caused by fatal ssl error, or ssl allocation error
-1353 Internal error caused by a random number seeding failure
-1354 Internal error caused by illegal cipher combination requested
-1355 Invalid public key certificate was specified
-1356 Invalid private key was specified
-1357 Unable to connect to remote listener. Can be caused by attempting to connect to a
non-ssl listener.
-1358 Unable to accept connection from the client. Can be caused by the client attempting
a non-ssl connection or by the client rejecting the supplied certificate
-1359 Unable to send data
-1360 Unable to read data
-1361 Unable to read data
-1362 Unable to verify supplied certificate
-1363 Initialization failed for ssl request
-1364 CN certificate value in the server certificate is not the expected value
-1365 OU certificate value in the server certificate is not the expected value
-1366 O certificate value in the server certificate is not the expected value
-1367 L certificate value in the server certificate is not the expected value
-1368 ST certificate value in the server certificate is not the expected value
-1369 C certificate value in the server certificate is not the expected value
-1400 Series Errors
Error codes related to pipe and transaction communications.
-1400 Generic pipe related error
-1401 Attempt to read or write with an improperly initialized pipe object
-1402 Failure during an attempt to read
-1403 Failure during an attempt to write
-1404 The read request aborted when sending output to a file
-1405 An unknown response code sent back from file transfer
-1406 Operation did not complete before the timeout expired
-1407 Transaction returned with a NO_ERROR response but there was a header mismatch
TouchNet Confidential

Error Code Reference
-1408 Pipe closed before the operation completed
-1409 Request made to a pipe that does not have a peer connected to it
-1410 Connection request made to a pipe that already has a peer connected to it
-1411 Request made for a pipe where no more instances are available
-1412 The pipe handle is not valid
-1413 Named pipe creation failed
-1600 Series Errors
Codes beginning with –1600 in the authorization or batch settlement reports indicate
that problems occurred at your credit card processor. The information here is based on
specifications provided by the credit card processor, and is subject to change by the
processor.
-16xx Credit Card processor specific
-1700 Series Errors
Codes beginning with -1700 indicate that Payment Gateway has signaled an error.
-1701 Occurs when a required value was not found in the configuration file. This error
commonly occurs if your current license does not allow an attempted operation, or if
you have added more merchant accounts than your license allows. It may also occur if
your Payment Gateway configuration is incorrect or incomplete.
-1702 Required card data was not present or failed verification check. This error may indicate
an invalid card number or type submitted by the payer. This error code indicates that
the request could not be filled as submitted.*
-1703 Generic bad authorization error and may occur in any case that might cause a card
issuer to deny a payment, such as insufficient funds.*
-1704 Occurs on a batch settlement in response to modem or other connection problems;
if merchant or modem configuration is incorrect; or if incorrect characters appear in
return data from the credit card processor. This error code indicates that the specific
batch settlement request could not be filled as submitted.
-1705 Occurs when a “start” signal was not sent by credit card processor. This error can
indicate a modem or other connection error.
-1706 Configuration file is not found
-1707 A response is not received before the timeout
-1708 Occurs when the maximum number of retries was exceeded. This error may have
occurred after part or all of the batch was settled by the credit card processor, but
before Payment Gateway received a response from the settlement.
-1709 Occurs when a response character was not received before the timeout. This error may
have occurred after part or all of the batch was settled by the credit card processor,
but before Payment Gateway received a response from the settlement.
-1710 Occurs when the request made for the transaction is not a valid request; the operation
you have attempted on the transaction is not allowed. If using the Payment Gateway
API, verify that the data passed to Payment Gateway is valid.
TouchNet Confidential

Error Code Reference
-1711 Occurs when there is a bad batch write. The batch was processed, but the batch file
could not be updated and may be corrupted.
-1712 Occurs when there is a bad read from the settlement batch file. Typically, this indicates
that the settlement data expected by the credit card processor does not match the
data sent with the batch settlement
-1713 Occurs when the ETX was not received
-1714 Occurs when modem processing has failed. This error may have occurred after part or
all of the batch was settled by the credit card processor, but before Payment Gateway
received a response from the settlement.
-1715 Occurs when the modem is unavailable
-1716 Occurs when a bad LRC accuracy check was received. Each request and response
includes a single character that verifies whether the response corresponds to the
request. This error indicates that the request and response characters did not match.
This error may have occurred after part or all of the batch was settled by the credit card
processor, but before Payment Gateway received a response from the settlement.
-1717 Occurs when the modem dial failed; either no dial tone was found, or another modem,
phone line, or other connection error has prevented the connection to the credit card
processor. The error may also indicate incorrect modem configuration.
-1718 Occurs when a modem write failed.
-1719 Occurs when a modem read failed.
-1720 Occurs when an invalid response is received. This may be caused by a modem,
phone line, or other connectivity problem occurring while receiving a response. Other
conditions that cause this error are incorrect merchant or modem configuration or
unexpected data received from the credit card processor.
-1721 Occurs when the batch settlement failed because a record was flagged as invalid by
the credit card processor.
-1722 Occurs when a duplicate batch was received
-1723 Occurs when an error occurred in receiving the batch. The error may indicate that the
host was busy. It may also indicate incorrect merchant configuration or credit card
processor phone number information.
-1724 Occurs when address verification failed. No correction is required.*
-1725 Occurs when the card is expired. No correction is required.*
-1726 Occurs when the batch was out of balance. This means that the payment amounts
expected by the credit card processor did not match the amount total of the batch.
-1727 Occurs when an invalid amount was specified. This error may indicate that you
attempted to reverse or credit an invalid amount, or attempted an authorization for
zero or fewer dollars.*
-1728 Occurs when reversals are not allowed for this transaction. The error occurs when you
try to process a credit on a payment that has not yet been settled, with a credit card
processor that does not allow reversals. If needed, you may remove the transaction
from the pending batch, then process a single authorization for the correct amount.*
-1729 Occurs when the operation has been attempted on a previously voided transaction.
This error indicates that no further activity is permitted for the transaction you selected
in the Operations Center.*
TouchNet Confidential

Error Code Reference
-1730 Occurs when the operation is not valid for a particular transaction. This error is
based off what your credit card processor allows to be processed. For example,
your processor might not allow you to perform a credit on an item that has not been
batched.*
-1731 Occurs when there is a bad settlement in which an error was determined by the credit
card processor. The credit card processor may have disconnected before completing
the settlement process.
-1732 Occurs when the ACH agreement is not found. This error provides security against
the submission of an ACH payment without a signed electronic agreement. No
troubleshooting is required.
-1733 Occurs when the ACH routing number is not found. This error provides security against
the submission of an ACH payment with an invalid routing number. No troubleshooting
is required.
-1734 Occurs when the attempted operation is not allowed for this transaction. For ACH
transactions, the error indicates that the current payment status does not allow the
attempted operation.
-1735 Occurs when the transaction was reinitiated too many times. ACH transactions may
only be included three times in generated ACH files. Payment Gateway allows two reinitiations.
This error indicates that the transaction cannot be reinitiated again.
-1736 Occurs when “settle now” is not allowed. This error will occur if a “settle now”
command is given when the “settle now” functionality has been disabled for your
system. In this case, the transaction must be settled with the next batch.
-1737 Occurs when an attempt is made which is not in accordance with the current license.
Your license is based on a specific number of licensed merchant accounts. You can
only process transactions for the number of merchants your license allows. Your
license is also based on the IP address of your Payment Gateway server, a specific
credit card processor and the server id or port associated with the licensed process.
If any of these items change, you will need a new license key which you may request
from Client Services.
-1738 Occurs when an unlicensed transaction is attempted. This error indicates an attempt
to process a transaction type that is not allowed by the processor.
-1739 Occurs when an invalid rejection code is attempted. For ACH transactions, this error
indicates that you have entered a rejection code not recognized by Payment Gateway.
Check your bank’s indicated rejection code and re-enter the code.
-1740 Occurs when an attempt to settle a batch is made when another batch is already in
progress. Wait until the first batch has settled, then settle the second batch.
-1741 Occurs when CVV2 verification failed and Payment Gateway is configured not to
settle the failed transaction. In this case, if the authorization was approved, the card
has been encumbered. This error will only occur if you have chosen not to settle
transactions failed for CVV2 reasons. You can change this configuration so that you
still settle transactions when they fail CVV2 verification.
-1742 Occurs when an ACH transaction had an invalid origin or SEC code.*
-1743 Occurs when an operation is attempted which is not allowed on a payment from a
savings account.
TouchNet Confidential

Error Code Reference
-1744 Occurs when the STX was not received.
*Note: This error code indicates that the request could not be filled as submitted. It does not
indicate a system error.
-2000 Series Errors
2000 series errors are from SQLLOG.
-2001 There were no events sent to sqllog
-2002 An sql exception was caught
-2003 Occurs when loading the events table fails during the reload transaction
-2004 There was an error when attempting to reconnect to the database
-2005 There was an error loading the jdbc driver. Often this would mean that you have the
class specified correctly, but the classpath is wrong. It can also mean that the class is
specified incorrectly.
-2006 There was a non-sql exception caught during sql operation
-2011 An exception was caught during xml parsing
-2012 An exception was caught during xml parsing
-2013 An exception was caught during xml parsing
-2014 An invalid character was found in the xml. This error is most likely caused by the wrong
character set or an unescaped character being used.
-2015 A required tag was not found in the input data.
-2016 There were no entries found in the sql_log_events table
-2018 A generic exception caught when processing events
-2019 Occurs when the tag to replace is empty. The tag is specified in the properties file and
the tag value should be valid “typeData”.
-2020 The sql update statement failed.
-2020 There are no events in the input xml document
-2100 Series Errors
Error codes -2100 through -2115 are known as inter-process communication (IPC) errors.
-2100 A general IPC error
-2101 The peer process failed to initialize
-2300 Series Errors
Series –2300 are known as TN_SQL (Standard Query Language) errors.
-2300 A generic code returned when a SQLexception is caught. This error usually occurs due
to a database connectivity error or invalid sql generated. Specific causes can only be
determined by looking at the exception data.
-2301 The class for the JDBC driver was not found. This error usually means that the
JDBC driver class was specified incorrectly or that the classpath didn’t include the
appropriate files for the driver.
TouchNet Confidential

Error Code Reference
-2302 There was an error executing a stored procedure. This error may be caused by incorrect
JDBC Drivers or bad data.
-2303 An exception was caught when trying to close a connection. This error can indicate that
there is no longer a connection to the database and can usually be ignored.
-2304 An exception was caught when trying to connect to the database. This error may be
caused by the database not being available, the username or password not being correct,
or other rights issues. The specific cause can only be determined by looking at the
exception data.
-2311 Can be returned from any select statement to the database. This error means the results
from another process were returned from a select statement to the database.
-2400 Series Errors
Error codes in the –24xx series are known as TN_XML (Extensible Markup Language) errors.
-2900 Series Errors
Codes beginning with –2000 are general error codes.
-2900 A general error
-2901 An error when attempting to open a file
-2902 An error when attempting to read an open file
-2903 An error when attempting to seek to a position within an open file
-2904 An error when attempting to allocate memory
-2905 An invalid tag found in the data (audio files, image files, HTTP response, SSL response,
etc...)
-2907 The requested item was not found
-2908 Required input or output data is missing
-2909 A required parameter was missing or an invalid parameter was specified
-2910 Unable to write to a file. This can occur because of low disk space.
-2911 An error creating subprocess
-2912 The response was not received before timeout expired
-2913 Invalid data was returned from a remote client
-2914 An internal error code indicating that invalid file information was sent to a read or write call
-2915 A disk drive hardware failure
-2916 An unexpected error returned by an OS specific API
-2917 An invalid request was attempted
-2923 The buffer is too small to contain the data
-2924 The COM port is not responding to commands
-2925 A general TouchNet API error
-2928 Occurs when an exception is caught
-2929 Means the function is not implemented
-2930 General error
-2931 Unable to parse URL
-2932 General error
TouchNet Confidential