Router manager's entry point to protocol failed

Router_manager_s_entry_point_to_protocol_failed_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary
The Routing Information Protocol version 2 (RIPv2) encountered an error in protocol''s callback function(s) to Router Manager.
 
Causes
The most common reasons for this error are:
  1. There is no enough available memory in the system.
  2. The protocol could not be enabled on the interface.
 
Resolutions
  1. If the server is low on memory, take appropriate action to increase the available memory. See Help and Support Center for information on low memory.
  2. Verify the configuration of the interface and make sure that RIP is enabled on it.
 
Sample Event
Sample Event#1: IPRIPv2 was unable to allocate memory from its heap.The data is the error code.
Sample Event#2: IPRIPv2 could not bind to IP address %1.Please make sure TCP/IP is installed and configured correctly.The data is the error code.
Sample Event#3: IPRIPv2 could not schedule a task to be executed.This may have been caused by a memory allocation failure.The data is the error code.
Sample Event#4: IPRIPV2 could not be enabled on the interface.Parameter %1 has an invalid value %2.
 
© 2004 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.Windows.Server.RRAS.Microsoft_Windows_2003_Routing_and_Remote_Access_Servers_Installation
CategoryEventCollection
EnabledTrue
Event SourceIPRIP2
Alert GenerateFalse
RemotableTrue
Event LogSystem
CommentMom2005ID='{B74F02FC-7CF4-4C22-BBA8-282C150DDEC2}';MOM2005ComputerGroupID={2C66DD87-4D20-48F6-B6A3-19A1598ED025}

Member Modules:

ID Module Type TypeId RunAs 
_907D4578_146C_11D3_AB21_00A0C98620CE_ DataSource Microsoft.Windows.EventProvider Default
CollectEventData WriteAction Microsoft.SystemCenter.CollectEvent Default
CollectEventDataWarehouse WriteAction Microsoft.SystemCenter.DataWarehouse.PublishEventData Default
GenerateAlert WriteAction System.Mom.BackwardCompatibility.AlertResponse Default

Source Code:

<Rule ID="Router_manager_s_entry_point_to_protocol_failed_1_Rule" Target="Microsoft.Windows.Server.RRAS.Microsoft_Windows_2003_Routing_and_Remote_Access_Servers_Installation" Enabled="true" ConfirmDelivery="true" Comment="Mom2005ID='{B74F02FC-7CF4-4C22-BBA8-282C150DDEC2}';MOM2005ComputerGroupID={2C66DD87-4D20-48F6-B6A3-19A1598ED025}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_907D4578_146C_11D3_AB21_00A0C98620CE_" Comment="{907D4578-146C-11D3-AB21-00A0C98620CE}" TypeID="WindowsLibrary!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesMOM2005BooleanRegularExpression</Operator>
<Pattern>^(30003|30016|30017|30056)$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>IPRIP2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.AlertResponse">
<AlertGeneration>
<GenerateAlert>false</GenerateAlert>
</AlertGeneration>
<InvokerType>1</InvokerType>
</WriteAction>
<WriteAction ID="CollectEventData" TypeID="SystemCenterLibrary!Microsoft.SystemCenter.CollectEvent"/>
<WriteAction ID="CollectEventDataWarehouse" TypeID="DataWarehouseLibrary!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>