How to fix problem 503 service unavailable in SSRS ?

Question

Hiiiii..

I am trying to open my ssrs reports trough the path http://<ServerName>/reports

but this gives me error 503 service unavailable. 

Plz give me solution for this problem.

thanks............

Answer 1

http://www.laschinger.net/?tag=error-503-service-unavailable

---

Best Regards,Uri Dimant SQL Server MVP,http://sqlblog.com/blogs/uri_dimant/

Blog : MS SQL Development and Optimization

Blog : Large scale of database and cleansing

Answer 2

Hi,

First thing is to verify that the SSRS service is running. Go to report server configuration manager and starts the service if stopped.

If you are running server on VM, Please have a look at below thread to see if it helps

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/dfd21c3f-f8c9-469f-a5d0-c7bb34fa99a2

Also, have a look at section "HTTP 503 Service is Unavailable" in below link, to see if it helps

http://msdn.microsoft.com/en-us/library/ms159778.aspx

Please revert if this does not resolve the issue.

---

- Chintak (My Blog)

Answer 3

SSRS 2016 has a similar HTTP Error 503 bug where after you change the port/cert bindings, it will go into the Service Unavailable state.  Simply restart SSRS service and it will begin working again with the new binding!

Answer 4

That link is broken.

Answer 5

https://youtu.be/FQ4cp429Gzs

Answer 6

Hi all I've the same problem when I've installed the SP2 on SQL2016

someone would have a solution?

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/bac7d15b-7087-4b07-8030-4f17bbd22082/sql-2016-with-sp2-http-error-503-the-service-is-unavailable?forum=sqlreportingservices

Answer 7

Hi. I had the same SSRS HTTP Error 503 problem after SP2 was installed. I also had the problem documented in the following link at the same time.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/dd78b8c3-15d9-466e-bcce-b0f7c2a9f9b4/ssrs-2016-logging-same-message-250-times-per-second?forum=sqlreportingservices

I ran the SQL that the Microsoft SSRS Team recommended in the link which simply creates a job (which is then deleted by SSRS) and BOTH problems were resolved.

Answer 8

Spot on. Can't believe it was so simple.
Never thought to restart it a the server had recently been rebooted.

Thanks

Answer 9

In my case I had apparently not finished configuring the Report Server. The place where things fell of in the configuration was defining the Report Server database. Once that was created, everything was peachy.