|
|
| goalie13 2003-09-03, 6:22 pm |
| I have a Citrix server (FR3) that I need to print from a published app. I have imported our print server and it shows up in the management console. Everything was working fine until today. The print job was sent to the print spooler and then locked up the print que. Both the Citrix generated printer and the print spooler on the Print sever were locked up. I was unable to clear either printer of the job.
As I said, it workred fine until today. I hope i have made myself clear. Thanks in Advance.
Matt | |
| dok klene 2003-09-04, 6:26 am |
| Go into the printer and delete all the jobs after the first one. Those jobs should delete without a problem. Now delete the first job. It probably will not delete. Now go to services and start and stop the print spooler service. Now your printers should work again.
The printer that caused the problem, what driver was it using? Was it a Lexmark or was it using Citrix's UPD? | |
| goalie13 2003-09-05, 9:32 am |
| Thanks for your reply. Sorry it took so long for me to get back to this thread.
I had already done what you suggested as far as deleting all the print jobs and you were right on target as far as the print jobs. I did stop the print spooler but when I went to restart it, the service refused to start up again.
I ended up rebooting the server and this finally cleared the metafile print job. The spooler restarted on reboot.
I have the actual print drivers installed on the Citrix box in the management console/printers menu item but it keeps defaulting to the UPD. I know I can check off to only use the printer's native driver, but I don't think that's the problem.
I appreciate any advice you can give. Thanks in advance.
Matt | |
| dok klene 2003-09-05, 4:57 pm |
| I try to avoid using the UPD because of what you listed above.
quote:
I have the actual print drivers installed on the Citrix box in the management console/printers menu item but it keeps defaulting to the UPD. I know I can check off to only use the printer's native driver, but I don't think that's the problem.
There are a couple of reasons why it could be using the UPD instead of the Native Drivers.
1. In the CMC, right click on printer management and select properties. Make sure "Use universal driver only if native driver is unavailable" is selected
2. If you are using a win9x client make sure that the printer driver name matches the printer driver name on the server. If the names don't match, the server thinks that it does not have the proper driver and switches to the UPD.
The only time I use the UPD, is for the road warriors who are connecting from different locations regularly.
Hope this helps. | |
| goalie13 2003-09-05, 6:47 pm |
| Thanks for your reply. I do have a question for you though. I need my Mac clients to be able to print from these same HP LaserJets as my W2K clients. If I check that box in the CMC, will it affect printing from my Mac clients? I suppose I could try it, but this is a production environment. Thanks again for your suggestions! | |
| dok klene 2003-09-07, 9:36 pm |
| I don't have any experience with Macs, so I can't give you a definite answer. What should happen is that first the server will try to match the drivers and if it can't it will then default to the UPD. | |
| goalie13 2003-09-08, 7:11 pm |
| Thanks for all your help. When (or if) I test the driver issue with thew Macs, I'll give you a heads up about it's performance.
Thanks again! |
|
|
|