Table of Contents
Here are some simple ways that can help you solve the event ID 39 cdm problem.
Updated
39 | |
Source | CDM |
Description < / td> | The readabilitydatatable = “0”> |
Could not find event description for event ID (39) in source (cdm). The local computer may not have the necessary registry information and message DLL files to view messages from a remote computer. The following information is always part of the event: Device CdmRedirector | |
Event Information | Based on information from the content of the newsgroup article, this event could be a CDM redirector – problem. The following steps can help your company solve this problem. Find out what type is causing this problem (com client connection, disk, LPT port, etc.) 1. Disable all proprietary device mappings in the Citrix connection configuration to the ICA listener you are communicating with. 2. From the client, connect to the suspicious device. 3. If you were able to connect and no CDM related events were displayed in Event Viewer, reactivate one type of software device at a time.Citrix connection configurations. 4. Repeat steps 2 or more until you find the device type. Then, at the command prompt, enter: This command creates a text file in which anyone can see a mapping of LPT1 in addition to LPT2. When troubleshooting, ensure that: Port is assigned to the CDM redirector. This is a Citrix redirector for client device mapping. If you see LanMan, a home redirector instead of a generic CDM redirector, it means that your current server’s port is mapped to another connector on the server’s network (using Microsoft networks). In the assignment for the client technology: LPTx: yy LPTz: LPTx is the port, the server side name, / yy / is the learning identifier, and LPTz is the client site port that LPTx is directed to. Finally, if you still have problems, try this: |
Referral Free links |
Stop Provocations Immediately
We work with you to quickly identify cyber threats and stop attacks before they cause damage.
There are obviously several possible reasons why this error log is displayed in Event Viewer:
Printer driver on client computer: The ica client confirmed and verified the correct printer drivers for its client during the connection process, although this process takes longer than the default timeout, a problem has occurred.
During the Citrix connection process
The Citrix server sends a request to the Citrix client for the final enumeration of client printers. At this wonderful moment, you might think that if you have “Connect only standard client devices”, only the default printer will appear in the list.
LIE! Each printer owned by a user or specified in a user’s connection profile It is checked for the presence of an established owner. Therefore, if there are likely 10 printers in the profile, it will check all 10 printers to see if any drivers are installed.
Now the best part is when the drivers are not installed, the client usually tries to get the drivers like a print server.
Although this is literally happening, the Citrix server is nearby, so the client sends some information back to the printer so it can try to generate it automatically. Even if it takes a significant amount of time, it will inevitably happen when the user downloads the printer drivers. Timeout occurs, which then causes CDM redirector errors to appear in the event client.
Once all the printer drivers are installed, CDM errors will not appear (for this reason, it seems that it only happens once) unless the user switches to another computer (it does not). there are drivers for the user’s network printers).
This is a pretty bad way of thinking about Citrix print management, especially when a user can link to multiple printers fromtheir profile page, and then switch to a destination that these printer operators do not have. installed.
Possible installation options:
(1) drivers typically required on a terminal server;
(2) forced use of generic driver
(source)
Citrix Executive Knowledge Base Article – CTX207308 suggests increasing the timeout value for registry queries.
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Cdm Parameters
Increase conditions for the following:
RequestTimeout: default is sixty miles per hour (in seconds)
default DirCacheTimeout nominal is 30 seconds
CacheTimeout – 50 seconds
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
Event-ID 39 Cdm
이벤트 ID 39 Cdm
Id. De Evento 39 Cdm
Идентификатор события 39 Cdm
Ereignis-ID 39 Cdm
Identifiant De L’événement 39 Cdm
Identyfikator Zdarzenia 39 Cdm
Gebeurtenis-ID 39 Cdm
Id Do Evento 39 Cdm
ID Evento 39 Cdm