Quantcast
Channel: Forum Remote Desktop Services (Terminal Services)
Viewing all articles
Browse latest Browse all 27650

Remote Desktop Server 2008 R2 - Printers disappear - timeout UmRdpService

$
0
0
We have an issue on a 2008 R2 Remote Desktop Server where printers in all the user sessions disappear. Also in the event log we have the following errors:

Log Name: System

Source: Service Control Manager

Event ID: 7011 A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

Log Name: System

Source: Service Control Manager

Event ID: 7011

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxSms service.

Log Name: System

Source: Service Control Manager

Event ID: 7011

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndpointBuilder service.

Log Name: System

Source: Service Control Manager

Event ID: 7011 A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.

Log Name: System

Source: Service Control Manager

Event ID: 7000

The Portable Device Enumerator Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log Name: System Source: DistributedCOM

Event ID: 10009

DCOM was unable to communicate with the computer "servername" using any of the configured protocols.

These errors fill the event log. The way to resolve the issue is to restart the print spooler. However this only appears to resolve the issue for an hour or so. To resolve the issue for a longer period the server needs to be restarted. This could be related, that every now and then on the server we have a 'Interaction Services Detection' pop up window, which comes from various HP printers, which need to be achknowledged. In an attempt to resolve the issue we have put the printer drivers in 'isolation' mode which has not resolve the errors.

This needs to be resolved promptly because, as you can imagine, this is causing a huge amount of disruption to our users who are becoming very frustrated. Regards


Viewing all articles
Browse latest Browse all 27650

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>