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.
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.
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 "<Add Key="SecureConnectionLevel" Value="3"/>"
to "<Add Key="SecureConnectionLevelValue="0"/>".
Value="3"
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.
- In Internet Information Services (IIS) Manager, expand
Server Name, expand Web Sites,
right-click the Default Web Site, and then click Properties.
- In Default Web Site Properties, click the
Directory Security tab.
- Under Secure communication, click
View certificate.
- Click the General tab, and then verify
that there are not any errors or warnings.
- Click the Certification Path tab, and then
verify that there are not any errors or warnings.
- 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. - Close Internet Information Services Manager.
- 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: Drive:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager\
- Locate the following line in the
RSWebApplication.config file:
<ReportServerURL>http://ComputerName/ReportServer/</ReportServerURL>
- Replace this line with the following line:
<ReportServerURL>http://Server FQDN/ReportServer/</ReportServerURL>
Important Do not change "http" to "https". - Save the RSWebApplication.config file.
- Click Start, click Run,
type iisreset, and then click
OK.
- Verify that you can open the SQL Reporting Services site by
connecting to the following URL in Internet Explorer:
https://FQDN/Reports
- Install MOM 2005 Reporting.
- 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.
- Save the RSWebApplication.config file.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
For more information about how to use a SSL connection for
SQL Server 2000 Reporting Services, visit the following Microsoft Web site: