KB-1174 How to get information on generic errors shown in the end-user interface

Nick Vigilante — Mon, 06 Mar 2017 17:04:02 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 5:04:02 PM

Appian errors in Tempo are typically displayed within a pink box popup that sometimes provide either generic or no information as to the root cause which might make it difficult to troubleshoot. For example, initiating an Action in Tempo may show the pink box with the following text:

An internal error has occurred.

The page could not be loaded. [HTTP Code = 500] (APNX-1-4279-001)

The application server log has no entries corresponding to this error by default, so it is difficult to identify the root cause of this error. In such scenarios, it is possible to enable additional logging to output a more detailed messaged corresponding to the error in the UI. To do this, add the following line in appian_log4j.properties located in <APPIAN_HOME>/ear/suite.ear/resources:

log4j.logger.com.appiancorp.rest.shared.AppianExceptionMapper=DEBUG

This prints the following line and a corresponding stacktrace for the same issue:

The form either does not exist or is not enabled for Tempo or mobile

Based on this information, it is now possible to determine the root cause of this error which is due to accessing a legacy Portal form in Tempo.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: web browser, user interface, how-to