HTTP Error 503. The service is unavailable

Anonymous · ‎10-10-2019

Hi,

I have Power BI Report Server (May 2019) installed on SQL Server 2016 Enterprise working perfectly.

But today I was upgrading to the September 2019 version, the installation completed normally, but when I opened the reports the following message was displayed in the browser:

HTTP Error 503. The service is unavailable

I checked everything:

- I checked logged in log files: C: \ Program Files \ Microsoft Power BI Report Server \ PBIRS \ LogFiles, but found no errors.

- I checked if service stopped.

- I uninstalled and installed, but the same error occurred.

But I was able to install Power BI Report Server (September 2019) on another server running SQL Server 2014.

Has anyone had this problem?
Is it a bug in this release, which does not let install in SQL Server 2016, only in SQL 2014?.

Thanks.
_Keny

d_gosbell · ‎10-10-2019

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-... 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.

View solution in original post

Anonymous · ‎10-11-2019

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.

View solution in original post

d_gosbell · ‎10-10-2019

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-... 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.

Anonymous · ‎10-11-2019

Hi,

I really appreciate your help.
Thanks.

Anonymous · ‎10-11-2019

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.

Anonymous · ‎10-15-2019

Hi,

I installed the new release of this link below, but it didn't work.

Could you please put the link to download the release?

Thanks

_Keny

d_gosbell · ‎10-15-2019

@Anonymous wrote:

I installed the new release of this link below, but it didn't work.

Have you tried manually installing a recent version of the .Net Framework as suggested earlier in this thread? This seems to be the fastest workaround for fixing this 503 error.