asked on 10/3/2011

print spooler in remote desktop

Hi,
past few weeks users have been trying to print through remote desktop and jobs dont print at all but when we stop and start the print spooler on the win 2003 server, the jobs push through. I looked at event viewer under system but just warnings about driver for certain printers might not be correct. Wondering how i would isolate what is causing this and why we would have to keep restarting print spooler. thanks.

Remote Access Printers and Scanners

Last Comment

dankyle67

10/4/2011

dankyle67

10/3/2011

ASKER

In addition, just noticed while checking application event log that it referenced event id 1000 "Faulting application spoolsv.exe version 5.2.3790.4759" hope this helps

Nick67

10/3/2011

<event id 1000 "Faulting application spoolsv.exe version 5.2.3790.4759">
The print spooler is crashing.
1. Check the spool service settings. Make sure it will continue to try to restart on all crashes, not just 1st and 2nd
2. Experiment with different remote clients. There is a bad print driver somewhere, crashing the spooler. Try to isolate which client has it. Remove that printer or replace that driver.
3. Make sure that the server DOES have the necessary drivers for all the clients.

dankyle67

10/3/2011

ASKER

Yes will adjust settings in spooler as you instructed. In the past i remember if i had a printer being used in remote desktop that didnt work properly or at all, i could resolve it by installing the correct driver which would be the win2003 server driver on that server and then i would have to make a mapping in the term server file which gives mapping to correct name of printer. For example if driver is called hplaserjet5a then would have to explicitly map this exact name to driver that is installed in 2003 server which might be called hplaserjet5b so that server knows which driver to use. I'm hoping to isolate the printer that is crashing and then install the correct driver as you mentioned. Does this sound right?

Nick67

10/3/2011

Sounds like it
Check the event logs and see if the print spooler crash co-incides with just one client's login
Has anybody installed a new printer on a client since this problem cropped up?

dankyle67

10/3/2011

ASKER

sounds good, i can see the spool crashes in application log of event viewer but where would i go to see which remote user just logged in prior to that approximate time? Will also check on any new printer installs within past month since it started happening 4weeks ago they said.

ASKER CERTIFIED SOLUTION

Nick67

10/3/2011

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

dankyle67

10/4/2011

ASKER

great, will try these all out and let you know. They mentioned that they were trying to print to a color printer that they hadnt tried before so most likely this is the one. Once its identified as the problem printer then i can just install correct driver and hopefully wont crash going forward.