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 RS – Error “Unable to create secure SSL/TLS channel” for one user (MinIO connection)
Hello, I'm encountering an issue with a Power BI Report Server (RS) connection to a MinIO source. The connection works perfectly on my machine, but not for another user that I assit, even though we are using the same Power BI RS version (installed via our company software center). Here's the situation: 🔹 I can connect to the Excel file hosted on MinIO via Web.Contents without any problem. 🔹 The other user receives this error: "Unable to create a secure SSL/TLS channel." We have verified the following: ✅ The user has access to the MinIO source via the browser (URL works). ✅ The user has access rights and the required role for the MinIO bucket. ✅ I tested with his accessKey/secretKey on my machine — and it worked fine. ✅ TLS 1.2 is enabled on both our machines (tested with PowerShell)=>but not sure of its efficacity ✅ Power BI Desktop settings were checked: certificate revocation level set to “None” for testing — same result. ✅ Registry entries under both HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 and WOW6432Node were checked — no SchUseStrongCrypto key found. It feels like a local machine or .NET config issue, but I can't pinpoint what blocks TLS/SSL on his machine only. 🔍 Any ideas or directions? Could this be tied to missing .NET patches, RS policies, or group security settings? Has anyone else dealt with MinIO access via Power BI RS in this context? Thanks a lot in advance! - we both use the same version of power Bi RS and i tired with service too
SSL Certificate Validation turning off
Hello! i am facing an issue with the power bi report, when i try to post it on powerbi publish it get pubished but when i try to refresh the data there it shows me this error: Can anyone tell me how to turn of the SSL validation in the publish area as i have already turned it off in the powerbi desktop but it still shows me this error.Problem after SSL certificate expired
On one of our PBIRS servers, the SSL certificate expired. We installed a new certificate, switched the bindings for Web Portal & Web Service to point to the new certificate and removed the old one, but now we are encountering problems when accessing any report via the portal. This is the error message: In our log file we have this message, corresponding to when someone clicks a report: 2023-07-12 14:51:36.7074|ERROR|12|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. at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at Microsoft.ReportingServices.Portal.ODataWebApi.Utils.PbixReportHelper.ShouldReShred(PowerBIReport entity, Uri basePortalUrl, ILogger logger, IPrincipal userPrincipal, String reportServerHostName) at Microsoft.ReportingServices.Portal.ODataWebApi.Common.CatalogItemControllerHelper`1.GetItem(String key) at Microsoft.ReportingServices.Portal.ODataWebApi.Common.CatalogItemControllerHelper`1.GetAllowedActions(String Id) at Microsoft.ReportingServices.Portal.ODataWebApi.V2.Controllers.PowerBIReportsController.GetAllowedActions(String Id) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass6_2.<GetExecutor>b__2(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__1.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__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.Controllers.ExceptionFilterResult.<ExecuteAsync>d__6.MoveNext().| RequestID = s_34e542e5-abf2-4042-984b-76dedbf4432c We were running the Jan 2023 version of PBIRS, and tried upgrading to May 2023 to resolve, but the problem remains. Any suggestions for fixing this are appreciated.
Port 80 requirement for /Reports and /ReportServer
Hi, I have added a certificate (not self signed) and enabled SSL on our development server. The first hurdle was that the alternate machine names were not recognised by the power bi server (!!). This article fixed that: https://support.microsoft.com/en-sg/help/2418246/you-cannot-view-some-of-your-ssl-certificates-in-reporting-services-co However when I disabled the port 80 bindings, I could no longer upload reports from the desktop, despite referencing the server on :443. The 3-dots menu on each report no longer works either. It seems you *must* have port 80 enabled to use report server. Can anyone confirm this is true and/or offer a way for us to work solely over SSL?https configuration
hi i have Microsoft Power BI Report Server Version 15.0.1110.120 i want to config HTTPS and i set this configuration: and below configuration but ihave problem when i want to login to reportserver or server when i want to login with this below link i can not login and face agein login page: https://*********/ReportServer what should i do?Unable to connect to Amazon Redshift - SSL certificate verification error
Recently I've encountered the following error while trying to connect to Redshift through Powerbi: However, i would like to mention that while using the same credentials, server address etc. i am able to successfully connectto my database while using a query program such as Dbeaver for eg. Any ideas what might cause this issue? Many thanks !Unable open any reports from the power bi report sever using https
Hi All, I have installed powerbi report server May2022 and uploaded one reports It is working fine with http. I installed SSL certificate and configured https from the report server manager as below, howerver unable to open the report When I open the report getting below error screen. working perfectly with http Report Server config Note: With https we can able to upload, download and delete the reports from the report server. unable to view the reports. Cretificate url is working as below Thanks in Advance,PostgreSQL- Publish Error
I'm having an issue around published dashboard that connect to PostgreSQL that do not work. From my Power BI desktop, I can connect to PostgreSQL and build a (direct query) viz with no issues. I can even publish and get the "success" window. However, when I go to view the published dashboard, I get an access error about credentials. I have not modified anything on the PostgreSQL/ AWS side, but I'm wondering if there is something outside of Power BI that needs to be modified (maybe ralated to SSL)? Thank you. Thank you in advanced
