218 - Inepro Back Office Suite
Troubleshooting
Terminal is not sending the transactions
Q
The transaction from the terminal (product sales, entering a card) are not send to the database.
A
The terminals will periodically send their transactions to the database, if this is impossible they will be stored on the
terminal.
If they are send but have the wrong format, or data that can't be matched in the database the transaction will be moved to
the 'Failed transactions' folder on the database server.
1) The transactions can't be send, because there is no network connection between the terminal and the server
a) Check if the netwerk connection is ok by pinging the terminal from the server
b) If the connection is not there, the message 'Trx. log full' is shown. The internal transaction storage is full and the
PayCon will not function until the connection to the server is restored. Restore the connection to the server. See
page:
2) The wrong PayConService Server is set in the PayCon
a) Check if the server address in the PayCon is set to the correct PayConService server address
3) There are no transactions to be send
a) No transactions have been made with the terminal, so none can be send to the database.
i) Check if there are any transactions in the PayCon in de 'DB settings -> Transaction Log -> Size' menu, if it's
zero, there are no transactions to be send.
4) The transactions have been send to the server but they contain values that cannot be inserted into the database
a) Go to the server
b) Open PayConServer from the System tray
c) Select 'File -> Retry Failed transactions' from the menu.
d) Note the errors from the transactions that are not processed.
i) A transaction with 'No item found for product x' (where 'x' is the Product ID) needs a product with that
number in the database before it can be processed.
ii) A transaction with 'Transaction from unassigned Terminals are not allowed' needs the terminal to be attached
to a device.
iii) A transaction with 'Violation of UNIQUE KEY constraint 'UK_TenderPurse'. Cannot insert duplicate key in object
'tblTenderPurse'' is caused during an database update and can only occur with software older than 4.10. This
will need a 4.10 update (or higher) to resolve, contact the Inepro Helpdesk.
5) The problem is not solved by these solutions
i) Call Inepro Support.
222
Summary of Contents for Back Office Suite
Page 2: ......
Page 9: ...Introduction PartI ...
Page 11: ...3 Overview IBOS Overview IBOS ...
Page 12: ......
Page 13: ...Hardware Installation PartII ...
Page 20: ......
Page 21: ...Software installation PartIII ...
Page 38: ......
Page 39: ...Steps PartIV ...
Page 120: ...112 Inepro Back Office Suite Steps Image 1 Image 2 Image 3 ...
Page 149: ...Advanced Tasks PartV ...
Page 153: ...145 Replacing a server PayCon Server ...
Page 157: ...Terms Concepts PartVI ...
Page 159: ...Configuration PartVII ...
Page 177: ...169 Import Data If the installation was successful the final screen of the installer is shown ...
Page 179: ...171 Import Data The following screen will appear ...
Page 206: ......
Page 207: ...Change Interface Settings PartVIII ...
Page 209: ...USB Stick Procedure PartIX ...
Page 211: ...Balance Scheduler PartX ...
Page 214: ......
Page 215: ...Scheduled Tasks PartXI ...
Page 218: ......
Page 219: ...Troubleshooting PartXII ...
Page 234: ......
Page 235: ...Glossery PartXIII ...
Page 238: ......
Page 239: ...Appendices PartXIV ...
Page 244: ...236 Inepro Back Office Suite Appendices ...
Page 246: ......
Page 248: ......