Generated Reports or testing from 'Change Reporting Config' within the System -> Configure page with a 503 Service Unavailable Error.


When generating a report that pulls from MS Reporting Services or testing from the 'Change Reporting Config' , a 503 Service Unavailable error comes up.

This could have been due to several factors such as a migration of the database, or application server. Or even improper permissions in the Web Service URL.

Be sure to follow the SSRS Setup Guide when setting up a new database if performing a migration to prevent overlooking the MS Reporting Service configurations when migrating.

This issue can occur due to several misconfigurations in SQL Server Reporting Services (SSRS) or the Service may have simply been stopped for any reason.


Steps that can be done to diagnose the issue can be to check the Service in the Services.msc section or on SQL Server Reporting Services.

If the Service has been confirmed to have been started, steps that would need to be done to resolve this would require the sa password to your Database and going through all the sections in Reporting Services Configuration Manager :

1. Be sure that the Web Service URL has the Local System account. You will need to make a temporary Backup Encryption Key (please keep note of the password).

2. In Web Service URL, be sure that you have a Virtual Directory set up so it can access the Web Service URL.

3. Be sure that the ReportServer Database exists in the Database Section.

If the Current Report Server Database section appears to be blank, then this will need to be implemented by going to 'Change Database' and creating a New Database.

Be sure to confirm that the connection to the Database works and implement SQL Server Account for Authentication Type and confirm that the Connection is Successful by running Test Connection.

Once that's done, be sure to enter sa Credentials once more in the Credentials section and review that everything's accurate in the Summary section and hit Apply to save the settings.

4. Be sure that the Report Manager URL section is initially configured. If it seems to not be configured yet, simply hit Apply for the default Reports Virtual Directory.

5. On the Execution Account, please be sure that no Execution Accounts are specified here as Kaseya doesn't support Execution Accounts running on MS Reporting Services.

6. On the Encryption Keys Section be sure to go ahead and Delete Encrypted Content as we don't support Encryption Keys when attempting to render reports.

Once all of the steps have been done, go to System -> Configure and click on Change Reporting Config and be sure that the host name matches the one you applied in Step 2 and confirm if you have a Success Connection to MS Reporting Services.


6.3 (also applies to other versions)

SQL Server (ALL Versions)