When an error occurs in Exago, a generic error message is displayed.
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.
- If you are accessing Exago directly in a browser:
- Append ‘?showerrordetail=true’ to the URL.
Example:.../Exagohome.aspx?showerrordetail=true - Refresh the page and recreate the error.
- Append ‘?showerrordetail=true’ to the URL.
- If you are accessing Exago through the API:
- Using the .NET API call the method GetUrlParamString and set showErrorDetail to True.
- Using the Web Service API call the method GetUrlParamString2 and set showErrorDetail to True.
- Enter Exago through the API and recreate the error.
Note: 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.