Power BI Report Server Scale-Out Issue - Reports Visible from One Node but Empty Folder from Another
Hi Folks I am experiencing a weird issue on newly built servers where I have migrated the report server databases from SQL 2017 to SQL 2025 and Powerb Report server (May 2026) is installed in a scale out deployment on the same SQL AG nodes. Environment Power BI Report Server (Native Mode) 2-node scale-out deployment ReportServer database hosted on a SQL Server Always On Availability Group Access through a cluster/network name (virtual hostname) HTTPS configured using a new SSL certificate Both PBIRS nodes point to the same ReportServer database The PBIRS web portal loads successfully on both nodes. Authentication succeeds. However, it always displays "This folder is empty message" when webportal is accessesed from primary replica node. When requests are served by Node B, All reports and folders are displayed correctly. The behavior appears to follow the active hosting node rather than the user account. Has anyone come across this issue or have a clue on what is going on? Thanks in advance.
ReportServer database procedures are continuously getting recreated in scale-out deployment
Hi, In a scale-out setup with two nodes, we started by having a standalone instance with May 2024 version, joined another one with Jan 2025 version, and started to have some transient issues (see related issue below). We followed the recommendation and brought both instances to Jan 2025 version by upgrading the first one too. They are now both at: Version1.22.9153.7886 (January 2025). We are still encountering some transient errors with the message "An error occured within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError)" BUT we caught an instance where the detail message was: "Could not find stored procedure 'GetSnapshotPromotedInfo'". We immediately asked the DBAs to check for this procedure, and it existed in the RS database, but its created_date was very recent (few minutes behind) and almost half an hour after we encountered the above message. Upon further checks it seems that this procedure is re-created regularly as created_date changes constantly. We then checked another separate instance that we have for a few years now, and on that one the created_date is very old, even though the instance is heavily used (over 20k executions daily). We believe that recreating these objects is actually not a normal behavior, and it might have something to do with the scale-out. 1. It's possible that the ReportServer database got somehow messed up because we had two versions of PBI RS connected to it? 2. What would be the best course of action to repair it without reinstall? note: there were also other stored procedures that were initially not found which are most likely in the same situation - with this particular one we dug deeper to check it. Thank you!
No scale-out deployment after upgrade PBIRS to May 2023
Hello , I conducted a test to upgrade the Power BI report from Sep 2021 to May 2023. My Power BI server utilizes SQL Server 2014 Standard Edition SP3, and I have four Power BI report servers connected to the same repository. During Sep 2021, in the scale-out deployment section, it still displayed information about the four nodes. However, after upgrading the Power BI report server to May 2023, the scale-out deployment section disappeared. Additionally, when attempting to restore the encryption key, errors occurred. Is there anyone familiar with this particular issue?Scale-out deployment - weird behavior on one server
Hello All! I have really weird situation happening on my scale out deployment. I have two servers that are connecting to MSaaS environment. Both servers are in version Jan 2021. Before them I have loadbalance URL that is distributing users between servers. For some reports, rather bigger than smaller, loading time is sometimes very long, counted in minutes and sometimes report never loads. When I clear cache problem usually disappears but happening pretty quickly again. I turned on developer tools and I found out that this long loading time is only happening with server which was connected as second in the scale out. Additionally all is being stuck on ModelsAndExploration, without new data being transferred. Eventually it ends with error message. I will paste screenshots tomorrow as I am off work already, but I am kinda running out of ideas what it could be - only on one server, and always the same one... Hardware and setup is identical. Edit: Please see error message and response from server:
"Datasource XXXXXX Not Found" PowerBI Refresh issues
Hi community! After installation of the Release May 2021 the error for the "Datasource XXXXXX Not Found" PowerBI Refresh issues are gone for the primary node of a Scale out Deployment. But for the second member the same error exists. The primary node in our landscape hosts the portal and the secondary node has the role "IsDataModelRefreshService". In both config.json the new setting "Hosting-databaseValidationStatus" is available. Does anyone have the same problems? Is there a special setting needed for the second scaleout member?
Scale-out Power BI Report Server behind HAProxy
Hello there, I'm exploring on-premise scale-out option and I would like to ask for some help. I'm using two Report Server nodes (version January 2021) and database in dedicated AlwaysOn SQL Server cluster. HAproxy as NLB in front of everything, designed to forward all traffic to one (master) node. Currently I'm able to connect to https://test-powerbi.domain.com/ NLB or directly to both nodes (https://server-1/Reports), browse folder structure, create/delete folders, but I'm unable to perform any action with reports: Error in logs is following: OData exception occurred: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. My scale-out solution is using same configuration and certificates as my other single-instance Report Servers (they all work just fine). All certificates are present in certstore of both machines and used in both Web Service and Web Portal configurations: My first thought was that NLB is messing with my certificate chain, but the same error is occuring even if I go directly to each node. I browsed other posts here and modified rsreportserver.config by adding Hostname and UrlRoot (same for both nodes): <Hostname>test-powerbi.domain.com</Hostname> <UrlRoot>https://test-powerbi.domain.com/ReportServer</UrlRoot> and ReportServerUrl (different for each node): <ReportServerUrl>https://server-1.domain.com/ReportServer</ReportServerUrl> I also created new multi-string value BackConnectionHostNames in registers with ServerName and FQDN (different for each node): "server-1", "server-1.domain.com" None of this helped, so I decided to stop trying with HTTPS and go back to HTTP, so I removed all certificates from configuration and re-added Web Server and Web Portal configurations and modified "https" into "http" in mentioned rsreportserver.config values, but to my amazement the issue remains exactly the same: So even if no certificates are used (https calls return 503 errors) in whole Report Server service, my http call directly to Report Server node still return invalid remote certificate. Considering that everything works perfectly, only actions with reports are failing, I expect that I made some mistake in report server configuration. Would be great if anyone pointed out what I missed. Thanks in advance MajkPBI Report Server dedicated to Subscriptions execution only
Anyone knows if Power BI report server when in a scale out configuration allows a specific server to be dedicated only to executing subscriptions? I think this was available as a conf in SSRS but I am not sure if this is configurable in PBIRS.PowerBI Report Server - The request failed with HTTP status 401: Unauthorized
I have 2 PowerBI Report Server installed in a scale-out deployment with a network load balancer. I followed the instructions described in https://docs.microsoft.com/en-us/sql/reporting-services/report-server/configure-a-report-server-on-a-network-load-balancing-cluster?view=sql-server-2017 In step 3 i configured BackConnectionHostNames, the netbios and fqdn for the loadbalancer. Also grant local security policies to the service account. I can login in the report portal on the load balancer URL. From PowerBI Desktop for reporting services i can reach the report server on the load balancer URL, but when trying to save or upload a report to the report server i receive the following message: In RSPortal.log: 2019-09-27 09:09:08.2137|ERROR|10|The remote server returned an error: (400) Bad Request.| RequestID = s_4c682cad-3eeb-41c2-8932-91d524c62e15 When trying to create a data source i cannot type a name and after a few seconds a error message appears: In RSPortal.log: 2019-09-27 08:55:35.7605|ERROR|33|OData exception occurred: System.Net.WebException: The request failed with HTTP status 401: Unauthorized. at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol() at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol) at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.ListExtensions(String extensionType) at Microsoft.ReportingServices.Portal.Services.SoapProxy.SoapAuthenticationHelper.ExecuteWithWindowsAuth[TReturn](SoapHttpClientProtocol soapClient, IPrincipal userPrincipal, Func`1 func) at Microsoft.ReportingServices.Portal.Repositories.SystemService.GetExtensions(IPrincipal userPrincipal, ExtensionType extensionType) at Microsoft.ReportingServices.Portal.Repositories.SystemService.ListExtensions(IPrincipal userPrincipal, ExtensionType extensionType) at Microsoft.ReportingServices.Portal.ODataWebApi.V2.Controllers.ExtensionsController.GetEntitySet(String castName) at Microsoft.ReportingServices.Portal.ODataWebApi.Controllers.Reflection.ReflectionODataController`1.Get(ODataPath oDataPath) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext().| RequestID = s_4172f9a5-09ad-4a77-8444-39d8591c710e Would be glad if anyone can help. Thanks, JE
