How to install Microsoft Operations Manager (MOM) 2005 Service Pack 1 databases and MOM 2005 Reporting on a computer that has Microsoft SQL Server 2005 installed (918481)

MORE INFORMATION

Steps to install MOM 2005 SP1 and MOM 2005 Reporting on SQL Server 2005

1. Install SQL Server 2005. Include the following components in the installation:
   • Database Engine
   • Reporting Services
   Configure Reporting Services during the installation, or use the Reporting Services configuration wizard.
   
   Note For information about how to install SQL Server Reporting Services, search on "Installing SQL Server Reporting Services" in SQL Server 2005 Books Online.
2. Make sure that the SQL Server Reporting Services Web site is running. For example, use your browser to visit the Reporting Manager Web site. For the application pool, we recommend that you create a new application pool. Use either the ASPNET local account or the Network service account to run the application pool.
3. Grant the write permission on the following folder to the Network Service account:

   %WinDir%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

4. Install MOM 2005 SP1.
5. Install the hotfixes that are discussed in the following Microsoft Knowledge Base (KB) articles:

   913812 After you install version 2.0 of the .NET Framework on a site server that is running Microsoft Operations Manager 2005 with S913812, you can no longer discover computers in Active Directory

   913801 You notice an increase in event and performance data latency after you upgrade the MOM 2005 Server OnePoint database to Microsoft SQL Server 2005

6. Install MOM 2005 Reporting.
   
   Note Manually enter the Reporting virtual directories. In the Prerequisite Checker for MOM 2005 Reporting, specify the virtual directory names of the report server and of the server that is running Report Manager. Do this instead of using URLs to point to these directories.
7. Install the hotfix that is discussed in the following KB article:

   915785 Error message when you use SQL Server 2005 Reporting Services or SQL Server 2000 Reporting Services to generate HTML reports in Microsoft Operations Manager 2005: "There is an error in XML document"

8. On the Start menu, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. Then open the properties of the Reports Web site. On the ASP.NET tab, change the ASP.NET version from 1.1 to 2.0.
   
   For more information about the "Check Prerequisites" task, click the following article number to view the article in the Microsoft Knowledge Base:

   909846 The "Check Prerequisites" task returns an error when you run the task from a slipstream version of MOM 2005 Service Pack 1

Additional steps

If you are not using Secure Sockets Layer (SSL) on your Reports pages

Make sure that the RSReportServer.config file includes the following section.

<Add Key="SecureConnectionLevel" Value="0"/>

The RSReportServer.config file is located in the following folder: Note If the value in this section is 3, SSL is required. If the value is 0, SSL is not required. MSSQL.x is a placeholder for the corresponding instance ID for the system. To determine the instance ID for the system, follow these steps:

1. Connect to the instance of the SQL Server Reporting Services service by using the Reporting Services Configuration tool.
2. Click to open the Report Server Status page.
3. On the Report Server Status page, note the instance ID information.

If you are using SSL on your Reports pages

If you cannot access the SQL Server Reporting Services Web site by using HTTPS, follow these steps:

1. Verify the value in the following section in the RSReportServer.config file.

   <Add Key="SecureConnectionLevel" Value="3"/>

   The RSReportServer.config file is located in the following folder:

   %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer

2. Verify that the certificate is using the server's fully qualified domain name (FQDN) instead of the server's NetBIOS name. To do this, follow these steps:
   1. Open IIS Manager.
   2. Open the properties of the Default Web Site Web site.
   3. Click the Directory Security tab.
   4. Under Secure communications, click View certificate. The Certificate dialog box appears.
   5. In the Certificate dialog box, make sure that no errors or warnings appear on the General tab or on the Certification Path tab.
   6. Note the FQDN. The FQDN appears in the Issued to field on the General tab and in the Subject property on the Details tab.
   7. Close IIS Manager.
3. Add the server FQDN to the SQL Server Reporting Services Web configuration file if it is required. To do this, follow these steps:
   1. On the computer that is running SQL Server 2005 Reporting Services, open the RSWebApplication.config file in a text editor such as Notepad.
      
      Note Typically, the RSWebApplication.config file is located in the following folder:

      %SystemDrive%\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportManager

   2. Locate the following line in the RSWebApplication.config file.

      <ReportServerURL>http://<NetBIOS_Name>/<ReportServer></ReportServerURL>

      Note <NetBIOS_Name> is a placeholder for the NetBIOS name of the computer that is running SQL Server 2005 Reporting Services. <ReportServer> is a placeholder for the computer name of the computer that is running SQL Server 2005 Reporting Services.
   3. Replace this line with the following line.

      <ReportServerURL>http://<Server FQDN>/<ReportServer></ReportServerURL>

      Note <Server FQDN> is a placeholder for the FQDN of the computer that is running SQL Server 2005 Reporting Services. <ReportServer> is a placeholder for the computer name of the computer that is running SQL Server 2005 Reporting Services.
4. Save the RSWebApplication.config file.
5. Click Start, click Run, type iisreset, and then click OK.
6. Verify that you can open the SQL Server Reporting Services Web site. To do this, use your browser to connect to the following URL:

   https://Server FQDN/ReportServer

7. If you can open the SQL Server Reporting Services Web site, try again to install MOM 2005 Reporting.