Accessing Application Exception Details

If an exception occurs, the user sees an error message that displays a GUID number and advises the user to contact the PPM administrator. The PPM administrator can then get detailed information about the exception from the new Search Exceptions page.

Note: To access the Search Exceptions page, you must have an Administrator license and the following access grants:

  • Server Tools: Execute admin tools
  • Sys Admin: Edit Services Schedules

To enable this functionality, set the LOG_EXCEPTIONS_TO_DB server configuration parameter value to true.

To access and use the Search Exceptions page:

  1. Log on to PPM.

  2. From the menu bar, select Search > Administrative > Exceptions.

    The Search Exceptions page opens.

  3. In the View Details for Exception GUID field, enter the GUID provided in the error message.

  4. Click Go.

    The Exception details page opens.

  5. The Exception details page displays the following information:

    Field

    Description

    User

    Full name of the logged-in user who encountered this exception. This field is empty if the exception was thrown by a background service.

    GUID

    GUID identifier for this exception. Most web exceptions are tagged with a GUID. Background service exceptions usually do not have a GUID.

    Name

    Name of the exception.

    URL

    URL of the page that encountered this exception.

    Reason

    Reason the exception occurred. For background service exceptions, this can be an error message.

    Node name

    Name of the node on which the exception occurred.

    Generated Time

    Time at which the exception occurred.

    Exception Stack trace

    Stack trace for the exception.

Purging Exceptions (Other than Services Exceptions)

Exceptions (except for services-related exceptions) older than 14 days are automatically purged by default. You can control the frequency with which exceptions are purged by setting a new value for the EXCEPTIONS_RETAIN_PERIOD server configuration parameter in the server.conf file.