Local Citrix Print Jobs are getting stuck!

[Candidog]

I have handful of users that have thier local printer mapped on my Citrix server. I'm having issues with the printers. The autocreation of the local printer works fine but at times when a user who's printer has been mapped by Citrix has issues. The user will complain that they can't print. When I look at the print queue the job get stuck in it. I try to delete the jobs or purge all the jobs and then the user is back in business. Sometimes the only way for me to purge or delete the jobs is to reboot the server. This is becoming annoying issue. Are these local printers just too unreliable for Citrix? How does everyone else handle this issue?

Any ideas or tips are welcomed....

Greg

 

[lb63640]

You don't have to reboot the server. You can stop and then restart the print spooler services and achieve the same effect of freeing up those stuck print jobs.

 

[Candidog]

I realize that but why are they getting stuck!

Greg

 

[mattjurado]

What print options do you have checked in the Citrix MMC?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[Candidog]

I have a Citrix Policy that allows printers to be connected at logon. The rule is actually not configured by default.

Then under printers and drivers, I have all my printers my users use.

Is this information what your looking for?

Greg

 

[DarraghFitzpatrick]

Greg

do you have the same version of each printers driver installed on both the server and the client ?

Also what version of citrix are you running ? What service pack and Feature release ?

Darragh

 

[Candidog]

They are not the same version because my client is a Windows 98 machine and my Terminal Server is Windows 2003. I'm using MF-XP with FR3. I'm trying it now with a universal driver ONLY. Hopefully this helps...do you agree?

Greg

 

[SomeCitrixGuy]

Are you using Citrix XP or 3.0?

This sounds like a print subsystem problem.
If you stop and start the print service does it clear up?

I avoided some issues by flushing all print jobs to a dedicated print server. That way the subsystem does not get overwhelmed while spooling print back to the requester.
Something to consider.