Protocol initialization failure

Protocol_initialization_failure_1_Rule (Rule)

Knowledge Base article:

Management Pack
The Internet Group Management Protocol version 2 (IGMPv2) encountered an error during initialization.
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.
  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: IGMP was unable to initialize a critical section.The data is the exception code.
Sample Event#2: IGMP received a start request when it was already running.
Sample Event#3: IGMP was unable to start Windows Sockets.The data is the error code.
Sample Event#4: IGMP was unable to create a semaphore.The data is the error code.
© 2004 Microsoft Corporation, all rights reserved.

Element properties:

Alert GenerateFalse
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_Rule" Enabled="true" Target="Microsoft.Windows.RemoteAccess.2012.Class.VPNServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
<XPathQuery Type="String">PublisherName</XPathQuery>
<WriteAction ID="WriteToDB" TypeID="SystemCenter!Microsoft.SystemCenter.CollectEvent"/>