J
Jim in Cleveland
Guest
I have a number of computers that have recently started getting application
errors when trying to print. The computers are running Windows XP, SP2.
When trying to print, they are getting either "Microsoft Application Error"
or spoolsv.exe Application errors. At first I thought it had something to do
with the print server but some people are getting these errors when printing
to local printers. I cannot try the problem to a particular print queue on
the print server as it is also happening to multiple print queues. In some
instances, the print spooler will stop on the local computer and has to be
restarted. Most errors are generating a 7031 or 7034 event ID on the local
computers. I searched the KB but onhly found KB890642 - print spooler
service stops responding & Event 7031 is logged in Windows 2000 and Windows
Server 2003. I have updated some of the computers to SP3. That has seemed
to help a little. Some people are still getting the errors but the print
spooler is not stopping. The only thing I can think of that has changed
domain-wide is maybe an update from Symantec. Any suggestions?
errors when trying to print. The computers are running Windows XP, SP2.
When trying to print, they are getting either "Microsoft Application Error"
or spoolsv.exe Application errors. At first I thought it had something to do
with the print server but some people are getting these errors when printing
to local printers. I cannot try the problem to a particular print queue on
the print server as it is also happening to multiple print queues. In some
instances, the print spooler will stop on the local computer and has to be
restarted. Most errors are generating a 7031 or 7034 event ID on the local
computers. I searched the KB but onhly found KB890642 - print spooler
service stops responding & Event 7031 is logged in Windows 2000 and Windows
Server 2003. I have updated some of the computers to SP3. That has seemed
to help a little. Some people are still getting the errors but the print
spooler is not stopping. The only thing I can think of that has changed
domain-wide is maybe an update from Symantec. Any suggestions?