A replay attack was detected. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Credentials Which ...

A replay attack was detected.

Subject:
	Security ID:		%1
	Account Name:		%2
	Account Domain:		%3
	Logon ID:		%4

Credentials Which Were Replayed:
	Account Name:		%5
	Account Domain:		%6

Process Information:
	Process ID:		%12
	Process Name:		%13

Network Information:
	Workstation Name:	%10

Detailed Authentication Information:
	Request Type:		%7
	Logon Process:		%8
	Authentication Package:	%9
	Transited Services:	%11

This event indicates that a Kerberos replay attack was detected- a request was received twice with identical information. This condition could be caused by network misconfiguration.

A registry value was modified. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Object: Object Name: ... A remote print driver package operation %1 failed with error code %2, server name %3. This was most likely caused by an unexpected ... A Remote Procedure Call (RPC) was attempted. Subject: SID: %1 Name: %2 Account Domain: %3 LogonId: %4 Process Information: ... A remote procedure call running locally took too long to complete. The client has likely cancelled this call. Additional ... A replay attack was detected. Subject: Security ID: %1 Account Name: %2 Account Domain: %3 Logon ID: %4 Credentials Which ... A replication connection was created from the following source directory service to the local directory service. Source directory ... A replication operation that began at the following start time has been taking longer than expected to complete. As a result, ... A request for a callback on a MTA thread failed. This should happen only if the system is in an extremely unstable state. ... A request for assistance with an error could not be sent because the email address of the recipient is blank. Details: Error: ...