View exceptions

You can view exception details to help end users troubleshoot the exceptions they encounter.

Search for and view exceptions

You can search for an exception by the GUID number, exception type, generation time, or the user who encountered the exception.

To search for and view an exception:

  1. Prerequisites:

    • The Search Exception functionality is enabled by setting the LOG_EXCEPTIONS_TO_DB server parameter to true.
    • You must have an Administrator license.
    • You must have the Server Tools: Execute admin tools and the Sys Admin: Edit Services Schedules access grants.

  2. Log on to PPM.

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

    The Search Exceptions page opens.

  4. If the GUID number is provided in the error message, enter the GUID number in the View Details for Exception GUID field and click Go.

  5. If you do not have the GUID number, provide search criteria in the Search for Exceptions to View section and click Search.

    The Exception details page opens.

    6. The Exception details page displays the following information:

    Field

    Description

    User

    Full name of the 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.
    Type

    Available in 10.0.3 and later versions.

    Type of the exception.

    Name

    Name of the exception.

    URL

    URL of the page that threw this exception.

    Reason

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

    Node name

    Name of the node on which the exception occurred.

    Generated Time

    Time when the exception occurred.

    Exception Stack trace

    Stack trace for the exception.

Back to top

Purge exceptions (other than services exceptions)

Exceptions (except for services-related exceptions) older than 14 days are automatically purged by default. To change the period, you can configure the EXCEPTIONS_RETAIN_PERIOD parameter in the server.conf file. For details, see Server parameters.

Back to top