Forum Discussion
Problems with PBIRS on-prem January 2025
We have upgraded from the January 2024 on-prem PBIRS to the January 2025 version. We now have several reports that do not run that ran previously. Most have the following error:
O Search
Favorites
File v
DOL MS Report Server Home > Load Testing > CAA Time Tracker #3
Browse
View v
Edit in Power BI Desktop
Explore
Refresh
×
Close
Something went wrong
Unable to load the data model for your Power BI report.
Please try again later or contact support. If you contact support, please provide these details.
undefined
Request ID 6436cebe-682e-a43d-f4bc-e6be17bae345
Status code 500
Time Wed Jun 25 2025 09:43:52 GMT-0400 (Eastern Daylight Time)
Service version /powerbi/libs
When opening the report in Power BI Desktop, performing a refresh of the data, and trying to save the report back to the server, we get the following error:
Saving to Power BI Report Server
An error occurred while attempting to save the report to Power BI
Report Server.
Please HELP!
11 Replies
Hi MHaggerty_DOL,
Thank you for reaching out to the Microsoft fabric community forum.
This error has been encountered by several users following the January 2025 update of Power BI Report Server.
Please ensure you are opening the report with the Jan 2025 Power BI Desktop Report Server edition, not the standard Power BI Desktop. The correct version can be downloaded from the official Microsoft site if required.Within Power BI Desktop, navigate to Options > Data Load and clear the cache. After refreshing the report manually, use "Save As" to save it under a new name rather than overwriting the existing file.
Additionally, review your connectors or data source methods, as version updates can sometimes impact them.
If the issue persists, check the Report Server logs using the error’s Request ID for further details.
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily. If you continue to face issues, feel free to reach out to us for further assistance.
Best Regards,
Harshitha.I have installed the correct version. The log files have errors.
2025-06-26 00:00:09.6998|ERROR|152|Failed to publish model for 2d8ffe9e-79ee-4da2-b375-00ae4fe48097_926253845Microsoft.PowerBI.ReportServer.AsServer.AsConnectionException: Failed to publish model for 2d8ffe9e-79ee-4da2-b375-00ae4fe48097_926253845 ---> Microsoft.AnalysisServices.OperationException: M Engine error: 'Microsoft.Data.Mashup; The type initializer for 'Microsoft.Data.Mashup.MashupConnection' threw an exception.'.
#2:
2025-06-26 00:00:09.7154|ERROR|202|Error Processing Data Model Refresh: SessionId: 0a72e85d-5145-414c-8007-9583a5939064, Status: Error Failed Streaming model to Analysis Server, Exception System.AggregateException: One or more errors occurred. ---> Microsoft.PowerBI.ReportServer.AsServer.AsConnectionException: Failed to publish model for 2d8ffe9e-79ee-4da2-b375-00ae4fe48097_926253845 ---> Microsoft.AnalysisServices.OperationException: M Engine error: 'Microsoft.Data.Mashup; The type initializer for 'Microsoft.Data.Mashup.MashupConnection' threw an exception.'.
Here are some of the additional errors:
] RSPowerBI_2025_06_26_00_00_09.log - Notepad
File Edit Format View Help
at System. Threading. Tasks. Task'1. InnerInvoke()|
at System. Threading. Tasks. Task. Execute()
--- 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 Microsoft. PowerBI. ReportServer.AsServer. AnalysisServicesServer .< LoadDatabaseAsync>d_16.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 Microsoft. PowerBI. ReportServer. AsServer. AnalysisServicesServer .< LoadDatabaseForRefreshAsync>d_17.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 Microsoft.PowerBI. ReportServer.WebHost. EventHandler. AnalysisServicesDataRefresh .< LoadDatabase>d_23.MoveNext() <---2025-06-26 06:48:03.6449| ERROR | 73|Error Processing Data Model Refresh: SessionId: d95abfeb-01f7-4b26-8c3a-6de67580ee36, Status: Error Failed Data Refresh, Exception Microsoft.PowerBI.ReportServer.AsServer.AsConnect
at Microsoft.AnalysisServices.XmlaClient. SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError, Boolean useBinaryXml)
at Microsoft.AnalysisServices.XmlaClient. ImageLoad(String databaseName, String databaseId, Stream sourceDbStream, Boolean allowOverwrite, String readWriteMode)
at Microsoft.AnalysisServices.Core.Server. ImageLoad(ImageLoadInfo imageLoadInfo)
at Microsoft. PowerBI. ReportServer. AsServer. AnalysisServicesServer .< >c_DisplayClass47_0 .< LoadDatabaseInAsAsync>b_0()
--- End of inner exception stack trace ---
at Microsoft. PowerBI. ReportServer.WebHost. EventHandler. DataRefreshScope. ExecuteActionWithLogging(Action methodToExecute, String description, String localizedDescription, String messageInFailure, RefreshInfo refre
at Microsoft. PowerBI.ReportServer.WebHost. EventHandler. AnalysisServicesDataRefresh. RefreshData(RefreshInfo refreshInfo)
at Microsoft. PowerBI. ReportServer.WebHost. EventHandler.DataRefreshScope. <>c_DisplayClass34_0 .< ExecuteActionWithLogging>b_0()
at Microsoft. PowerBI. ReportServer.WebHost. EventHandler.DataRefreshScope .< ExecuteFuncWithLogging>d_33'1.MoveNext()
2025-06-26 06:50:03.6173|INFO|44|Handling event with data: TimeEntered: 6/26/2025 10:50:00 AM, Type: Event, SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, EventType: DataModelRefresh
2025-06-26 06:50:03.6173| INFO|44| Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Starting Data Refresh.
2025-06-26 06:50:03.6173|INFO| 44| Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Starting Retrieving PBIX AsDatabaseInfo.
2025-06-26 06:50:03.6329|INFO|90|Finding model for refresh sessionId=df6eb64f-9bfc-4042-98e7-674565b8a472, catalogId=2d8ffe9e-79ee-4da2-b375-00ae4fe48097, lastCatalogItemUpdate =8/24/2022 8:50:47 AM, lastModelUpdate
2025-06-26 06:50:03.6329| INFO| 44| Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Starting Verifying all the data sources are embedded.
2025-06-26 06:50:03.6329| INFO| 44| Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Starting Verifying connection strings are valid.
2025-06-26 06:50:03.6485|INFO| 44|Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Starting Streaming model to Analysis Server.
2025-06-26 06:50:03.7266|ERROR | 88|Failed to publish model for 2d8ffe9e-79ee-4da2-b375-00ae4fe48097_926253845Microsoft.PowerBI. ReportServer. AsServer. AsConnectionException: Failed to publish model for 2d8ffe9e-79ee-4at Microsoft. AnalysisServices. XmlaClient. SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError, Boolean useBinaryXml)
at Microsoft.AnalysisServices. XmlaClient. ImageLoad(String databaseName, String databaseId, Stream sourceDbStream, Boolean allowOverwrite, String readWriteMode)
at Microsoft.AnalysisServices.Core. Server. ImageLoad(ImageLoadInfo imageLoadInfo)
at Microsoft. PowerBI.ReportServer.AsServer. AnalysisServicesServer .< >c_DisplayClass47_0 .< LoadDatabaseInAsAsync>b_0()
--- End of inner exception stack trace ---
2025-06-26 06:50:03.7266| ERROR| 44|Error Processing Data Model Refresh: SessionId: df6eb64f-9bfc-4042-98e7-674565b8a472, Status: Error Failed Streaming model to Analysis Server, Exception System.AggregateException: (at Microsoft.AnalysisServices. XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError, Boolean useBinaryXml)
- 0
X
Ln 15761, Col 50
100% Windows (CRLF)
UTF-8
Opening the Desktop Client by right-clicking and selecting Run as Administrator opens the app, but attempting to open a report from the Report Server gives this error:
- Poojara_D12
Super User
The issue you're facing after upgrading from the January 2024 to the January 2025 version of Power BI Report Server (PBIRS) is a known challenge that sometimes arises during major version transitions—especially when report models or server configurations are not fully compatible between versions. The error you're seeing—"Unable to load the data model for your Power BI report" with a 500 status code—indicates a server-side failure, often due to unsupported model features, version mismatches between the Power BI Desktop you're using and the PBIRS version, or changes in how models are processed in the newer PBIRS engine.
One key requirement after a PBIRS upgrade is to ensure that you're using the exact same version of Power BI Desktop that matches the upgraded Report Server build—in your case, the January 2025 PBIRS-compatible Power BI Desktop (not the regular Power BI Desktop from the Microsoft Store or general release). If you use a mismatched or newer Desktop version to open and re-save reports, the file may include model features or metadata that the server doesn't yet support, leading to upload or rendering failures.
Another possible issue is that some reports may now include features (e.g., DAX functions, query transformations, or connector behaviors) that were supported or loosely tolerated in earlier PBIRS builds but are now strictly validated or enforced in the newer version. This could result in previously functional reports failing post-upgrade.
To resolve this:
Ensure you're using the PBIRS-aligned Power BI Desktop for January 2025 (download it from the PBIRS download page, not from the Store).
Open the failing reports in this Desktop version, refresh the data, and re-publish them to PBIRS.
If the error persists, inspect the data sources, model size, and transformations—especially in reports that use unsupported features like calculated tables, unsupported visuals, or newer DAX functions not fully compatible with PBIRS.
Also, review the PBIRS server logs (RSHostingService.log, ReportServerService_*.log) around the timestamp of the error. These logs often give more detailed error messages than the generic UI.
In summary, this issue is most likely due to version incompatibility between your Power BI Desktop and the upgraded PBIRS, or due to newer validations in the PBIRS rendering engine that weren't enforced in the prior version. Aligning the tools and reviewing logs should guide you toward resolving the failures.
