"Setup failed to validate specified Reporting Services Report Server" Error occurs when you install Microsoft Dynamics CRM

This article provides a solution to an error that occurs when you install Microsoft Dynamics CRM.

Applies to:   Microsoft Dynamics CRM
Original KB number:   2011889

Symptoms

When you install Microsoft Dynamics CRM with SQL 2008 Reporting Services, the following error occurs in the Environmental Diagnostics Wizard (EDW):

"Setup failed to validate specified Reporting Services Report Server <ReportServerURL>. Error: The operation you are attempting requires a secure connection (HTTPS)."

Cause

The error occurs because the SSRS (SQL Server Reporting Services) server is configured to accept connections only via HTTPS.

Resolution

Update the RSReportServer.config file using the following steps:

  1. In Windows Explorer, locate the ReportServer directory. The following path is the default path of this directory:
    C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
  2. Right-click RSReportServer.config, select Open With, select Notepad, and then select OK.
  3. Locate the following Add Key entry: <Add Key="SecureConnectionLevel" Value="2"/>
  4. Change the Value setting from 2 to 0.

More information

The following table is accepted as inputs for the secureconnectionlevel key.

Level Description Web Methods Requiring SSL
0 Least secure. The report server doesn't check for a secure connection when Web service methods are invoked. However, all calls to the Web service can still be made to the report server over a secure connection. None.
1 Minimally secure. All Web service calls that are made over an insecure connection and which might pass sensitive data such as user credentials are rejected. However, this setting doesn't guarantee security. It's still possible for sensitive data sent by the client to the report server to be exposed before the report server handles the request and rejects it. Render (when the credential setting for the report that is being rendered is set to prompt), CreateDataSource, GetDataSourceContents, SetDataSourceContents, GetReportDataSources, SetReportDataSources, CreateReport, GetReportDefintion, SetReportDefinition, CreateDataDrivenSubscription, SetDataDrivenSubscriptionProperties, GetDataDrivenSubscriptionProperties, and PrepareQuery.
2 Secure. All rendered reports and all Web service calls require a secure connection. Which includes all calls to the Render method and requests for rendered reports made through URL access. Using this secure connection level, subscription delivery can include only URLs to reports. Rendered reports cannot be embedded or included in a delivery. All Level 1 methods, Render (all calls), and RenderStream.
3 Most secure. All calls made to the Reporting Services SOAP API require a secure connection. All.