Link to home
Start Free TrialLog in
Avatar of dankyle67
dankyle67

asked on

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.
Avatar of dankyle67
dankyle67

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
Avatar of Nick67
<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.
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?
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?
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
Avatar of Nick67
Nick67
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.