Microsoft-Windows-RasServer
Event ID 50001: IPMGM was unable to initialize a critical section.
#Description
IPMGM was unable to initialize a critical section. The data is the exception code.
Message #
Event ID 50002: IPMGM was unable to create a heap.
#Description
IPMGM was unable to create a heap. The data is the error code.
Message #
Event ID 50003: IPMGM was unable to allocate memory from its heap.
#Description
IPMGM was unable to allocate memory from its heap. The data is the error code.
Message #
Event ID 50004: IPMGM received a start request when it was already running.
#Event ID 50005: IPMGM was unable to create a synchronization object.
#Description
IPMGM was unable to create a synchronization object. The data is the error code.
Message #
Event ID 50006: IPMGM was unable to create an event.
#Description
IPMGM was unable to create an event. The data is the error code.
Message #
Event ID 50007: IPMGM was unable to create a semaphore.
#Description
IPMGM was unable to create a semaphore. The data is the error code.
Message #
Event ID 50008: IPMGM has started successfully.
#Event ID 50009: IPMGM could not schedule a task to be executed.
#Description
IPMGM could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the error code.
Message #
Event ID 50010: IPMGM could not find the protocol component (param1, param2).
#Event ID 50011: Protocol component has already registered with IPMGM
#Event ID 50012: IPMGM failed to register the protocol component.
#Description
IPMGM failed to register the protocol component. The data is in the error code.
Message #
Event ID 50013: The protocol component that is attempting to deregister is currently enabled on one or more interfaces.
#Event ID 50014: This protocol component has already been enabled on this interface
#Event ID 50015: Specified interface was not present in MGM.
#Event ID 50016: Another routing protocol component has already been enabled on this interface.
#Description
Another routing protocol component has already been enabled on this interface. Only one routing protocol component may be enabled on an interface at any time.
Message #
Event ID 50017: IGMP is not enabled on this interface
#Event ID 50018: No routing protocol has been enabled on this interface
#Event ID 50019: The handle specified by the protocol component is not valid.
#Description
The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM.
Message #
Event ID 50020: Interface cannot be deleted because IGMP is still active on this interface.
#Message #
Event ID 50021: Failed to set timer for forwarding entry.
#Description
Failed to set timer for forwarding entry. The error code is in the data.
Message #
Event ID 50022: Failed to register with RTM.
#Description
Failed to register with RTM. The error code is in the data.
Message #
Event ID 50099: IPMGM has stopped.
#Provenance
ETW provider GUID 29d13147-1c2e-48ec-9994-e29dfe496eb3
Defined in rtm.dll, which carries the event manifest.
- WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02 — Manifest XML pack, 1.9 MB
- Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02 — Manifest XML pack, 2.0 MB