Home
  •  

Protocol initialization failure

Protocol_initialization_failure_2_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary
The DHCP Relay Agent (IPBOOTP) encountered an error during initialization.
 
Causes
The most common reasons for this error are:
  1. The protocol 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.
 
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: IPBOOTP was unable to initialize a critical section.The data is the exception code.
Sample Event#2: IPBOOTP was unable to allocate memory from its heap.The data is the error code.
Sample Event#3: IPBOOTP was called to start when it was already running.
Sample Event#4: IPBOOTP was unable to initialize Windows Sockets.The data is the error code.
Sample Event#5: IPBOOTP was unable to create a synchronization object.The data is the exception code.
Sample Event#6: IPBOOTP was unable to create a table to hold interface information.The data is the error code.
Sample Event#7: IPBOOTP was unable to create a semaphore.The data is the error code.
Sample Event#8: IPBOOTP was unable to create an event.The data is the error code.
Sample Event#9: IPBOOTP was unable to create a timer queue using CreateTimerQueue.The data is the error code.
Sample Event#10: IPBOOTP was unable to register an event with the ntdll wait threads.The data is the error code.
 
© 2004 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.Windows.RemoteAccess.2012.Class.VPNServer
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_2_1_Rule" Enabled="true" Target="Microsoft.Windows.RemoteAccess.2012.Class.VPNServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

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

      <ComputerName>$Target/Host/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|30007|30008|30009|30010|30029)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

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

              </ValueExpression>

              <Operator>ContainsSubstring</Operator>

              <Pattern>IPBOOTP</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

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

  </WriteActions>

</Rule>