Urgent!!! Can not print PDF out in Windows Terminal server+Citrix

[_Fei_Xing_]

Hi, All
Please help me on the problem.
System environment:
Server: Windows 2000 Terminal server + SP4 + Citrix MetaFrame FR2
Client: Thin Client +eLux+ICA client.
Adobe Acrabat Reader 5.1.0.9 is installed on the terminal server
A network printer is published in Citrix to all thin client users.

Several users reported that cannot print PDF document out when logon to terminal server through ICA session.
They can print out MS word documents and other office docu but any pdf document.But it is very strange that some users in same domain/site/group, under the same GPO, logon to the same terminal server, can print pdf docu out and can also print out the pdf documents which can not be print out by the first several users.

the problem happens like this: After the user clicked the print button, a file was always created in the same folder which the pdf docu is stored in. and the temp created file's name is the network printer port name. like "IP_172.17.159.203"

I have checked the system log on the print server and also terminal server, no any log recorded for the user's print operation
I guess that in normal case, the temp file created should be sent to print pool and waiting for print, so that log system can record any information occurred during the operation. But for the problem's case, the temp file was failed to be sent to print server's print pool for some reason.

I have tried to ask problem users to logon to the same termianl user through RDP session, but got the same failure.

I have asked the user to delete the old queue and add the new queue with the same setting and tried out, but got the same problem again. No any warning and error message shows up during the print operation.

Please help me if anyone have experience on this. Thank you very much

[_brooska_lowalski_]

We are experiencing the same issue...
System environment:
Server: Windows 2000 Terminal server + SP3 + Citrix MetaFrame FR3
Client: ICA client.
Adobe Acrobat Reader 5.0.5/5.1/6.0 is installed on the terminal server
A network printer is published in AD to all thin client users.

When a user attempts print a pdf that has been loaded from a network share, they get the same temp file written back to the network location (same file name as printer name with no extension) and nothing is spooled to the print queue.

If the user loads a PDF from a local source to the server (within their profile) the job prints correctly. We have tested with different versions of reader and file permissions set to 'everyone' full control across the entire drive with the same result.

Anyone got any ideas?

Regards,

Bruce Low
bruce.low@london.sema.slb.com

[_Fei_Xing_]

Yes, I have got the temporary solution for the problem
1. copy the pdf file to the user's windows desktop, which definitely housed in the user's profile
2. use Internet Explorer to open the PDF file, then print it.
but, there must be something behind.
waiting for experts to track on this issue.

[_vincent_leekl_]

Use 3rd Party software edocprinter at www.iteksoft.com

Hope you can help me to solve the problem I email to you.

Thank you.

vincent.lee@dsm.com

[_Adam_Henning_]

I got mine to work by changing the driver to the PostScript equivilant for my printer.

[_Dycom_Doug_]

Another thread on this site relating to WinXP and printing to network printers led to the following Google Groups thread:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=utOIRoTTCHA.1644%40tkmsftngp13&rnum=4&prev=/groups%3Fq%3Dacrobat%2Bprint%2Bfrom%2Bnetwork%2Bdrive%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3DutOIRoTTCHA.1644%2540tkmsftngp13%26rnum%3D4

Quote:
"Using UNC notation to open the file resolves the problem, as does copying the file to a local drive, then printing it. Adobe Acrobat and text files are affected by this problem. Microsoft word is not."

It turned out to be Win2K SP3 related and Microsoft released a fix either under Win2K SP4 (not on my production Terminal Servers - not in this lifetime) or it was rolled into MS02-070.

http://www.microsoft.com/downloads/details.aspx?FamilyId=52EAC216-A360-4E2D-9C6B-AD4D31C40BA2&displaylang=en

I have tested this fix and it solves the problem for my farm.

[_Jonathan_Jessen_]

Was the product originally installed in a terminal session? I was having the same problem until I reinstalled it from the console!