A request was received by the RPC server on %1 endpoint from %2 but there is no provider registered for %1 endpoint. This can happen if the provider failed to initialize but was not marked as critical or if a malicious code is trying to probe for available services. The binary data contains the first 32 bytes of the request.
A request was made to authenticate to a wired network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
A request was made to authenticate to a wireless network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
A request was made to authenticate to a wireless network. Subject: Security ID: %2 Account Name: %3 Account Domain: %4 Logon ...
A request was made with a payload that was too big or to a URI that was too long. Parameter Reference Context: %1 RequestId: ...
A request was received by the RPC server on %1 endpoint from %2 but there is no provider registered for %1 endpoint. This ...
A request was received by the RPC server on %1 endpoint from %2. The request was denied because of the security permissions ...
A request was received by the RPC server on %1 endpoint from %2. The request was received on authenticated channel but the ...
A request was received by the RPC server on %1 endpoint from %2. The request was received on unauthenticated channel but ...
A request was received that identified itself as a WS-Federation Passive Requestor Profile (WS-F PRP) sign-in message, but ...