Reporting services http error 503 - Исправление ошибок и поиск оптимальных решений проблем

I have been wanting to deploy my SSRS reports to a Test server. However I found that on that server the SSRS service had stopped, and I had to change the setting so that it used a built in Network Service account. After doing that I found I could start the service. However when I key in the ReportService url in my browser, I get the above error message.

One problem that I had when I changed the settings to the Network Service account is that I got the error message:

«A connection could not be established with the information provide. Hit OK to change your connection settings.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: named Pipes Privider, error: 40 — Could not open a connection to SQL Server)»

Even so, this did not stop the service from starting.
As a result of all this I still cannot deploy my reports. How do I fix this?

asked Dec 14, 2011 at 15:25

arame3333arame3333

9,65725 gold badges120 silver badges203 bronze badges

If you are running SSRS 2016, restart the SSRS services:

SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)

answered Sep 30, 2016 at 21:21

TarzanTarzan

4,1327 gold badges49 silver badges69 bronze badges

The best way to find the answer is to check the log files.

You can find the log files for report server at below path:
In SQL Server Reporting Services 2016 or earlier: C:Program FilesMicrosoft SQL ServerMSRS13.MSSQLSERVERReporting ServicesLogFiles

In SQL Server Reporting Services 2017: C:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogFiles

Thanks & Regards
Karan

answered Apr 1, 2020 at 14:58

Error 503 Usually comes if the database credentials are wrong , you can test the connection from Reporting Configuration Manager.
Otherwise, Check the Reportserver config file "rsreportserver" at path

C:Program FilesMicrosoft SQL ServerMSRS13.MSSQLSERVERReporting ServicesReportServer

and find the following tags are correct or not.!

        <Authentication>
        <AuthenticationTypes>
        <RSWindowsNTLM/>
        </AuthenticationTypes>
        <RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
 <RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
        <EnableAuthPersistence>true</EnableAuthPersistence>
     </Authentication>

According to user permissions/properties you can change <AuthenticationTypes> tag.

Restart Following Services

SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)

answered Mar 21, 2019 at 7:18

This error is also generated if you are using a trial version of SSRS and it has expired.

answered Mar 11, 2021 at 11:05

Find <IsWebServiceEnabled>False</IsWebServiceEnabled> and change to
<IsWebServiceEnabled>True</IsWebServiceEnabled> in the rsreportserver
config file.

answered May 21, 2018 at 5:24

I was getting this error and tried deleting the URL’s from the rsreportserver.config file.
After lots of frustration, I found that the permissions on that file and directory itself did not allow ReportServer user to modify the file. Once I gave the reporting user permission on the file, all was good to remove / update URL’s, and returned SSRS back into service.

Try explicitly adding the user permissions to the config file.

Good luck!

answered Feb 18, 2016 at 20:44

patmanpatman

1261 silver badge6 bronze badges

In rsreportserver.config, my value was not correct. It was showing up as: http://+:80. Of course, this needs to map to the URL specified in the Report Server Configuration Manager, Web Portal URL (ie the blue URL link that was bringing me to a «not connected» browser screen). It did not, so I got Service Unavailable with a 503 (HTTP error).

The solution: edit the value/address to match the Web Portal URL.

Web Service URL -> URLs: http://MYSERVERNAME:80/Reports

rsreportserver.config -> http://MYSERVERNAME:80/Reports

Once I saved the rsreportserver.config with the edited value to match accordingly (above), I could click on the provided link in the Web Portal section of the Report Server Configuration Manager, and it brought up the SQL Server Reporting Services page. Note: I didn’t need to restart anything.

Cheers!

answered Dec 10, 2022 at 17:06

Источник

One problem that I had when I changed the settings to the Network Service account is that I got the error message:

Even so, this did not stop the service from starting.
As a result of all this I still cannot deploy my reports. How do I fix this?

asked Dec 14, 2011 at 15:25

arame3333arame3333

9,65725 gold badges120 silver badges203 bronze badges

If you are running SSRS 2016, restart the SSRS services:

SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)

answered Sep 30, 2016 at 21:21

TarzanTarzan

4,1327 gold badges49 silver badges69 bronze badges

The best way to find the answer is to check the log files.

You can find the log files for report server at below path:
In SQL Server Reporting Services 2016 or earlier: C:Program FilesMicrosoft SQL ServerMSRS13.MSSQLSERVERReporting ServicesLogFiles

In SQL Server Reporting Services 2017: C:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogFiles

Thanks & Regards
Karan

answered Apr 1, 2020 at 14:58

C:Program FilesMicrosoft SQL ServerMSRS13.MSSQLSERVERReporting ServicesReportServer

and find the following tags are correct or not.!

        <Authentication>
        <AuthenticationTypes>
        <RSWindowsNTLM/>
        </AuthenticationTypes>
        <RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
 <RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
        <EnableAuthPersistence>true</EnableAuthPersistence>
     </Authentication>

According to user permissions/properties you can change <AuthenticationTypes> tag.

Restart Following Services

SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)

answered Mar 21, 2019 at 7:18

This error is also generated if you are using a trial version of SSRS and it has expired.

answered Mar 11, 2021 at 11:05

Find <IsWebServiceEnabled>False</IsWebServiceEnabled> and change to
<IsWebServiceEnabled>True</IsWebServiceEnabled> in the rsreportserver
config file.

answered May 21, 2018 at 5:24

Try explicitly adding the user permissions to the config file.

Good luck!

answered Feb 18, 2016 at 20:44

patmanpatman

1261 silver badge6 bronze badges

The solution: edit the value/address to match the Web Portal URL.

Web Service URL -> URLs: http://MYSERVERNAME:80/Reports

rsreportserver.config -> http://MYSERVERNAME:80/Reports

Cheers!

answered Dec 10, 2022 at 17:06

Источник

Remove From My Forums

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

Answers

- Marked as answer by
  Mike Yin
  Sunday, August 26, 2012 12:32 PM
- Marked as answer by
  Mike Yin
  Sunday, August 26, 2012 12:32 PM

All replies

- Marked as answer by
  Mike Yin
  Sunday, August 26, 2012 12:32 PM
- Marked as answer by
  Mike Yin
  Sunday, August 26, 2012 12:32 PM
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!
- Proposed as answer by
  Sohail_I
  Friday, July 21, 2017 1:54 PM
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
Spot on. Can’t believe it was so simple.
Never thought to restart it a the server had recently been rebooted.

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

Источник

Upon a server reboot on Monday, I have been unable to have a working SSRS instance. All I get is Error 503 on both Web Service URL and Web Portal URLs. The server reboot on Monday was due to May patches being installed, however, I am unsure
if there is a link to those patches, or if it was just because the server rebooted. The website was working great before then with zero downtime issues. Here is a list of things I have tried and a copy of the error logs:

1. Restart of SSRS Service

2. Reboot Server

3. Uninstall .net patch from May and reboot

4. Download and install .net framework 4.8

5. Download latest SSRS 2017. Now version 14.0.7393.5407 Reboot

6. Remove web portal URL and Web Service URL and add back again.

7. Change service account from virtual service account to network service and back while testing between each change.

8. Add service account to local admin group

9. Verify firewall port rule in effect to allow port 80, 443, 1433, 1434.

10. Try to setup on alternate VM, however license is SQL Server Standard, which does not allow scale-out.

11. Look at error logs for additional clues. Nothing seems obvious as the log is quite limited.

12. Uninstall remaining May 2020 patches, reboot.

Other information to note about this server is that it is also running IIS and those websites are not affected. They work perfectly fine. It is just the SSRS. Any help on how to trace the issue further is greatly appreciated. This
is installed on windows 2012 R2 OS.

Here is the log files:

RSHostingService_2020_06_04_13_44_22.log

2020-06-04 13:44:22.1220|INFO|1|File Logger created: ‘D:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogFilesRSHostingService_${DailyDate}.log’ — level Info, will roll at 32 Mb, process id 12148
2020-06-04 13:44:22.1376|INFO|1|CFG : WebApiMaxWaitMS = [1000] (default)
2020-06-04 13:44:22.1376|INFO|1|CFG : WebApiBackOffExpireSeconds = [60] (default)
2020-06-04 13:44:22.1376|INFO|1|CFG : WebApiInitialWaitMS = [10] (default)
2020-06-04 13:44:22.1376|INFO|1|CFG : WebApiBackoffMultiplier = [2] (default)
2020-06-04 13:44:22.1376|INFO|1|CFG : ServiceWatchdogIntervalInSeconds = [10] (default)
2020-06-04 13:44:22.1376|INFO|1|Current Directory : D:Program FilesMicrosoft SQL Server Reporting ServicesSSRSRSHostingService
2020-06-04 13:44:22.3251|INFO|5|Updating application config files
2020-06-04 13:44:22.3251|INFO|5|Syncing service machine key
2020-06-04 13:44:22.3720|INFO|5|CFG : MaxWaitMinutes = [60] (default)
2020-06-04 13:44:22.3720|INFO|5|CFG : BackOffExpireMinutes = [60] (default)
2020-06-04 13:44:22.3720|INFO|5|CFG : InitialWaitSeconds = [30] (default)
2020-06-04 13:44:22.3720|INFO|5|CFG : BackOffMultiplier = [2] (default)
2020-06-04 13:44:22.3876|INFO|5|Launching Process : Management Service
2020-06-04 13:44:22.3876|INFO|5|Starting Process: D:Program FilesMicrosoft SQL Server Reporting ServicesSSRSManagementRSManagement.exe

RSManagement_2020_06_04_13_44_22.log

2020-06-04 13:44:22.6063|INFO|1|File Logger created: ‘D:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogFilesRSManagement_${DailyDate}.log’ — level Info, will roll at 32 Mb, process id 11036
2020-06-04 13:44:22.7157|INFO|1|CFG : Dumper.path = [..LogFiles] (env)
2020-06-04 13:44:22.7157|INFO|1|CFG : Name = [] (env)
2020-06-04 13:44:22.7157|INFO|1|CFG : Dumper.flags = [SendToWatson, AllThreads, AllMemory] (env)
2020-06-04 13:44:22.7157|INFO|1|CFG : Dumper.preventIfContains = [Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException] (env)
2020-06-04 13:44:22.7157|INFO|1|Do not dump on: Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException
2020-06-04 13:44:22.7157|INFO|1|CFG : listenerUrl = [http://+:8082/] (env)
2020-06-04 13:44:22.7157|INFO|1|CFG : rsConfigFilePath = [..ReportServerrsreportserver.config] (env)
2020-06-04 13:44:22.7313|INFO|1|SKU: SQL Server Standard
2020-06-04 13:44:22.8563|INFO|1|The web server needs to run elevated
2020-06-04 13:44:22.8563|INFO|1|Web Server is running.

Edited by

Thursday, June 4, 2020 7:26 PM
Add OS info.

Источник

Introduction

I was writing a blog post about Troubleshooting BitLocker Management in ConfigMgr 2002 Current Branch and one of the things I was trying to do was install the web portals, but I was seeing errors shown below.

Get-ReportServiceUri : Caught exception querying report service at http://cm01.windowsnoob.lab.local/Reportserver

I assumed this was because SSRS was not installed or configured but after checking the lab, I could see it was indeed installed and configured. However when I browsed the http://cm01.windowsnoob.lab.local/ReportServer URL in Internet Explorer it produced a HTTP Error 503. The Service is unavailable.

A quick search gave some clues and things to try but in reality the reason it was not working was because:

SSRS was installed in evaluation mode
SSRS evaluation had expired

This was revealed in the logs stored at C:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogfiles

To upgrade the evaluation version you’d normally just need to upgrade the edition of SSRS from Evaluation to Production via change/uninstall in Control Panel, however the way this installation was packaged (WIX bundle) meant that it retained the original download link in a bundled file called state.rsm

and that was looking in the IE cache as you can see in the SSRS installation log files

That path no longer existed. Manually recreating that path and copying the SQLServerReportingServices.exe file to that path did not help, it reported another error.

I could keep trying to hack my way around these errors or fix it once and for all.

Fixing the evaluation version

As this is just a lab I decided to rip SSRS out completely and then add it back.

Note: If you are doing this in production then make sure to backup all your custom reports first and if necessary backup the reporting databases also.

I decided to try the following:

uninstall reporting from ConfigMgr
delete the 2 reporting db’s in SQL
uninstall SQL Reporting Services in control panel
restart server
reinstall SSRS
reconfigure SSRS

Keep in mind that unless you want the same problem occurring in 180 days or so, you’ll need the product key that was used when installing SQL. If this process doesn’t pick it up from your installed instance of SQL, you can find that key in the installation media.

DefaultSetup.ini

To find the product key in your installation media, the PID is contained within the DefaultSetup.ini file located under RootX86 or Rootx64 folder.

Let’s get started. In ConfigMgr remove the SSRS role.

Confirm that it’s removed successfully via the SRSRPSetup.log.

read the rest of this blog post here on windows-noob.com

This entry was posted in 2002, BitLocker Management, Reporting. Bookmark the permalink.

Источник

The other day, I have powered ON my Configuration Manager lab after long a time to test something on the reporting and found that, the reporting URL does not work.

Browsing the reports URL leads to service unavailable with http error 503, The service unavailable.

I have verified that, the SQL server reporting services is running fine and i have restarted the service as well to check if this works or not but no luck.

I have realized that, there is something seriously wrong and took sometime to troubleshoot further.

The first log to check is srsrp.log (ConfigMgr log) for reporting services located in your configMgr installation directorylogs folder.

The log has the following errors:

The request failed with HTTP status 503: Service Unavailable.

(!) SRS not detected as running

Failures reported during periodic health check by the SRS Server CMserver.domain.name

I have also checked the reporting server configuration manager, everything seems to be fine.

The next is to look at the SQL server reporting services log located in

C:Program FilesMicrosoft SQL Server Reporting ServicesSSRSLogFiles

The log has the following error messages:

configmanager!DefaultDomain!5018!04/04/2021-14:23:28:: e ERROR: Error loading configuration file: The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired. A license is now required.

appdomainmanager!DefaultDomain!5018!04/04/2021-14:23:28:: e ERROR: Appdomain:1 DefaultDomain failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. —> Microsoft.ReportingServices.Diagnostics.EvaluationCopyExpiredException: The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired. A license is now required..

AS you can see in the log, the license has expired for SQL server reporting services.

When you install the SQL server reporting services, you will be asked for the trail of 180 days or input the license key of the SQL server.

If you choose trail, then after 180 days, you will have the same issue like mine.

So now, we found that, the license for the SQL server reporting services is expired, how do we activate it now?

The only way that I could find is to reinstall the reporting services.

Run the SQL server reporting services installation wizard (I did 2019), you will see the following options. Choose upgrade, you will be asked for the key to activate it.

Once the installation is completed, wait for the reporting services to check the license status and rebuild the reports (there wont be any changes your default/custom reports) and after sometime, your reporting URL will be up and running.

hope this helps!

Источник

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" alt="RRS feed" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif?cver=0001" />

Question

Answers

All replies

Introduction

DefaultSetup.ini