We ran into a similar issue on our Citrix farm due to the higher utilization of printing large maps the issue was caused by the HP Universal Print driver. I manage two farms, a Citrix XenApp 6.0 farm for GIS applications and an RDS farm for office applications.
I bet you have the HP Universal Print driver installed on the machines? I have exactly same problem with my two Terminal Servers (Windows 2008 SP2) and I dont find any resolution. Has anyone else faced this or is facing it at the moment? Other people post about this issue, but haven't come across anything that states the cause and resolution. In the end, the server has to be restarted for us to access it and for users to connect to it.ĭoing some research, I cam across this KB article ( ), but not sure if it applies to this situation. 81008AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.80938AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the wuauserv service.80907AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.80851AM - The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.80837AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinVNC4 service.80807AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxSms service.80737AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.80707AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.80637AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the seclogon service.80607AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.80537AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service.80507AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.80437AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.80407AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.80237AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.80307AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.80237AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndpointBuilder service.Here are the lists of services that timed out on one of these servers, along with the time it happened. The services that time out are not exactly the same across all the servers, but a number of them are the same on all of them.
I have now seen this issue happen on multiple Windows Server 2008 Terminal server setups. I have left the other thread open because I believe this is not just applicable to the Remote Desktop Services Role.
The Native drivers seem to work fine for now, but from previous experience Native drivers are a nightmare to manage in XenApp as they tend to crash the spooler frequently.There is another thread open under the "General" section. The pages either print blank or the font is just completely wrong and out of alignment, and it can also cause the spooler to crash on the print server. We only have 4 different models across the fleet).
I know Citrix likes to push the use of the Citrix Universal drivers as the recommended option, and that the XPS/EMF printing is designed to reduce bandwidth, however it simply does not work on more of our devices than what it works on (we have a Lexmark Print fleet. The difficult part is knowing what drivers to use (Citrix Universal vs Native). My plan is to deploy these printers to users via Citrix Policies. We do have a print server with all of the required print queues installed.
The users all have thin clients so we are unable to add printers to these devices. I am publishing XenApp Desktops (Server 2008 R2) to all of our users.
I am currently testing my new XenApp 6.5 farm.ĭesigning the Print solution for the farm is very confusing as every white paper has a different recommended method.