Symptoms
Certain users could not print using the “Print Function” from a custom application that generated reports using Adobe Acrobat 7.x. If the application's
Print Preview option was chosen, the documents printed.
Users often inquire about what they need to do to make their application print within Citrix.
Below is a common question:
Q: How do you determine if the issue is with the application or if it is a potential Citrix design flaw or issue?
A: By understanding the printer function calls the application is making and what these printer application programming interfaces (APIs) within the application are doing at the time they print to a printer. Often, general troubleshooting and the ability to accurately define the issue do not warrant the need for advanced debugging. The debugging process often involves the investigation of the spooler service and Citrix Diagnostic Facility (CDF) tracing of the Citrix components. Such analysis may expose buffer overflows, memory conflicts, and hard-coded printer name lengths.
Cause
This issue was reproducible outside of Citrix when the printer name's length was approximately 60-61 characters.
Copying the Citrix Client Printer name to Notepad, renaming a local printer using the same Citrix Client Printer name, right-clicking a .pdf file and choosing Print failed to send a job to the local print queue. If Adobe was opened (mimicking Print Preview) before opening the file, a job was sent to the print queue.
Resolution
Upgrade to
Adobe Acrobat 8.x or later.
More Information
CTX112856 –
Certain Users Could Not Print Using the "Print Function" From a Custom Application That Generated Reports Using Adobe Acrobat 7.x contains a troubleshooting case study on this issue.
Source