This is a migrated thread and some comments may be shown as answers.

HTML5 ReportViewer - Works in localhost with SQL storage

2 Answers 23 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Jon
Top achievements
Rank 1
Jon asked on 13 Sep 2017, 04:04 AM

Any suggestions on how to figure out why a report will never finish processing when deployed to a web farm, but works great on my local machine?

When the c# web app with the Telerik REST service setup with it runs on the web server there are no errors displayed. In Fiddler the ReportViewer keeps waiting for the report to finish processing and just returns the 202 Accepted response nonstop. On my localhost it will return 200 OK and render the report catalog properly.

GET  /api/reports/clients/{clientId}/instances/{instanceId}/documents/{documentId}/info

http://docs.telerik.com/reporting/telerik-reporting-rest-documents-api-get-document-info

http://docs.telerik.com/reporting/t-telerik-reporting-cache-mssqlserverstorage

 

2 Answers, 1 is accepted

Sort by
0
Lucas Boshoff-James
Top achievements
Rank 1
answered on 29 Jan 2018, 09:25 PM
I have this exact problem.  It also seems to be intermittent, or perhaps breaks only on some deployments.  Very frustrating.  Has anyone found a solution?
0
Lucas Boshoff-James
Top achievements
Rank 1
answered on 29 Jan 2018, 10:32 PM
I just solved this on my own production servers. In my case ther reports did indeed render but took up to about 5 minutes, and always showed broken images. In my case the problem wasn't so much the sql server, it was the photobox's on the reports.  The url provided to them was correct and did resolve from outside.  By adding an entry to my host file for the internal ip of the site I host my images with, the problem was fixed and the reports now render instantly (with working images).  Hope this helps, it had me stumped for a long time.
Tags
General Discussions
Asked by
Jon
Top achievements
Rank 1
Answers by
Lucas Boshoff-James
Top achievements
Rank 1
Share this question
or