Event ID 21213 or event ID 21216 occurs and you cannot connect to the OnePoint database in Microsoft Operations Manager 2005 (917665)


The information in this article applies to:

  • Microsoft Operations Manager 2005
  • Microsoft Operations Manager 2000

SYMPTOMS

When you use the OnePoint database on a computer that is running Microsoft Operations Manager (MOM) 2005 or MOM 2000, the size of the OnePoint database increases quickly. Therefore, some MOM rule scripts may run in an infinite loop.

When this problem occurs, one or more of the following event messages may be logged in the Application log.
Event ID numberBasic description
21213Indicates a Heartbeat update failure from one or more MOM agents
21216Indicates that the MOM server was not able to process incoming configuration information
Additionally, the following event messages may be logged in the Application log.
Event ID numberBasic description
21418 (MOM 2000 only)Indicates a script running in an infinite loop
21421 (MOM 2005 only)Indicates a script running in an infinite loop
25101Indicates a failure to insert data into the database
25102indicates an unrecoverable database error
21268Indicates that the incoming queue is blocked and is not able to accept data.
21269Indicates that the queue has been unblocked and can accept data
25402 Indicates that the WMI provider could not register a query
Note On a computer that is running MOM 2005, you can also view the event messages in the previous tables in the event views pane of the Operator console.

CAUSE

This problem occurs because the transaction log runs out of space. This behavior may occur if the OnePoint database Recovery Model is set to Full and if a backup has not been run for some time. In this situation, you can only truncate the transaction logs by backing up the transaction log.

RESOLUTION

To resolve this problem, follow these steps:
  1. Set the OnePoint database recovery model to Simple. To do this, follow these steps:
    1. Open SQL Server Enterprise Manager.
    2. Under Microsoft SQL Server, expand SQL Server Group.
    3. Click the name of the server computer that is hosting the OnePoint database, and then expand Databases.
    4. Right-click the OnePoint database, and then click Properties
    5. In the OnePoint Properties dialog box, click the Options tab.
    6. In the Recovery section, select Simple from the Model menu, and then click OK.
  2. Truncate the transaction log by backing up the OnePoint database.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MajorLast Reviewed:6/27/2006
Keywords:kbExpertiseInter kbtshoot kbfix kbprb KB917665 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.