Forum Discussion
Power BI Report Server January 2026 – msmdsrv restarts, SQLDmpr files
Hi JacksonWearne ,
We experienced the same issue after upgrading to the January 2026 Power BI Report Server release (msmdsrv restarts and continuous SQLDmpr dump generation).
We opened a support case with Microsoft, and they confirmed this is a known issue in this release. The product team is currently working on a fix.
Temporary Workaround (from Microsoft Support)
Until a fixed build is released, Microsoft advised deleting the generated mini dump files to prevent disk exhaustion:
Default path:
C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFilesDelete files ending with:
.mdmpThis is only a temporary mitigation and does not resolve the root cause.
You can monitor the official PBIRS changelog for updates:
https://learn.microsoft.com/power-bi/report-server/changelog
If this response was helpful, please accept it as a solution and give kudos to support other community members
Hi JacksonWearne ,
After upgrading to the January 2026 release of Power BI Report Server, intermittent msmdsrv.exe restarts and repeated SQLDmpr dump files should be resolved by following Microsoft’s troubleshooting steps for embedded SQL Server Analysis Services. Ensure that your server and Power BI Desktop for Report Server versions match, and open, re-save, and republish reports using the January 2026 Desktop build to avoid metadata issues from the standard cloud version. Reset the Analysis Services workspace by stopping the Report Server service, deleting the PBIRS\ASEngine\Workspaces folder contents, and restarting the service so tabular models reload cleanly. Check the January 2026 release notes for known issues or hotfixes and apply any suggested fixes. If SQLDmpr files continue to appear, you can temporarily limit dump generation through Windows Error Reporting to prevent disk space issues while keeping samples for analysis. Also, verify that the PBIRS service account has proper read/write permissions to the installation path, ASEngine workspace, temp directories, and ReportServer databases, as permission errors can cause instability. If problems persist, Microsoft recommends opening a support case and providing SQLDmpr files, msmdsrv.log, PBIRS trace logs, and the build number. For production environments where stability is essential and the issue started after the upgrade, you can uninstall the current PBIRS version and reinstall the previous supported release, restoring encryption keys and databases to return to a stable state.
Microsoft Documentation Reference
https://learn.microsoft.com/power-bi/report-server/
https://learn.microsoft.com/power-bi/report-server/get-started
https://learn.microsoft.com/troubleshoot/sql/tools/use-sqldumper-generate-dump-file
https://learn.microsoft.com/windows/win32/wer/collecting-user-mode-dumps
https://learn.microsoft.com/power-bi/report-server/changelog
Thank you.
Hi,
Thank you for your response! I have gone through all of these steps in order to troubleshoot this issue and none fixed the problem... I have found out in the meantime, that these dumps primarily occur upon uploading/rendering a report. I don't have access to open a support case.
In deleting and regenerating the workspace folder contents, the files all regenerated, but I saw the error persitst.
A similar remedy I have seen is renaming the ASEngine\workspaces folder to workspaces_old and have the report server restart rebuild that folder. I have ensured the service account has write access to ASEngine (as well as workspaces), and that does not seem to work either.
Are there any other potential solutions to this?
Hi JacksonWearne ,
If the issue persists after isolating the report and testing the above steps, this may indicate an Analysis Services engine level issue. In that case, Microsoft would need to review the generated dump files for deeper investigation.If you have a Power BI Pro license (or your organization has a valid support plan), you should be able to raise a support ticket directly using the official process here:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketEven if you personally don’t have access to create a support ticket, you may want to escalate internally to your Global Admin, as they can raise a support request on your behalf.
Hi JacksonWearne ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
