Microsoft Knowledge Base Email Alertz

The Reporting DTS task does not run and reports do not work when Microsoft Operations Manager (MOM) 2005 fails over to the secondary node of a server cluster

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: 938439 - Last Review: August 2, 2007 - Revision: 1.1

The Reporting DTS task does not run and reports do not work when Microsoft Operations Manager (MOM) 2005 fails over to the secondary node of a server cluster

SYMPTOMS

Consider the following scenario. You install Microsoft Operations Manager (MOM) 2005 on a server cluster. MOM 2005 fails over to the secondary node of the server cluster. In this scenario, the MOM 2005 Reporting Data Transformation Services (DTS) task no longer runs successfully. Therefore, MOM reports do not work when MOM 2005 runs on the secondary cluster node. If you fail back MOM 2005 to the primary cluster node, MOM 2005 works as expected.

CAUSE

When you install MOM 2005 on the secondary node of a server cluster, the MOM 2005 installation program does not add the user logon information to Microsoft SQL Server. Therefore, when MOM 2005 fails over to the secondary cluster node, the user account under which the DTS task runs cannot access the following databases:
  • The OnePoint database
  • The SystemCenterReporting database

WORKAROUND

To work around this problem, manually configure the appropriate MOM database rights for the secondary cluster node. To do this, follow these steps.

Note In these steps, the secondary cluster node is named Cluster2.
  1. Fail over or move the group that contains the MOM 2005 resources to the secondary cluster node. For this article, fail over or move the group to Cluster2.
  2. Start the SQL Server Management Studio program, and then run the following SQL Server statement:
    Use OnePoint
    Go
    execute p_SetupLogins 'example\momDAS','Cluster2',0
    Note In this code, example\momDAS represents the name of the Data Access Server (DAS) account in MOM 2005.
  3. Run the following SQL Server statement:
    Use SystemCenterReporting
    Go
    execute p_SetupLogins 'Cluster2'

STATUS

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

MORE INFORMATION

For more information about how to install the MOM database on a server cluster, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc179693.aspx (http://technet.microsoft.com/en-us/library/cc179693.aspx)

APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbtshoot kbprb kbpending kbbug KB938439
       

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