Error Cdm Event Id 39
Contents |
log appeared in the Event Viewer: Printer drivers on client’s computer: ICA client was verifying and checking appropriate printer drivers from the client during the log on process, when this process is
Event Id 39 Iscsiprt
taking longer than the default time out value, the error occurred. During the Citrix ctx207308 logon process, The Citrix server will send a request to the Citrix client to enumerate the client printers. Now at
Ctx109668
this point you may think that if you have "Connect to Clients default printer only" then only the default printer will be enumerated. WRONG! 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 it. So, if there are 10 printers in profile, all 10 printers will be checked to see if there are drivers installed. Now the best bit - if the drivers are not installed, the client will try to get the drivers from the print server. 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. If this takes too long, which it inevitably will as the client is downloading the printer drivers. A timeout occurs which then results in the CDM redirector errors appearing in the event viewer. Once the printer drivers are installed, you won't see it the CDM errors anymore (that's why it seems like it happens once) unless the user moves to a different PC (that doesn't have printer drivers for the user's network printers). It's a pretty poor of way of designing the print process by Citrix, especially if a user may have several printers referenced in their profile and they then move to a client which doesn't have those printer drivers installed. Possible solutions: (1) Install the required drivers on the terminal server (2) Force to use Universal Driver (source) Citrix’ official knowledge base article – CTX207308 suggests to increase request timeout value in registry. 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... Related Written by Nicolas Lin Posted in windows, XenApp Tagged w
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Getting error message "The CDM redirector has timed out a request to https://innitec.wordpress.com/2009/10/13/event-viewer-error-id39-the-cdm-redirector-has-timed-out-a-request-to-session-id-xx/ SessionID 1 - Event ID 39" in my Citrix metaframe XP server Want to Advertise Here? Solved Getting error message "The CDM redirector has timed out a request to SessionID 1 - Event ID 39" in my Citrix metaframe XP server Posted on 2008-04-02 Citrix Windows 2000 1 Verified Solution 3 Comments 7,487 Views Last 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 Modified: 2010-04-21 I have metaframe XP installed on windows 2000 terminal server. Every now and then I get an event ID 39 "The CDM redirector has timed out a request to SessionID 1" on system log. I noticed onething, for security reason my server has been configured to automatically logoff users from the sessions if they are idle for 2 mins. This particular event is getting generated whenever there is a forced logoff.. After each forced logoff, I get couple of these errors. Any idea what exactly it is and how to fix it??? 0 Question by:Viswa8888 Facebook Twitter LinkedIn Google LVL 10 Best Solution bytboy6423 This may be your answer: http://hqextsrvsft01.citrix.com/forums/thread.jspa?forumID=1&threadID=55464&tstart=0 Go to Solution 3 Comments LVL 10 Overall: Level 10 Windows 2000 2 Citrix 1 Message Accepted Solution by:tboy64232008-04-02 This may be your answer: http://hqextsrvsft01.citrix.com/forums/thread.jspa?forumID=1&threadID=55464&tstart=0 0 Message Author Comment by:Viswa88882008-04-02 Thanks, it was a nice explanation, I have not tested it but I can understand the problem at least..
password CAPTCHAThis question is for testing whether or not you are a human visitor and to prevent automated spam submissions. Error Event ID 39 is Logged Inside the System Event Log Submitted by RoyATokeshi on Wed, 06/21/2006 - 10:10 Citrix states in their http://tokeshi.com/node/4495 article: CTX109668 Document ID: CTX109668, Created on: Jun 13, 2006, Updated: Jun 16, 2006 Products: Citrix http://musumeci.blogspot.com/2007/07/ctx-event-39-cdm-redirector-has-timed.html Access Essentials 1.0, Citrix Access Essentials 1.5, Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows 2000, Citrix Presentation Server 4.0 for Microsoft Windows 2003, Citrix Presentation Server 4.0 for Microsoft Windows 2000, Citrix Presentation Server 4.0 for Microsoft Windows 2003, Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003 Symptoms Error Event ID 39 event id is logged inside the system event log with the following description: “Event Log: System Event Type: Error Event Source: Cdm Event Category: Event ID: 39 Date: xx/xx/xxxx Description: The CDM redirector has timed out a request to SessionID x” -And- • The client default printer is not set as default inside your ICA session. • Client printer autocreation is inconsistent. • Session printer(s) are not randomly created or the defaults properly set / changed. • Client event id 39 printers are sometimes created indirectly or vice versa. • Client side printer properties could not be read. Application event 1103 is logged. Resolution Only apply this to systems experiencing the problems described in this article. These problems are caused by pdfFactory 2.x or earlier versions. Obtain pdfFactory Server Edition. Status FinePrint confirmed on their Web page that the software can cause Error Event ID 39 inside a Terminal Server environment. FinePrint changed the licensing model for their software. If you encounter any problems with your FinePrint software, contact FinePrint Technical Support. More Information FinePrint Software Google+ DISCLAIMER: None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no
CdmEvent Category: NoneEvent ID: 39Date: 03/07/2007Time: 5:07:34User: N/AComputer: SERVERDescription: The CDM redirector has timed out a request to SessionID XX.This can happen when an application is attempting to access a client device during a disconnect. Check Citrix Server Administration when you see this event appear.The best way to determine what client device is causing this issue is to turn off client device mapping (client drive, client COM ports, client printers).Enable them one at a time and monitor the client's logon process.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\ParametersIncrease the settings for the following:RequestTimeout: Default is 60 (seconds)DirCacheTimeout: Default is 30 (seconds)CacheTimeout: Default is 60 (seconds)Incresea these timeout x 2 or x3 (registry example)--- Start Registry File ---Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters]"CacheTimeout"=dword:000000b4"DirCacheTimeout"=dword:0000005a"RequestTimeout"=dword:000000b4--- End Registry File --- Posted by Guillermo Musumeci at 3:33 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: CTX No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) My Citrix XenApp 6.5 Book My new book about Citrix XenApp 6.5. Available Now at Amazon and PacktPub Citrix XenApp 6 Book My book about Citrix XenApp 6. Available at Amazon and PacktPub About Me Guillermo Musumeci Singapore, Singapore Windows Infrastructure Architect specialized in Automation, Citrix, Cloud (Amazon AWS, Microsoft Azure and Google Cloud) and Virtualization with 19 years of experience and passion for designing, building, deploying, and supporting Windows solutions in America, Asia and Europe. Guillermo wrote two books about Citrix XenApp, published by Packt Publishing. He is the founder and developer of KopiCloud, which provides tools for multi-cloud (AWS, Azure and GCE) infrastructure as a code. Also, he is the founder and developer of the popular site CtxAdmTools, which provides free automation tools to manage Citrix environments, Cloud (AWS and Azure), Active Directory, Virtualization and more. View my complete profile Blog Archive