Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 52 Source: TermService

Object Name not found.
According to one Microsoft Knowledge base article this symptom can occur if the RDP-tcp listener is not initialized or if the Terminal Device driver is not started. See ME258021.
The RDP-tcp connection may have to be reset. To reset the RDP-tcp connection in the Terminal Services Configuration management console, right-click the connection, and then click Disable. Confirm the changes when you are prompted to do so. Repeat the process, and then click Enable.
This solved my problem. Check ME258021.
In our case, the data section of the event would display "RDPTCP". It appeared after an update in the control panel and the registry to activate some language on the DC/GC (see ME301314). We had to add the Client creator file (Add/Remove programs) in oder to force the operating system to repeat the install and restore the missing element. The server was restarted and the errors disappeared after that.
Data section: ICA-tcp. Several IBM X335 servers running Citrix occasionally hang after a scheduled reboot, with this error 52 message in the system log. After a cold boot the systems run fine.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.