Troubleshooting
- 3 minutes to read
This document lists common issues that can occur in a Web Reporting application and describes solutions. For information on how to identify the cause of the issue, refer to the Reporting Application Diagnostics topic.
The application works on the development machine but displays an error in production.
Ensure that all the required libraries are deployed on the production environment. See the following topics for more information:
| Platform | Topic |
|---|---|
| ASP.NET WebForms | Application Deployment |
| ASP.NET MVC | Application Deployment |
Document export does not work in an application with token-based authentication
The Web Document Viewer performs most of its API calls as AJAX requests, but print and export requests are performed by the browser. For this reason, print and export requests do not have HTTP headers and cannot be authorized. See the following example for details on how to negate this limitation:
Web Document Viewer - How to export documents in an application with token-based authentication
A web reporting application stops working shortly after deployment
Note
This issue only occurs in ASP.NET WebForms and ASP.NET MVC but does not affect ASP.NET Core.
Make sure to reinitialize the reporting controls after the AppPool was recycled. To do this, call the corresponding control’s StaticInitialize method at application startup:
- ASPxWebDocumentViewer.StaticInitialize - Reinitialize the Document Viewer.
- ASPxReportDesigner.StaticInitialize - Reinitialize the Report Designer and Document Viewer.
The browser console outputs an “Unable to process binding” error
This indicates that client scripts are registered incorrectly. To solve the issue, make sure that:
- The script files are registered in the correct order
- There are no duplicate registrations
- There are no conflicts between the scripts
- The version of the DevExpress scripts matches the version of the server-side libraries.
See the Client Side Diagnostics section of the Reporting Application Diagnostics article for more information.
The browser console displays CORS policy errors in a JS-based reporting application
Make sure that Cross-Origin Resource Sharing (CORS) is correctly configured in your server application. See the following article for more information: Enable Cross-Origin Requests (CORS) in ASP.NET Core
If the issue persists, there is a possibility that the server application generates an error during its execution, but the generated error page is not configured to use CORS. In this case, use logging to identify the cause of the problem. Refer to the following article for more information: Logging in .NET Core and ASP.NET Core
The Document Viewer displays an “Internal Server Error” popup
This means that an error occurred on the server during DXXRDV request processing. The error was handled by the DevExpress Reporting server code, so the program execution was not interrupted and the client received a 200 response code. Implement a LoggerService to catch these errors on the server side and diagnose the problem based on the obtained error information.
See the Server Side Diagnostics section of the Reporting Application Diagnostics article for more information.
The Document Viewer displays an “Error when trying to populate the data source” popup.
This means that the report’s data source generated an error on the server. Detailed information about this error is hidden from the client for security reasons. To access the error on the server, implement a custom LoggerService.
See the Server Side Diagnostics section of the Reporting Application Diagnostics article for more information.
The Logger Service does not log any errors
Check if the service is implemented and registered correctly. If so, an error occurs before the DevExpress Reporting code runs. In this case, use your platform’s general error logging approach:
| Platform | Article |
|---|---|
| ASP.Net Web Forms, ASP.Net MVC |
Adding Error Logging Support |
| ASP.Net Core | Logging in .NET Core and ASP.NET Core |