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)