Print Spooler Terminating. Event ID 7031

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This is my event log message:

The Print Spooler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

I have Win2k ADV SRVR with Service pack 4. I saw a patch for this if you are running Windows 2000 SP3 and said that SP4 should fix it. Well it hasn't.... is there another patch?

Please help
Mark
 
The service pack is one possible solution but if it
hasn't worked try looking at your drivers. If there is
are a large number you may want to remove the unused
ones. The more drivers on a server the less stable it
becomes. Also, if you are using three different drivers
for the same model of printer, find the one that works
best and use it for all printers of that model (remove
the others). This will increase server stability and
reduce the likelyhood of corrupt drivers getting into the
mix.
-----Original Message-----
This is my event log message:

The Print Spooler service terminated unexpectedly. It
Click to expand...
has done this 1 time(s). The following corrective action
will be taken in 0 milliseconds: No action.
I have Win2k ADV SRVR with Service pack 4. I saw a
Click to expand...
patch for this if you are running Windows 2000 SP3 and
said that SP4 should fix it. Well it hasn't.... is there
another patch?
 
The service pack is one possible solution but if it
hasn't worked try looking at your drivers. If there is
are a large number you may want to remove the unused
ones. The more drivers on a server the less stable it
becomes. Also, if you are using three different drivers
for the same model of printer, find the one that works
best and use it for all printers of that model (remove
the others). This will increase server stability and
reduce the likelyhood of corrupt drivers getting into the
mix.
Click to expand...

Could you possibly explain better what you mean and how this would
make the spooler unstable. I have exactly the same problem, as others
seem to. If you go into the server properties and select drivers
there is one driver file defined for each printer. I don't understand
why having multiple drivers on your machine will cause problems
because the printer properties is defined for only one specific file.
I keep hoping MS will come up with a fix for this but so far I have
seen nothing from them.

Thanks,

Hal
 
Back
Top