Microsoft KB Archive/899720

= The Microsoft Operations Manager Prerequisite Checker generates an &quot;Unable to contact the Microsoft SQL Server Reporting Services server via Web Service&quot; error message for Microsoft Operations Manager 2005 Reporting =

Article ID: 899720

Article Last Modified on 1/30/2007

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005

-





SYMPTOMS
Consider the following scenario:
 * You select the option to use Secure Sockets Layer (SSL) when you install Microsoft SQL Server 2000 Reporting Services.
 * You assign a certificate to the SQL Reporting Services Web site that lists the server's fully qualified domain name (FQDN) instead of the server's NetBIOS name.
 * You try to install Microsoft Operations Manager (MOM) 2005 Reporting.

In this scenario, the Prerequisite Checker for MOM 2005 Reporting fails and generates the following message:

Minimum Requirement: Microsoft SQL Server Reporting Services

Required For: MOM Reporting

Detected Value: Unable to contact the Microsoft SQL Server Reporting Services server via Web Service.

Resolution: Please refer to the MOM 2005 installation guide for more information.

Additionally, if you try to open the SQL Reporting Services site by using Microsoft Internet Explorer, you receive the following error message:

The underlying connection was closed: Could not establish trust relationship with remote server.



CAUSE
This occurs because the SQL Reporting Services Web configuration file uses the server's NetBIOS name in the ReportServerURL parameter. This is true even if the certificate on the Web site uses the server's FQDN. If the certificate on the Web site uses the server's FQDN, you cannot open the Web site, and the Prerequisite Checker for MOM 2005 Reporting does not detect the site.



WORKAROUND
To work around this problem, use one of the following methods.

Method 1: SSL is not required
 Use Notepad to open the following file:

Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config

 Change &quot;&quot; to &quot;&quot;.

Value=&quot;3&quot; indicates that SSL is configured. Save the RSReportServer.config file. Install MOM 2005 Reporting.

Method 2: SSL is required
 Click Start, click Run, type inetmgr.exe, and then click OK.</li> In Internet Information Services (IIS) Manager, expand, expand Web Sites, right-click the Default Web Site, and then click Properties.</li> In Default Web Site Properties, click the Directory Security tab.</li> Under Secure communication, click View certificate.</li> Click the General tab, and then verify that there are not any errors or warnings.</li> Click the Certification Path tab, and then verify that there are not any errors or warnings.</li> Click the General tab, and then note the FQDN in the Issued to field.

Note You can also find the FQDN in the Subject property on the Details tab.</li> Close Internet Information Services Manager.</li> Add the server FQDN to the SQL Reporting Services Web configuration file. To do this, follow these steps:  Open the RSWebApplication.config file on the Microsoft SQL Server 2000 Reporting Services server.

Note The RSWebApplication.config file is typically located in the following folder on the SQL Server 2000 Reporting Services server:



</li> Locate the following line in the RSWebApplication.config file:

< >http:// /ReportServer/</ >

</li> Replace this line with the following line:

< >http:// /ReportServer/</ >

Important Do not change &quot;http&quot; to &quot;https&quot;.</li> Save the RSWebApplication.config file.</li></ol> </li> Click Start, click Run, type iisreset, and then click OK.</li> <li>Verify that you can open the SQL Reporting Services site by connecting to the following URL in Internet Explorer:

https:// /Reports

</li> <li>Install MOM 2005 Reporting.</li> <li>After you finish using the MOM Prerequisite Checker, change the line that you modified in step 9c back to the original line that is mentioned in step 9b.</li> <li>Save the RSWebApplication.config file.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="references_section">