Structure of an Error Message

The following is an example of the structure of an error message: 
<?xml version="1.0"?>
<!— X.400 incoming status-->
<x400statusIn>

<error>
	<documented>TN documented</documentId> if available
	<functionName>function name</functionName>
	<class>error group (UAFI or X.400 gateway)</class>
	<code>error code</code>
	<text>error text</text>
</error>

</x400statusIn>

Text of X.400 Gateway Error Messages

Internal X.400 Gateway error messages have the following:

  • <class> tag = X.400 gateway
  • <code> tag = -1

The following lists X.400 Gateway internal error texts.

  • Error while parsing the UAFI response file 'xxx'.
  • Error while converting X.400 ip-message into UAFI syntax.
  • Error while converting X.400 edi-message into UAFI syntax.
  • Error while converting X.400 notification into UAFI syntax.
  • Cannot delete file 'xxx'.

The following lists the X.400 Gateway exception error texts.

  • IOException
    • IOException: cannot read UAFI response file 'xxx': <exception info>
    • IOException: cannot write UAFI command file 'xxx'. <exception info>
    • IOException: cannot close UAFI response file 'xxx': <exception info>
    • IOException: cannot close header file 'xxx': <exception info>
    • IOException: cannot read header file 'xxx': <exception info>
    • IOException: cannot close input file 'xxx': <exception info>
    • IOException: cannot close output file 'xxx': <exception info>
  • InterruptedException
  • Exception while creating an inbound X.400 submitted notification
  • Exception while creating an inbound X.400 non-submitted notification
  • Exception while creating an inbound X.400 delivery report
  • Exception while creating an inbound X.400 non-delivery report
  • Exception while creating an inbound X.400 receipt notification
  • Exception while creating an inbound X.400 non-receipt notification
  • Exception while creating an inbound X.435 positive EDI notification
  • Exception while creating an inbound X.435 negative EDI notification
  • Exception while creating an inbound X.435 forwarded EDI notification
  • Exception while parsing an XML string
  • Exception while parsing a XML file 'xxx'
  • Exception while creating a XML file
  • Exception while creating UAFI file
  • Exception while renaming the file 'xxx' into 'yyy'
  • Exception while deleting files
  • Exception while updating the correlation file
  • Exception while converting 'xxx'

Text of ADDONMAIL UA-FI Error Messages

The following lists the UA-FI error message texts reported via the UA-FI response file. The wm.x400gateway.Gw:sendAndFetch, wm.x400gateway.Gw:send and wm.x400gateway.Gw:fetch services store both the error text from the UA-FI response file and the error code in the error message (Trading Networks document type x400statusIn).

Supported UA-FI error groups are:

  • DELETED
  • LOGON
  • WARNING
  • ERROR
  • FATAL-ERROR
  • ABORTED

For more information about the UA-FI error codes and error text, see the chapter about error handling in the UA-FI Programmer’s Guide.