0x0000C351 | IPMGM was unable to initialize a critical section. The data is the exception code. |
IPMGM was unable to initialize a critical section. The data is the exception code. |
0x0000C352 | IPMGM was unable to create a heap. The data is the error code. |
IPMGM was unable to create a heap. The data is the error code. |
0x0000C353 | IPMGM was unable to allocate memory from its heap. The data is the error code. |
IPMGM was unable to allocate memory from its heap. The data is the error code. |
0x0000C354 | IPMGM received a start request when it was already running. |
IPMGM received a start request when it was already running. |
0x0000C355 | IPMGM was unable to create a synchronization object. The data is the error code. |
IPMGM was unable to create a synchronization object. The data is the error code. |
0x0000C356 | IPMGM was unable to create an event. The data is the error code. |
IPMGM was unable to create an event. The data is the error code. |
0x0000C357 | IPMGM was unable to create a semaphore. The data is the error code. |
IPMGM was unable to create a semaphore. The data is the error code. |
0x0000C358 | IPMGM has started successfully. |
IPMGM has started successfully. |
0x0000C359 | 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. |
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. |
0x0000C35A | IPMGM could not find the protocol component (%1, %2) |
IPMGM could not find the protocol component (%1, %2) |
0x0000C35B | Protocol component has already registered with IPMGM |
Protocol component has already registered with IPMGM |
0x0000C35C | IPMGM failed to register the protocol component. The data is in the error code. |
IPMGM failed to register the protocol component. The data is in the error code. |
0x0000C35D | The protocol component that is attempting to deregister is currently enabled on one or more interfaces. |
The protocol component that is attempting to deregister is currently enabled on one or more interfaces. |
0x0000C35E | This protocol component has already been enabled on this interface |
This protocol component has already been enabled on this interface |
0x0000C35F | Specified interface was not present in MGM. |
Specified interface was not present in MGM. |
0x0000C360 | 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. |
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. |
0x0000C361 | IGMP is not enabled on this interface |
IGMP is not enabled on this interface |
0x0000C362 | No routing protocol has been enabled on this interface |
No routing protocol has been enabled on this interface |
0x0000C363 | The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM |
The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM |
0x0000C364 | Interface cannot be deleted because IGMP is still active on this interface. |
Interface cannot be deleted because IGMP is still active on this interface. |
0x0000C365 | Failed to set timer for forwarding entry. The error code is in the data. |
Failed to set timer for forwarding entry. The error code is in the data. |
0x0000C366 | Failed to register with RTM. The error code is in the data. |
Failed to register with RTM. The error code is in the data. |
0x0000C3B3 | IPMGM has stopped. |
IPMGM has stopped. |
0x10000038 | Classic |
Classic |
0x90000001 | Microsoft-Windows-RasServer |
Microsoft-Windows-RasServer |