Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micros RES Ver 5 - Credit Card Batches Hung Up

Status
Not open for further replies.

charliescarface

Technical User
Feb 10, 2013
20
US
We have a series of CC batches that won't settle. We alternately get the errors: "No Response From CA Driver" or "Timeout Awaiting Poll." I've renamed the HISTORY folder a few times and had success with two batches but now the errors persist. From the CC Batch module I've run the diagnostic tests for the drivers, all tests had successful results. We have continued to process cards without problem. Except for the batches piling up, our processor (Heartland) shows no problems on their end. I now have two and a half days of batches waiting to transfer. Thanks for any guidance.
 
I'd rotate your 3700d log, try running a settle; and see if the error leads you anywhere.
 
Sun Feb 18 07:14:22 2018 | M1-6745670 | CCS | 0 | ERROR Loading [CaTVCA.dll] |
Sun Feb 18 07:14:22 2018 | M1-6745670 | CCS | 0 | ERROR Loading [CaTVCS.dll] |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Driver CaHLS Version 4.9.21.2298 received Batch Open Request |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Driver will use current verbosity [0] |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Can't open History Key in Registry |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Batch Seq 5377 Settlment Attempt No. 1 |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Batch Seq from Database is 5377 |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Batch Number is 251 |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Expected Count= 300 Expected Balance= 1871.72 |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | TCP/IP Frame Channel received Batch Open Request |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Can't read byte from socket |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Winsock Error Code = [10054] |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Error detected while waiting for ENQ |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Failed to receive ENQ as expected |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Closing Socket 968 |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Msg1[Both] |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Msg2[Both] |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Msg3[Both] Timeout Awaiting POLL |
Sun Feb 18 07:14:24 2018 | M1-6745670 | CaHLS | 0 | Msg4[Both] |
 
Well...I've had other programmers tell me it doesn't make a difference; but I've had it work so...

You've still got TransactionVault drivers (TVCA/TVCS), even though you're on Heartland now (HLS).

I'd triple-check, which driver is current; make sure all CCs are linked to the correct one...then blow-out, presumably the TV Auth and Settle.

Clean re-start, try again.
 
When we ran into this problem a full system reboot would resolve it. Most of our sites that ran into this issue was right after an improper reboot.
 
Out of curiosity are you behind a firewall, and are keeping up to date with windows updates? The specific error you’re getting is essentially a connection reset by host. Quite a few things can cause that.

My first two questions are only relevant because we’ve recently had similar issues with a large number of our stores that aren’t on EMV yet, and digging revealed two main culprits: because we had windows update turned off our root ca’s were laughably out of date, and one of our firewall vendors was blocking one of the main CRL end points.
 
Have you checked which versions of TLS are active on your system as well as which versions Heartland are currently supporting?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top