MPOS-AJB Connection Is Not Re-established When Resuming Application, Resulting in PIN Pad Cable Error (Doc ID 2049125.1)

Last updated on JULY 19, 2017

Applies to:

Oracle Retail Point-of-Service - Version 14.0.1 and later
Information in this document applies to any platform.

Symptoms

The MPOS-AJB connection is not re-established when resuming the application, resulting in a PIN Pad Cable error.


Steps to Reproduce:

  1. Launch a newly installed MPOS application on IPad.
  2. Confirm that the AJB connection is established.
  3. Log in using valid user credentials. 
  4. Select POS. 
  5. Enter an item (e.g., 4321).
  6. Select Pay > Credit/Debit. 
  7. Press Cancel on the pinpad of the sled. 
  8. Press Back on the Payment Error screen. 
  9. Lock the iPad and unlock.   Alert indicates that the transaction was cancelled, which occurs as applications are switched.  Select OK.
  10. Log in to POS. 
  11. Enter an item and select Pay > Credit/Debit. 
  12. Payment Error screen with 'Authorization is offline' message is seen. 
  13. [Esc]ape back and select Credit/Debit. 
  14. Now a swipe message appears on the sled and the transaction is completed.
  15. The following is seen in the FipayEPS.log:    
 2015/04/28 00:06:57.429 S-300000 FIPAYEPS  FIPAYEPS :     PinPad: WaitAck
 Error:DeviceDisconnected  Req(3,S00)  2015/04/28 00:06:57.429 S-300000
 FIPAYEPS  FIPAYEPS :   Swpe: Response DeviceDisconnected track2=  2015/04/28
 00:06:57.429 I-100001 FIPAYEPS  FIPAYEPS :  Transaction Info:
 Swipe-Result=DeviceDisconnected, Keyed, Invoice=0060134, debit Binlookup
 $10.53  2015/04/28 00:06:57.437 I-100001 FIPAYEPS  FIPAYP1 :   TSEND
 D(127,102, ====== TRANSACTION RECORD ======        DebitTransactionReceipt  
               ---------------------------------------  ) N(7,FIPAYP1)
 2015/04/28 00:06:57.437 I-100001 FIPAYEPS  FIPAYP1 :   TSEND
 D(245,101,134,,8,115,debit,0,04241,102,Binlookup,,,,,,1053,0060134,,,,*Tokeniz
 ation,,324934846,,,,,,,,,,,,04241102134,730,,CHECK PIN PAD CABLE
 ,,,,,,,,,,,,04282015,000657,,,,,,,,,,CHECK PIN PAD CABLE
 ,,,000657430,,,,,,,,,,,,,,,,,CHECK PIN PAD CABLE ,,) N(7,FIPAYP1)  2015/04/28
 00:06:57.529 A-200000 FIPAYEPS  FIPAYEPS :  Term# 102. Sending to POS: 102,
 ====== TRANSACTION RECORD ======        DebitTransactionReceipt              
    ---------------------------------------    2015/04/28 00:06:57.529
 A-200000 FIPAYEPS  FIPAYEPS :  Term# 102. Sending to POS:
 101,134,,8,115,debit,0,04241,102,Binlookup,,,,,,1053,0060134,,,,*Tokenization,
 ,324934846,,,,,,,,,,,,04241102134,730,,CHECK PIN PAD CABLE
 ,,,,,,,,,,,,04282015,000657,,,,,,,,,,CHECK PIN PAD CABLE
 ,,,000657430,,,,,,,,,,,,,,,,,CHECK PIN PAD CABLE ,,  2015/04/28 00:06:57.831
 S-300000 FIPAYEPS  FIPAYEPS :  TermPmp102 Inv# 65 Eps Ready for Next Command
 2015/04/28 00:06:59.765 I-100001 FIPAYEPS  FIPAYEPS :
 TCP_SERIAL_BASE.OpenSerial() - Pinpad IP  Connection set to TCPCommNv2
 instance: 10.154.105.62:49293 port 25002 using Packetization *INTNOH
 2015/04/28 00:07:16.956 S-300000 FIPAYEPS  FIPAYEPS :   PINPAD 102:   Success
  Read(4,#099)  2015/04/28 00:07:16.957 S-300000 FIPAYEPS  FIPAYEPS :   PINPAD
 102:   Success  Send(4,#099)  2015/04/28 00:07:17.296 S-300000 FIPAYEPS
 FIPAYEPS :  p_TcpData FipayFep Req:
 100,135,,,120,debit,,04241,102,Binlookup,,,,,,1053,0060135,,,,*Tokenization,,,
 ,,,,,,,,,,,04241102135,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
 ,,,,,,,,,,,,,,,,,,,,,,,,,,,,  2015/04/28 00:07:17.297 S-300000 FIPAYEPS
 FIPAYEPS :  TermPmp102 Inv# 65 FipayFep Rsp:
 100,135,,,120,debit,,04241,102,Binlookup,,,,,,1053,0060135,,,,*Tokenization,,,
 ,,,,,,,,,,,04241102135,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
 ,,,,,,,,,,,,,,,,,,,,,,,,,,,,  2015/04/28 00:07:17.297 S-300000 FIPAYEPS
 FIPAYEPS :  TermPmp102 Inv# 66 POS Started EPS Transaction : Binlookup
 Eps#:66 POS#: $ 10.53  2015/04/28 00:07:17.297 I-100001 FIPAYEPS  FIPAYP1 :  
 TDATA
 D(184,100,135,,,120,debit,,04241,102,Binlookup,,,,,,1053,0060135,,,,*Tokenizat
 ion,,,,,,,,,,,,,,04241102135,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
 ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,) N(7,FIPAYP1)  2015/04/28 00:07:17.298
 S-300000 FIPAYEPS  FIPAYEPS :   PINPAD 102:   Success  Send(4,#011)
 2015/04/28 00:07:17.729 S-300000 FIPAYEPS  FIPAYEPS :   PINPAD 102:   Success
  Send(62,D30~1c1~1c1 ~1c0INSERT OR SWIPE ~1c0CARD            ~1c0            
    )  2015/04/28 00:07:18.202 S-300000 FIPAYEPS  FIPAYEPS :   PINPAD 102:  
 Success  Read(5,D3000)  2015/04/28 00:07:18.202 S-300000 FIPAYEPS  FIPAYEPS :
   PINPAD 102:   Success  Send(3,Q40)

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms