Print Spooler Error Id 7031
Contents |
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Hello
Print Spooler Service Terminated Unexpectedly 7031
ever since early yesterday the print spooler service has went down periodically event id 7034 print spooler windows 7 a total number of 14 times so far which is causing issues. I have been looking into this issue,
Event 7031 Print Spooler Windows 7
but have yet to find the cause. Server 2008 R2 Anyone have any ideas? Reply Subscribe RELATED TOPICS: Print Spooler Problem Turning Pandemic Why does my print spooler keep stopping? Print print spooler service terminated unexpectedly 7034 Spooler Madness   20 Replies Datil OP Philip5403 Aug 22, 2012 at 10:26 UTC have you check the system logs to see if it generates you an error? 0 Tabasco OP GaryGCS Aug 22, 2012 at 10:26 UTC GCS Technologies is an IT service provider. Did you check the spool directory for any stuck print jobs? Windows\system32\spool\printers. adplus tool If you see any files with a date and time stamp from more than a few minutes old, try deleting those files, restarting the print spooler, and see if it stops crashing. 0 Chipotle OP bsumorgan Aug 22, 2012 at 10:27 UTC Check the logs and look over your print drivers. I find it's usually a crappy HP driver that does it for me. 0 Cayenne OP MattsSonicScrewDriver Aug 22, 2012 at 10:30 UTC Serenity Solutions Ltd is an IT service provider. +1 for HP Drivers. I had a few small HP1000 series for some execs. It was a very common problem. 0 Datil OP Philip5403 Aug 22, 2012 at 10:31 UTC and if you still have no luck resolving: Go to Start / Run and type in "services.msc" without quotation marks, then press Enter or click OK. In the window that opens (Services) look for "Print Spooler" on the right Right-click "Print Spooler" and select "Properties". Click on the "Recovery" tab and change all 3 drop-down boxes to "Restart The Service". Make sure the 2 tex
when ever he rebooted or even tried to open up the Windows XP printers screen he would get a message that
Event Id 7034 Print Spooler Server 2012
"The Print Spooler service terminated unexpectedly." If I looked in the Windows event id 7031 the print spooler service terminated unexpectedly services applet the Print Spooler service was stopped. If I tried to start it, it would start but as
Event Id 7034 Print Spooler Windows 10
soon as I tried to look at the installed printers or try to print from any application it would give me the same error again. In the Windows Event log I found https://community.spiceworks.com/topic/252754-print-spooler-constantly-stopping many Event ID 7031 errors.I did come across a windows kb article that sounded somewhat similar but it didn't help in my case.The solution I found was fairly simple:First I needed to stop the spooler service (which was already stopped and would not start ayway)Second I opened up a Windows Explorer window and browsed to C:\WINDOWS\System32\spool\PRINTERS. I simply deleted all the files in this http://itfixed.blogspot.com/2009/11/it-fixed-it-for-me-event-id-7031-source.html folder.Once this was done I could start the print spooler service and everything worked again.This worked for me on a Windows XP pro machine so I am not sure if it will work for Windows Vista or Windows 7. If anyone tries this on those operating systems please let me know if it worked by posting a comment. Apparently it had to do with an application that sent a print job to the spooler that got corrupted or was not in the correct format. As usual this may not be the only way to remove the software but "It Fixed It for me"For more ItFixed It for Me articles please click here. Posted by Scott Mckeown at 2:44 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Itfixed it for me, Microsoft Windows 2 comments: Anandhan said... Thanks Scott!That fixed for me in a Win2003 Citrix Box. June 9, 2010 at 11:58 AM Anonymous said... it worked for win7 thanks October 2, 2012 at 4:56 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Facebook It Fixed by mcgraphix Inc Google+ Badge Abou
Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: https://www.windowsbbs.com/threads/spooler-error-event-id-7031.37799/ Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... WindowsBBS Forums > Operating Systems > Windows XP > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. You are print spooler viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations. Cookies Registration Notice Spooler error event id: 7031 Discussion in 'Windows XP' started by snhnic, 2004/11/22. Thread Status: Not open for further replies. 2004/11/22 snhnic Inactive Thread Starter Joined: 2004/11/22 Messages: 10 Likes Received: print spooler service 0 Trophy Points: 76 Computer Experience: Intermediate Edit note: split this from the thread Here so you can see details of what the user tried by clicking on that link. I put this into a thread of it's own because the problems don't appear identical. Different event log errors. Newt Got the same question did alle the above mentioned things, but no luck! It is driving me nuts! Please help. What esle can be the problem? ===== Date: 22-nov-04 Source: Service Control Manager Time: 4:40:35 PM Category: none Type: Error Event ID:7031 User: N/A Computer: me The Print Spooler service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ============== Also I deleted all my printers with Cleanspl.exe: (Spooler Cleaner). No luck with that to. Then I thought of doing a selective startup but with almost nothing running still the same results,