power bi report server upgrade problem

6 Topics

Power BI Report Server January 2025 Upgrade - No (.pbix) Reports will open, "An error has occurred"
Hello, I recently upgraded Power BI Report Server to the January 2025 release and Power BI Desktop for RS to January 2025 version. Now when I navigate through the portal url to access reports, Paginated reports load as expected but all Power BI (.pbix) reports when clicked on to open render, "An error has occurred. Something went wrong. Please try again later." dialogue box. Same for any attempts to click the three-dots for other options. After digging into the logs at C:\Program Files\Microsoft Power BI Report Server\XXXXX\LogFiles, I found the entry noted further below. Not sure if worth noting, but this is for our Dev server which can only be accessed currently as HTTP and not HTTPS? Dev: http://xxxxx-dev/bi-Reports/ Prod: https://xxxxx-prod/bi-Reports/ or http://xxxxx-prod/bi-Reports/ Does anyone have any thoughts on how to resolve? I inherited this system for upgrade after my team lead left, and know more about using Power BI Report Server and Development than Configuration. Thanks! 2025-03-14 09:05:10.3352|ERROR|45|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.V2.Controllers.CatalogItemsController.GetEntity(String key, String castName) at Microsoft.ReportingServices.Portal.ODataWebApi.Controllers.Reflection.EntitySetReflectionODataController`1.GetRoot(ODataPath oDataPath, Int32& index) 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__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.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__6.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__6.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__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.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_f0aaefca-1a6b-4716-b40d-54cc08f5ccdd 2025-03-14 09:05:10.3352|INFO|71|Sending response. Response code XXXXDOM\XXXXXXXX 500, Elapsed time 0:00:00.0211895| RequestID = s_f0aaefca-1a6b-4716-b40d-54cc08f5ccdd
Solved
JScurlock
1 year ago Place Report Server
1.6KViews
0likes
2Comments
i wanna upgrade PowerBi server to the latest version so i can upload my reports that i build in powe
Hey PowerBi community, I'm currently facing a frustrating issue with Power BI Desktop and Power BI Report Server, and I'm seeking some guidance. Here are the details: Problem: I'm encountering an error stating, "We cannot load this report. It was created with a recent version of Power BI Desktop that is not yet supported by this server," when trying to upload a report to Power BI Report Server. What I've Tried: - UpdatedPower BI Report Server to the latest version(not sure if it was the right way i just download the latest version i did an upgrade). Versions: - Power BI Desktop: December 2023 - Power BI Report Server: January 2023
Solved
Mohammed_K
2 years ago Place Report Server
1KViews
1like
1Comment
After upgraded the new Power bi report server,we lost the connect string.
Dear All: I got a problem about upgrade the new version( 2022 may. upgrade to 2022 sep. or upgrade to 2023 jan.), all connection string change to garbled text. ( like below picture) I has been studied other message about this error and try to restart the server ( no matter windows server & report server ) but it's still not work,so i think i need more help. Thanks for heated any suggestion.
Ray-Chiou
3 years ago Place Report Server
563Views
0likes
1Comment
Just upgraded to the latest (January 2023) PowerBI - Now Home Page Blank
Just upgraded to the latest version of Power BI (January 2023) and the Home page is now blank for average users. It states "Could not load folder contents. Something went wrong. Please try again later." For those of us that are administrattors on the SQL Server the Home page loads just fine. After doing some testing, I found that if I take a normal user and add them to teh Administrators (local) on the SQL Server that is running Power BI, the Home page will load just fine. Also found that if we send the normal user the link to their requested report in the subfolders from the Home page that they can access the page just fine and run their needed report. Teh issue is something with permissions around users loading the Home page. I tried adding users to "Power Users" (local) security group and that did not help. Everything was working on the previous version of Power BI (a 2019 version).
serobertson03
3 years ago Place Report Server
555Views
0likes
0Comments
How to update Power BI Report Server Version from Jan2021 to latest version
Hi, Can anyone please help me in guiding/ provide the steps on how to update Power BI Report Server Version from jan2021 to latest version in detail. we are using the PBI report server jan2021 version, need to update the prod server version to latest version power bi report server. we have multiple paginated reports which are having the data driven subscriptions which sends the eamils to 300+ users daily. we need to know whether all these subscriptions will remains as is when we upgrade the version or not? and if we have any process to backup these subscriptions then please guide how it can be done? Regards, Sravani
Solved
Anonymous
4 years ago Place Report Server
4.3KViews
0likes
2Comments
Being Asked For License Key During Power BI Report Server Upgrade
Running the file PowerBIReportServer.exe on the VM hosting our on-prem Power BI Report Server does not give us the option to Upgrade. It only gives us the option to Install and then asks for a license key. We don't want a new installation to overwrite our configurations. We are licensed for the Power BI Report Server through a SQL Server Enterprise 2016 product key. We are upgrading from PBIRS version January 2020 to January 2021. The executable was downloaded from the link below. Shown in the attachment is what we see after launching the executable - an option to "Install" Power BI Report Server, NOT to "Upgrade". It should be able to tell that Power BI Report Server is already installed on the machine. https://powerbi.microsoft.com/en-us/report-server/
Solved
Patt_N
5 years ago Place Report Server
1.8KViews
0likes
2Comments