Anatomy of a Fatal Error Message

Last reviewed: 12/19/2002
Article ID: R10757

The information in this article applies to:

SUMMARY

This article discusses how fatal errors are reported and provides a detailed description of each of the fields in a fatal error message.

MORE INFORMATION

Nobody likes to receive a fatal error message. Fortunately, STI systems are very reliable, so fatal errors should be few and far between. In the event that you do encounter a fatal error message, though, do not panic. This article will help you to understand the information provided in the fatal error message.

If a fatal error occurs, the information from the message is stored in a file called STERROR.LOG, located in the STI program directory. This makes it easy to track information from the error even after the original error message has been cleared from the screen. Following are instructions for viewing the STERROR.LOG file.

The layout used and information included in a fatal error message depends on the format of the fatal error message. For programs such as TABS III, PracticeMaster and Trust Accounting System, errors numbered between 1300 and 1499 use the Extended Error Format. For all other errors in all STI systems, the Standard Error Format is used. (Note: The Extended Error Format may be used in the Accounts Payable System if an error numbered in the 1300-1499 range occurs while performing integration-related functions such as passing cost entries to TABS III.)

Below are images of two fatal error messages, each followed by its entry in the STERROR.LOG file. Each of the fields shown is explained in the sections following the screen shots.

Extended Error Format

 Extended Error Format


STERROR.LOG

FIELD DESCRIPTION
Error Number

This is a series of error codes returned by the application. The Extended Error Format for Error Numbers is NNNN-LL-RRRR-CCCC.

For a breakdown of each segment of the Error Number, see STI Article R10044.

FileName The FileName indicates the name of the source file where the error occurred. This information can sometimes be useful in determining the cause or solution for a fatal error.
Function This field indicates the Function (i.e., the program operation or file access) that the application was attempting to perform when the error occurred. The contents of this field will usually match the first line of the Function Traceback Path.
Message The Message section of the fatal error dialog box repeats the Error Number and describes the error, while providing additional information about the nature of the error and which file is affected. In the example above, we can see that an error 1310-1-12-5, Error Opening, has occurred. The following additional information is provided:
  • Filename: The name of the file involved in the error. In the example, the Filename is t3fee.
  • uerr: This represents the file handler error code. In most cases, this information is provided in the RRRR position of the Error Number field. Sometimes, however, the Error Number field has a zero in the RRRR position. In such situations the uerr information becomes much more useful.
  • sysicod: This represents the operating system error code. Like the uerr, this information is usually provided in the Error Number field, in the CCCC section. In the event the CCCC has a zero, though, the sysiocod may provide the information needed to troubleshoot the error.
Function Traceback Path This field lists the Functions (i.e., the program operations or file accesses) that the application performed immediately prior to the occurrence of the fatal error. The Functions are listed beginning with the most recent Function and going backwards chronologically. This information can sometimes be useful in determining the cause or solution for a fatal error.

Standard Error Format

 Standard Error Format


STERROR.LOG

FIELD DESCRIPTION
Error Number

This is a series of error codes returned by the application. The Standard Error Format for Error Numbers is NNNN-LL-CCCC. The Standard Error Format does not include a file handler error code.

For a breakdown of each segment of the Error Number, see STI Article R10044.
FileName The FileName indicates the name of the source file where the error occurred. This information can sometimes be useful in determining the cause or solution for a fatal error.
Function This field indicates the Function (i.e., the program operation or file access) that the application was attempting to perform when the error occurred. The contents of this field will usually match the first line of the Function Traceback Path.
Message The Message section of the fatal error dialog box repeats the Error Number and describes the error, while providing additional information about the nature of the error and which file is affected. In the example above, we can see that an error 1020-1-3, Error Opening, has occurred. The following additional information is provided:
  • Filename: The name of the file involved in the error. In the example, the Filename is C:\STI\2001GL\G5log.dta.
  • path: This field represents the directory path to the file involved in the fatal error. Often, though, the fatal error may not be caused by path issues. In such cases, the path field simply reflects the Filename involved in the fatal error, as with the previous field.
  • flags: This information, which indicates a parameter used by certain program functions, can sometimes be useful in determining the cause or solution for a fatal error.
Function Traceback Path This field lists the Functions (i.e., the program operations or file accesses) that the application performed immediately prior to the occurrence of the fatal error. The Functions are listed beginning with the most recent Function and going backwards chronologically. This information can sometimes be useful in determining the cause or solution for a fatal error.

REFERENCES

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

© 1999-2003 Software Technology, Inc.   All rights reserved.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com