Stuck Batch on PAX

Check on CBOS if there is a stuck batch, usually shown in RED under Capture

Check if batch is the same number as JK

Click on windows folder > C: Drive > Navigate to jk Restaurant/Retail folder  > logs >  scroll all the way down click on the last log > scroll all the way down and find the last batch number. 

This is to confirm the number you will be changing in order to perform the batch out } 

On the pax A35 / A920 - Click on the square on the upper right side of the screen > Host settings > click on batch number. Change batch number to 10 above the one you saw in the notepad. 
Confirm choice press the red key pad to exit > proceed to JK batch out method in Management.

If that doesn't work, check if the transaction that got stuck was EBT/Debit or Credit. Differentiate in CBOS using 100 and 200 and 400.

100 - Credit

200 - Debit 

400 - EBT

If the stuck transaction is a EBT, you can clear the EBT transactions
On the pax A35 / A920 - Click on the square on the upper right side of the screen > Host settings> Clear EBT Transactions

Try to batch.

Once you can confirm that you can see all the transactions and the transaction isn't a stuck EBT transaction, and the problem persists, we can wipe all the transactions in the same way from the pin pad(Clear all Transactions instead of EBT only) and try to batch out again with the NEW batch number. 

Now we must run the transactions offline. Grab all the transactions after the last successful, paste into excel after settings format to Text(except for column H, which will be Number), paste it in as Unicode text and get rid of all the non-needed information(all that is needed is card number, expiration date, amount and auth number. Also make sure to get rid of transactions with 200, 400 or blank auths) 
Encrypt it with the ZIP code, and send to tech support to be ran offline.
 
Sometimes you might need to reinstall 3.5 POSLink after uninstalling the current POSLink.