Power BI Report Server- Loading report in Web page gives undefined error with status code 500

[Dhivya_123456]

In Power BI report server, when we open report it loads for a long time and gives the below error
------
Something went wrong
Please try again later or contact support. If you contact support, please provide these details.
undefined:
Request ID: 97e3ad1c-46e0-6128-a7ae-17c06e10712f
Status code: 500
Time: Tue Sep 16 2025 09:30:48 GMT+0400 (Gulf Standard Time)
Service version: /powerbi/libs
----

Please help me to resolve this.

[grazitti_sapna · Accepted solution]

 @Dhivya_123456 
Yes, Even when your report is set to Import mode, you still need to provide the proper data source permissions in the Power BI service or Report Server.

Here’s why from my experience:

When you refresh a report in Power BI Desktop and publish it, you’re essentially uploading a snapshot of the data at that moment. But once it’s published, the Power BI service or Report Server runs its own scheduled or on-demand refreshes to keep the data up to date. Those refreshes require access to the original data source, so the service or gateway uses the configured data source credentials to connect and pull fresh data.

So, even though the data is imported (cached inside the PBIX), the service still needs permission to reach the data source during refresh operations. If the credentials or permissions aren’t set properly in the service or gateway, you’ll run into connectivity or permission errors after a while ,which explains why the error comes back even after republishing.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

[v-agajavelly]

Hi @Dhivya_123456 ,

I hope the response provided helped in resolving the issue. If you still have any questions, please let us know we are happy to address.

Thanks,
Akhil.

[v-agajavelly]

Hi @Dhivya_123456 ,


Circling back once more, were you able to test those steps with the data source credentials, cache clear, and server logs? If you’re still running into 500 errors, please share any recent error details or screenshots, so we can help narrow down the root cause.

Thanks,
Akhil.

[v-agajavelly]

Hi @Dhivya_123456 ,

Just checking in were you able to try the steps shared earlier regarding data source credentials, clearing cache, and checking server logs? If it resolved the 500 errors, that’s great! If not, let us know where you’re still facing issues, and we’ll be happy to assist further.

Thanks,
Akhil.

[v-agajavelly · Accepted solution]

Hi @Dhivya_123456 ,

Thanks a lot @grazitti_sapna  for the detailed explanation your clarification on Import mode and why PBIRS still needs data source permissions is spot on. That’s definitely one of the key reasons why the error keeps coming back after republishing.

Just to add (for anyone else facing the same issue), a couple of additional points that usually help this down.

1. Check the Data Source Credentials in Report Manager

* Go to the report in the PBIRS web portal → click the dropdown → Manage → Data Sources.

* Make sure the credentials are stored securely and test the connection.

* Even for Import datasets, the server still validates the source at refresh time.

2. Clear Cache & Temp Files

* Sometimes the ReportServer TempDB or the RS cache folders hold onto stale metadata, which can surface as 500 errors. Restarting the PBIRS service and clearing temp files often resolves intermittent crashes.

3. Server Logs

* Check the RSPortal and RSService logs under:

C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles

*These logs usually give the exact failing data source or permissions issue behind the generic “undefined” error.

4. Upgrade if Possible

* If you’re not on the latest PBIRS build, consider upgrading. Several “500 undefined” bugs were fixed in cumulative updates.

With the above your guidance on permissions, should have a complete, if you still face any issue we are happy to help you.

Thanks,
Akhil.

[grazitti_sapna]

Hi @Dhivya_123456 

Generally a status code 500 with “undefined” error in Power BI Report Server typically points to a server side  fault often due to corrupted report definitions, missing database content, or permission/configuration issues on the back-end. This error may surface when the server is unable to load or find the required report resources within its database, or if there’s a bug in how extended report content is fetched.

There are some troubleshooting steps that you can follow:

• Check Report Exists & Is Not Corrupted : Ensure the report exists and is not corrupted. If possible, try re-uploading or redeploying the PBIX file to the Report Server.
• Permissions and Path : Double check that permissions are correctly set for the Report Server service account and that the report paths and data source references are accurate
• Logs and Upgrades :  Review the server’s log files for the specific error message Also, consider upgrading PBIRS if you’re on an older version, as bugs like this have been solved in later builds

Please share if you encounter any further issues

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

[Dhivya_123456]

Thanks for your response.

Yes, we republished all the reports, but the error reappears after about a week.

Regarding permissions and paths — the issue occurs even with reports that are manually refreshed in Power BI Desktop and then published to the service. Data source permissions have also been granted through the web portal.

Could you please clarify this for me- even though the data is in Import mode, is it still necessary to provide data source permissions?

[grazitti_sapna · Accepted solution]

 @Dhivya_123456 
Yes, Even when your report is set to Import mode, you still need to provide the proper data source permissions in the Power BI service or Report Server.

Here’s why from my experience:

When you refresh a report in Power BI Desktop and publish it, you’re essentially uploading a snapshot of the data at that moment. But once it’s published, the Power BI service or Report Server runs its own scheduled or on-demand refreshes to keep the data up to date. Those refreshes require access to the original data source, so the service or gateway uses the configured data source credentials to connect and pull fresh data.

So, even though the data is imported (cached inside the PBIX), the service still needs permission to reach the data source during refresh operations. If the credentials or permissions aren’t set properly in the service or gateway, you’ll run into connectivity or permission errors after a while ,which explains why the error comes back even after republishing.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

[Dhivya_123456]

Since upgrading to the latest Power BI version, we haven’t encountered the error message again.

Thanks for your help.