In the following you will find the system and error messages that can be recorded in the file "errlog". Each system and error message will be described in short and you will find information on how to proceed in error cases.
In the directory work of the MICROS Retail OSCAR POS installation you will find the file "errlog" in which the system and error messages of the MICROS Retail OSCAR POS application will be recorded. If you delete the file it will be re-generated automatically with the next program start.
System and error messages will only be recorded in the file "errlog" during multi-user operation. During single-user operation, there will be no entries in this file.
For login clients, there is a separate file called "errlog.login".
Note:
By activating various debug
parameters in file "oscar.ini" and in various devices,
additional protocol output information can be generated in the file "errlog"
in the directory "work". Further notes can be found in the
documentation Initialisation File
"oscar.ini".
Warning:
Alternatively, the system and error messages can be provided in so-called OML files instead of in file “errlog” or “errlog.login”. After setting parameter “MICROS Retail OSCAR POS_OMLPATH=..\logs.30” and “MICROS Retail OSCAR POS_CONSOLE=MESSLOG” the system and errors messages in *.OML files in an optional directory (see MICROS Retail OSCAR POS Message Logger).
|
Error message |
Description |
Remedy |
|
Fatal error: reading local transaction nnnn
|
The Client tries unsuccessfully to send a (another) recorded transaction to the server for confirmation. This fails because the transaction cannot be read from the client database |
Try to find out the reason. Check the transaction number of this POS client on the server and change it in the last booked transaction number, if applicable (cp. Application -> Sales -> Transaction Header). If the transaction no. equals the last booked transaction, check why the client cannot read the transaction no. from its own database or cannot write (cp. System -> Configuration -> Process Unit Status -> Operation. Sometimes stopping and re-starting the client might help. If this is not the case, the database of the client must be loaded again. All transactions that have not been confirmed will then be lost.
|
|
Fatal error: wrong transaction counter lvbS / htnC
|
The client tries to send the server a transaction which has already been confirmed by the server. The transaction number is lower than the last booked transaction number for this client on the server.
|
Try to find out the reason. Check the last booked transaction number for this client on the server (cp. Application -> Sales -> Transaction Header). Enter this number + 1 in the process unit status of the client (cp. System -> Configuration -> Process Unit Status -> Operation). After the client has been stopped and re-started, all missing transactions will be transferred to the server and booked. Or: By loading the client database again, the transaction number of the client will be determined correctly, too, but all transactions which have not yet been confirmed, will be lost. |
|
transupd: error on commit: 5MoneyHead Terminal 1 TransNo 20 (FATAL) |
The client tries to send the server a transaction that has already been confirmed by the server .
|
Check the last booked transaction number for this client on the server (cp. Application -> Sales -> Transaction Header). Enter this number + 1 in the process unit status of the client (cp. System -> Configuration -> Process Unit Status -> Operation). After the client has been stopped and re-started, all missing transactions will be transferred to the server and booked.
|
|
|
|
|