Power BI Report Server May 2025 – Intermittent Status Code 500 Error After Upgrade

[ArwaAldoud]

Hi,
After upgrading to Power BI Report Server May 2025, I started encountering an intermittent error when opening reports. The error message is:
 
Something went wrong
Please try again later or contact support.
undefined
Status code: 500
Service version: /powerbi/libs

This issue:
- Happens randomly, without a specific pattern.
- Affects older reports and new ones.
- Appears to be server-side, as the error is generic and not tied to a specific report logic.
 
I’d like to understand:
- What is the root cause of this error?
- Are there any known issues with the May 2025 release?

[v-echaithra]

Hi @ArwaAldoud ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Best Regards,
Chaithra E.

[ArwaAldoud]

Hi @v-echaithra 

Thank you for following up. The issue has been resolved. I appreciate your support.

[R1k91]

have you already checked the PBIRS log files (ReportServerService_<timestamp>.log )?

you should be able to find stacktrace of the errors.

I've seen something similar happening after an upgrade (1-2 years ago) and it was related to subscriptions.

[v-echaithra · Accepted solution]

Hi @ArwaAldoud ,

Check Server Resources: Ensure the server has enough memory and CPU resources. Power BI Report Server can sometimes fail with a 500 error if there are insufficient resources. Check the server performance, especially during high load times. Make sure there’s adequate disk space, particularly where logs, reports, and temporary files are stored.

Review Logs: Examine the Power BI Report Server logs (typically located in the C:\Program Files\Microsoft Power BI Report Server\PBIRS\Logs) for detailed error messages. Check the ReportServerService.log and Rssrvpolicy.config for any specific error details that could help identify the root cause.

Database Connectivity: Ensure the Report Server can properly connect to the database. A disrupted or slow database connection might cause intermittent issues.
Check if there are any connectivity issues or timeouts between the Report Server and the underlying SQL Server or data source.

Clear the Cache: Sometimes cached data can cause problems. Clear the report cache and restart the Report Server to ensure it’s not an issue with old or corrupted cache data.

Review Configuration: Ensure the Power BI Report Server configuration in RSReportServer.config aligns with the latest settings recommended for your version. If there were any custom configurations or integrations with other services, verify they are compatible with the May 2025 version.

Contact Microsoft Support: If your issue still persists, please consider raising a support ticket for further assistance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

Hopefully, these steps help you resolve the intermittent 500 error. Let me know how it goes!
Thank you.

[ArwaAldoud]

Thank you so much for the detailed guidance.
You were absolutely right after checking the server metrics, we discovered the issue was caused by high utilization of server resources. Once we optimized resource allocation, the intermittent 500 error was resolved.

Appreciate your help and detailed explanation

[Thomaslleblanc]

Please create a support ticket with Microsoft to resolve issue.

[ArwaAldoud]

Hi @Thomaslleblanc 

Appreciate the advice. We found the issue was related to server resource utilization.