Initialization failure

Initialization_failure_1_Rule (Rule)

Knowledge Base article:

Management Pack


The Multicast Group Manager (MGM) encountered an error during initialization.



The most common reasons for this error are:

1.     The protocol failed because 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.

Sample Event

Sample Event#1: IPMGM was unable to allocate memory from its heap. The data is the error code.
Sample Event#2: IPMGM received a start request when it was already running.
Sample Event#3: IPMGM was unable to create a semaphore. The data is the error code.
Sample Event#4: Failed to register with RTM. The error code is in the data.


© 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="Initialization_failure_1_Rule" Enabled="true" Target="Microsoft.Windows.Server.RRAS.2008.Server" 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="SC!Microsoft.SystemCenter.CollectEvent"/>