1. The report being executed requires access to a Data Object that is not accessible in the current Role.

1. Check the settings for the current Role and insure that all of the Data Objects that are needed are available. For more information, review Roles.

An error has occurred. Please contact your administrator.

HTTP Status code: 200

http://localhost/exago/exagohome.aspx?showerrordetail=true

The error message will be displayed as a full stack trace. Use this information to correct issues such as data source connectivity trouble, incorrect web server configuration or to send the information to the Exago Support Group for additional support.

Additional information can be found in the system log. Review the Accessing the Log File article to locate the log files.

1. The Exago server or website is not running
2. The port is not open to the Exago server

1. Restart the web server and website.
2. Open the necessary port in the firewall.

1. A language file that is specified in the configuration does not exist, or cannot otherwise be found.

1. Verify that every language file in Admin Console > General > Main Settings > Language File exists in the <WebApp>/Config/Langugesdirectory.

The Scheduler Service is not running, or the Web Application server cannot reach the Scheduler Service.

Start the Scheduler Service, or check the Admin Console > General > Scheduler Settings and the Scheduler Service Configuration file to insure they are correct and the service is reachable.

1. The Scheduler Service is not running, or the Web Application server cannot reach the Scheduler Service.
2. For pre-v2020.1, the permissions on the Admin Console > General > Main Settings > Report Path do not allow Exago to write to that location.

1. Start the Scheduler Service, or check the Admin Console > General > Scheduler Settings and the Scheduler Service Configuration file to insure they are correct and the service is reachable.
2. For pre-v2020.1, grant full permissions to the Report Path for the IIS user or to the associated system user (e.g. apache or exago)

See An error has occurred. Please contact your administrator above.

1. The Web Application and the REST Web Service API are unable to communicate because their is no common encryption protocol between them.

1. Add the SecurityProtocol node to both the Web Application's and the REST Web Service API's appsettings.config files. There must be at least one common encryption protocol between the two. For more information, review the Application Settings article.

1. Add the file name to the URL.

   http://<YourServer>/Exago/admin.aspx

2. Add exagohome.aspx as the default document in the web server's configuration.

1. Using the incorrect URL to the Exago resource
2. In the REST Web Service API, the wrong method was being used (e.g. GET when a POST was expected)
3. In an environment using cookieless sessions, the session has expired.

1. Check that the request URL path is correct. On Linux, paths are case-sensitive.
2. Refer to the List of REST Endpoints to make sure the endpoint supports the method in use. Change to a supported method if necessary.
3. Renew the session. Consider using another cross-origin embedding strategy. Review the Cross-Origin Embedding of Exago article.

Note

The placeholders <report path> and <content ID> are used below to reference the folder and report name, and the content ID (as a GUID) in the system.

Report '<report path>:<content ID>' not found.

Example

Report 'My Reports\Sales\Products\2020 Profit:70aa978f-7f00-42ab-a2ec-c4548ee4ab53' not found.

1. The configuration file, or the static configuration file in a static-dynamic pair was changed
2. Exago is dropping sessions
3. The web server is restarting unexpectedly.
4. Exago is accessed from a different origin as the host application over HTTP

1. Changes made to the configuration file in a single configuration file environment, or the static configuration file of static-dynamic file pair will always invalidate all user sessions. Avoid modifying these files when users are engaged with the system. For more information, review Configuration File Options and Optimizations and Modifying Configs in a Production Environment.
2. Exago recommends utilizing a State Server. Review the Setting Up a State Server article to do so. If a state server is already in use, make sure it is configured properly and running.
3. Check for and troubleshoot disruptions to the web server's uptime.
4. Review the Cross-Origin Embedding of Exago for full details about the proper way of deploying Exago cross-origin.

1. An incorrect version of the mono runtime is installed.
2. Unpatched System.Web.dll when using cookieless sessions

1. Insure one of the supported Mono versions is installed.
2. Replace System.Web.dll with our patched version

1. A Top N Filter with a For Each group was added to the report, but a Group field was not chosen.

1. Return to the Top/Bottom tab of the Report Filters dialog, and either remove the Top N Filter by unchecking the Limit the report to the top/bottom values checkbox or choose a Group field from the dropdown.

1. The execution cache for this report is invalid or out of date.
2. A fatal error has occurred on a report being executed by the Scheduler Service, and report execution has stopped.

1. Click the Execution Cache icon in the toolbar to refresh the report's execution cache
2. Investigate the Scheduler Service's log file to determine root cause.

1. A Top N Filter was added to the report, but a Value field was not chosen.

1. Return to the Top/Bottom tab of the Report Filters dialog, and either remove the Top N Filter by unchecking the Limit the report to the top/bottom values checkbox or choose a Value field from the dropdown.

1. The data type that was returned from the data source for this cell does not match the data types required in the conditional formula. Either apply a filter to eliminate invalid records from the report, or modify the formula accordingly.

• No Data Qualified Options
• User Support Lab — No Data Qualified (video)

1. The Enable 32-Bit Applications setting is set to True for the IIS Application Pool.
2. The SQLite driver being accessed is the wrong version.

1. Set Enable 32-Bit Applications to False for the IIS Application Pool.
2. Delete the SqliteInterop.dll file from the /bin directory.
3. Replace the SqliteInterop.dll in the /bin/x86/ and /bin/x64/ directories. Exago can supply these if necessary.

Note

The placeholders <data object name> and <database name> are used below to reference the name of a data object and data source name in the environment that will be referenced by name in the error message.

1. The application pool is attempting to access a data source using Integrated Authentication but the data source is not setup for that.

   Note

   A variant of this error message may also appear in the Web Application's log file.

1. Review the notes about Integrated Authentication in the Connection String section of the Data Sources article to configure the environment properly.

Note

This error message may also appear in the Web Application main user interface as well.

1. Verify that the Admin Console > Storage Management > Assembly Location and Class Name are correct. Click the Validate Assembly icon to make sure a connection can be made to the Storage Management assembly.

   Tip

   It is recommended to always use an absolute file path to the Storage Management assembly.

2. The Storage Management assembly in the Assembly Location noted above is out of date. Check the Web Application's log file to find the absolute file path that Exago is using to load the library, and update it as needed.

Note

The placeholder <GUID> is used below to reference a Globally Unique Identifier that is appended to the end of the filename. This will vary with each instance of the error message.

Error: Could not find file '/opt/Exago/Config/WebReports.xml.<GUID>'

Error: Could not find file 'C:\Program Files\Exago\ExagoWeb\Config\WebReports.xml.<GUID>'

1. The permissions on the /Config directory and temp path do not allow the web server to read from one or both.
2. Exago is installed in a web farm and temporary files created by one node in the farm are unreachable by another node in the farm.
3. A cloud temporary path is configured, but the cloud service is not supported or accessible by Exago.

1. Configure the permissions appropriately, as described in the corresponding installation article (Windows, Linux or Azure)
2. Set the <webfarmsupport> node in the configuration XML file to true. Review the Hidden Flags and Set Up Exago in a Web Farm articles.
3. Make sure the Admin Console > General > Main Settings > Temp Cloud Service is a valid connection string to a supported cloud storage method such as Azure blob storage or Amazon S3 or EC2.

Note

The placeholder <database> is used below to reference the name of a CData driver in the environment that will be referenced by name in the error message.

1. Correct the cell references on the chart to reference the correct locations.

1. In the report's Export Settings, disable Flatten Groups in Excel and CSV.
2. Select a different report export format
3. Remove the chart from the report.

1. In the report's Export Settings, disable Flatten Groups in Excel and CSV.
2. Make sure detail rows are included in the report.

Note

The path and file name will vary based on environment and configuration.

1. Change the Admin Console > General > Main Settings > Temp Path to a directory outside of the operating system's temporary directory. Exago will handle its own removal of temporary files. It is possible the operating system may delete files before Exago is done with them.

Note

The placeholders a.b.c.d and w.x.y.z have been used below to represent two different Exago version numbers. These numbers will vary in each environment

Exception during Page_Load
Type: System.ArgumentException
Message: Illegal characters in path.

Exception during Page_Load
Type: System.NullReferenceException
Message: Object reference not set to an instance of an object.

1. One or more reports in the storage management database contains one of the illegal characters such as ? : / \ * “ > <.
2. The ROOT content item in the storage management database contains anything in place of null for values that should be null such as the name and description fields.

1. Remove illegal characters from report names. A simple SELECT can be used to find illegal names.
2. Remove any non-null values from the ROOT item, including the string "null".

1. In pre-v2019.2, the Puppeteer rendering library is enabled and shadow copying is also enabled.

1. Disable shadow copying. More information is available from MSDN.
2. Update the installed version of Exago to the latest version.

1. Using an unsupported temp file cloud storage service, or the service is misconfigured.
2. Using an unsupported session state service.

1. Ensure that the temporary file cloud storage service is setup correctly. Review the Amazon S3 File Storage or Azure
2. Ensure that the session state service is setup properly. Review the Setting up a State Server article.

[Rest.RESTErrorHandler.OnException] Error in REST Service
Type: WebReports.Rest.ExagoRestException
Message: The requested report is either missing, or is not supported for this service.
Source: WebReportsRest

1. The report that is trying to be loaded does not exist anymore, or the path and report name provided are incorrect.
2. One of the GetExecute() methods was called on a Dashboard.
3. One of the GetExecute() methods was called on an ExpressView in a version of the application pre-v2019.1.31, pre-v2019.2.19 or pre-v2020.1.1.5.

1. Check that the report exists in the folder that it is expected to be in. Check spelling of path and report name.
2. Dashboards are not supported by the GetExecute() methods. Use a different execution method. For more information, review the Executing Reports with the API article.
3. GetExecute() for ExpressView is supported in v20191.31+, 2019.2.19+ and v2020.1.5+ only. Update to one of those versions, or use a different execution method. For more information, review the Executing Reports with the API article.

Type: System.Exception Message: setupDs is null; setupFn: <path>.api.enc
 Source: WebReportsRest TargetSite: WebReports.Api.Api LoadApi(System.String)
 StackTrace: at WebReports.Rest.RESTHelper.LoadApi(String sid)

{
 "reason": "setupDs is null; setupFn: <path>.api.enc",
 "stacktrace": null
}

1. The session was consumed because the AppUrl has already been visited.
2. An invalid session ID was supplied in the ?sid= parameter when making API calls
3. The web server was restarted

1. Do not browse to the AppUrl until all calls have been made, as this closes the session and prevents any further changes to it.
2. Check to verify that the session ID is correct. Discard the session and start a new one if required.

Note

The path and file name will vary based on environment and configuration.

1. Verify that the <working_directory> in the Scheduler Service configuration file exists and is available for reading and writing by the Scheduler Service.
2. Verify that the <working_directory> in the Scheduler Service configuration file has not changed. If it has, copy all of the working files from the old location to the new one then restart the Scheduler Service.