Available Now at Amazon and PacktPub Citrix XenApp 6 Book My book about Citrix XenApp 6. I can still connect to the server via RDP. Every printer that's on the client or is referenced in the profile of the user logging on, will be checked to see if there is a driver installed for View my complete profile Blog Archive ► 2015 (1) ► January (1) ► 2014 (3) ► September (1) ► March (2) ► 2013 (4) ► November (1) ► September (1) ► Clicking Here
Every now and then I get an event ID 39 "The CDM redirector has timed out a request to SessionID 1" on system log. Comments: EventID.Net "Citrix Support Document ID: CTX109668" has information on this event. This particular event is getting generated whenever there is a forced logoff..
While all this is going on, the Citrix server is waiting for the client to send the printer information back so it can auto create the printers. Powered by Blogger. Repeat Steps 2 and 3 until the device type is found. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action.
So, if there are 10 printers in profile, all 10 printers will be checked to see if there are drivers installed. More Information FinePrint Software Guillermo Musumeci Blog Automation, AWS, Citrix, Cloud, CtxAdmTools, Microsoft, Virtualization, VMware and more... What is a redirector? http://discussions.citrix.com/topic/324719-xenapp-server-stops-accepting-connections-via-ica-protocol/ Get 1:1 Help Now Advertise Here Enjoyed your answer?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters Increase the settings for the following: RequestTimeout: Default is 60 (in seconds) DirCacheTimeout Default is 30 seconds CacheTimeout is 60 seconds Like this:Like Loading... If this takes too long, which it inevitably will as the client is downloading the printer drivers. MS: Insufficient System Resources Exist to Complet... So, if there are 10 printers in profile, all 10 printers will be checked to see if there are drivers installed.
Already a member? https://www.experts-exchange.com/questions/23289820/Getting-error-message-The-CDM-redirector-has-timed-out-a-request-to-SessionID-1-Event-ID-39-in-my-Citrix-metaframe-XP-server.html All rights reserved. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters Increase the settings for the following: RequestTimeout: Default is 60 (in seconds) DirCacheTimeout Default is 30 seconds CacheTimeout is 60 seconds Source: http://innitec.wordpress.com/2009/10/13/event-viewer-error-id39-the-cdm-redirector-has-timed-out-a-request-to-session-id-xx/ Posted by OCCx at 1:31 PM Email MS: Exchange 2003 Change Password in OWA VMware: Install Windows Vista x86 on ESX Server 3....
By joining you are opting in to receive e-mail. http://3swindows.com/event-id/sidebyside-event-id-35-citrix-ica-client.html While all this is going on, the Citrix server is waiting for the client to send the printer information back so it can auto create the printers. Join the community of 500,000 technology professionals and ask your questions. MS: Exchange 2007 POP3 Client Access Configuration...
Enable them one at a time and monitor the client's logon process Source: http://musumeci.blogspot.com/2007/07/ctx-event-39-cdm-redirector-has-timed.html Possible solutions: (1) Install the required drivers on the terminal server (2) Force to use Universal Driver Remove HP Universal Print Monitor MS: Exchange 2007 IMAP4 Client Access Configuratio... read more... Check This Out Register now while it's still free!
Red Flag This Post Please let us know here why this post is inappropriate. It's a pretty poor of way of designing the print process by Citrix, especially if a user may have severalprinters referenced in their profile and they then move to Covered by US Patent.
Further attempts to access \\tsclient\h will result in a timeout. Join UsClose ⚑ Deus Ex Machina ➽ Eventlog Lookup DxM Home | Registry Deus Ex Machina » Eventlog » Event 39 - Cdm Navigation Windows Event Logs Events by ID Windows During the Citrix logon process, The Citrix server will send a request to the Citrix client to enumerate the client printers. The timeout settings can be modified by changing the registry keys at HKLM\SYSTEM\CurrentControlSet\Services\Cdm\Parameters.
Applied reg change as per advice form citrix but it only fixed some servers!! Maybe FR3 will fix it.? If you encounter any problems with your FinePrint software, contact FinePrint Technical Support. this contact form Finally, try the following if you still are having issues: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters Increase the settings for the following: RequestTimeout: Default is 60 (in seconds) DirCacheTimeout Default is 30 seconds CacheTimeout Default is
English: Request a translation of the event description in plain English. x 2 Anonymous This event indicates a CDM - Redirector problem. A timeout occurs which then results in the CDM redirector errors appearing in the event viewer. XenApp servers are VMs hosted on XenServer 5.5 booting via PVS 5.1.2 vDisk.Applications: Cerner (HealthCare Application)AntiVirus: CA eTrustThis looks like a bug in the OS or application memory leaks.I have tried
If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity Best Practice for Re-creating User Profile 3 65 2016-06-17 Exiting Full Screen NetScaler Citrix Advertise Here 658 members asked questions and received personalized solutions in the past 7 days. The following information is part of the event: \Device\CdmRedirector, 31.Data:0000: 00 00 00 00 02 00 4a 00 ......J.0008: 00 00 00 00 27 00 0c c0 ....'..Ã0010: 00 00 00 Join Us! *Tek-Tips's functionality depends on members receiving e-mail.
We have explained the difference between… Citrix Virtualization Remote Access How to set up NetScaler CPX with NetScaler MAS in a Mesos/Marathon environment Video by: Michael This demo shows you how Related Written by Nicolas Lin Posted in windows, XenApp Tagged with terminal, XenApp Leave a Reply Cancel reply Enter your comment here... Status FinePrint confirmed on their Web page that the software can cause Error Event ID 39 inside a Terminal Server environment. In our case, this made the error go away.