Microsoft-Windows-MPRMSG

253 events across 1 channel

Event IDTitleChannel
20001Cannot load the NetBIOS gateway DLL component because of the following error.Operational
20002Cannot access registry key values.Operational
20003Cannot enumerate Registry key values.Operational
20004Parameter %1 has an invalid type.Operational
20005Cannot enumerate the Remote Access Connection Manager ports.Operational
20006The Remote Access Service is not configured to receive calls or all ports …Operational
20007Cannot receive initial frame on port {param1} because of the following error: …Operational
20008The user connected to port {param1} has been disconnected due to inactivity.Operational
20009The user connected to port %1 has been disconnected because there is not enough …Operational
20010The user connected to port %1 has been disconnected due to a system error.Operational
20011The user connected to port %1 has been disconnected due to a critical network …Operational
20012The user connected to port %1 has been disconnected due to a critical network …Operational
20013The communication device attached to port %1 is not functioning.Operational
20014The user {param1} has connected and failed to authenticate on port {param2}.Operational
20015The user {param1} has connected and has been successfully authenticated on port …Operational
20016The user connected to port %1 has been disconnected because there was a …Operational
20018Cannot reset the network adapter for LANA %1.Operational
20019Remote Access Server Security Failure.Operational
20020Remote Access Server Security Failure.Operational
20021Remote Access Server Security Failure.Operational
20022Remote Access Server Security Failure.Operational
20023Remote Access Server Security Failure.Operational
20024Remote Access Server Security Failure.Operational
20025The user connected to port %1 has been disconnected because there are no …Operational
20026The user connected to port %1 has been disconnected because of a failure to lock …Operational
20027Remote Access Connection Manager failed to start because NDISWAN could not be …Operational
20028Remote Access Connection Manager failed to start because it could not initialize …Operational
20029Remote Access Connection Manager failed to start because no endpoints were …Operational
20030Remote Access Connection Manager failed to start because it could not load one …Operational
20031Remote Access Connection Manager failed to start because it could not locate …Operational
20032Remote Access Connection Manager failed to start because it could not access …Operational
20033Remote Access Connection Manager failed to start because it could not register …Operational
20034Remote Access Connection Manager failed to start because it could not create …Operational
20035Remote Access Connection Manager failed to start because it could not create …Operational
20036Remote Access Connection Manager failed to start because it could not access …Operational
20037Remote Access Connection Manager service failed to start because it could not …Operational
20038Remote Access Server Configuration Error.Operational
20039RASSER.Operational
20040An attempt by RASSER.Operational
20041RASMXS.Operational
20042The Remote Access server cannot allocate a route for the user connected on port …Operational
20043Cannot allocate memory in the admin support thread for the Remote Access …Operational
20044Cannot create an instance thread in the admin support thread for the Remote …Operational
20045Cannot create a named pipe instance in the admin support thread for the Remote …Operational
20046General named pipe failure occurred in the admin support thread for the Remote …Operational
20047An invalid request was sent to the admin support thread for the Remote Access …Operational
20048The user {param1} connected on port {param2} on {param3} at {param4} and …Operational
20049The user connected to port {param1} has been disconnected because the …Operational
20050The user {param1} connected to port {param2} has been disconnected because no …Operational
20051The user connected to port %1 has been disconnected because an internal …Operational
20052The NetBIOS gateway has been configured to access the network but there are no …Operational
20053The user %1 established a NetBIOS session between the remote workstation %2 and …Operational
20054Remote Access Service failed to start because the Remote Access Connection …Operational
20055Cannot add the remote computer name %1 on LANA %2 for the client being connected …Operational
20056Cannot delete the remote computer name %1 from LANA %2 for the client being …Operational
20057Cannot add the remote computer group name %1 on LANA %2.Operational
20058Cannot delete the remote computer group name %1 from LANA %2.Operational
20059The modem on %1 moved to an unsupported BPS rate.Operational
20060The serial driver could not allocate adequate I/O queues.Operational
20061Remote Access Connection Manager could not reopen biplex port %1.Operational
20062Internal Error: Disconnect operation on %2 completed with an error.Operational
20063Remote Access Connection Manager failed to start because the Protocol engine [.Operational
20064Remote Access service failed to start because the all Protocol engine failed to …Operational
20065The Remote Access Gateway Proxy could not create a process.Operational
20066The Remote Access Gateway Proxy could not create a named pipe.Operational
20067The Remote Access Gateway Proxy could not establish a named pipe connection with …Operational
20068A general error occurred reading from the named pipe in the Remote Access Proxy.Operational
20069Cannot open or obtain information about the PPP key or one of its subkeys.Operational
20070Point to Point Protocol engine was unable to load the %1 module.Operational
20071The Point to Point Protocol module %1 returned an error while initializing.Operational
20072The Point to Point Protocol failed to load the required PAP and/or CHAP …Operational
20073The following error occurred in the Point to Point Protocol module on port: …Operational
20076The password for user {param1}\{param2} connected on port {param3} has expired.Operational
20077The account for user {param1}\{param2} connected on port {param3} has expired.Operational
20078The account for user {param1}\{param2} connected on port {param3} does not have …Operational
20079The software version of the user %1\%2 connected on port %3 is unsupported.Operational
20080The server machine is configured to require data encryption.Operational
20081Remote Access Server Security Failure.Operational
20082The Remote Access Server could not reset lana %1 (the error code is the data) …Operational
20084The Remote Access Server will stop using IP Address %1.Operational
20085The Remote Access Server was unable to renew the lease for IP Address %1 from …Operational
20086The Remote Access Server was unable to acquire an IP Address from the DHCP …Operational
20087The Remote Access Server was unable to acquire an IP Address from the DHCP …Operational
20088The Remote Access Server acquired IP Address %1 to be used on the Server …Operational
20089The Remote Access Server's attempt to callback user {param1} on port {param2} at …Operational
20090A general error occurred writing to the named pipe in the Remote Access Proxy.Operational
20091Cannot open the RAS security host Registry key.Operational
20092Cannot load the Security host module component.Operational
20093The user %1 has connected and failed to authenticate with a third party security …Operational
20094The user connected to port %1 has been disconnected because the following …Operational
20095Cannot receive initial data on port {param1} because of the following error: …Operational
20096The user was authenticated as %1 by the third party security host module but was …Operational
20097A user was unable to connect on port {param1}.Operational
20098A user was unable to connect on port %1.Operational
20099Cannot access Registry value for %1.Operational
20100Cannot access the Registry key %1.Operational
20101Using the default value for Registry parameter %1 because the value given is not …Operational
20102Cannot enumerate keys of Registry key %1.Operational
20103Unable to load %1.Operational
20104Memory allocation failure.Operational
20105Unable to load the interface %1 from the registry.Operational
20106RoutingDomainID- %1: Unable to add the interface %2 with the Router Manager for …Operational
20107RoutingDomainID- %1: Unable to remove the interface %2 with the Router Manager …Operational
20108Unable to open the port %1 for use.Operational
20109Cannot recognize initial frame received on port {param1}.Operational
20110An error occurred in the Point to Point Protocol module on port %1 while trying …Operational
20111RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 on port …Operational
20112Cannot open the RAS third party administration host DLL Registry key.Operational
20113Cannot load the RAS third party administration DLL component.Operational
20114The Service will not accept calls.Operational
20125RoutingDomainID- %1: A Demand Dial persistent connection to the remote interface …Operational
20126A packet from %1 destined to %2 over protocol 0x%3 caused interface %4 to be …Operational
20127RoutingDomainID- %1: The Demand Dial interface %2 was not loaded.Operational
20128Cannot load the Appletalk Remote Access DLL component because of the following …Operational
20129An error occurred in the Appletalk Remote Access Protocol module on port …Operational
20130The following error occurred in the Appletalk Remote Access Protocol module on …Operational
20131A user was unable to connect on port {param1}.Operational
20132Remote Access Connection Manager failed to start because the RAS RPC module …Operational
20138RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 failed …Operational
20139The port {param1} has been disconnected due to inactivity.Operational
20140The port {param1} has been disconnected because the user reached the maximum …Operational
20141The user {param1} has connected and has been successfully authenticated on port …Operational
20142The user {param1} has connected and has been successfully authenticated on port …Operational
20143Unable to load the interface %1 from the registry.Operational
20144The Demand-Dial interface %1 was not registered with the Router.Operational
20145Cannot initialize the Remote Access and Router service to accept calls using the …Operational
20146The RADIUS server %1 did not respond to the initial request.Operational
20147The Remote Access service failed to start because the Point to Point was not …Operational
20148The RADIUS server name %1 could not be successfully resolved to an IP address.Operational
20149No global configuration was supplied to the IP Router Manager.Operational
20150Unable to add demand dial filters for interface %1.Operational
20151The Control Protocol %1 in the Point to Point Protocol module %2 returned an …Operational
20152The currently configured authentication provider failed to load and initialize …Operational
20153The currently configured accounting provider failed to load and initialize …Operational
20157The interface %1 could not be enabled for multicast.Operational
20158The user {param1} successfully established a connection to {param2} using the …Operational
20159The connection to {param1} made by user {param2} using device {param3} was …Operational
20161The user {param1} successfully established a connection to {param2} using the …Operational
20162The Remote Access Server established a connection to {param1} for the user …Operational
20163The connection to {param1} made by user {param2} using device {param3} was …Operational
20164The Remote Access Server wants to disconnect a link in the connection to …Operational
20165A connection has been established on port %1 using interface %2, but no IP …Operational
20166A connection has been established on port %1 using interface %2, but the remote …Operational
20167RoutingDomainID- %1: No IP address is available to hand out to the dial-in …Operational
20168Could not retrieve the Remote Access Server's certificate due to the following …Operational
20169Unable to contact a DHCP server.Operational
20170The user %1 has connected and failed to authenticate because of the following …Operational
20171Failed to apply IP Security on port %1 because of error: %2.Operational
20172Multicast scope mismatch with %1: Locally-configured name "%2", …Operational
20173Multicast scope address mismatch for scope ".Operational
20174Possible leaky multicast Local Scope detected between this machine and %1, since …Operational
20175Multicast scope '.Operational
20176A leak was detected in multicast scope '.Operational
20177Interface %1 is unreachable because of reason %2.Operational
20178Interface %1 is now reachable.Operational
20179RoutingDomainID- %1: Interface %2 is unreachable because there are no modems (or …Operational
20180RoutingDomainID- %1: Interface %2 is unreachable because the connection attempt …Operational
20181RoutingDomainID- %1: Interface %2 is unreachable because it has been …Operational
20182RoutingDomainID- %1: Interface %2 is unreachable because the Routing and …Operational
20183RoutingDomainID- %1: Interface %2 is unreachable because it is not allowed to …Operational
20184RoutingDomainID- %1: Interface %2 is unreachable because it is not currently …Operational
20185RoutingDomainID- %1: Interface %2 is unreachable because the network card for …Operational
20186RoutingDomainID- %1: Interface %2 is now reachable.Operational
20187The user {param1} failed an authentication attempt due to the following reason: …Operational
20188The user {param1}; attempting to connect on {param2}; was disconnected because …Operational
20189The user {param1} connected from {param2} but failed an authentication attempt …Operational
20190Because no certificate has been configured for clients dialing in with EAP-TLS, …Operational
20191Because the certificate that was configured for clients dialing in with EAP-TLS …Operational
20192A certificate could not be found.Operational
20193CoID=.Operational
20194The user {param1} connected on port {param2} on {param3} at {param4} and …Operational
20195The user {param1} has been disconnected on port {param2}.Operational
20196An invalid response was received from the RADIUS server %1.Operational
20197Ras Audio Acceleration failed to %1.Operational
20198Choosing radius server %1 for authentication.Operational
20199IPinIP tunnel interfaces are no longer supportedOperational
20200The user {param1} connected on port {param2} has been assigned address {param3}.Operational
20201The user with ip address {param1} has disconnected.Operational
20202An error occurred while trying to revert impersonation.Operational
20203Cannot load the Security host module component.Operational
20204Cannot load the RAS third party administration DLL component.Operational
20205IPX routing is no longer supported.Operational
20206Disk full.Operational
20207Disk full.Operational
20208Disk full.Operational
20209A connection between the VPN server and the VPN client %1 has been established, …Operational
20210The Network Access Protection (NAP) enforcement client failed to register with …Operational
20211The Network Access Protection (NAP) enforcement client could not start PPP …Operational
20212The request sent to the Network Access Protection Agent (NAPAgent) failed.Operational
20213The Network Access Protection (NAP) enforcement client received an invalid …Operational
20214The Network Access Protection (NAP) enforcement client received an invalid …Operational
20215The IAS/RADIUS server has passed an invalid value to the server running Routing …Operational
20216The Routing and Remote Access service could not start.Operational
20217An error occurred while trying to disable %1 packet filtering for Routing and …Operational
20218An error occurred while trying to enable %1 packet filtering for Routing and …Operational
20219%1 packet filtering has been disabled.Operational
20220The connection to %1 made using device %2 was terminated.Operational
20221CoId=.Operational
20222CoId=.Operational
20223CoId=.Operational
20224CoId=.Operational
20225CoId=.Operational
20226CoId=.Operational
20227CoId=.Operational
20228The remote access connection with the correlation ID %1 has Network Access …Operational
20229The remote access connection with the correlation ID %1 received an …Operational
20230The connection from user %1 on port %2 has been disconnected because the Session …Operational
20247CoId=.Operational
20248CoId=.Operational
20249CoId=.Operational
20250RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been …Operational
20251RoutingDomainID- %1: CoId=%2: The user %3 connected on port %4 on %5 at %6 and …Operational
20252CoId=.Operational
20253RoutingDomainID- %1: CoId=%2: The user %3 connected to port %4 has been …Operational
20254CoId=.Operational
20255CoId=.Operational
20256CoId=.Operational
20257CoId=.Operational
20258CoId=.Operational
20259CoId=.Operational
20260CoId=.Operational
20261CoId=.Operational
20262CoId=.Operational
20263CoID=.Operational
20264CoID=.Operational
20265RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been …Operational
20266RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been …Operational
20267CoID=.Operational
20268CoID=.Operational
20269CoId=.Operational
20270CoID=.Operational
20271CoId=.Operational
20272RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 on %5 at %6 and …Operational
20273CoId=.Operational
20274RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 has been assigned …Operational
20275RoutingDomainID- %1: CoID=%2: The user with ip address %3 has disconnected.Operational
20276CoId=.Operational
20277CoId=.Operational
20278CoId=.Operational
20279CoId=.Operational
20280RoutingDomainID- %1: CoID=%2: The correlation ID on the server is %3.Operational
20281CoID=.Operational
20282RoutingDomainID- %1: Failed to enable IPv4 forwarding on interface %2 with …Operational
20283RoutingDomainID- %1: Failed to disable IPv4 forwarding on interface %2 with …Operational
20284RoutingDomainID- %1: Failed to plumb IKEv2 policies for one or more demand dial …Operational
20285Did not find the certificate configured to be used for IKEv2 local …Operational
20286Failed to plumb the custom IKEv2 policy.Operational
20287RoutingDomainID- %1: Did not find the PreSharedKey configured to be used for …Operational
20288RoutingDomainID- %1: IPv4 routes are not added for the demand dial connection as …Operational
20289RoutingDomainID- %1: IPv6 routes are not added for the demand dial connection as …Operational
20290Disabling S2S interface %1 (RoutingDomain: %2) because either there is no …Operational
20291%1 requires attention.Operational
20292Retrieving Max connections failed.Operational

Event ID 20001 — Cannot load the NetBIOS gateway DLL component because of the following error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the NetBIOS gateway DLL component because of the following error: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20002 — Cannot access registry key values.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot access registry key values.

Fields

NameDescription
__binLength
binary

Event ID 20003 — Cannot enumerate Registry key values.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot enumerate Registry key values. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20004 — Parameter %1 has an invalid type.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Parameter %1 has an invalid type.

Fields

NameDescription
param1
__binLength
binary

Event ID 20005 — Cannot enumerate the Remote Access Connection Manager ports.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot enumerate the Remote Access Connection Manager ports. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20006 — The Remote Access Service is not configured to receive calls or all ports configured for receiving calls are in use by other applications.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Service is not configured to receive calls or all ports configured for receiving calls are in use by other applications.

Fields

NameDescription
__binLength
binary

Event ID 20007 — Cannot receive initial frame on port {param1} because of the following error: {param2} The user has been disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot receive initial frame on port {param1} because of the following error: {param2} The user has been disconnected.

Fields

NameDescription
param1
param2

Event ID 20008 — The user connected to port {param1} has been disconnected due to inactivity.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port {param1} has been disconnected due to inactivity.

Fields

NameDescription
param1

Event ID 20009 — The user connected to port %1 has been disconnected because there is not enough memory available in the system.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because there is not enough memory available in the system.

Fields

NameDescription
param1
__binLength
binary

Event ID 20010 — The user connected to port %1 has been disconnected due to a system error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected due to a system error.

Fields

NameDescription
param1
__binLength
binary

Event ID 20011 — The user connected to port %1 has been disconnected due to a critical network error on the local network.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected due to a critical network error on the local network.

Fields

NameDescription
param1
__binLength
binary

Event ID 20012 — The user connected to port %1 has been disconnected due to a critical network error on the async network.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected due to a critical network error on the async network.

Fields

NameDescription
param1
__binLength
binary

Event ID 20013 — The communication device attached to port %1 is not functioning.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The communication device attached to port %1 is not functioning.

Fields

NameDescription
param1
__binLength
binary

Event ID 20014 — The user {param1} has connected and failed to authenticate on port {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} has connected and failed to authenticate on port {param2}. The line has been disconnected.

Fields

NameDescription
param1
param2

Event ID 20015 — The user {param1} has connected and has been successfully authenticated on port {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} has connected and has been successfully authenticated on port {param2}.

Fields

NameDescription
param1
param2

Event ID 20016 — The user connected to port %1 has been disconnected because there was a transport-level error during the authentication conversation.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because there was a transport-level error during the authentication conversation.

Fields

NameDescription
param1
__binLength
binary

Event ID 20018 — Cannot reset the network adapter for LANA %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot reset the network adapter for LANA %1. The error code is the data.

Fields

NameDescription
param1
__binLength
binary

Event ID 20019 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. Cannot locate the computer name. GetComputerName call has failed.

Fields

NameDescription
__binLength
binary

Event ID 20020 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. Cannot add the name for communication with the security agent on LANA %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20021 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. Cannot access the network adapter address on LANA %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20022 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. The security agent has rejected the Remote Access server's call to establish a session on LANA %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20023 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. The security agent has rejected the Remote Access server's request to start the service on this computer on LANA %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20024 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure. A network error has occurred when trying to establish a session with the security agent on LANA %1. The error code is the data.

Fields

NameDescription
param1
__binLength
binary

Event ID 20025 — The user connected to port %1 has been disconnected because there are no operating system resources available.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because there are no operating system resources available.

Fields

NameDescription
param1
__binLength
binary

Event ID 20026 — The user connected to port %1 has been disconnected because of a failure to lock user memory.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because of a failure to lock user memory.

Fields

NameDescription
param1
__binLength
binary

Event ID 20027 — Remote Access Connection Manager failed to start because NDISWAN could not be opened.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because NDISWAN could not be opened.

Fields

NameDescription
__binLength
binary

Event ID 20028 — Remote Access Connection Manager failed to start because it could not initialize the security attributes.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not initialize the security attributes. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20029 — Remote Access Connection Manager failed to start because no endpoints were available.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because no endpoints were available. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator.

Fields

NameDescription
__binLength
binary

Event ID 20030 — Remote Access Connection Manager failed to start because it could not load one or more communication DLLs.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20031 — Remote Access Connection Manager failed to start because it could not locate port information from media DLLs.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not locate port information from media DLLs. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20032 — Remote Access Connection Manager failed to start because it could not access protocol information from the Registry.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not access protocol information from the Registry. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20033 — Remote Access Connection Manager failed to start because it could not register with the local security authority.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not register with the local security authority. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20034 — Remote Access Connection Manager failed to start because it could not create shared file mapping.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not create shared file mapping. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20035 — Remote Access Connection Manager failed to start because it could not create buffers.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not create buffers. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20036 — Remote Access Connection Manager failed to start because it could not access resources.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because it could not access resources. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20037 — Remote Access Connection Manager service failed to start because it could not start worker threads.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager service failed to start because it could not start worker threads. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator.

Fields

NameDescription
__binLength
binary

Event ID 20038 — Remote Access Server Configuration Error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Configuration Error. Cannot find the LANA numbers for the network adapters. Remote clients connecting with the NBF protocol will only be able to access resources on the local machine.

Fields

NameDescription
__binLength
binary

Event ID 20039 — RASSER.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RASSER.DLL cannot open the SERIAL.INI file.

Event ID 20040 — An attempt by RASSER.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An attempt by RASSER.DLL to get an async media access control handle failed.

Event ID 20041 — RASMXS.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RASMXS.DLL cannot load RASSER.DLL.

Event ID 20042 — The Remote Access server cannot allocate a route for the user connected on port %1 because of the following error: %2 The user has been disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access server cannot allocate a route for the user connected on port %1 because of the following error: %2 The user has been disconnected. Check the configuration of your Remote Access Service.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20043 — Cannot allocate memory in the admin support thread for the Remote Access Service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot allocate memory in the admin support thread for the Remote Access Service.

Fields

NameDescription
__binLength
binary

Event ID 20044 — Cannot create an instance thread in the admin support thread for the Remote Access Service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot create an instance thread in the admin support thread for the Remote Access Service.

Fields

NameDescription
__binLength
binary

Event ID 20045 — Cannot create a named pipe instance in the admin support thread for the Remote Access Service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot create a named pipe instance in the admin support thread for the Remote Access Service.

Fields

NameDescription
__binLength
binary

Event ID 20046 — General named pipe failure occurred in the admin support thread for the Remote Access Service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

General named pipe failure occurred in the admin support thread for the Remote Access Service.

Fields

NameDescription
__binLength
binary

Event ID 20047 — An invalid request was sent to the admin support thread for the Remote Access Service, possibly from a down-level admin tool.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An invalid request was sent to the admin support thread for the Remote Access Service, possibly from a down-level admin tool.  The request was not processed.

Fields

NameDescription
__binLength
binary

Event ID 20048 — The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.  The user was active for {param7} minutes {param8} seconds.  {param9} bytes were sent and {param1}0 bytes were received. The port speed was {param1}1.  The reason for disconnecting was {param1}2.

Fields

NameDescription
param1
param2
param3
param4
param5
param6
param7
param8
param9

Event ID 20049 — The user connected to port {param1} has been disconnected because the authentication process did not complete within the required amount of time.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port {param1} has been disconnected because the authentication process did not complete within the required amount of time.

Fields

NameDescription
param1

Event ID 20050 — The user {param1} connected to port {param2} has been disconnected because no network protocols were successfully negotiated.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} connected to port {param2} has been disconnected because no network protocols were successfully negotiated.

Fields

NameDescription
param1
param2

Event ID 20051 — The user connected to port %1 has been disconnected because an internal authentication error occurred.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because an internal authentication error occurred.

Fields

NameDescription
param1
__binLength
binary

Event ID 20052 — The NetBIOS gateway has been configured to access the network but there are no network adapters available.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The NetBIOS gateway has been configured to access the network but there are no network adapters available. Remote clients connecting with the NBF protocol will only be able to access resources on the local machine.

Fields

NameDescription
__binLength
binary

Event ID 20053 — The user %1 established a NetBIOS session between the remote workstation %2 and the network server %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user %1 established a NetBIOS session between the remote workstation %2 and the network server %3.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20054 — Remote Access Service failed to start because the Remote Access Connection Manager failed to initialize because of the following error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Service failed to start because the Remote Access Connection Manager failed to initialize because of the following error: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20055 — Cannot add the remote computer name %1 on LANA %2 for the client being connected on port %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot add the remote computer name %1 on LANA %2 for the client being connected on port %3. The error code is the data.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20056 — Cannot delete the remote computer name %1 from LANA %2 for the client being disconnected on port %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot delete the remote computer name %1 from LANA %2 for the client being disconnected on port %3. The error code is the data.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20057 — Cannot add the remote computer group name %1 on LANA %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot add the remote computer group name %1 on LANA %2. The error code is the data.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20058 — Cannot delete the remote computer group name %1 from LANA %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot delete the remote computer group name %1 from LANA %2. The error code is the data.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20059 — The modem on %1 moved to an unsupported BPS rate.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The modem on %1 moved to an unsupported BPS rate.

Fields

NameDescription
param1
__binLength
binary

Event ID 20060 — The serial driver could not allocate adequate I/O queues.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The serial driver could not allocate adequate I/O queues. This may result in an unreliable connection.

Fields

NameDescription
__binLength
binary

Event ID 20061 — Remote Access Connection Manager could not reopen biplex port %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager could not reopen biplex port %1. This port will not be available for calling in or calling out. Restart all Remote Access Service components.

Fields

NameDescription
param1
__binLength
binary

Event ID 20062 — Internal Error: Disconnect operation on %2 completed with an error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Internal Error: Disconnect operation on %2 completed with an error. %1

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20063 — Remote Access Connection Manager failed to start because the Protocol engine [.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because the Protocol engine [%2] failed to initialize. %1

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20064 — Remote Access service failed to start because the all Protocol engine failed to initialize.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access service failed to start because the all Protocol engine failed to initialize. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20065 — The Remote Access Gateway Proxy could not create a process.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Gateway Proxy could not create a process.

Fields

NameDescription
__binLength
binary

Event ID 20066 — The Remote Access Gateway Proxy could not create a named pipe.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Gateway Proxy could not create a named pipe.

Fields

NameDescription
__binLength
binary

Event ID 20067 — The Remote Access Gateway Proxy could not establish a named pipe connection with the Remote Access Supervisor Proxy.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Gateway Proxy could not establish a named pipe connection with the Remote Access Supervisor Proxy.

Fields

NameDescription
__binLength
binary

Event ID 20068 — A general error occurred reading from the named pipe in the Remote Access Proxy.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A general error occurred reading from the named pipe in the Remote Access Proxy.

Fields

NameDescription
__binLength
binary

Event ID 20069 — Cannot open or obtain information about the PPP key or one of its subkeys.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot open or obtain information about the PPP key or one of its subkeys. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20070 — Point to Point Protocol engine was unable to load the %1 module.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Point to Point Protocol engine was unable to load the %1 module. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20071 — The Point to Point Protocol module %1 returned an error while initializing.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Point to Point Protocol module %1 returned an error while initializing. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20072 — The Point to Point Protocol failed to load the required PAP and/or CHAP authentication modules.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Point to Point Protocol failed to load the required PAP and/or CHAP authentication modules.

Fields

NameDescription
__binLength
binary

Event ID 20073 — The following error occurred in the Point to Point Protocol module on port: {param1}; UserName: {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The following error occurred in the Point to Point Protocol module on port: {param1}; UserName: {param2}. {param3}

Fields

NameDescription
param1
param2
param3

Event ID 20076 — The password for user {param1}\{param2} connected on port {param3} has expired.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The password for user {param1}\{param2} connected on port {param3} has expired.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3

Event ID 20077 — The account for user {param1}\{param2} connected on port {param3} has expired.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The account for user {param1}\{param2} connected on port {param3} has expired.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3

Event ID 20078 — The account for user {param1}\{param2} connected on port {param3} does not have Remote Access privilege.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The account for user {param1}\{param2} connected on port {param3} does not have Remote Access privilege.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3

Event ID 20079 — The software version of the user %1\%2 connected on port %3 is unsupported.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The software version of the user %1\%2 connected on port %3 is unsupported. The line has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20080 — The server machine is configured to require data encryption.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The server machine is configured to require data encryption.  The machine for user %1\%2 connected on port %3 does not support encryption.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20081 — Remote Access Server Security Failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Server Security Failure.  Could not reset lana %1 (the error code is the data).  Security check not performed.

Fields

NameDescription
param1
__binLength
binary

Event ID 20082 — The Remote Access Server could not reset lana %1 (the error code is the data) and will not be active on it.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server could not reset lana %1 (the error code is the data) and will not be active on it.

Fields

NameDescription
param1
__binLength
binary

Event ID 20084 — The Remote Access Server will stop using IP Address %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server will stop using IP Address %1 (either because it was unable to renew the lease from the DHCP Server, the administrator switched between static address pool and DHCP addresses, or the administrator changed to a different network for DHCP addresses). All connected users using IP will be unable to access network resources. Users can re-connect to the server to restore IP connectivity.

Fields

NameDescription
param1
__binLength
binary

Event ID 20085 — The Remote Access Server was unable to renew the lease for IP Address %1 from the DHCP Server.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server was unable to renew the lease for IP Address %1 from the DHCP Server. The user assigned with this IP address will be unable to access network resources using IP. Re-connecting to the server will restore IP connectivity.

Fields

NameDescription
param1
__binLength
binary

Event ID 20086 — The Remote Access Server was unable to acquire an IP Address from the DHCP Server to assign to the incoming user.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server was unable to acquire an IP Address from the DHCP Server to assign to the incoming user.

Fields

NameDescription
__binLength
binary

Event ID 20087 — The Remote Access Server was unable to acquire an IP Address from the DHCP Server to be used on the Server Adapter.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server was unable to acquire an IP Address from the DHCP Server to be used on the Server Adapter. Incoming user will be unable to connect using IP.

Fields

NameDescription
__binLength
binary

Event ID 20088 — The Remote Access Server acquired IP Address %1 to be used on the Server Adapter.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server acquired IP Address %1 to be used on the Server Adapter.

Fields

NameDescription
param1
__binLength
binary

Event ID 20089 — The Remote Access Server's attempt to callback user {param1} on port {param2} at {param3} failed because of the following error: {param4}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server's attempt to callback user {param1} on port {param2} at {param3} failed because of the following error: {param4}

Fields

NameDescription
param1
param2
param3
param4

Event ID 20090 — A general error occurred writing to the named pipe in the Remote Access Proxy.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A general error occurred writing to the named pipe in the Remote Access Proxy.

Fields

NameDescription
__binLength
binary

Event ID 20091 — Cannot open the RAS security host Registry key.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot open the RAS security host Registry key. The following error occurred: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20092 — Cannot load the Security host module component.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the Security host module component. The following error occurred: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20093 — The user %1 has connected and failed to authenticate with a third party security on port %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user %1 has connected and failed to authenticate with a third party security on port %2. The line has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20094 — The user connected to port %1 has been disconnected because the following internal authentication error occurred in the third party security module...

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user connected to port %1 has been disconnected because the following internal authentication error occurred in the third party security module: %2

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20095 — Cannot receive initial data on port {param1} because of the following error: {param2} The user has been disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot receive initial data on port {param1} because of the following error: {param2} The user has been disconnected.

Fields

NameDescription
param1
param2

Event ID 20096 — The user was authenticated as %1 by the third party security host module but was authenticated as %2 by the RAS security.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user was authenticated as %1 by the third party security host module but was authenticated as %2 by the RAS security. The user has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20097 — A user was unable to connect on port {param1}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A user was unable to connect on port {param1}. No more connections can be made to this remote computer because the computer has exceeded its client license limit.

Fields

NameDescription
param1

Event ID 20098 — A user was unable to connect on port %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A user was unable to connect on port %1. The NetBIOS protocol has been disabled for the Remote Access Server.

Fields

NameDescription
param1
__binLength
binary

Event ID 20099 — Cannot access Registry value for %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot access Registry value for %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20100 — Cannot access the Registry key %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot access the Registry key %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20101 — Using the default value for Registry parameter %1 because the value given is not in the legal range for the parameter.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Using the default value for Registry parameter %1 because the value given is not in the legal range for the parameter.

Fields

NameDescription
param1
__binLength
binary

Event ID 20102 — Cannot enumerate keys of Registry key %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot enumerate keys of Registry key %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20103 — Unable to load %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to load %1.

Fields

NameDescription
param1
__binLength
binary

Event ID 20104 — Memory allocation failure.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Memory allocation failure.

Fields

NameDescription
__binLength
binary

Event ID 20105 — Unable to load the interface %1 from the registry.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to load the interface %1 from the registry. The following error occurred: %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20106 — RoutingDomainID- %1: Unable to add the interface %2 with the Router Manager for the %3 protocol.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Unable to add the interface %2 with the Router Manager for the %3 protocol. The following error occurred: %4

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20107 — RoutingDomainID- %1: Unable to remove the interface %2 with the Router Manager for the %3 protocol.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Unable to remove the interface %2 with the Router Manager for the %3 protocol. The following error occurred: %4

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20108 — Unable to open the port %1 for use.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to open the port %1 for use. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20109 — Cannot recognize initial frame received on port {param1}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot recognize initial frame received on port {param1}. The line has been disconnected.

Fields

NameDescription
param1

Event ID 20110 — An error occurred in the Point to Point Protocol module on port %1 while trying to initiate a connection.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An error occurred in the Point to Point Protocol module on port %1 while trying to initiate a connection. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20111 — RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 on port %3 was successfully initiated but failed to complete successfully ...

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 on port %3 was successfully initiated but failed to complete successfully because of the  following error: %4

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20112 — Cannot open the RAS third party administration host DLL Registry key.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot open the RAS third party administration host DLL Registry key. The following error occurred: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20113 — Cannot load the RAS third party administration DLL component.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the RAS third party administration DLL component. The following error occurred: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20114 — The Service will not accept calls.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Service will not accept calls. No protocols were configured for use.

Fields

NameDescription
__binLength
binary

Event ID 20125 — RoutingDomainID- %1: A Demand Dial persistent connection to the remote interface %2 failed to be initiated successfully.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: A Demand Dial persistent connection to the remote interface %2 failed to be initiated successfully. The following error occurred: %3

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20126 — A packet from %1 destined to %2 over protocol 0x%3 caused interface %4 to be brought up.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A packet from %1 destined to %2 over protocol 0x%3 caused interface %4 to be brought up. The first %5 bytes of the packet are in the data.

Fields

NameDescription
param1
param2
param3
param4
param5
__binLength
binary

Event ID 20127 — RoutingDomainID- %1: The Demand Dial interface %2 was not loaded.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: The Demand Dial interface %2 was not loaded. The router was not started in in Demand Dial mode.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20128 — Cannot load the Appletalk Remote Access DLL component because of the following error: {param1}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the Appletalk Remote Access DLL component because of the following error: {param1}

Fields

NameDescription
param1

Event ID 20129 — An error occurred in the Appletalk Remote Access Protocol module on port {param1} while trying to initiate a connection.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An error occurred in the Appletalk Remote Access Protocol module on port {param1} while trying to initiate a connection. {param2}

Fields

NameDescription
param1
param2

Event ID 20130 — The following error occurred in the Appletalk Remote Access Protocol module on port {param1}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The following error occurred in the Appletalk Remote Access Protocol module on port {param1}. {param2}

Fields

NameDescription
param1
param2

Event ID 20131 — A user was unable to connect on port {param1}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A user was unable to connect on port {param1}. The Appletalk Remote Access protocol has been disabled for the Remote Access Server.

Fields

NameDescription
param1

Event ID 20132 — Remote Access Connection Manager failed to start because the RAS RPC module failed to initialize.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Remote Access Connection Manager failed to start because the RAS RPC module failed to initialize. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20138 — RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 failed to be initiated successfully.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 failed to be initiated successfully. The following error occurred: %3

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20139 — The port {param1} has been disconnected due to inactivity.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The port {param1} has been disconnected due to inactivity.

Fields

NameDescription
param1

Event ID 20140 — The port {param1} has been disconnected because the user reached the maximum connect time allowed by the administrator.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The port {param1} has been disconnected because the user reached the maximum connect time allowed by the administrator.

Fields

NameDescription
param1

Event ID 20141 — The user {param1} has connected and has been successfully authenticated on port {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} has connected and has been successfully authenticated on port {param2}. Data sent and received over this link is encrypted.

Fields

NameDescription
param1
param2

Event ID 20142 — The user {param1} has connected and has been successfully authenticated on port {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} has connected and has been successfully authenticated on port {param2}. Data sent and received over this link is strongly encrypted.

Fields

NameDescription
param1
param2

Event ID 20143 — Unable to load the interface %1 from the registry.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to load the interface %1 from the registry. There are no routing enabled ports available for use by this demand dial interface. Use the Routing and RemoteAccess Administration tool to configure this interface to use a device that is routing enabled. Stop and restart the router for this demand dial interface to be loaded from the registry.

Fields

NameDescription
param1
__binLength
binary

Event ID 20144 — The Demand-Dial interface %1 was not registered with the Router.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Demand-Dial interface %1 was not registered with the Router. Demand-Dial interfaces are not supported on a Windows NT Workstation.

Fields

NameDescription
param1
__binLength
binary

Event ID 20145 — Cannot initialize the Remote Access and Router service to accept calls using the TCP/IP transport protocol.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot initialize the Remote Access and Router service to accept calls using  the TCP/IP transport protocol. The following error occurred: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20146 — The RADIUS server %1 did not respond to the initial request.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The RADIUS server %1 did not respond to the initial request.  Please make sure that the server name or IP address and secret are correct.

Fields

NameDescription
param1
__binLength
binary

Event ID 20147 — The Remote Access service failed to start because the Point to Point was not initialized successfully.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access service failed to start because the Point to Point was not initialized successfully. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20148 — The RADIUS server name %1 could not be successfully resolved to an IP address.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The RADIUS server name %1 could not be successfully resolved to an IP address. Please make sure that the name is spelled correctly and that the RADIUS server is running correctly.

Fields

NameDescription
param1
__binLength
binary

Event ID 20149 — No global configuration was supplied to the IP Router Manager.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

No global configuration was supplied to the IP Router Manager. Please rerun setup.

Fields

NameDescription
__binLength
binary

Event ID 20150 — Unable to add demand dial filters for interface %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to add demand dial filters for interface %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20151 — The Control Protocol %1 in the Point to Point Protocol module %2 returned an error while initializing.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Control Protocol %1 in the Point to Point Protocol module %2 returned an error while initializing. %3

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20152 — The currently configured authentication provider failed to load and initialize successfully.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The currently configured authentication provider failed to load and initialize successfully. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20153 — The currently configured accounting provider failed to load and initialize successfully.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The currently configured accounting provider failed to load and initialize successfully. %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20157 — The interface %1 could not be enabled for multicast.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The interface %1 could not be enabled for multicast. %2 will not be activated over this interface.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20158 — The user {param1} successfully established a connection to {param2} using the device {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} successfully established a connection to {param2} using the device {param3}.

Fields

NameDescription
param1
param2
param3

Event ID 20159 — The connection to {param1} made by user {param2} using device {param3} was disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The connection to {param1} made by user {param2} using device {param3} was disconnected.

Fields

NameDescription
param1
param2
param3

Event ID 20161 — The user {param1} successfully established a connection to {param2} using the device {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} successfully established a connection to {param2} using the device {param3}. This connection happened automatically because the bandwidth utilization was  high.

Fields

NameDescription
param1
param2
param3

Event ID 20162 — The Remote Access Server established a connection to {param1} for the user {param2} using the device {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server established a connection to {param1} for the user {param2} using the device {param3}. This connection happened automatically because the bandwidth utilization was high.

Fields

NameDescription
param1
param2
param3

Event ID 20163 — The connection to {param1} made by user {param2} using device {param3} was disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The connection to {param1} made by user {param2} using device {param3} was disconnected. This disconnection happened automatically because the bandwidth utilization was low.

Fields

NameDescription
param1
param2
param3

Event ID 20164 — The Remote Access Server wants to disconnect a link in the connection to {param1} made by user {param2} because the bandwidth utilization is too low.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Remote Access Server wants to disconnect a link in the connection to {param1} made by user {param2} because the bandwidth utilization is too low.

Fields

NameDescription
param1
param2

Event ID 20165 — A connection has been established on port %1 using interface %2, but no IP address was obtained.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A connection has been established on port %1 using interface %2, but no IP address was obtained.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20166 — A connection has been established on port %1 using interface %2, but the remote side got no IP address.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A connection has been established on port %1 using interface %2, but the  remote side got no IP address.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20167 — RoutingDomainID- %1: No IP address is available to hand out to the dial-in client.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: No IP address is available to hand out to the dial-in client.

Fields

NameDescription
param1
__binLength
binary

Event ID 20168 — Could not retrieve the Remote Access Server's certificate due to the following error.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Could not retrieve the Remote Access Server's certificate due to the  following error: %1

Fields

NameDescription
param1
__binLength
binary

Event ID 20169 — Unable to contact a DHCP server.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Unable to contact a DHCP server. The Automatic Private IP Address %1 will be assigned to dial-in clients. Clients may be unable to access resources on the network.

Fields

NameDescription
param1
__binLength
binary

Event ID 20170 — The user %1 has connected and failed to authenticate because of the following error: %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user %1 has connected and failed to authenticate because of the following error: %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20171 — Failed to apply IP Security on port %1 because of error: %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Failed to apply IP Security on port %1 because of error: %2.  No calls will be accepted to this port.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20172 — Multicast scope mismatch with %1: Locally-configured name "%2", Remotely-configured name "%3".

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Multicast scope mismatch with %1: Locally-configured name "%2", Remotely-configured name "%3".

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20173 — Multicast scope address mismatch for scope ".

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Multicast scope address mismatch for scope "%1", Locally-configured range is %4-%5, Remotely-configured range is %2-%3

Fields

NameDescription
param1
param2
param3
param4
param5
__binLength
binary

Event ID 20174 — Possible leaky multicast Local Scope detected between this machine and %1, since a boundary appears to exist for %2, but not for the local scope.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Possible leaky multicast Local Scope detected between this machine and %1, since a boundary appears to exist for %2, but not for the local scope.  If this warning continues to occur, a problem likely exists.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20175 — Multicast scope '.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Multicast scope '%1' is non-convex, since border router %2 appears to be outside.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20176 — A leak was detected in multicast scope '.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A leak was detected in multicast scope '%1'.  One of the following routers is misconfigured: %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20177 — Interface %1 is unreachable because of reason %2.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Interface %1 is unreachable because of reason %2.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20178 — Interface %1 is now reachable.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Interface %1 is now reachable.

Fields

NameDescription
param1
__binLength
binary

Event ID 20179 — RoutingDomainID- %1: Interface %2 is unreachable because there are no modems (or other connecting devices) available for use by this interface.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because there are no modems (or other connecting devices)  available for use by this interface.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20180 — RoutingDomainID- %1: Interface %2 is unreachable because the connection attempt failed.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because the connection attempt failed.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20181 — RoutingDomainID- %1: Interface %2 is unreachable because it has been administratively disabled.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because it has been administratively disabled.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20182 — RoutingDomainID- %1: Interface %2 is unreachable because the Routing and RemoteACcess service is in a paused state.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because the Routing and RemoteACcess service is in a  paused state.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20183 — RoutingDomainID- %1: Interface %2 is unreachable because it is not allowed to connect at this time.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because it is not allowed to connect at this time. Check the dial-out hours configured on this interface.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20184 — RoutingDomainID- %1: Interface %2 is unreachable because it is not currently connected to the network.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because it is not currently connected to the network.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20185 — RoutingDomainID- %1: Interface %2 is unreachable because the network card for this interface has been removed.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is unreachable because the network card for this interface has been  removed.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20186 — RoutingDomainID- %1: Interface %2 is now reachable.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Interface %2 is now reachable.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20187 — The user {param1} failed an authentication attempt due to the following reason: {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} failed an authentication attempt due to the following reason: {param2}

Fields

NameDescription
param1
param2

Event ID 20188 — The user {param1}; attempting to connect on {param2}; was disconnected because of the following reason: {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1}; attempting to connect on {param2}; was disconnected because of the following  reason: {param3}

Fields

NameDescription
param1
param2
param3

Event ID 20189 — The user {param1} connected from {param2} but failed an authentication attempt due to the following reason: {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} connected from {param2} but failed an authentication attempt due to the following reason: {param3}

Fields

NameDescription
param1
param2
param3

Event ID 20190 — Because no certificate has been configured for clients dialing in with EAP-TLS, a default certificate is being sent to user %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Because no certificate has been configured for clients dialing in with EAP-TLS, a default certificate is being sent to user %1. Please go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).

Fields

NameDescription
param1
__binLength
binary

Event ID 20191 — Because the certificate that was configured for clients dialing in with EAP-TLS was not found, a default certificate is being sent to user %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Because the certificate that was configured for clients dialing in with EAP-TLS was not found, a default certificate is being sent to user %1. Please go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).

Fields

NameDescription
param1
__binLength
binary

Event ID 20192 — A certificate could not be found.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A certificate could not be found. Connections that use the L2TP protocol over IPsec  require the installation of a machine certificate, also known as a computer  certificate. No L2TP calls will be accepted.

Fields

NameDescription
__binLength
binary

Event ID 20193 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: An error occurred while configuring IP packet filters for user %2 over port %3.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20194 — The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.  The user was active for {param7} minutes {param8} seconds.  {param9} bytes were sent and {param1}0 bytes were received. The reason for disconnecting was {param1}1.

Fields

NameDescription
param1
param2
param3
param4
param5
param6
param7
param8
param9

Event ID 20195 — The user {param1} has been disconnected on port {param2}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} has been disconnected on port {param2}. {param3}

Fields

NameDescription
param1
param2
param3

Event ID 20196 — An invalid response was received from the RADIUS server %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An invalid response was received from the RADIUS server %1. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20197 — Ras Audio Acceleration failed to %1.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Ras Audio Acceleration failed to %1. %2

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20198 — Choosing radius server %1 for authentication.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Choosing radius server %1 for authentication.

Fields

NameDescription
param1
__binLength
binary

Event ID 20199 — IPinIP tunnel interfaces are no longer supported

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

IPinIP tunnel interfaces are no longer supported

Fields

NameDescription
__binLength
binary

Event ID 20200 — The user {param1} connected on port {param2} has been assigned address {param3}.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user {param1} connected on port {param2} has been assigned address {param3}

Fields

NameDescription
param1
param2
param3

Event ID 20201 — The user with ip address {param1} has disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The user with ip address {param1} has disconnected

Fields

NameDescription
param1

Event ID 20202 — An error occurred while trying to revert impersonation.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An error occurred while trying to revert impersonation.

Fields

NameDescription
__binLength
binary

Event ID 20203 — Cannot load the Security host module component.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the Security host module component. The following error occurred: %1 is not a valid win32 application.

Fields

NameDescription
param1
__binLength
binary

Event ID 20204 — Cannot load the RAS third party administration DLL component.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Cannot load the RAS third party administration DLL component. The following error occurred: %1 is not a valid win32 application.

Fields

NameDescription
param1
__binLength
binary

Event ID 20205 — IPX routing is no longer supported.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

IPX routing is no longer supported.

Fields

NameDescription
__binLength
binary

Event ID 20206 — Disk full.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Disk full. Deleted older logfile %1 to create free space.

Fields

NameDescription
param1
__binLength
binary

Event ID 20207 — Disk full.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Disk full. Could not delete older logfile %1 to create free space.

Fields

NameDescription
param1
__binLength
binary

Event ID 20208 — Disk full.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Disk full. Could not find older logfile to delete and create free space.

Fields

NameDescription
__binLength
binary

Event ID 20209 — A connection between the VPN server and the VPN client %1 has been established, but the VPN connection cannot be completed.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

A connection between the VPN server and the VPN client %1 has been established, but the VPN connection cannot be completed. The most common cause for this is that a firewall or router between the VPN server and the VPN client is not configured to allow Generic Routing Encapsulation (GRE) packets (protocol 47).

Fields

NameDescription
param1
__binLength
binary

Event ID 20210 — The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

Fields

NameDescription
__binLength
binary

Event ID 20211 — The Network Access Protection (NAP) enforcement client could not start PPP renegotiation on the following remote access connection: %d.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Network Access Protection (NAP) enforcement client could not start PPP renegotiation on the following remote access connection: %d. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

Fields

NameDescription
__binLength
binary

Event ID 20212 — The request sent to the Network Access Protection Agent (NAPAgent) failed.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The request sent to the Network Access Protection Agent (NAPAgent) failed. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

Fields

NameDescription
__binLength
binary

Event ID 20213 — The Network Access Protection (NAP) enforcement client received an invalid request for the following remote access connection: %d.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Network Access Protection (NAP) enforcement client received an invalid request for the following remote access connection: %d. The connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server.

Fields

NameDescription
__binLength
binary

Event ID 20214 — The Network Access Protection (NAP) enforcement client received an invalid request for the remote access connection.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Network Access Protection (NAP) enforcement client received an invalid request for the remote access connection. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

Fields

NameDescription
__binLength
binary

Event ID 20215 — The IAS/RADIUS server has passed an invalid value to the server running Routing and Remote Access for the following RADIUS attribute: Attribute Typ...

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The IAS/RADIUS server has passed an invalid value to the server running Routing and Remote Access for the following RADIUS attribute: Attribute Type %1, Vendor ID %2, Vendor specific type %3. Use the netsh ras set trace command to enable packet tracing. Ensure that the RADIUS packets conform to the standards specified in RFC 2548.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20216 — The Routing and Remote Access service could not start.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The Routing and Remote Access service could not start. The most common reason could be because %1 protocol is not installed on the remote access server.

Fields

NameDescription
param1
__binLength
binary

Event ID 20217 — An error occurred while trying to disable %1 packet filtering for Routing and Remote Access service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An error occurred while trying to disable %1 packet filtering for Routing and Remote Access service.

Fields

NameDescription
param1
__binLength
binary

Event ID 20218 — An error occurred while trying to enable %1 packet filtering for Routing and Remote Access service.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

An error occurred while trying to enable %1 packet filtering for Routing and Remote Access service.

Fields

NameDescription
param1
__binLength
binary

Event ID 20219 — %1 packet filtering has been disabled.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

%1 packet filtering has been disabled. Static filters configured for Routing and Remote Access service will not be applied.

Fields

NameDescription
param1
__binLength
binary

Event ID 20220 — The connection to %1 made using device %2 was terminated.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The connection to %1 made using device %2 was terminated. %3

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20221 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 has started dialing a %3 connection using a %4 connection profile named %5. The connection settings are: %6.

Event ID 20222 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 is trying to establish a link to the Remote Access Server for the connection named %3 using the following device: %4.

Event ID 20223 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 has successfully established a link to the Remote Access Server using the following device: %3.

Event ID 20224 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The link to the Remote Access Server has been established by user %2.

Fields

NameDescription
param1
param2

Event ID 20225 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 has dialed a connection named %3 to the Remote Access Server which has successfully connected. The connection parameters are:%4.

Event ID 20226 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 dialed a connection named %3 which has terminated. The reason code returned on termination is %4.

Fields

NameDescription
param1
param2
param3
param4

Event ID 20227 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 dialed a connection named %3 which has failed. The error code returned on failure is %4.

Fields

NameDescription
param1
param2
param3
param4

Event ID 20228 — The remote access connection with the correlation ID %1 has Network Access Protection (NAP)-Enforcement enabled on it.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The remote access connection with the correlation ID %1 has Network Access Protection (NAP)-Enforcement enabled on it. The corresponding NAP correlation ID for this connection is %2.

Fields

NameDescription
param1
param2

Event ID 20229 — The remote access connection with the correlation ID %1 received an unexpected/mismatched response to its Statement of Health (SoH) from the server.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The remote access connection with the correlation ID %1 received an unexpected/mismatched response to its Statement of Health (SoH) from the server. The NAP correlation ID for this transaction is %2.

Fields

NameDescription
param1
param2

Event ID 20230 — The connection from user %1 on port %2 has been disconnected because the Session Timeout received from the RADIUS server has expired.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

The connection from user %1 on port %2 has been disconnected because the Session Timeout received from the RADIUS server has expired. This connection received only an IPv6 address from the RRAS server and it is invalid to configure the MS-Quarantine-Session-Timeout attribute on the NPS server for IPv6-only connections.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20247 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Cannot receive initial frame on port %2 because of the following error: %3 The user has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20248 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user connected to port %2 has been disconnected due to inactivity.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20249 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 has connected and failed to authenticate on port %3. The line has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20250 — RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20251 — RoutingDomainID- %1: CoId=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoId=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8.  The user was active for %9 minutes %10 seconds.  %11 bytes were sent and %12 bytes were received. The port speed was %13.  The reason for disconnecting was %14. The tunnel used was %15. The quarantine state was %16.

Fields

NameDescription
param1
param2
param3
param4
param5
param6
param7
param8
param9
param10
param11
param12
param13
param14
__binLength
binary

Event ID 20252 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user connected to port %2 has been disconnected because the authentication process did not complete within the required amount of time.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20253 — RoutingDomainID- %1: CoId=%2: The user %3 connected to port %4 has been disconnected because no network protocols were successfully negotiated.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoId=%2: The user %3 connected to port %4 has been disconnected because no network protocols were successfully negotiated.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20254 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 on port %3 was called back at the number %4.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20255 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The following error occurred in the Point to Point Protocol module on port: %2, UserName: %3. %4

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20256 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The password for user %2\%3 connected on port %4 has expired.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20257 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The account for user %2\%3 connected on port %4 has expired.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20258 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The account for user %2\%3 connected on port %4 does not have Remote Access privilege.  The line has been disconnected.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20259 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The Remote Access Server's attempt to callback user %2 on port %3 at %4 failed because of the following error: %5

Fields

NameDescription
param1
param2
param3
param4
param5
__binLength
binary

Event ID 20260 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Cannot receive initial data on port %2 because of the following error: %3 The user has been disconnected.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20261 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: A user was unable to connect on port %2. No more connections can be made to this remote computer because the computer has exceeded its client license limit.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20262 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Cannot recognize initial frame received on port %2. The line has been disconnected.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20263 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: The port %2 has been disconnected due to inactivity.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20264 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: The port %2 has been disconnected because the user reached the maximum connect time allowed by the administrator.

Fields

NameDescription
param1
param2
__binLength
binary

Event ID 20265 — RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4. Data sent and received over this link is encrypted.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20266 — RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4. Data sent and received over this link is strongly encrypted.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20267 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: The user %2 successfully established a connection to %3 using the device %4.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20268 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: The connection to %2 made by user %3 using device %4 was disconnected.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20269 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 failed an authentication attempt due to the following reason: %3

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20270 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: The user %2, attempting to connect on %3, was disconnected because of the following  reason: %4

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20271 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: The user %2 connected from %3 but failed an authentication attempt due to the following reason: %4

Fields

NameDescription
param1
param2
param3
param4
param5
__binLength
binary

Event ID 20272 — RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8.  The user was active for %9 minutes %10 seconds.  %11 bytes were sent and %12 bytes were received. The reason for disconnecting was %13. The tunnel used was %14. The quarantine state was %15.

Fields

NameDescription
param1
param2
param3
param4
param5
param6
param7
param8
param9
param10
param11
param12
param13
param14
__binLength
binary

Event ID 20273 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId={param1}: The user {param2} has been disconnected on port {param3}. {param4}

Fields

NameDescription
param1
param2
param3
param4

Event ID 20274 — RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 has been assigned address %5.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 has been assigned address %5

Fields

NameDescription
param1
param2
param3
param4
param5
__binLength
binary

Event ID 20275 — RoutingDomainID- %1: CoID=%2: The user with ip address %3 has disconnected.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The user with ip address %3 has disconnected

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20276 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Layer=%2: SubLayer=%3: The connection attempt failed on port: %4 because of the authentication protocol selected. Check to see if the authentication protocol is supported in the operating systems at the client and server ends of the connection

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20277 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Successfully processed MOBIKE update for connection named '%2'. The new tunnel end points are %3.

Fields

NameDescription
param1
param2
param3

Event ID 20278 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Unable to process MOBIKE update for connection named '%2'. The error code returned is %3.

Fields

NameDescription
param1
param2
param3

Event ID 20279 — CoId=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoId=%1: Disabling PPP AUTH for %2\\%3 on port %4.

Fields

NameDescription
param1
param2
param3
param4
__binLength
binary

Event ID 20280 — RoutingDomainID- %1: CoID=%2: The correlation ID on the server is %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: CoID=%2: The correlation ID on the server is %3.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20281 — CoID=.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

CoID=%1: Connection supports MOBIKE.

Fields

NameDescription
param1
__binLength
binary

Event ID 20282 — RoutingDomainID- %1: Failed to enable IPv4 forwarding on interface %2 with error: %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Failed to enable IPv4 forwarding on interface %2 with error: %3.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20283 — RoutingDomainID- %1: Failed to disable IPv4 forwarding on interface %2 with error: %3.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Failed to disable IPv4 forwarding on interface %2 with error: %3.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20284 — RoutingDomainID- %1: Failed to plumb IKEv2 policies for one or more demand dial interfaces.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Failed to plumb IKEv2 policies for one or more demand dial interfaces.

Fields

NameDescription
param1
__binLength
binary

Event ID 20285 — Did not find the certificate configured to be used for IKEv2 local authentication.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Did not find the  certificate configured to be used for IKEv2 local authentication.

Fields

NameDescription
__binLength
binary

Event ID 20286 — Failed to plumb the custom IKEv2 policy.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Failed to plumb the custom IKEv2 policy.

Fields

NameDescription
__binLength
binary

Event ID 20287 — RoutingDomainID- %1: Did not find the PreSharedKey configured to be used for local or remote authentication for the IKEv2 connection.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: Did not find the  PreSharedKey configured to be used for local or remote authentication for the IKEv2 connection.

Fields

NameDescription
param1
__binLength
binary

Event ID 20288 — RoutingDomainID- %1: IPv4 routes are not added for the demand dial connection as IPv4 transport is not available on the corresponding interface.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: IPv4 routes are not added for the demand dial connection as IPv4 transport is not available on the corresponding interface.

Fields

NameDescription
param1
__binLength
binary

Event ID 20289 — RoutingDomainID- %1: IPv6 routes are not added for the demand dial connection as IPv6 transport is not available on the corresponding interface.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

RoutingDomainID- %1: IPv6 routes are not added for the demand dial connection as IPv6 transport is not available on the corresponding interface.

Fields

NameDescription
param1
__binLength
binary

Event ID 20290 — Disabling S2S interface %1 (RoutingDomain: %2) because either there is no destination IP configured or DNS resolution failed for the configured des...

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Disabling S2S interface %1 (RoutingDomain: %2) because either there is no destination IP configured or DNS resolution failed for the configured destination IP address. To enable this interface, configure destination IP address. If you are using FQDN, make sure it is getting resolved. Then try to enable the interface.

Fields

NameDescription
param1
param2
param3
__binLength
binary

Event ID 20291 — %1 requires attention.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

%1 requires attention.

Fields

NameDescription
param1
__binLength
binary

Event ID 20292 — Retrieving Max connections failed.

Provider
Microsoft-Windows-MPRMSG
Channel
Operational

Message

Retrieving Max connections failed. MaxCon: %1. HResult: %2

Fields

NameDescription
Retrieving_Max_connections_failed_MaxConRetrieving Max connections failed. MaxCon.
HResult
MaxCount
__binLength
binary