Protocol Initialization failure

Protocol_Initialization_failure_1_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary
The Routing Information Protocol version 2 (RIPv2) encountered an error during initialization.
 
Causes
The most common reasons for this error are:
  1. The protocol initialization failed as there are not enough available system resources that are required. The system could be running in low memory.
  2. The protocol received a request to start when it is already started.
  3. The protocol failed to register with Route Table Manager (RTM). The most common reason for this error is registry information could be corrupt or not found.
 
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. Stop and restart the Routing and Remote Access service.
  3. If the problem persists, you might need to repair or reinstall the Windows operating system.
 
Sample Event
Sample Event#1: IPRIPv2 was unable to initialize a critical section.The data is the exception code.
Sample Event#2: IPRIPv2 received a start request when it was already running.
Sample Event#3: IPRIPv2 was unable to start Windows Sockets.The data is the error code.
Sample Event#4: IPRIPv2 was unable to create a synchronization object.The data is the error code.
Sample Event#5: IPRIPv2 was unable to initialize a table to hold informationabout configured network interfaces.The data is the error code.
Sample Event#6: IPRIPv2 was unable to initialize a table to hold informationabout neighboring IPRIP routers.The data is the error code.
Sample Event#7: IPRIPv2 was unable to initialize a table to hold informationabout local IP addresses.The data is the error code.
Sample Event#8: IPRIPv2 was unable to create a semaphore.The data is the error code.
Sample Event#9: IPRIPv2 was unable to register with the Routing Table Manager.The data is the error code.
Sample Event#10: IPRIPv2 could not register a timer queue with the Ntdll thread.The data is the error code.
Sample Event#11: IPRIPv2 was unable to allocate memory from its heap.The data is the error code.
Sample Event#12: IPRIPv2 could not register an event with the Ntdll wait thread.The data is the error code.
 
© 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 GenerateTrue
Alert SeverityError
Alert PriorityLow
RemotableTrue
Alert Message
Protocol Initialization failure

$Data/EventDescription$
Event LogSystem
CommentMom2005ID='{E868F350-CCA2-47A7-B13C-5A8D1BFAA0B8}';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="Protocol_Initialization_failure_1_1_Rule" Target="Microsoft.Windows.Server.RRAS.Microsoft_Windows_2003_Routing_and_Remote_Access_Servers_Installation" Enabled="true" ConfirmDelivery="true" Comment="Mom2005ID='{E868F350-CCA2-47A7-B13C-5A8D1BFAA0B8}';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>^(30001|30003|30004|30005|30006|30008|30009|30010|30011|30013|30054|30055)$</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>true</GenerateAlert>
<Owner/>
<Description>
$Data/EventDescription$
</Description>
<AlertLevel>70</AlertLevel>
<ResolutionState/>
<Source>
$Data/PublisherName$
</Source>
<Name>Protocol Initialization failure</Name>
<CustomFields>
<CustomField>
$Data/Params/Param[1]$
</CustomField>
<CustomField>
$Data/Params/Param[2]$
</CustomField>
<CustomField/>
<CustomField/>
<CustomField/>
</CustomFields>
</AlertGeneration>
<InvokerType>0</InvokerType>
</WriteAction>
<WriteAction ID="CollectEventData" TypeID="SystemCenterLibrary!Microsoft.SystemCenter.CollectEvent"/>
<WriteAction ID="CollectEventDataWarehouse" TypeID="DataWarehouseLibrary!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>