Microsoft Knowledge Base Email Alertz

When you to try to install Microsoft Operations Manager 2005 Reporting on a computer that is running Microsoft SQL Server 2005, the installation fails

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 922337 - Last Review: August 21, 2007 - Revision: 3.1

When you to try to install Microsoft Operations Manager 2005 Reporting on a computer that is running Microsoft SQL Server 2005, the installation fails

SYMPTOMS

When you to try to install Microsoft Operations Manager (MOM) 2005 Reporting on a computer that is running Microsoft SQL Server 2005, the installation fails. Additionally, the following error may be logged in the System event log:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: date
Time: time
User: user name
Computer: computer name
Description:
Product: Microsoft Operations Manager 2005 Reporting -- Error 25316. WMI error accessing SQL Services Reporting Server. Error Code: -2147467259 (Unspecified error).
For more information, see Help and Support Center at http://support.microsoft.com.
Data:
0000: 7b 36 33 43 38 34 37 43 {63C847C
0008: 36 2d 30 37 41 30 2d 34 6-07A0-4
0010: 41 36 46 2d 38 41 37 38 A6F-8A78
0018: 2d 38 41 30 36 36 43 39 -8A066C9
0020: 46 39 37 37 33 7d F9773}

CAUSE

This problem occurs when the following conditions are true:
  • You try to install MOM 2005 Reporting on a computer that is running a 32-bit version of Microsoft SQL Server 2005.
  • The 32-bit version of SQL Server 2005 is running on a cluster that is based on a 64-bit version of Microsoft Windows Server 2003.
  • You do not provide the full Microsoft Windows Installer path in the command line. For example, you type a command that resembles the following:
    msiexec /i momreporting.msi SQLSVR_INSTANCE=MOM ROSETTA_SERVER=computer name TASK_USER_ACCOUNT=S-MOM DTS account TASK_USER_PASSWORD=password TASK_USER_DOMAIN=SPS REPORTING_USER=S-MOM Reporting account REPORTING_PASSWORD=password REPORTING_DOMAIN=domain name MOM_DB_SERVER=computer name\MOMvAUTOMATICALLY_DETECT_ROSETTA_VDIRS=1 REPORT_SERVER_URL=ReportServer REPORT_URL=Reports PREREQ_COMPLETED=1 /l* c:\mom.log /qn

RESOLUTION

To resolve this problem, type the full Windows Installer path in the command that you type when you install MOM 2005 Reporting. For example, type a command that resembles the following:
msiexec.exe /i "\\path\momreporting.msi" /lv* D:\logs\REPORTING_Install.log MOM_DB_SERVER="computer name\Instance" SQLSVR_INSTANCE="computer name\Instance" TASK_USER_ACCOUNT="MOM DTS account" TASK_USER_DOMAIN="domain name" TASK_USER_PASSWORD="password" REPORTING_USER="MOM Reporting account" REPORTING_DOMAIN="domain" REPORTING_PASSWORD="password" ROSETTA_SERVER="computer name" PREREQ_COMPLETED="1" REPORT_SERVER_VDIR="ReportServer" REPORT_MANAGER_VDIR="Reports" AUTOMATICALLY_DETECT_ROSETTA_VDIRS="0" /Qn

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Under certain conditions, you must install MOM 2005 Reporting by using the MSIExec command. For example, install MOM 2005 Reporting by using the MSIExec command when you are using a configuration that resembles the following:
  • A MOM server that is running the following software:
    • A 32-bit version of Windows Server 2003 R2
    • The MOM Management service
    • The Management Web console
    • Microsoft Management Console (MMC)
  • A SQL Server 2005 cluster that is configured as follows:
    • First node configuration
      • A 64-bit version of Windows Server 2003 R2
      • Microsoft ASP.NET 1.1 and ASP.NET 2.0
      • SQL Server non-clustered instances
        • A named instance of SQL Server 2005 Standard Edition (32-bit) that is hosting the MOM OnePoint database
        • A named instance of SQL Server 2005 Standard Edition (32-bit) that is hosting the Reporting Services database
    • Second node configuration
      • A 64-bit version of Windows Server 2003 R2
      • ASP.NET 2.0
      • SQL Server clustered instances
        • A default instance of SQL Server 2005 Standard Edition (32-bit)
        • A named instance of SQL Server 2005 Standard Edition (32-bit)
If you are running this sample configuration, you must install MOM 2005 Reporting by using the MSIExec command. You cannot select a non-clustered instance by using the MOM 2005 Reporting Service Setup Wizard. Although you can select the clustered 64-bit version of SQL Server by using the wizard, this version of SQL Server 2005 is not supported. To install MOM 2005 Reporting on the supported version of SQL Server 2005 (32-bit), run the MSIExec command.

However, the MSIExec command that is documented on the following Microsoft Web site does not run successfully for the sample configuration:
http://technet.microsoft.com/en-us/library/cc179728.aspx (http://technet.microsoft.com/en-us/library/cc179728.aspx)
The MSIExec command fails because the full path of the .msi file must be specified in the command line.

For more information about supported Microsoft SQL Server 2005 configurations, click the following article number to view the article in the Microsoft Knowledge Base:
917615  (http://kbalertz.com/Feedback.aspx?kbNumber=917615/ ) The MOM 2005 Service Pack 1 operational database and Reporting data warehouse now support SQL Server 2005

APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbtshoot kbprb KB922337
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate