Microsoft Knowledge Base Email Alertz

SQL backup events triggering MOM events in Microsoft Operations Manager 2005

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: 909389 - Last Review: October 27, 2006 - Revision: 1.2

You receive two MOM event messages after you install the SQL Server 2000 Management Pack for MOM 2005

SYMPTOMS

After you install the Microsoft SQL Server 2000 Management Pack for Microsoft Operations Manager 2005, you receive the following two MOM 2005 event messages:

Message 1

Could not allocate memory for replication.

Message 2

The system tables for merge replication could not be dropped successfully.

These two MOM 2005 events are triggered by regular SQL Server backup informational events.

CAUSE

This problem occurs because the SQL Server 2000 Management Pack rule criteria is not specific enough.

RESOLUTION

To resolve this problem, prevent SQL Server backup informational events from triggering MOM 2005 events. To do this, follow these steps:
  1. Open the MOM 2005 Administrator Console, expand Management Packs, expand Rule Groups, expand Microsoft SQL Server, expand SQL Server 2000, expand SQL Server 2000 Event Collection, expand SQL Server Replication, and then click Event Rules.
  2. Right-click the Could not allocate memory for replication rule, click Properties, click the Criteria tab, and then click Advanced.
  3. In the Field list, click Event Type.
  4. In the Condition list, click not equals.
  5. In the Value list, click Information.
  6. Click Add to List, click Close, and then click OK.
  7. Right-click the The system tables for merge replication could not be dropped successfully rule, and then click Properties.
  8. Click the Criteria tab, and then click Advanced.
  9. In the Field list, click Event Type.
  10. In the Condition list, click not equals.
  11. In the Value list, click Information.
  12. Click Add to List, click Close, and then click OK.
  13. Right-click Management Packs in the left pane, and then click Commit Configuration Change to commit the configuration changes to the management group.

STATUS

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

MORE INFORMATION

Other Microsoft SQL Server informational events may also trigger the MOM 2005 event messages that are listed in the "Symptoms" section. The steps in the Resolution section will also prevent any other SQL informational events from triggering these MOM events.

APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbtshoot kbfix kbbug kbprb KB909389
       

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