--- title: 1108(S) The event logging service encountered an error while processing an incoming event published from %1. (Windows 10) description: Describes security event 1108(S) The event logging service encountered an error while processing an incoming event published from %1. ms.pagetype: security ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library author: Mir0sh --- # 1108(S): The event logging service encountered an error while processing an incoming event published from %1. **Applies to** - Windows 10 - Windows Server 2016 Event 1108 illustration ***Subcategory:*** [Other Events](other-events.md) ***Event Description:*** This event generates when event logging service encountered an error while processing an incoming event. It typically generates when logging service will not be able to correctly write the event to the event log or some parameters were not passed to logging service to log the event correctly. You will typically see a defective or incorrect event before 1108. For example, event 1108 might be generated after an incorrect [4703](event-4703.md) event: Event 4703, partial illustration > **Note**  For recommendations, see [Security Monitoring Recommendations](#security-monitoring-recommendations) for this event.
***Event XML:*** ``` - - 1108 0 2 101 0 0x4020000000000000 5599 Security WIN-GG82ULGC9GO.contoso.local - - 0 Microsoft-Windows-Security-Auditing ``` ***Required Server Roles:*** None. ***Minimum OS Version:*** Windows Server 2008 R2, Windows 7. ***Event Versions:*** 0. ***Field Descriptions:*** **%1** \[Type = UnicodeString\]: the name of [security event source](https://msdn.microsoft.com/en-us/library/windows/desktop/aa363661(v=vs.85).aspx) from which event was received for processing. You can see all registered security event source names in this registry path: “HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\EventLog\\Security”. Here is an example: Subkeys under Security key illustration ## Security Monitoring Recommendations For 1108(S): The event logging service encountered an error while processing an incoming event published from %1. - We recommend monitoring for all events of this type and checking what the cause of the error was.