This article applies to:

• Marshal Reporting Console
• Configuration of SSRS URL

Symptoms:

• MRC Configuration Wizard attempting to connect to SQL Reporting Server
• Setting the URL for SQL Server Reporting Services (SSRS)
• Error message: Problem connecting to Report Server - The service might not be running or you might not have access to the URL

Causes:

Each of the following unrelated issues could raise this error message:

• Website URL incorrectly entered, site stopped, or site requires login: Verify that the SQL Reporting Server website is running at the expected URL and does not require authentication.
• Proxy Settings: System proxy settings for the logged on user on the MRC server may be forcing the connection through a proxy that requires authentication.
• Secure Connections: SQL Server Reporting Services (SSRS) report server configuration may be configured to require secure connections. If SSL Certificates are available on the server, by default SSRS requires SSL (HTTPS connection). However, SSL is not supported by MRC.

Resolution:

To resolve the issues:

Proxy settings:

1. On the MRC server, edit system proxy settings (using the Network & Internet > Proxy Control panel).
2. Set direct access, or add the SQL Reporting Server (by name) to the exclusions.

Secure Connections:

Configure SSRS to allow HTTP connections.

• Edit the RSReportServer.config file. The following key and value should be present:
  
  <Add Key="SecureConnectionLevel" Value="0" />
  
  
• If the value is not 0, change it to 0.
• Save the file and then restart the SQL Server Reporting Services service for the instance.

Notes:

• If your network enforces proxy settings through a domain policy or auto-configuration, you may need to exclude the MRC server from the policy.
• If you need to edit RSReportServer.config, LevelBlue recommends that you use an XML editing program that validates the XML code. You can use XML Notepad (a free tool from Microsoft).
  • Download XML Notepad
• For more information about RSReportServer.config, see this Microsoft Technet entry.