Forum Discussion
HTTP Error 503. The service is unavailable
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
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.
8 Replies
- d_gosbellSuper User
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.
- AnonymousNot applicable
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.
- AnonymousNot applicable
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
- AnonymousNot applicable
Hi,
I really appreciate your help.
Thanks.