Prerequisite Checker errors that may occur when you install Microsoft Operations Manager 2005 Reporting (919954)

MORE INFORMATION

Prerequisite verification may be unsuccessful if you do not run it from the installation program

If you manually run the Check Prerequisites task, you may receive incorrect results. For more information, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this problem, run the MOM Reporting installation program to verify the installation prerequisites.

You receive a "Could not get SQL Server instance names" verification failure with SQL Server 2000 Service Pack 3

When you use Microsoft SQL Server 2000 Service Pack 3 (SP3) or SQL Server 2000 SP3a, the MOM Reporting prerequisite checking process fails. Additionally, the prerequisite report contains the following information.

Minimum Requirement	Recommended (if different from minimum)	Required For	Detected Value	Resolution
Microsoft SQL Server 2000 SP3 or a later version	blank	MOM Reporting	Could not get SQL Server instance names	Download the required version from http://www.microsoft.com/downloads/

This problem occurs if SQL Server 2000 SP3 or SQL Server 2000 SP3a is not installed on the same computer on which you are trying to install MOM Reporting. In this case, the installation of MOM Reporting cannot be directed to an instance of SQL Server that is running on a different computer.

To resolve this problem, install SQL Server on the same computer on which you are trying to install MOM Reporting. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You receive an "Incorrect version of Microsoft SQL Server Reporting Services is installed," "Microsoft SQL Server 2000 SP3a or above required," or "SQL Server 2000 SP3 or later not detected" verification failure

You receive one or more error messages that resemble the following error messages:

Message 1Message 2Message 3 The message varies with the version of SQL Server and occurs when you start to install MOM 2005 Database components. This problem occurs because the Check Prerequisites task expects the version number of SQL Server Reporting Services to have a specific format.

To work around this problem, run the MOM Reporting installation to make sure that all prerequisites except SQL Server Reporting Services are successfully met. Then, use the Msiexec command to install MOM Reporting. To skip the Check Prerequisites task, use the PREREQ_COMPLETED=1 option. To install MOM Reporting by using the Msiexec command, use the following command syntax:Note You cannot apply this workaround when MOM 2005 Reporting is installed on a server cluster because of limitations in the silent installation features of MOM 2005. When you install MOM 2005 Reporting on a server cluster that is running SQL Server Reporting Services SP2, the installation is unsuccessful. In this situation, you must uninstall SQL Server Reporting Services. Then, you must reinstall SQL Server Reporting Services together with SQL Server Reporting Services Service Pack 1 (SP1) instead of with SQL Server Reporting Services SP2. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

You receive a "Microsoft World Wide Web Service is not installed" verification failure

When you try to install MOM Reporting, the prerequisite checking process fails. Additionally, the prerequisite report contains the following information.

Minimum Requirement	Recommended (if different from minimum)	Required For	Detected Value	Resolution
Microsoft World Wide Web Service is not installed	blank	MOM Reporting	Microsoft World Wide Web Service is not installed	blank

To resolve this problem, make sure that the World Wide Web Publishing service is started and that the startup mode is set to Automatic. If the World Wide Web Publishing service does not appear in the list of services, install Microsoft Internet Information Services (IIS).

You receive an "Unable to contact the Microsoft SQL Server Reporting Services server via Web service" verification failure

You may experience this problem if one or more of the following conditions are true.

The Reports virtual directory or the ReportServer virtual directory was not created in IIS during the installation of SQL Server Reporting Services

To resolve this problem, uninstall and then reinstall SQL Server Reporting Services.

You ran the Check Prerequisites process by itself

To resolve this problem, run the MOM Reporting installation program to verify the installation prerequisites. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

SQL Server Reporting Services is not configured to use Secure Sockets Layer (SSL)

If SQL Server Reporting Services is not configured to use SSL, you must make sure that the default Web site does not require SSL. To do this, follow these steps:

1. Start the Internet Information Services (IIS) Manager tool.
2. Locate and then right-click Default Web Site, and then click Properties.
3. Click the Directory Security tab, and then click Edit under Secure communications.
4. Click to clear the Require secure channel (SSL) check box, and then click OK two times.

The certificate that is bound to the SQL Server Reporting Services Web site lists the fully qualified domain name (FQDN) of the server instead of the NetBIOS name of the server

This problem occurs because the SQL Server Reporting Services Web configuration file uses the NetBIOS name of the server in the ReportServerURL parameter. This is true even if the certificate on the Web site uses the FQDN of the server. If the certificate on the Web site uses the FQDN of the server, you cannot open the Web site. Therefore, the MOM Reporting Check Prerequisites task cannot detect the Web site.

To resolve this problem, use one of the following methods, as appropriate for your situation.If SSL is not requiredIf SSL is not required, follow these steps:

1. Open the %ProgramFiles%\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config file by using a text editor such as Notepad.
2. Modify the following entry to change the value of 3 to 0 (zero):

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

   The modified entry appears as follows:

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

   
   
   Note A value of 3 indicates that SSL is configured.
3. Save the changes to the file, and then exit the text editor.

If SSL is requiredModify the RSWebApplication.config file to use the FQDN of the server. To do this, follow these steps:

1. Verify the FQDN that the certificate uses. To do this, follow these steps:
   1. Start the Internet Information Services (IIS) Manager tool.
   2. Locate and then right-click Default Web Site, and then click Properties.
   3. On the Directory Security tab, click View Certificate.
   4. Examine the information that is on the General tab and that is on the Certification Path tab of the certificate to make sure that warning information does not appear.
   5. Note the name that appears in the Issued to field on the General tab. This name is the FQDN of the server.
   6. Exit IIS Manager.
2. Add the FQDN of the server to the SQL Server Reporting Services Web configuration file. To do this, follow these steps:
   1. On the computer that is running SQL Server Reporting Services, open the RSWebApplication.config file by using a text editor such as Notepad. By default, this file is located in the following folder:

      %ProgramFiles%\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\

   2. Locate the following entry in the RSWebApplication.config file:

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

   3. Modify this entry to make it resemble the following:

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

      
      
      Important When you modify this entry, do not change "http" to "https."
   4. Save the changes to the RSWebApplication.config file, and then exit the text editor.
   5. Reset the IIS service. To do this, type iisreset at the command prompt, and then press ENTER.
   6. Verify that you can visit the SQL Server Reporting Services Web site by connecting to the following URL:

      https://Server FQDN/Reports

3. If you can successfully connect to the SQL Server Reporting Services Web site, install MOM Reporting.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You receive an "ASP.NET cannot be validated" verification failure

When you try to install the MOM 2005 Reporting component, and then you try to confirm the prerequisites for the component by clicking Check Prerequisites on the Setup Tasks tab of the Microsoft Operations Manager 2005 Setup Resources dialog box, you may receive the following error message:Additionally, when you click Install Microsoft Operations Manager, you may receive the following message on the Setup Tasks tab of the Microsoft Operations Manager 2005 Setup Resources dialog box:Also, when you click View Log, you receive the following error message: This problem occurs when you try to install the MOM Reporting component on a computer, but the MOM Reporting SystemCenterReporting database resides on a different computer.

To resolve this problem, install IIS on the computer before you install the MOM Reporting component. Then, you can uninstall IIS after you successfully install MOM Reporting. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You receive an "Access is denied" error message when you install MOM Reporting Services together with a remote SQL Server Reporting Services server

This problem occurs if the administrator account under which the installation runs does not have sufficient permissions to the registry on the remote computer that is running SQL Server Reporting Services.

To test access to the remote registry, start a command prompt on the computer on which you want to install the MOM Reporting component. Then, type the following command, and then press ENTER:To resolve this problem, verify the following:

• Make sure that File and Printer sharing is enabled on the computer that is running SQL Server Reporting Services.
• Make sure that the Remote Registry feature is enabled on the computer that is running SQL Server Reporting Services.
• Make sure that the administrator account under which the installation runs has sufficient rights to the HKEY_LOCAL_MACHINE registry hive on the remote computer. Alternatively, make sure that the administrator account under which the installation runs is a member of the local Administrators group on the remote computer.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

You receive an "Unable to contact the Microsoft SQL Server Reporting Services server via WMI" verification failure

This problem may occur if one or both of the following conditions are true:

• SQL Server Reporting Services cannot be contacted on the local computer or on the remote computer that was specified during the installation.
• You are running Microsoft SQL Server 2005 Reporting Services. This problem occurs because the Windows Management Instrumentation (WMI) namespace location was changed in SQL Server 2005 Reporting Services.

To resolve this problem, use one of the following methods, as appropriate for your situation.

Method 1

Verify that SQL Server Reporting Services is installed and configured on the local or remote computer. If you use a remote computer that is running SQL Server Reporting Services, make sure that you specify this during the installation of MOM Reporting.

Method 2

If you want to install MOM Reporting on a computer that is running SQL Server 2005 Reporting Services, click to clear the Automatically detect virtual directories check box in the SQL Server Reporting Services Server dialog box. Then, enter the name of the SQL Server 2005 Reporting Services report server virtual directory in the Report Server Virtual Directory box. Additionally, enter the name of the reports virtual directory in the Report Manager Virtual Directory box.

Note When you enter the virtual directory names, do not type the full URL to the virtual directory. Instead, type the name of the virtual directory only. By default, the report server virtual directory is named ReportServer. By default, the reports virtual directory is named Reports. If you do not know the names of the virtual directories, you can obtain them by using the IIS Microsoft Management Console (MMC) snap-in on the computer that is running SQL Server 2005 Reporting Services.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: