Event ID: 39 Source: CDM

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

EvLog 3.0 – Monitor an unlimited number of servers with $49/year

With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Event ID: 39 Source: CDM

Source: CDM

Type: Error

Description:
The CDM redirector has timed out a request to SessionID <value>.

English: Request a translation of the event description in plain English.

Concepts to understand:
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
What is a redirector?

Comments:
EventID.Net
"Citrix Support Document ID: CTX109668" has information on this event.
Click if the comment is good!

^{x
6}

Thomas 'TC' Kuhn
This can also happen if the client has for example LPT1 and LPT2 and the server has only LPT1. Then the event is created based on the problem of the LPT2-redirection.
Click if the comment is good!

^{x
2}

Anonymous
This event indicates a CDM - Redirector problem. The following is a series of troubleshooting steps that can be taken in order to assist in resolving this issue:
First, find out what client device type is causing the issue (Client com port, Drive, LPT port, etc)
1. Disable all client device mappings in Citrix Connection Configuration for the ICA Listener that you connect with.
2. Logon from the client with the suspect device.
3. If you were able to logon, and no events in the Events Viewer appeared associated with CDM, re-enable one client device type at a time in Citrix Connection Configuration.
4. Repeat Steps 2 and 3 until the device type is found.

Next, Within the session, at the command prompt, type:
QOBJECT /DEVICE > QOBJECT.TXT

This command creates a text file where you can see the mapping for LPT1 and LPT2. During troubleshooting, ensure the following: The port has been mapped using the CDM redirector. This is the Citrix redirector for mapping client devices. If instead of the CDM redirector you see the LanMan redirector, it indicates that the port on the server is being mapped to another port on the server network (using Microsoft networking). In the mapping for the client device: LPTx:\yy\LPTz: LPTx is the port name at the server side, /yy/ is the session ID, and LPTz is the port on the client site, where LPTx is pointing to.

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 60 seconds

*** Note: For Microsoft Windows NT Server 4.0 Terminal Server Edition, Windows 2000 Server and Windows 2000 Advanced Server - QUERY replaces QUSER, QPROCESS, QOBJECT, QAPPSERV, QWINSTA from Citrix Winframe. See ME186592.
Click if the comment is good!

^{x
3}

Gerry Locke
Check to see if any users have more than 1 active session listed in the Citrix Management Console. If so, reset the active sessions. In our case, this made the error go away.
Click if the comment is good!

^{x
7}

Private comment: Subscribers only. See example of private comment

Links: Citrix Solution Knowledge Base

Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...

Feedback: Send comments or solutions - Notify me when updated

Printer friendly