Home
  •  

Protocol Initialization failure

Protocol_Initialization_failure_1_1_Rule (Rule)

Knowledge Base article:

Management Pack

Summary

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 because there are not enough available system resources ed. 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 that 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 information about configured network interfaces. The data is the error code.
Sample Event#6: IPRIPv2 was unable to initialize a table to hold information about neighboring IPRIP routers. The data is the error code.
Sample Event#7: IPRIPv2 was unable to initialize a table to hold information about 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.2008.Server
CategoryEventCollection
EnabledTrue
Alert GenerateFalse
RemotableTrue
Event LogSystem

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
WriteToDB WriteAction Microsoft.SystemCenter.CollectEvent Default

Source Code:

<Rule ID="Protocol_Initialization_failure_1_1_Rule" Enabled="true" Target="Microsoft.Windows.Server.RRAS.2008.Server" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>System</LogName>

      <Expression>

        <And>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesRegularExpression</Operator>

              <Pattern>^(30001|30003|30004|30005|30006|30008|30009|30010|30011|30013|30054|30055)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>ContainsSubstring</Operator>

              <Pattern>IPRIP2</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectEvent"/>

  </WriteActions>

</Rule>