Unwanted PowerBI MIgration Launched!

[CallMeCrazy]

Hello, in the process of learning PowerBI, I published a report and it broke my external web access to the reports portal.  The actual browser interface still works perfectly.  Luckily, i have two identical environments so I was able to locate the 6 new options added to ReportServer.ConfigurationInfo and set these three to false ('EnablePowerBIReportMigrate', 'TileViewByDefault' and 'UsePortalV2').  I completely removed my workspace in PowerBI  Still, my external web access to the reports portal is returning a 404 message.  I'm stumped.  Can anyone think of what might be interfereing?  Thanks!

[v-pnaroju-msft]

Thankyou, @Ritaf1983, for your response.

Hi @CallMeCrazy,

Thank you for your detailed follow-up.

Based on my understanding of the symptoms and your setup, it appears that when the report was published using Power BI Desktop, the version used was likely optimized for Power BI Report Server and the report was published to an SSRS instance with PBIRS compatibility mode enabled. This inadvertently triggered the modern portal mode, resulting in the unexpected behaviour and the 404 error encountered when accessed externally.

Kindly follow the steps below which may help to resolve the issue:

1. Confirm the version of your Power BI Desktop; if it mentions “optimized for Report Server,” it could trigger changes to the portal mode.
2. Ensure that the modern portal settings are disabled.
3. Perform an IIS reset using the command iisreset so that the changes are fully applied.
4. Review the IIS bindings for external access, and confirm that the external hostname is correctly configured.
5. Verify DNS settings and NSG/firewall rules in Azure to ensure there is no blockage preventing external access.
6. Check the server logs (both SSRS and IIS) for any additional information or clues regarding the 404 error.

Additionally, concerning the [ConfigurationInfo] entries, please note that these are automatically added by PBIRS during the first .pbix publish, particularly when using Power BI Desktop for Report Server.

If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will greatly assist other community members facing similar issues.

Should you have any further queries, please feel free to reach out to the Microsoft Fabric community.

Thank you.

[CallMeCrazy · Accepted solution]

Hi again Rita, I sure appreciate your responses.  The problem is now resolved.  The cause of the issue was a single report that was saved AFTER the the option "EnablePowerBIReportMigrate" was set to true.   Hopefully this thread will help another user who ends up in the same spot.

[Ritaf1983]

Hi @CallMeCrazy 

It sounds like you're running Power BI Report Server and encountered an issue after publishing a report that triggered a portal behavior change. You've correctly reverted the modern portal settings (`EnablePowerBIReportMigrate`, `TileViewByDefault`, and `UsePortalV2`), but you're still facing a 404 error externally.

A few things to check:

1. Can you access the portal internally via `localhost` or the internal IP? If yes, the issue might be network/firewall/IIS-related rather than a Power BI setting.
2. Double-check your IIS bindings and see if there's any redirection or URL rewrite affecting external access.
3. Make sure the external URL you're using matches the one configured for the portal.
4. Try resetting the portal app in IIS or reviewing the `Web.config` for any custom changes or conflicts.

If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly

[CallMeCrazy]

Thanks Rita, I am not intentionally running a Power BI reports server.  At no point did I attempt to link my PowerBI to my production evironment.  My environment is an Azure Managed instance.  I had connected to a single database for testing (no idea that this would impact my environment).   Where would I expect to find this PowerBI Reports server - my local PC? (PowerBI Desktop was what i used to Publish the report)  or PowerBI online?  or my Azure Mangaged Instance?  or my SSRS Virtual PC (didn't find any evendience of any PowerBI there).  I expect something was modified on my Azure Managed Instance which houses both the test database and my report server.  Any additional suggestions greatly appreciated.  Also, any idea of what is the mechanism that automatcially recreates those PowerBI settings in [reportserver].[dbo].[configurationinfo] ?   Maybe the solution lies there.  Thanks very much!