This article contains information about the troubleshooting process for printing issues with auto-creation failure and Citrix Print Manager crashing. Background The following information was collected from consistent use of the same procedure to troubleshoot multiple printing issues with auto-created printers and the Citrix Print Manager service crashing. Troubleshooting Process Non-native print drivers are the main cause for the failure of auto-creation causing a slew of other issues that must be considered after identifying the drivers to remove from the server. This is a dynamic key and does not affect any existing sessions on the server. This ensures that all new sessions receive the new group policies on the server. The best way to identify non-native print drivers is to observe the registry. If this version is 6. If it reads 0. For more information, refer to the Knowledge Center article CTX126093— At this point use the Citrix Print Driver Stress Test tool to see if this driver is causing the issues. For more information, refer to the Knowledge Center article CTX109374 —. In the following example of the 5x5 setup for testing, 5 concurrent AddPrinter events are created and repeats it 5 times: image from the stress test tool After you remove the drivers from the server, you should check what contents are left behind from the bad drivers. Drivers must respond to the AddPrinter , XcvData , and DeletePrinter API function calls. This might cause the Citrix Print Manager service to crash, not be able to restart, or even to stop functioning. Note: Sometimes print drivers can be problematic to remove from servers since they are loaded once the spooler is running. Using the following method is the easiest way to remove a problematic print driver: Caution! Refer to the Disclaimer at the end of this article before using Registry Editor. Click on the driver tab and remove the problematic driver. Refer to the Disclaimer at the end of this article before using Registry Editor. Print drivers that do not respond to the DeletePrinter API correctly will leave stale records in the registry, these records can build up if the driver is not removed causing printing problems in your XenApp environment. You should remove anything in this hive that has a comma after the session number along with another arbitrarily generated number. You should ensure that the printing values you remove do not currently have sessions logged onto the server. If it does, then it can cause problems to the user session. Do not remove any of the local printers on the server. Remove only the printers created with session numbers and commas after them, or any other irregularities. These irregular printers are created when the print driver does not respond to the DeletePrinter API function call. Open the Command window with administrator credentials. Refer to article, CTX124406 —. Note: DSCHECK applies only to XenApp versions 6. Although this will not remove the actual driver replication from the servers, it deletes all the replication information stored in the datastore. After you have run all the purge commands and the datastore is clean, recreate the Local Host Cache on all the servers. Refer to the Disclaimer at the end of this article before using Registry Editor. If you still experience a printing issue, we will need to clear any entries under the Current Users registry key. In this example, the spooler is run under the Local System: We can see from the following entries, two printers were auto-created and their entries were placed in the. These two accounts are mirrors of each other since the. DEFAULT profile, is the systems profile. If one of these hives has hundreds if not thousands of entries, it will populate both registry hives causing the spooler and the Citrix Print manager to have to query all entries in that hive causing delays and crashes. Refer to the Disclaimer at the end of this article before using Registry Editor. To simplify the cleanup of these hives, run the following commands in a command window. Once the commands have been run, restart the print spooler for the new data to be added to those entries. The S-1-5-18 account does not need to be cleaned out as it is a mirror of the. Refer to the Disclaimer at the end of this article before using Registry Editor. Other locations that store user print device preference information can also get filled up with data if not purged regularly. This can also cause problems with your spooler and your Citrix Print Manager services. CTX104375 — CTX115553 — CTX117008 — The following CTX Case Study article is a good reference to use when the CpSvc. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it. Automatic translation This article was translated by an automatic translation system and was not reviewed by people. Citrix provides automatic translation to increase access to support content; however, automatically-translated articles may can contain errors. Citrix is not responsible for inconsistencies, errors, or damage incurred as a result of the use of automatically-translated articles. Traduzione automatica Questo articolo è stato tradotto da un sistema di traduzione automatica e non è stata valutata da persone. Citrix fornisce traduzione automatica per aumentare l'accesso per supportare contenuti; tuttavia, articoli automaticamente tradotte possono possono contenere degli errori. Citrix non è responsabile di incongruenze, errori o danni derivanti dell'uso di articoli automaticamente tradotte. Automatische Übersetzung Dieser Artikel wurde mit einem automatischen Übersetzungssystem übersetzt und nicht von Personen überprüft. Citrix bietet automatische Übersetzungen, um den Zugriff auf Supportinhalte zu erweitern. Automatisch übersetzte Artikel können jedoch Fehler enthalten. Citrix ist nicht verantwortlich für Inkonsistenzen, Fehler oder Schäden infolge der Verwendung automatisch übersetzter Artikel. Tradução automática Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей. Citrix recurre a la traducción automática para mejorar e incrementar el acceso a páginas de asistencia técnica. No obstante, la información publicada mediante traducción automática puede contener errores. Citrix no se responsabiliza por inconsistencias, errores o daños incurridos como resultado del uso de información generada por un sistema de traducción automática.
