Expose ReportController Errors

[Kori]

Hi,

I've been seeing this issue for a long time, but I can't seem to find where to log the errors that are being thrown when users are generating reports with the WebAPI/HTML5 report viewer.

I see tons of exceptions happening that look like this:

* /api/reports/clients/094113-ecd1/instances/094113-5731/documents/094113-aabb094141-da97 - 500 Internal Server Error

* /api/reports/clients/094843-e940/instances/095003-e56b/documents/095003-5023095009-20af - 500 Internal Server Error

* /api/reports/clients/112823-f291/instances/113024-cb46/documents/113024-837d113030-be3d - 500 Internal Server Error

* /api/reports/clients/112823-f291/instances/113219-b3dd/documents/113219-bc2d113229-8387 - 500 Internal Server Error

Is there anything I can do to catch these? Is it as simple as adding a filter to catch the webapi unhandled exceptions and logging them?

 

[Stef]

Hi,

You can add filters for specific errors. If there is an error message displayed in the viewer, you can catch the error at the client through the viewer's error event. Please consider the examples posted in the HTML5 Report Viewer - Custom Error Message from Custom Report Resolver forum thread (the case is not specific for custom resolvers).

On a side note, internal errors may be result of misconfiguration or issues on the server where reports are rendered. Please check the error message delivered with the response of the failing requests and post the details.

Regards,
Stef
Telerik

[Krishna Sumanth]

Hi .any luck

[Kori]

No, no luck here. Users are still seeing periodic errors and I can't capture them since I can't reproduce.

[Katia]

Hello kfrancis,

Is it possible to ask some of the users that reproduce the errors to capture the application requests using Fiddler? To create a trace they will need to use Fiddler > File > Save > All sessions option.
You can forward the produced trace file to us via ticketing system or post the information about requests sent by HTML5 viewer here. This way we can check more detailed information about requests and the error messages. Information about request can be seen in Fiddler > Inspectors > Raw tab.


Regards,
Katia
Progress Telerik

[Krishna Sumanth]

Hi ,

I am getting this issue when in api servers where telerik rest services were is in load balancer. and reportviwer in web are also in load balancers.

If i stopped one web server and one api server report works fine

Thanks,

Sumanth

[Todor]

Hi Sumanth,

The problem might occur when using File cache or Database cache IStorage interface implementation in WebFarm.
For WebFarms we recommend using MsSqlServerStorage or RedisStorage. Check this article for more details.

Regards,
Todor
Progress Telerik