MOM 2000 Generates Numerous Entries About Event ID 21252 (300076)



The information in this article applies to:

  • Microsoft Operations Manager 2000

This article was previously published under Q300076

SUMMARY

This article describes why Microsoft Operations Manager (MOM) may log a large number of instances of Event ID 21252.

MORE INFORMATION

MOM logs a large number of instances of Event ID 21252 if the Agent Manager attempts to process responses on an item whose timeout has expired. Multiple entries within a short period of time may indicate that a timed event is occurring too frequently, for example, if the time it takes to run an associated script exceeds the time interval between events.

Note that Event ID 21252 is normally benign and has no adverse impact on MOM.

The error message that you receive about Event ID 21252 may read as follows:
The Operations agent attempted to process responses on an item whose timeout has expired. This event is normally benign, and will often occur when the system attempts to process timed events generated during an earlier run. If you see these events frequently, however, it may mean that some timed event is occurring too frequently, possibly because it runs a script that takes longer to run than the interval between the events.
You can use the search utility within the MOM Administrator Console to find the rule that is generating the events. Examine the parameters of the script and increase the timeout value, or if no timeout parameter is available, reconfigure the timed event so that it triggers the rule at a lower interval.

Alternatively, you can run a query on the OnePoint database to find the rule that is generating the events. Start the Microsoft SQL Server Query Analyzer tool, and then run the following query on the OnePoint database:

Select * from processrule where idprocessrule='Enter the ruleid GUID here'

The results of this query identify the group where the relevant item resides so that you can locate and reconfigure the item.

Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbinfo kbpolicy KB300076