placeholder
On this page you can find information about following topics:

Error handling     go to the TOP

  • If an error occurs for a sent command there is an exception in the Reply file behind this command.
  • Since TransUC3 version 2.00 there is created additional Status-File if there are one or more exceptions in the Reply File.
  • The status file has always the same file name like the Response-File with the text "...._Status.xml" at the end of the filename.
  • To check if there are any exceptions in the Reply-file it's now possible to check if there are any error-codes listed in the status file. In this case this error-codes must be checked in the Reply-file.
  • If the Status-file has no entries there aren't any exceptions in the Reply-file.
  • The exceptions gives more detailed information about the problem.
  • For each command where has been a problem in the TransUC3 communication is a separate exception in the Reply-File.
  • In the Status-File is every error code which occurs in the Reply-File only listed one time to have a hint what exceptios exist in the Reply-File.

Example-File     go to the TOP

  • If an error occurs for a sent command there is in the reply file an exception behind this command which gives more detailed information.
  • In the following example there is no PLU 9999 for department 1 available in the UC3 scales. So there is in the exception a hint, that this record was not found in the database
emptyRequest:

empty<?xml version="1.0" encoding="UTF-16" ?>
empty<scaledata>
empty<articles>
empty<article mode="read">
empty<department_no>1</department_no>
empty<plu_no>1</plu_no>
empty</article>
empty<article mode="read">
empty<department_no>1</department_no>
empty<plu_no>9999</plu_no>
empty</article>
empty</articles>
empty</scaledata>

emptyStatus-File:

empty<?xml version="1.0" encoding="UTF-16" ?>
empty<status>
empty<exceptions>
empty<exception>
empty<error_no>301</error_no>
empty<error>ERR_NOT_FOUND_IN_DB</error>
empty</exception>
empty</exceptions>
empty</status>

emptyReply:

empty<?xml version="1.0" encoding="UTF-16" ?>
empty<scaledata>
empty<articles>
empty<article mode="read">
empty<department_no>1</department_no>
empty<plu_no>1</plu_no>
empty<uan>0000000012345</uan>
empty<name>Department1 / Article 1</name>
empty<shortname>0</shortname>
empty<matchcode>Article 1</matchcode>
empty<customer_id>ShelfID 1</customer_id>
empty<price1>990</price1>
empty<price2>870</price2>
empty<article_group_no>1</article_group_no>
empty<vat1_no>0</vat1_no>
empty<vat2_no>0</vat2_no>
empty<purchase_price>0</purchase_price>
empty<price_flag>0</price_flag>
empty<locked_flag>0</locked_flag>
empty<discount_flag>1</discount_flag>
empty<smiley>0</smiley>
empty<smiley_limit_high>0</smiley_limit_high>
empty<smiley_limit_low>0</smiley_limit_low>
empty<extratext_mode>4</extratext_mode>
empty<extratext_no>1</extratext_no>
empty<tare_no/>
empty<plu_type>0</plu_type>
empty<last_change>2005-03-15T23:20:21</last_change>
empty</article>
empty<article mode="read">
empty<department_no>1</department_no>
empty<plu_no>9999</plu_no>
empty</article>
empty<exceptions>
empty<exception>
empty<error_no>301</error_no>
empty<error>ERR_NOT_FOUND_IN_DB</error>
empty</exception>
empty</exceptions>
empty</articles>
empty</scaledata>

List of error numbers     go to the TOP

The table below shows the current error numbers and strings that are available in the TransUC3 version on which this documentation is based.

Mettler-Toledo is reserving the right to extend the list of errors.

No String Description
100 ERR_COMMAND_ERROR a general command error.
101 ERR_INPUT_NOT_WELLFORMED the XML interpreter got problems when interpreting the command.
102 ERR_ELEMENT_MISSING a required element is missing or its value is empty.
103 ERR_MODE_UNKNOWN the mode is unknown.
104 ERR_ELEMENT_UNKNOWN the root element of the command is unknown.
200 ERR_NETWORK_ERROR a general network error.
201 ERR_UNREACHABLE_DEVICES not all devices could be contacted.
202 ERR_NO_TARGET_DEVICES no address for a target device.
300 ERR_EXECUTION_ERROR a general execution error.
301 ERR_NOT_FOUND_IN_DB the item could not be found in database.
302 ERR_ELEMENT_OUT_OF_RANGE a value of an element is out of range.
303 ERR_REF_INTEGRITY the referiential integrity has been violated.
this occurs when you tried to delete an item which is still referenced from another item,
e.g. the tare with the number x shall be deleted while is is referenced from an article.
304 ERR_DATE_TIME_INVALID the value or format of date / time is invalid
800 ERR_SYSTEM_ERROR a general system error.
801 ERR_UNKNOWN an unknown error occurred.
802 ERR_DB_ERROR error getting access to the database.