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.
Power BI Report Server Service Issue
Users complain about reports are not opening and giving error "Unable to load Data Model". When we connect to the machine we checked Memory & CPU both were fine & we thought that there might be a Service issue so we restarted the service but receive the following error then we tried to change the service user to admin any applied changes in the Report Server configuration still we received the following error System.InvalidOperationException: Cannot start service PowerBIReportServer on computer 'Server'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at ReportServicesConfigUI.Panels.ConfigurationPanelWithErrors.StartOrStopServiceTask(Boolean start, String serviceName)
Bug - New Card visual in 202601 PBIRS (Updated)
Dear MS, here is the change log: Change log for Power BI Report Server - Power BI | Microsoft Learn i have tried the latest version of PBIRS, but there is still a bug on New Card visual. bugs: 1. can not show the category column. 2. can not apply any style i have set in format pane. when i open the report which has New Card visual, the DevTool shows 3 errors: (i don't know whether these errors are related to the New Card visual) 1. GET https://testmachine.aaaa.com/powerbi/libs/scripts/stylelibrary.js net::ERR_ABORTED 404 (Not Found) 2. Refused to execute script from 'https://testmachine.aaaa.com/powerbi/libs/scripts/stylelibrary.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled. 3. ERROR NullInjectorError: R3InjectorError(y)[InjectionToken CopilotCapabilityService -> InjectionToken AgentMetadataService -> InjectionToken PBICopilotProxy -> InjectionToken PBICopilotProxy] reportServerHostModern.js:158 btw, i have confirmed that the bug of button slicer is fixed.
Failed to connect to AS
I currently have a server running PBIRS Version 1.25.9558.32914 (January 2026), and I'm experiencing this type of error on several dashboards during automatic refreshes. " Failed to connect to AS " What could be the problem? The server resources aren't overloaded, as I've monitored the CPU and RAM usage during these refreshes. What can I check, given that this is happening so frequently?
PBIRS with Custom Authentication in Non-Domain Environment
Due to various operational constraints, our Power BI Report Server (PBIRS) has to be deployed in a non-domain environment. The Windows authentication mechanism in PBIRS has proven to be very cumbersome. Specifically, when the webpage loads, the call to the `api/v2.0/me` endpoint consistently takes 6-7 seconds to complete, which severely degrades the user experience. Additionally, we've encountered a critical issue: Power BI Desktop and the Power BI mobile app are unable to connect to the report server via the REST API when Custom Authentication is enabled. This has been a long-standing problem that has significantly impacted our daily workflow. We sincerely hope the official team can prioritize and optimize this as soon as possible. It would be greatly appreciated if compatibility with Power BI Desktop and the Power BI app under Custom Authentication could be added in a future update. Without this improvement, our daily work will remain very inconvenient, which is truly disappointing. Looking forward to your timely updates. Petebro
