I understand. If I get a chance to try it on a newer version of SSRS I will let you know 
1 Like
Hi enchev,
i have the same version (slightly newer) like you and the same problem as @ADefWebserver
http://[myserver]/Reportserver/Pages/ReportViewer.aspx?%2fTrentReports/[myreport]&rs:Command=Render&rs:Embed=true
in browser works fine after authentication
Thomas
I’m unable to reproduce the issue and that is why I cannot tell what’s causing it. The code of controller is part of the application provided for free and can be debugged.
@enchev I got access to a 2017 SSRS that is the exact same version of @ThomasS and my screen looks exactly like his. I zipped up the project and sent it to you as a private message. Hopefully that will help.
Hi @ADefWebserver most probably your project will work on my setup still I’ll try it tomorrow.
1 Like
I've checked the app now. There are two problems:
- Please change the report server from
http://localhost/reportservertohttp://localhost/ReportServer - Try to place the report in a sub folder with different name instead
reports. For exampleMyFolder
It works! Thank-you-so-much!
The answer is you cannot use:
http://{{YOUR SERVER}}/reportserver
You must use:
http://{{YOUR SERVER}}/ReportServer
2 Likes
Glad it worked! I’ll do my best to include fix to ignore the case in the next update.
Also it works on my 2016 (13.0.1601.5) SSRS too!
Yep, the issue was fixed immediately and the fix will be part of our next update!
Everything works fine locally, but, when I deploy to Azure (using the Deploy wizard on the deploy section). I get:
You probably need to change the report server setting as it seems to have an extra /443/ in the path. Again you can compare the URLs used with and without proxy.
This is what I have in the settings:
I don't have 443 in the settings at all.
This works fine locally, it only stops working when I publish to Azure.
Thanks
Then the only option is to compare the generated URLs with and without UseProxy. Unfortunately we don't have a SSRS hosted in Azure and cannot test.
I sent you the project by private message
Follow up: Radzen version [2.44.8 - 2020-04-02] fixed the issue with the Report viewer working on Azure.
1 Like
Hello,
for my part, using 2.46.2 I got this when using proxy.
At the Radzen app, here is what shown
And the Custom ReportController is like this
