Forum Discussion
reportserver error after 2023-May update (custom authentication)
Hello,
Last week we upgraded from 2021-Sep to 2023-May.
Previously, when accessing the bi portal using custom authentication, the following url was used.
https://domain_name/ReportServer/logon.aspx?ReturnUrl=/ReportServer/localredirect?url=%252freports%252f
But after update, the following error occurs when connecting to bi portal home.
webserver!ReportServer_0-3!74f0!07/10/2023-09:00:52:: e ERROR: RS.Server.HttpHandlerError {"shortHttpDescription":"Server Error","code":"500","path":"reportServiceHandlerWriteError","exceptionType":"Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException"}
runningrequests!ReportServer_0-3!9f14!07/10/2023-09:02:08:: w WARN: localredirect has been rejected as redirect URL does not point to registered local directory! URL: /reports
library!ReportServer_0-3!9f14!07/10/2023-09:02:08:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: , Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.AbortCurrentThread()
at Microsoft.ReportingServices.WebServer.Global.DispatchRequest()
at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
--- End of inner exception stack trace ---;
webserver!ReportServer_0-3!9f14!07/10/2023-09:02:08:: e ERROR: RS.Server.HttpHandlerError {"shortHttpDescription":"Server Error","code":"500","path":"reportServiceHandlerWriteError","exceptionType":"Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException"}
As an interim measure
we eliminated url encoding and changed url setting as below and we could connect bi portal.
But the rs:embed=true option is not working properly and specific folder open is not possible now.
https://Domain Name/ReportServer/logon.aspx?ReturnUrl=/reports/
It's been too long since the 2021-sep version, and it seems that there have been changes in url processing.
Please help us in what part to take action.
4 Replies
a) Do you have backup of these files? If yes, compare these current files vs backup files
- RSReportServer.config,
- ReportingServicesService.exe.config, and
- RSReportDesigner.config.
I am suspecting you might have configured custom or forms authentication and this need to be reconfigured.
Check this link for details:
b) Also, check the Report Server Configuration Manager
check the web service URL, web portal URL working fine? (from local server and from your computer)
c) Check the report server logs, event viewer for all details
Hope this helps!
I've compared configuration files but no suspect points are found.
And we didn't change any of custom authentication sources during upgrade. 😞
Thank you for your advice.
I am aware report embedding had some issues in 2020 updates but not after 2021.
https://learn.microsoft.com/en-us/power-bi/report-server/changelog
Can you try the customheaders changes like mentioned in this one? ***Take backup before you do any server config changes***
hi... i know this reply is way late.. but i had this exact same error and i hope my reply may help someone else who stumbles upon this error. We did also upgrade to the may version but also migrated to a different server (we are using forms/custom auth) so ours was a bit more complex. Tho... as i said, we had the same error. in the end...
It appears that the <VirtualDirectory>Reports</VirtualDirectory> within the InstallDrive\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\reportserver.config ..... IS case sensitive !!! This obviously is a bug.
So i changed the VirtualDirectory to : <VirtualDirectory>reports</VirtualDirectory> and it works, or if you use https://pbiserver.com/Reports vs https://pbiserver.com/reports
More users with the same issue
https://community.fabric.microsoft.com/t5/Issues/Report-Server-September-2019-instance-name-in-URL-suddenly-case/idi-p/804401 Seems there is an update for PBI that addresses this. (see last post in that thread)
