404 on /api/reports/version

[sitefinitysteve]

I am using reporting 15.2 in Sitefinity 14.3, works great

Updated to sitefinity 15.3 copied over all the reporting assemblies and now it's throwing this error

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

It's clearly not CORS related, but the 404 not found is weird.  Any thoughts?

 

Request URL

https://dev.x.ca/api/reports/version

Request Method

GET

Status Code

404 Not Found

[Lance | Senior Manager Technical Support]

Hi Steve,

I would recommend opening this in the Sitefinity forums. The Sitefinity environment change is what is apparently causing the difference and we cannot advise on the Sitefinity side of things.

The error you shared looks like it is copy/pasted from the HTML5 ReportViewer, and it means there is no REST service running at the URL you put into the HTML5 ReportViewer.

When you get connected with someone form Sitefinity, please also share the following information:

• The version of Telerik Reporting you're using
• Share the errors from your TraceListener logs (see Cannot access the Reporting REST service. Enable CORS if needed for some suggestions, including our recommendation to enable TraceListener ).

My guess is there was some changes in Sitefinity between those major versions, and there are considerations when upgrading. However, this is within Sitefinity's environment. when you do connected to someone in the Sitefinity team, you can tell them to reach out to me internally if they have any Telerik Reporting questions.

[sitefinitysteve]

Oh they wont know ANYTHING since it's not really "there" or used :/. I think it was added years ago for eComm which they killed.  This is me downloading it from my telerik products and adding it to BIN.

It's NOT CORS related, its all same domain

Yeah it might be like a newer version of webapi or some other microsoft assembly, they won't touch this at all so I guess I'll have to just migrate off telerik reporting into local grids or something instead.

Thanks for the links

[Lance | Senior Manager Technical Support]

Ah, so you're sort of ad-hoc'ing the REST service. I would highly recommend starting at the top, a lot has changed in the past 2 years in Telerik Reporting. Lots of optimization, security improvements, rendering system improvements (i.e. adding Skia rendering), adding minimal API config and more.

Here's where I would start => ASP.NET Core Web API Implementation Overview. Once you've gone through that, then choose one of the implementation approaches you want to use:

they all implement the REST service in an ASP.NET core host project, but with a different approach.

[sitefinitysteve]

Iit's not .Core though, 4.8 MVC

All the routes are (still) registered in global.asax.cs (as they have been for 5ish years), but it's just a black box atm and I can't debug what might be going on, there's no errors, just routes not working (now).

[Lance | Senior Manager Technical Support]

My apologies, not a problem, just shift up one section in the docs where we have the MVC stuff

Indeed, I can't imagine how you'd be able to get better diagnostic information if the routes are not wired up (meaning the REST service isn't actually hosted yet).  Just in case, have you enabled a TraceListener? That will catch any Telerik Reporting errors, but as you suspect, the app isn't' even getting to the point where it might throw an error starting up with service.