ComTechAS
asked on
PCL XL Error when printing from a redirected printer in XenApp
Hello,
I have a user who tries to print to a redirected printer in a Citrix XenApp 6.5 session.
The printer gets redirected and everything but it only prints the following error on the sheet:
PCL XL Error
illegal attribute value
operator read image
Do anyone have a clue?
I have a user who tries to print to a redirected printer in a Citrix XenApp 6.5 session.
The printer gets redirected and everything but it only prints the following error on the sheet:
PCL XL Error
illegal attribute value
operator read image
Do anyone have a clue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Felix Leven
Some drivers like kyocera can be set to other PCL Versions PCL XL = 6. Version 5x will work.
Check the event log on the server to determine if you are seeing an error related to the inability to map a printer correctly. Chances are these appear, confirming that it is a printer driver issue.
If you have your environment set to use the Citrix Universal Printer driver as a fallback (default), then it could be that this printer just doesn't work with UPD. Or, it could be that the printer driver was updated or changed client-side and not server-side, so the two can't talk to each other properly. Vice versa could also be true but not as likely.
When a user connects to a XenApp server and printers are mapped, the same driver must be on both sides. Citrix UPD is installed on the client side within Citrix Receiver, and of course, as part of the XenApp installation. So, it makes sense to use this as the least common denominator.
If you have your printer settings on your XenApp server set to use native drivers and/or session printer settings, then you must have that same driver on both sides.
If you have your environment set to use the Citrix Universal Printer driver as a fallback (default), then it could be that this printer just doesn't work with UPD. Or, it could be that the printer driver was updated or changed client-side and not server-side, so the two can't talk to each other properly. Vice versa could also be true but not as likely.
When a user connects to a XenApp server and printers are mapped, the same driver must be on both sides. Citrix UPD is installed on the client side within Citrix Receiver, and of course, as part of the XenApp installation. So, it makes sense to use this as the least common denominator.
If you have your printer settings on your XenApp server set to use native drivers and/or session printer settings, then you must have that same driver on both sides.
ASKER
Sorry for the late feedback.
I found a solution to this, and it was to set the local printer to use the "Generic PostScript Printer Driver" in MAC OSX.
Thanks for your replies.
I found a solution to this, and it was to set the local printer to use the "Generic PostScript Printer Driver" in MAC OSX.
Thanks for your replies.