Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 52 Source: TermService
Object Name not found.
|English: Request a translation of the event description in plain English.|
Michael P. Piron
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.
G.S. van Kuilenburg
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.
Christophe Lubrano di Ciccone
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.
Rob van der Woude
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.
|Private comment: Subscribers only. See example of private comment|
|Links: ME301314, ME258021|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated