Tse connection error

If a hardware TSE is used, the error message "Tse connection error." may be returned after createDocument.

Possible scenarios:

TSE not connected

TSE is not connected to the cash register (to the system on which the RetailForce Middleware is installed).

Troubleshooting:

Connect the TSE to the system.

TSE connected - test shows "OK

The error is returned, but the TSE is connected to the system, also a self-test

• POST /api/v1/management/germany/tse/{tseSerial}/selftest returns
• "200 - Success",

as does a connection test:

• PUT /api/v1/management/germany/{clientId}/tse/connectTest,
• "200 - Success".

Possible Cause:

The limit of open transactions has been reached! The swissbit hardware TSE can manage a maximum of 512 open transactions. These are usually transactions that were started with createDocument but were not completed correctly later (with storeDocument or cancelDocument). This can occur, for example, if the POS system crashes after a createDocument and has not "remembered" that there is still an open transaction.

The number of open transactions can be read out with the following endpoint:

• GET /api/v1/management/germany/tse

Open transactions are displayed in the response in the field "startedTransactions":

[
   {
      ...
      "startedTransactions": 512,
      "maxStartedTransactions": 512,
      "createdSignatures": 2238,
      "maxSignatures": 20000000,
      ...
   }
]

Troubleshooting:

Close the open transactions. 

With the endpoint

• GET /api/v1/management/germany/{clientId}/tse/listTransactions,

open transactions are returned in packets.

Example:

[
   45,
   1,
   2,
   3,
   4,
   5,
   6,
   7
]

For test TSEs, it may make more sense to reset the TSE to factory settings instead of closing all transactions. More information on this can be found in the article "Swissbit Hardware TSE".