Exago Logo
Generic filters
Exact matches only

See Full Error Details

When an error occurs in Exago, a generic error message may be displayed.


Sample error message that could occur when executing a report with errors on it

This generic message is meant to prevent end users from seeing the full stack trace of the error.

There are two ways to see detailed error messages.

  1. If you are accessing Exago directly in a browser:
    1. Append ?showerrordetail=true to the URL.
      Example: /Exagohome.aspx?showerrordetail=true
    2. Refresh the page and recreate the error.
  2. If you are accessing Exago through one of the APIs:
    • With the .NET API call the method GetUrlParamString and set showErrorDetail to True.
    • With the REST Web Service API, set the showErrorDetail property of the Session object to True before starting the session.
  3. Enter Exago through the API and recreate the error.


The status code on the generic error message corresponds to standard HTTP status codes. For example if the status code is 408 it means there was a request timeout. For status code 200 the request completed successfully and the error lies elsewhere.

If you would like more details after seeing the full error message please see the section Read the Log File.

Was this article helpful?
1.5 out of 5 stars
5 Stars 0%
4 Stars 25%
3 Stars 0%
2 Stars 0%
1 Stars 75%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents