• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 854
  • Last Modified:

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.
0
dankyle67
Asked:
dankyle67
  • 4
  • 3
1 Solution
 
dankyle67Author Commented:
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
0
 
Nick67Commented:
<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.
0
 
dankyle67Author Commented:
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?
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
Nick67Commented:
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?
0
 
dankyle67Author Commented:
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.
0
 
Nick67Commented:
Usually you wind up a bunch of eventID 3, 4 and 8 when any given client logs off.
You can also turn on auditing for log on and log off events.
That should help you bracket when the spooler is crashing, and what machine had loggged on.
The Events also pick up the names other printers, so you can give the suspected printers distinctive names and see if they appear in the log
0
 
dankyle67Author Commented:
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.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now