A Reference Guide to Network “Unable to Process” Codes
Occasionally, when a driver swipes a card to process a fueling transaction at a Pacific Pride location, the network is unable to process the transaction. As a result, the FSC3000™ Fuel Site Controller issues an “Unable to Process” code.
In most cases, the driver should be able to re-swipe the card to complete the authorization process. But in the event that additional information is needed regarding the error, the FSC3000’s “Unable to Process” codes can help users and technicians determine the reason for the unsuccessful authorization.
When an unsuccessful authorization occurs, a number code is displayed at the end of an “Unable to Process” message:
Example: Unable to Process: 11
In addition, a short text description is displayed with unsuccessful transactions from the “SHOW TRANSACTION” command.
For the convenience of technicians and users seeking to diagnose the source of processing errors, the following table lists all “Unable to Process” codes, their short text descriptions and the cause that prompted the FSC3000 to generate the code.
| Code |
Short Text |
Cause |
| 0 |
NO ERROR |
Network connection failed or was never established based on any known error conditions. |
| 1 |
BAUD 300 ERROR |
Modem connected at baud rate not configured for use with specific network. Check communication parameters. |
| 3 |
NO CARRIER |
Line answered, but modem could not establish connection. |
| 4 |
ERROR IN FORMAT |
Connection was established, but network rejected the authorization request packet due to corrupted data and/or invalid packet checksum. Possible poor line condition (line noise). |
| 5 |
BAUD 1200 ERROR |
Modem connected at baud rate not configured for use with specific network. Check communication parameters. |
| 6 |
NO DIAL TONE |
Modem never detected a Dial Tone – Check phone line or connection. |
| 7 |
BUSY |
Modem returned an error, indicating the dialed number is busy. |
| 8 |
NO ANSWER |
Modem dialed but time-out from “No Answer” – Check primary/secondary phone numbers are correct on fleet table. |
| 10 |
BAUD 2400 ERROR |
Modem connected at baud rate not configured for use with specific network. Check communication parameters. |
| 11 |
TIMEOUT NO ANSR |
FSC no answer time-out. Used as failsafe for result code 8, in case modem time-out does not fire. |
| 12 |
MODEM NOT CNFGD |
Result code could occur if no response is seen from modem after the communication parameters have been sent. Check modem is powered and/or connected to FSC. |
| 13 |
NO CONNECT NTWK |
Indicates that the modem has established a connection (with DCD high), but an ENQ was never received from network. ENQ wait period is 30 seconds for modem and 15 seconds for device server. Note: under device server operation, this result can be displayed without a valid connection being established. |
| 14 |
NO PHONE or ID |
No phone or site ID is not configured for the specific network. |
| 15 |
NTWKS EXHAUSTED |
Usually indicates that a connection was previously established for the current transaction, but was lost and cannot be re-established. |
| 16 |
NO MODEM RES. |
Modem had been previously configured, but currently non-responsive to standard AT commands. Check modem. |
| 17 |
<EOT> FROM NTWK |
Network sent an EOT and terminated the connection before completion. This could occur if the FSC NAKs three bad packets from network. |
| 18 |
LOCAL AUTH ALL |
Local authorization is enabled for all transactions specific to network. |
| 19 |
NO NET Response |
An ENQ was received from the network, but an ACK or NAK was never received from a transmitted packet. The FSC has attempted to send a packet 3 times, waiting about 45 seconds between each packet. |
| 20 |
NTWK DC NO<EOT> |
Host disconnected without sending an EOT. |
| 21 |
UNKNOWN DENIAL |
Host denied transaction without any reason text returned. |
| 22 |
LOCAL AUTH PROD DENIED |
When locally authorized and product was denied because it was flagged to deny on local authorization. |
Back to Top