Yes No Can you tell us more? Ask a Question Recent Comments PK: Hover your mouse on the code and on the ride side you will see an icon of + sign... This includes messed up 'drivers' for PDF or XPS etc. –Brian Oct 10 '12 at 11:34 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote First more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed news
To configure the logging options, open the Printers applet on the server from within Control Panel. Reply eowin August 6, 2013 at 3:14 pm I followed the fix it myself manually, but it didn´t work. It should look something like this: takeown /f C:\windows\system32\oldfile. Press Apply in the lower right to save your changes. 4 Change the recovery options.
Did this article help you? However rebooted your machine and yes it showed up. asked 3 years ago viewed 27160 times active 3 years ago Blog Stack Overflow Podcast #93 - A Very Spolsky Halloween Special Related 5Logging and Reporting on W2k3 print server printing3Windows
Find this file on another computer with the same version of Windows, and transfer it to yours. Here's how to replace the corrupted file with a new one: In Command Prompt, type takeown /f followed by a space and the exact path and file name of the corrupt Transfer the new file by entering copy (path to new file) (path to corrupt file), replacing the words in parentheses with the correct paths and file names. Enable Print Spooler Logging Windows 2008 Click on Change Permission.
Right-click the icon for the printer that's failing to print. Print Spooler Log Windows 7 Reply Grace August 15, 2013 at 7:41 pm Thanks, it worked for me Reply James August 14, 2013 at 6:42 pm Thank you so much, your tool was awesome, it has Usually this type of error is estimated to occur due to a virus infection or other malicious interference. http://answers.microsoft.com/en-us/windows/forum/windows_7-security/about-log-spooler-information/9bd4203c-9882-41b2-b1be-0af3f9b67222 You may need to try more than one method to fix the spooler.
Your solution excellent!! Print Spooler Log Server 2012 After this fix your problem will be solved, Your spooler will be repaired automatically, and get start working again, it will restore the spooler service as per default stage, which they Though it is nice to see what jobs printed and when to help you track down missing stuff. 7 years ago Reply Egon On Windows 7 this seems not to work… Sadly, explaining how to use it to analyze a problem such as this one is far outside of the scope of this answer.
Create an account EXPLORE Community DashboardRandom ArticleAbout UsCategoriesRecent Changes HELP US Write an ArticleRequest a New ArticleAnswer a RequestMore Ideas... read this article Group list elements using second list When I added a resistor to a set of christmas lights where I cut off bulbs, it gets hot. Log Spooler Information Events Server 2012 This can be exceptionally useful in tracking down where print jobs are deleted, especially if you haven’t tightened security on your print queues. Print Spooler Event Log Method 3 Scanning System Files 1 Restart your computer in Safe Mode.
You saved me. 🙂 Reply micheal May 7, 2013 at 2:16 am Yes it's Fixed after alot of researching, your tool fixed it in few seconds. navigate to this website Techexpert: Your're welcome! Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Thanks so much. Enable Print Logging Server 2008
Reply Akam September 30, 2016 at 3:47 pm Works Great, Thanks for this great Tool (Fixing Windows Print Spooler) Reply Ann Onymous August 17, 2016 at 4:52 pm Excellent tool! Community Q&A Ask a Question Submit Already answered Not a question Bad question Other If this question (or a similar one) is answered twice in this section, please click here to Reply SM May 28, 2015 at 4:34 pm The autofix works but the problem re-occurs after I turn off the computer entirely (not a reboot). http://introbuilder.net/print-spooler/windows-spooler-error.php Rinse and repeat.
It immediately resolved the issue. Printer Logs Windows Server 2008 R2 Reply Ray W March 17, 2015 at 5:42 pm Worked like a charm for that 1053 error code! Glad to know that our tool worked fo...
and great work Reply Ava September 3, 2013 at 5:37 pm Finally i got your page and got the solution of my spooler issue, I wanted to install my new printer There are a lot of folders in there and the screenshots don't show where this option is located. –William W Nov 19 '15 at 23:56 add a comment| Your Answer windows-7 troubleshooting printing print-spooler share|improve this question edited Oct 10 '12 at 11:52 Oliver Salzburg♦ 56.5k37186245 asked Oct 10 '12 at 11:26 Miles Hayler 1091318 1 If you installed and Enable Print Logging Windows 7 Your printer software may be corrupted.
Click on Add Button Type Everyone, then click on OK, and then check mark all the boxes of allow row, then click on OK Click on OK to finish that. Right-click each driver used by that printer, and select "Delete" to uninstall it. (You will not be able to uninstall it if another printer is using it.) Alternatively, right-click the driver Write an Article 184 × Home Products ► Products◄ Overview PaperCut NG ► PaperCut NG ◄ Overview Download Free Trial PaperCut NG Pricing Get a Quote Online Buy PaperCut NG Latest http://introbuilder.net/print-spooler/windows-vista-spooler-error.php Change the settings to match the following: First failure: Restart the Service Second failure: Restart the Service Subsequent failures: Take No Action Reset fail count after: 1 days Restart service after:
A few adjustments will maximize the chance of the spooler solving its own issues, and minimize the chance of it causing a crash. Then I went to services page to start the print spooler service manually, now I got a another error message "Windows could not start the Print spooler service on Local Computer I have set the service to restart on all subsequent failures, but it still drops out after 2 minutes, restarts after 1 minute, then crashes again after a further 2 minutes.