If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

About the Error Log Form

Aptify has the Error Log form to record exceptions. The database publisher in the Exception Manager must be enabled for exceptions to be saved as Error Log records. See Configuring the Exception Manager for more information.

Attachments Tab

This tab contains any files related to this record.

Details Tab

Error Log - Details Tab


This field lists the message associated with this exception.


This field identifies the source of the exception.

Stack Trace

This field contains a trace of the exception through the call stack.

Target Site

This field identifies the target site associated with the exception.


This field specifies the severity level of the exception.

App Domain

This field identifies the application domain associated with this exception.

Machine Name

This field identifies the name of the machine associated with this exception.

Windows Identity

This field contains information about the Windows identity (domain user) data for this exception. For exception that are captured from an application server, this would be the user running the application thread. For exceptions captures from Aptify web, this is the user the run Aptify web.

Exception Manager

This field identifies the associated Exception Manager.


This field identifies the time and date that the exception occurred.

Thread Identity

This field identifies the thread identity information for this exception.

General Tab

Error Log - General Tab

Exception Text

This field contains the text that provides information about the exception. In cases where the exceptions are recorded as a chain, the Exception Text field of the root exception (the start of the chain) contains the exception text from the other exceptions (Inner Exceptions) in the chain.

Inner Exceptions Tab

Inner Exceptions

If this exception is part of a chain, this field links to the record for the next exception in the chain. Exceptions in .NET can occur as a chain of exceptions. The first exception in a chain is referred to as the root exception. As exceptions bubble up through the call stack, many of the exceptions are single exceptions, while some will add to the chain. Usually exceptions are added to the chain to add more information. The chain is built using the InnerException property of a .NET Exception. The exception at the start of the change is thrown and the first exception handler is called. That exception handler may create a new exception with the original exception as it’s InnerException. The exception handler can also treat the exception as if it never happened, or just pass it along with no changes, and no new exception added to the chain. For the exception publishers, the exception text consists of information from all the exceptions in the chain, so that the user does not have to navigate the chain to find the desired information. For the database publisher, each exception in the chain is recorded as an Error Log record, using the InnerExceptionID field to link to the next exception in the chain. In most cases, people reviewing the Error Log records should only need to look at Root Exceptions (IsInnerException=0/false). The exception text for the root exception contains information from the inner exceptions listed below the root exception information. 


The field in this tab lists any associated XML data for this exception.

Copyright © 2014-2019 Aptify - Confidential and Proprietary