Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 917665 - Last Review: October 27, 2006 - Revision: 1.2
Event ID 21213 or event ID 21216 occurs and you cannot connect to the OnePoint database in Microsoft Operations Manager 2005
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.
Collapse this tableExpand this table
| Event ID number | Basic description |
|---|
| 21213 | Indicates a Heartbeat update failure from one or more MOM agents
|
| 21216 | Indicates that the MOM server was not able to process incoming configuration information |
Additionally, the following event messages may be logged in the Application log.
Collapse this tableExpand this table
| Event ID number | Basic 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
|
| 25101 | Indicates a failure to insert data into the database
|
| 25102 | indicates an unrecoverable database error
|
| 21268 | Indicates that the incoming queue is blocked and is not able to accept data. |
| 21269 | Indicates that the queue has been unblocked and can accept data
|
| 25402 | Indicates that the WMI provider could not register a query |
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.
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.
To resolve this problem, follow these steps:
- Set the OnePoint database recovery model to Simple. To do this, follow these steps:
- Open SQL Server Enterprise Manager.
- Under Microsoft SQL Server, expand SQL Server Group.
- Click the name of the server computer that is hosting the OnePoint database, and then expand Databases.
- Right-click the OnePoint database, and then click Properties
- In the OnePoint Properties dialog box, click the Options tab.
- In the Recovery section, select Simple from the Model menu, and then click OK.
- Truncate the transaction log by backing up the OnePoint database.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft Operations Manager (MOM) 2005
- Microsoft Operations Manager 2000 Enterprise Edition
| kbexpertiseinter kbtshoot kbfix kbprb KB917665 |
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