1. 503 Service
2. 503 Error For Website

1. Symptoms

Before updating my SQL Server 2014 I was able to publish my reports and connect to my server using Microsoft Report Builder 3.0 (see Figure 1 & Figure 3). Subsequently, a weird error raised (see Figure 2). Therefore, I was not only able to reach the main page of the http://localhost/Reports, but also to connect to http://localhost/ReportServer, I tried hard to figure out what's going on by reading blogs, Forums..... etcetera, without success to find a solution.

What Does 503 Service Temporarily Unavailable Mean? Long answer short: Server overload causes your website to throw the 503 Server Temporarily Unavailable Error. A server is where your websites are hosted. Think of it as a plot of land on which your house is built. A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request. This may be due to the server being overloaded or down for maintenance. This particular response code differs from a code like the 500 Internal Server Error we explored some time ago.

This morning, I was lucky because I found out how to correct the above error by using the Reporting Services Configuration Manager despite I used it to update the port #80 to 8080 and adding port 443.

2. Solution

1. Check if there is any down Sql Server service (services.msc)
2. Go to Reporting Services Configuration Manager
3. Connect to the default Instance
4. Go to the Web Service URL tab
5. Change the name of the virtual Directory (in my case I changed it to MyReportServer)
6. Click Apply
7. Go to the Report Manager URL
8. Change the name of the virtual Directory (in my case I changed it to MyReport)
9. Click Apply
10. Initialize the Report Server by deleting the Encrypted Content in Encryption Keys Tab

3. Result

503 Service

• Report Builder 3.0
• http://TheServerName/MyReport
• The following figure shows the new vdir under IIS (v8.5.9600.16384)

503 Error For Website