Microsoft-Windows-MPRMSG
253 events across 1 channel
Event ID 20001 — Cannot load the NetBIOS gateway DLL component because of the following error: param1.
Event ID 20002 — Cannot access registry key values.
Event ID 20003 — Cannot enumerate Registry key values.
Event ID 20004 — Parameter param1 has an invalid type.
Event ID 20005 — Cannot enumerate the Remote Access Connection Manager ports.
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.
Event ID 20007 — Cannot receive initial frame on port {param1} because of the following error: {param2} The user has been disconnected.
Event ID 20008 — The user connected to port {param1} has been disconnected due to inactivity.
Event ID 20009 — The user connected to port param1 has been disconnected because there is not enough memory available in the system.
Event ID 20010 — The user connected to port param1 has been disconnected due to a system error.
Event ID 20011 — The user connected to port param1 has been disconnected due to a critical network error on the local network.
Event ID 20012 — The user connected to port param1 has been disconnected due to a critical network error on the async network.
Event ID 20013 — The communication device attached to port param1 is not functioning.
Event ID 20014 — The user {param1} has connected and failed to authenticate on port {param2}.
Event ID 20015 — The user {param1} has connected and has been successfully authenticated on port {param2}.
Event ID 20016 — The user connected to port param1 has been disconnected because there was a transport-level error during the authentication conversation.
Event ID 20018 — Cannot reset the network adapter for LANA param1.
Event ID 20019 — Remote Access Server Security Failure.
Event ID 20020 — Remote Access Server Security Failure.
Event ID 20021 — Remote Access Server Security Failure.
Event ID 20022 — Remote Access Server Security Failure.
Event ID 20023 — Remote Access Server Security Failure.
Event ID 20024 — Remote Access Server Security Failure.
Event ID 20025 — The user connected to port param1 has been disconnected because there are no operating system resources available.
Event ID 20026 — The user connected to port param1 has been disconnected because of a failure to lock user memory.
Event ID 20027 — Remote Access Connection Manager failed to start because NDISWAN could not be opened.
Event ID 20028 — Remote Access Connection Manager failed to start because it could not initialize the security attributes.
Event ID 20029 — Remote Access Connection Manager failed to start because no endpoints were available.
Event ID 20030 — Remote Access Connection Manager failed to start because it could not load one or more communication DLLs.
Event ID 20031 — Remote Access Connection Manager failed to start because it could not locate port information from media DLLs.
Event ID 20032 — Remote Access Connection Manager failed to start because it could not access protocol information from the Registry.
Event ID 20033 — Remote Access Connection Manager failed to start because it could not register with the local security authority.
Event ID 20034 — Remote Access Connection Manager failed to start because it could not create shared file mapping.
Event ID 20035 — Remote Access Connection Manager failed to start because it could not create buffers.
Event ID 20036 — Remote Access Connection Manager failed to start because it could not access resources.
Event ID 20037 — Remote Access Connection Manager service failed to start because it could not start worker threads.
Event ID 20038 — Remote Access Server Configuration Error.
Event ID 20039 — RASSER.
Description
RASSER.DLL cannot open the SERIAL.INI file.
Message #
Event ID 20040 — An attempt by RASSER.
Description
An attempt by RASSER.DLL to get an async media access control handle failed.
Message #
Event ID 20041 — RASMXS.
Description
RASMXS.DLL cannot load RASSER.DLL.
Message #
Event ID 20042 — The Remote Access server cannot allocate a route for the user connected on port param1 because of the following error: param2 The user has been disconnected.
Description
The Remote Access server cannot allocate a route for the user connected on port because of the following error: The user has been disconnected. Check the configuration of your Remote Access Service.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20043 — Cannot allocate memory in the admin support thread for the Remote Access Service.
Event ID 20044 — Cannot create an instance thread in the admin support thread for the Remote Access Service.
Event ID 20045 — Cannot create a named pipe instance in the admin support thread for the Remote Access Service.
Event ID 20046 — General named pipe failure occurred in the admin support thread for the Remote Access Service.
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.
Event ID 20048 — The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.
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.
Event ID 20050 — The user {param1} connected to port {param2} has been disconnected because no network protocols were successfully negotiated.
Event ID 20051 — The user connected to port param1 has been disconnected because an internal authentication error occurred.
Event ID 20052 — The NetBIOS gateway has been configured to access the network but there are no network adapters available.
Event ID 20053 — The user param1 established a NetBIOS session between the remote workstation param2 and the network server param3.
Event ID 20054 — Remote Access Service failed to start because the Remote Access Connection Manager failed to initialize because of the following error: param1.
Event ID 20055 — Cannot add the remote computer name param1 on LANA param2 for the client being connected on port param3.
Event ID 20056 — Cannot delete the remote computer name param1 from LANA param2 for the client being disconnected on port param3.
Event ID 20057 — Cannot add the remote computer group name param1 on LANA param2.
Event ID 20058 — Cannot delete the remote computer group name param1 from LANA param2.
Event ID 20059 — The modem on param1 moved to an unsupported BPS rate.
Event ID 20060 — The serial driver could not allocate adequate I/O queues.
Event ID 20061 — Remote Access Connection Manager could not reopen biplex port param1.
Event ID 20062 — Internal Error: Disconnect operation on param2 completed with an error.
Event ID 20063 — Remote Access Connection Manager failed to start because the Protocol engine [param2] failed to initialize.
Event ID 20064 — Remote Access service failed to start because the all Protocol engine failed to initialize.
Event ID 20065 — The Remote Access Gateway Proxy could not create a process.
Event ID 20066 — The Remote Access Gateway Proxy could not create a named pipe.
Event ID 20067 — The Remote Access Gateway Proxy could not establish a named pipe connection with the Remote Access Supervisor Proxy.
Event ID 20068 — A general error occurred reading from the named pipe in the Remote Access Proxy.
Event ID 20069 — Cannot open or obtain information about the PPP key or one of its subkeys.
Event ID 20070 — Point to Point Protocol engine was unable to load the param1 module.
Event ID 20071 — The Point to Point Protocol module param1 returned an error while initializing.
Event ID 20072 — The Point to Point Protocol failed to load the required PAP and/or CHAP authentication modules.
Event ID 20073 — The following error occurred in the Point to Point Protocol module on port: {param1}; UserName: {param2}.
Event ID 20076 — The password for user {param1}\{param2} connected on port {param3} has expired.
Event ID 20077 — The account for user {param1}\{param2} connected on port {param3} has expired.
Event ID 20078 — The account for user {param1}\{param2} connected on port {param3} does not have Remote Access privilege.
Event ID 20079 — The software version of the user param1\param2 connected on port param3 is unsupported.
Event ID 20080 — The server machine is configured to require data encryption.
Description
The server machine is configured to require data encryption. The machine for user param1\param2 connected on port param3 does not support encryption. The line has been disconnected.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20081 — Remote Access Server Security Failure.
Event ID 20082 — The Remote Access Server could not reset lana param1 (the error code is the data) and will not be active on it.
Event ID 20084 — The Remote Access Server will stop using IP Address param1.
Event ID 20085 — The Remote Access Server was unable to renew the lease for IP Address param1 from the DHCP Server.
Event ID 20086 — The Remote Access Server was unable to acquire an IP Address from the DHCP Server to assign to the incoming user.
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.
Event ID 20088 — The Remote Access Server acquired IP Address param1 to be used on the Server Adapter.
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}.
Event ID 20090 — A general error occurred writing to the named pipe in the Remote Access Proxy.
Event ID 20091 — Cannot open the RAS security host Registry key.
Event ID 20092 — Cannot load the Security host module component.
Event ID 20093 — The user param1 has connected and failed to authenticate with a third party security on port param2.
Event ID 20094 — The user connected to port param1 has been disconnected because the following internal authentication error occurred in the third party security module...
Event ID 20095 — Cannot receive initial data on port {param1} because of the following error: {param2} The user has been disconnected.
Event ID 20096 — The user was authenticated as param1 by the third party security host module but was authenticated as param2 by the RAS security.
Description
The user was authenticated as param1 by the third party security host module but was authenticated as param2 by the RAS security. The user has been disconnected.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20097 — A user was unable to connect on port {param1}.
Event ID 20098 — A user was unable to connect on port param1.
Event ID 20099 — Cannot access Registry value for param1.
Event ID 20100 — Cannot access the Registry key param1.
Event ID 20101 — Using the default value for Registry parameter param1 because the value given is not in the legal range for the parameter.
Event ID 20102 — Cannot enumerate keys of Registry key param1.
Event ID 20103 — Unable to load param1.
Event ID 20104 — Memory allocation failure.
Event ID 20105 — Unable to load the interface param1 from the registry.
Event ID 20106 — RoutingDomainID- param1: Unable to add the interface param2 with the Router Manager for the param3 protocol.
Description
RoutingDomainID- param1: Unable to add the interface param2 with the Router Manager for the param3 protocol. The following error occurred: param4.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20107 — RoutingDomainID- param1: Unable to remove the interface param2 with the Router Manager for the param3 protocol.
Description
RoutingDomainID- param1: Unable to remove the interface param2 with the Router Manager for the param3 protocol. The following error occurred: param4.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20108 — Unable to open the port param1 for use.
Event ID 20109 — Cannot recognize initial frame received on port {param1}.
Event ID 20110 — An error occurred in the Point to Point Protocol module on port param1 while trying to initiate a connection.
Event ID 20111 — RoutingDomainID- param1: A Demand Dial connection to the remote interface param2 on port param3 was successfully initiated but failed to complete successfully ...
Description
RoutingDomainID- param1: A Demand Dial connection to the remote interface param2 on port param3 was successfully initiated but failed to complete successfully because of the following error: param4.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20112 — Cannot open the RAS third party administration host DLL Registry key.
Event ID 20113 — Cannot load the RAS third party administration DLL component.
Event ID 20114 — The Service will not accept calls.
Event ID 20125 — RoutingDomainID- param1: A Demand Dial persistent connection to the remote interface param2 failed to be initiated successfully.
Description
RoutingDomainID- param1: A Demand Dial persistent connection to the remote interface param2 failed to be initiated successfully. The following error occurred: param3.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20126 — A packet from param1 destined to param2 over protocol 0xparam3 caused interface param4 to be brought up.
Description
A packet from param1 destined to param2 over protocol 0xparam3 caused interface param4 to be brought up. The first param5 bytes of the packet are in the data.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20127 — RoutingDomainID- param1: The Demand Dial interface param2 was not loaded.
Event ID 20128 — Cannot load the Appletalk Remote Access DLL component because of the following error: {param1}.
Event ID 20129 — An error occurred in the Appletalk Remote Access Protocol module on port {param1} while trying to initiate a connection.
Event ID 20130 — The following error occurred in the Appletalk Remote Access Protocol module on port {param1}.
Event ID 20131 — A user was unable to connect on port {param1}.
Event ID 20132 — Remote Access Connection Manager failed to start because the RAS RPC module failed to initialize.
Event ID 20138 — RoutingDomainID- param1: A Demand Dial connection to the remote interface param2 failed to be initiated successfully.
Event ID 20139 — The port {param1} has been disconnected due to inactivity.
Event ID 20140 — The port {param1} has been disconnected because the user reached the maximum connect time allowed by the administrator.
Event ID 20141 — The user {param1} has connected and has been successfully authenticated on port {param2}.
Event ID 20142 — The user {param1} has connected and has been successfully authenticated on port {param2}.
Event ID 20143 — Unable to load the interface param1 from the registry.
Event ID 20144 — The Demand-Dial interface param1 was not registered with the Router.
Event ID 20145 — Cannot initialize the Remote Access and Router service to accept calls using the TCP/IP transport protocol.
Event ID 20146 — The RADIUS server param1 did not respond to the initial request.
Event ID 20147 — The Remote Access service failed to start because the Point to Point was not initialized successfully.
Event ID 20148 — The RADIUS server name param1 could not be successfully resolved to an IP address.
Event ID 20149 — No global configuration was supplied to the IP Router Manager.
Event ID 20150 — Unable to add demand dial filters for interface param1.
Event ID 20151 — The Control Protocol param1 in the Point to Point Protocol module param2 returned an error while initializing.
Event ID 20152 — The currently configured authentication provider failed to load and initialize successfully.
Event ID 20153 — The currently configured accounting provider failed to load and initialize successfully.
Event ID 20157 — The interface param1 could not be enabled for multicast.
Event ID 20158 — The user {param1} successfully established a connection to {param2} using the device {param3}.
Event ID 20159 — The connection to {param1} made by user {param2} using device {param3} was disconnected.
Event ID 20161 — The user {param1} successfully established a connection to {param2} using the device {param3}.
Event ID 20162 — The Remote Access Server established a connection to {param1} for the user {param2} using the device {param3}.
Event ID 20163 — The connection to {param1} made by user {param2} using device {param3} was disconnected.
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.
Event ID 20165 — A connection has been established on port param1 using interface param2, but no IP address was obtained.
Event ID 20166 — A connection has been established on port param1 using interface param2, but the remote side got no IP address.
Event ID 20167 — RoutingDomainID- param1: No IP address is available to hand out to the dial-in client.
Event ID 20168 — Could not retrieve the Remote Access Server's certificate due to the following error: param1.
Event ID 20169 — Unable to contact a DHCP server.
Event ID 20170 — The user param1 has connected and failed to authenticate because of the following error: param2.
Event ID 20171 — Failed to apply IP Security on port param1 because of error: param2.
Event ID 20172 — Multicast scope mismatch with param1: Locally-configured name "param2", Remotely-configured name "param3".
Event ID 20173 — Multicast scope address mismatch for scope "param1", Locally-configured range is param4-param5, Remotely-configured range is param2-param3.
Description
Multicast scope address mismatch for scope "param1", Locally-configured range is param4-param5, Remotely-configured range is param2-param3.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20174 — Possible leaky multicast Local Scope detected between this machine and param1, since a boundary appears to exist for param2, but not for the local scope.
Event ID 20175 — Multicast scope 'param1' is non-convex, since border router param2 appears to be outside.
Event ID 20176 — A leak was detected in multicast scope 'param1'.
Event ID 20177 — Interface param1 is unreachable because of reason param2.
Event ID 20178 — Interface param1 is now reachable.
Event ID 20179 — RoutingDomainID- param1: Interface param2 is unreachable because there are no modems (or other connecting devices) available for use by this interface.
Event ID 20180 — RoutingDomainID- param1: Interface param2 is unreachable because the connection attempt failed.
Event ID 20181 — RoutingDomainID- param1: Interface param2 is unreachable because it has been administratively disabled.
Event ID 20182 — RoutingDomainID- param1: Interface param2 is unreachable because the Routing and RemoteACcess service is in a paused state.
Event ID 20183 — RoutingDomainID- param1: Interface param2 is unreachable because it is not allowed to connect at this time.
Event ID 20184 — RoutingDomainID- param1: Interface param2 is unreachable because it is not currently connected to the network.
Event ID 20185 — RoutingDomainID- param1: Interface param2 is unreachable because the network card for this interface has been removed.
Event ID 20186 — RoutingDomainID- param1: Interface param2 is now reachable.
Event ID 20187 — The user {param1} failed an authentication attempt due to the following reason: {param2}.
Event ID 20188 — The user {param1}; attempting to connect on {param2}; was disconnected because of the following reason: {param3}.
Event ID 20189 — The user {param1} connected from {param2} but failed an authentication attempt due to the following reason: {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 param1.
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 param1.
Event ID 20192 — A certificate could not be found.
Event ID 20193 — CoID=param1: An error occurred while configuring IP packet filters for user param2 over port param3.
Event ID 20194 — The user {param1} connected on port {param2} on {param3} at {param4} and disconnected on {param5} at {param6}.
Event ID 20195 — The user {param1} has been disconnected on port {param2}.
Event ID 20196 — An invalid response was received from the RADIUS server param1.
Event ID 20197 — Ras Audio Acceleration failed to param1.
Event ID 20198 — Choosing radius server param1 for authentication.
Event ID 20199 — IPinIP tunnel interfaces are no longer supported
Event ID 20200 — The user {param1} connected on port {param2} has been assigned address {param3}.
Event ID 20201 — The user with ip address {param1} has disconnected.
Event ID 20202 — An error occurred while trying to revert impersonation.
Event ID 20203 — Cannot load the Security host module component.
Event ID 20204 — Cannot load the RAS third party administration DLL component.
Event ID 20205 — IPX routing is no longer supported.
Event ID 20206 — Disk full.
Event ID 20207 — Disk full.
Event ID 20208 — Disk full.
Event ID 20209 — A connection between the VPN server and the VPN client param1 has been established, but the VPN connection cannot be completed.
Event ID 20210 — The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service.
Event ID 20211 — The Network Access Protection (NAP) enforcement client could not start PPP renegotiation on the following remote access connection: %d.
Event ID 20212 — The request sent to the Network Access Protection Agent (NAPAgent) failed.
Event ID 20213 — The Network Access Protection (NAP) enforcement client received an invalid request for the following remote access connection: %d.
Event ID 20214 — The Network Access Protection (NAP) enforcement client received an invalid request for the remote access connection.
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...
Event ID 20216 — The Routing and Remote Access service could not start.
Event ID 20217 — An error occurred while trying to disable param1 packet filtering for Routing and Remote Access service.
Event ID 20218 — An error occurred while trying to enable param1 packet filtering for Routing and Remote Access service.
Event ID 20219 — param1 packet filtering has been disabled.
Event ID 20220 — The connection to param1 made using device param2 was terminated.
Event ID 20221 — CoId=.
Description
CoId=: The user has started dialing a connection using a connection profile named . The connection settings are: .
Message #
Event ID 20222 — CoId=.
Description
CoId=: The user is trying to establish a link to the Remote Access Server for the connection named using the following device: .
Message #
Event ID 20223 — CoId=.
Description
CoId=: The user has successfully established a link to the Remote Access Server using the following device: .
Message #
Event ID 20224 — CoId=param1: The link to the Remote Access Server has been established by user param2.
Event ID 20225 — CoId=.
Description
CoId=: The user has dialed a connection named to the Remote Access Server which has successfully connected. The connection parameters are:.
Message #
Event ID 20226 — CoId=param1: The user param2 dialed a connection named param3 which has terminated.
Event ID 20227 — CoId=param1: The user param2 dialed a connection named param3 which has failed.
Event ID 20228 — The remote access connection with the correlation ID param1 has Network Access Protection (NAP)-Enforcement enabled on it.
Event ID 20229 — The remote access connection with the correlation ID param1 received an unexpected/mismatched response to its Statement of Health (SoH) from the server.
Event ID 20230 — The connection from user param1 on port param2 has been disconnected because the Session Timeout received from the RADIUS server has expired.
Event ID 20247 — CoId=param1: Cannot receive initial frame on port param2 because of the following error: param3 The user has been disconnected.
Event ID 20248 — CoId=param1: The user connected to port param2 has been disconnected due to inactivity.
Event ID 20249 — CoId=param1: The user param2 has connected and failed to authenticate on port param3.
Event ID 20250 — RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been successfully authenticated on port param4.
Event ID 20251 — RoutingDomainID- param1: CoId=param2: The user param3 connected on port param4 on param5 at param6 and disconnected on param7 at param8.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
param6 UnicodeString | — |
param7 UnicodeString | — |
param8 UnicodeString | — |
param9 UnicodeString | — |
param10 UnicodeString | — |
param11 UnicodeString | — |
param12 UnicodeString | — |
param13 UnicodeString | — |
param14 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20252 — CoId=param1: The user connected to port param2 has been disconnected because the authentication process did not complete within the required amount of time.
Event ID 20253 — RoutingDomainID- param1: CoId=param2: The user param3 connected to port param4 has been disconnected because no network protocols were successfully negotiated.
Description
RoutingDomainID- param1: CoId=param2: The user param3 connected to port param4 has been disconnected because no network protocols were successfully negotiated.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20254 — CoId=param1: The user param2 on port param3 was called back at the number param4.
Event ID 20255 — CoId=param1: The following error occurred in the Point to Point Protocol module on port: param2, UserName: ,UserName.
Event ID 20256 — CoId=param1: The password for user param2\param3 connected on port param4 has expired.
Event ID 20257 — CoId=param1: The account for user param2\param3 connected on port param4 has expired.
Event ID 20258 — CoId=param1: The account for user param2\param3 connected on port param4 does not have Remote Access privilege.
Description
CoId=param1: The account for user param2\param3 connected on port param4 does not have Remote Access privilege. The line has been disconnected.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20259 — CoId=param1: The Remote Access Server's attempt to callback user param2 on port param3 at param4 failed because of the following error: param5.
Description
CoId=param1: The Remote Access Server's attempt to callback user param2 on port param3 at param4 failed because of the following error: param5.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20260 — CoId=param1: Cannot receive initial data on port param2 because of the following error: param3 The user has been disconnected.
Event ID 20261 — CoId=param1: A user was unable to connect on port param2.
Event ID 20262 — CoId=param1: Cannot recognize initial frame received on port param2.
Event ID 20263 — CoID=param1: The port param2 has been disconnected due to inactivity.
Event ID 20264 — CoID=param1: The port param2 has been disconnected because the user reached the maximum connect time allowed by the administrator.
Event ID 20265 — RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been successfully authenticated on port param4.
Description
RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been successfully authenticated on port param4. Data sent and received over this link is encrypted.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20266 — RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been successfully authenticated on port param4.
Description
RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been successfully authenticated on port param4. Data sent and received over this link is strongly encrypted.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20267 — CoID=param1: The user param2 successfully established a connection to param3 using the device param4.
Event ID 20268 — CoID=param1: The connection to param2 made by user param3 using device param4 was disconnected.
Event ID 20269 — CoId=param1: The user param2 failed an authentication attempt due to the following reason: param3.
Event ID 20270 — CoID=param1: The user param2, attempting to connect on param3, was disconnected because of the following reason: param4.
Event ID 20271 — CoId=param1: The user param2 connected from param3 but failed an authentication attempt due to the following reason: param4.
Description
CoId=param1: The user param2 connected from param3 but failed an authentication attempt due to the following reason: param4.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20272 — RoutingDomainID- param1: CoID=param2: The user param3 connected on port param4 on param5 at param6 and disconnected on param7 at param8.
Message #
Fields #
| Name | Description |
|---|---|
param1 UnicodeString | — |
param2 UnicodeString | — |
param3 UnicodeString | — |
param4 UnicodeString | — |
param5 UnicodeString | — |
param6 UnicodeString | — |
param7 UnicodeString | — |
param8 UnicodeString | — |
param9 UnicodeString | — |
param10 UnicodeString | — |
param11 UnicodeString | — |
param12 UnicodeString | — |
param13 UnicodeString | — |
param14 UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |
Event ID 20273 — CoId=.
Event ID 20274 — RoutingDomainID- param1: CoID=param2: The user param3 connected on port param4 has been assigned address param5.
Event ID 20275 — RoutingDomainID- param1: CoID=param2: The user with ip address param3 has disconnected.
Event ID 20276 — CoId=.
Event ID 20277 — CoId=param1: Successfully processed MOBIKE update for connection named 'param2'.
Event ID 20278 — CoId=param1: Unable to process MOBIKE update for connection named 'param2'.
Event ID 20279 — CoId=param1: Disabling PPP AUTH for param2\\param3 on port param4.
Event ID 20280 — RoutingDomainID- param1: CoID=param2: The correlation ID on the server is param3.
Event ID 20281 — CoID=param1: Connection supports MOBIKE.
Event ID 20282 — RoutingDomainID- param1: Failed to enable IPv4 forwarding on interface param2 with error: param3.
Event ID 20283 — RoutingDomainID- param1: Failed to disable IPv4 forwarding on interface param2 with error: param3.
Event ID 20284 — RoutingDomainID- param1: Failed to plumb IKEv2 policies for one or more demand dial interfaces.
Event ID 20285 — Did not find the certificate configured to be used for IKEv2 local authentication.
Event ID 20286 — Failed to plumb the custom IKEv2 policy.
Event ID 20287 — RoutingDomainID- param1: Did not find the PreSharedKey configured to be used for local or remote authentication for the IKEv2 connection.
Event ID 20288 — RoutingDomainID- param1: IPv4 routes are not added for the demand dial connection as IPv4 transport is not available on the corresponding interface.
Event ID 20289 — RoutingDomainID- param1: IPv6 routes are not added for the demand dial connection as IPv6 transport is not available on the corresponding interface.
Event ID 20290 — Disabling S2S interface param1 (RoutingDomain: param2) because either there is no destination IP configured or DNS resolution failed for the configured des...
Event ID 20291 — param1 requires attention.
Event ID 20292 — Retrieving Max connections failed.
Description
Retrieving Max connections failed. MaxCon: Retrieving_Max_connections_failed_MaxCon. HResult: HResult.
Message #
Fields #
| Name | Description |
|---|---|
Retrieving_Max_connections_failed_MaxCon | Retrieving Max connections failed. MaxCon. |
HResult UnicodeString | — |
MaxCount UnicodeString | — |
__binLength UInt32 | — |
binary Binary | — |