[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2902
  • Last Modified:

Terminal Server error caused by Spoolsv.exe.

I am getting an error when remote users try to connect to the Terminal Server (Windows 2003 Server). The Terminal Server is setup for as an Applican Server.  After the remote user connects, in most cases, the sppolsv.exe causes an error and hangs.  This causes the whole server to hang and no remote user can print locally and the only solution is to reboot the Terminal Server.

We have also noticed that if the user disables the local printer sharing when connecting to the Terminal Server then the spoolsv.exe no longer causes a fault but then we can no longer print to the local printer which kind of defeats our purposes.  Any idea what is going on?
0
esabet
Asked:
esabet
  • 2
  • 2
  • 2
1 Solution
 
victornegriCommented:
Stop your print spooler on  your server and then look in the spool folder (Printers --> File --> Server Properties --> Advanced to find out the path).

Delete anything in there.

Restart your print spooler.
0
 
stea1micCommented:
You might have a printer driver on the users workstation that is causing the problem.  Can you determine if it is only when a specific user connects, or is it for all users that it kills the spooler?
0
 
esabetAuthor Commented:
victornegri:  How do you stop the print spooler?  I did not stop the print spooler but went to the spooler folder and there was nothing to delete, it was empty.

stea1mic: I personally have no issue when i connect myslef. Mine has never caused the spooler to fault. But i have Vista on my local PC but the other users have Win XP on theirs, could that be the issue?  I am also trying out your theory to see if it is only one user that is causing the problem.  If so then how do i narow it down from there?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
victornegriCommented:
To stop the print spooler: Administrative Tools --> Services --> Stop the "Print Spooler" service.

Are there any errors in your event log?

0
 
stea1micCommented:
Typing "net stop spooler" from a command prompt will also work.  Then "net start spooler" to start it.

You would need to check into the event viewer application log (ususally) to see what errors are cropping up just before the spooler crashes.  You should be able to see what printers it is trying to map for your users.  If it seems like one user keeps crashing it, I would delete all their printers and start adding them back one by one and see when it crashes.  
0
 
esabetAuthor Commented:
Tnak you very much everyone.  We found out that it was one Printer Driver that was causing the issue.  I downloaded the new driver from HP and installed it on the Server and it solved the issue.  Apperantly the older printer was not functioning properly.  

Thanks a million.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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