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

HTML5 Asp.NET Viewer (not core)

1 Answer 15 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
David
Top achievements
Rank 1
Veteran
David asked on 07 Feb 2021, 12:50 AM

I have a large program with more than 20 reports which has been based on legacy Asp.net Web Forms Viewer.  Given the legacy state of that control I decided to try to tackle the HTML5 viewer.  

I have taken an existing project, forked it.  Added a HTML5 viewer template based solution.  That created a report controller which I had to customize.  I chose to implement a custom resolver and it seems to be working well.  In my development environment it works flawlessly.    When deployed to my production server nothing I do gets it working.  That server is as follows:

IIS 10 on Windows 2016 Server.

The error I keep getting is shown below.  Symptomatically it seems that the routing, again in production only, is not happening.  I have, to the best of my ability, implemented "CORS" although I am not sure I actually require it.  The URL shown below is correct.  I have tried using /Text/FInance/City-Import/api/reports/formats as suggested to no avail.  Again, no routing seems to be happening.

I have tried using Fiddler and Chrome tools to no avail. They provide no clues other than it is not working.

Can anyone aid my troubles with a pointer towards what to look for?  Given my successes on development IIS servers (older vintages), I suspect it might be something I have overlooked.  Hopefully someone has something for me to look it at.

 

(Error message I am fighting)

Cannot access the Reporting REST service. (serviceUrl = '/Test/Finance/City-Import/api/reports/'). Make sure the service address is correct and enable CORS if needed. (https://enable-cors.org)

1 Answer, 1 is accepted

Sort by
0
David
Top achievements
Rank 1
Veteran
answered on 07 Feb 2021, 04:45 PM

Well, I solved my own problem.  I tracked it down to an exception being raised during the constructor phase of the report controller.  The exception conditions did not exist EXCEPT in the production environment.  That explains why things worked everywhere but "real life".

Sorry to report a false condition.  Glad to see things are working finally.

My 2 cents on the HTML5 versus prior reporting viewers?  As a programmer I dislike the complexity of the steps required to render a report.  They are vastly more complex the previous.  They do render far faster now so I can see the trade off an why Telerik likely made the decisions they did.  Kudos on a great product.  I still think you need help on the interface but I can live with it. :-}

 

Tags
General Discussions
Asked by
David
Top achievements
Rank 1
Veteran
Answers by
David
Top achievements
Rank 1
Veteran
Share this question
or