Forum Discussion
HTTP Error 503. The service is unavailable
- 6 years ago
This issue has been reported before, but it only appears to be affecting a small amount of users and as of yet I don't think anyone has been able to isolate the root cause.
The existing thread is here https://community.powerbi.com/t5/Report-Server/Getting-503-error-child-process-RSPortal-died-Report-Server-Sept/m-p/809674#M11745 it's probably worth adding a comment to that thread as there is a PowerBI team member on that thread trying to capture more information about this issue.
- Anonymous6 years ago
The solution is to install the newest .Net Version on the machine (4.8 in my case). After that, the 503 error is gone. See other thread for details.
hi
Hi Keny, the HTTP 503 error you are seeing after the September 2019 upgrade is a common issue and typically isn't a bug with SQL Server 2016 itself. The most frequent cause is that this specific release of Power BI Report Server requires .NET Framework 4.8 to function properly. Even if the installation finishes without errors, the service will fail to initialize the web portal if the correct .NET version is missing. I recommend manually installing .NET Framework 4.8 on your server and performing a reboot as this resolves the majority of these cases. If the issue persists after the update, you should open the Report Server Configuration Manager and re-apply your Service Account credentials and URL reservations to ensure all permissions and bindings are refreshed for the new version. Your SQL Server 2016 Enterprise environment is fully supported, so this is likely just a missing dependency or a configuration glitch during the upgrade process.