TAXMAN Posted February 17, 2021 Report Posted February 17, 2021 I have gotten this error about 5 times today. Program has encountered an error and needs to close. My co worker said he got it 3 times today. Any one have an idea what is going on? Quote
Pacun Posted February 18, 2021 Report Posted February 18, 2021 I got it a couple of times today. I have 16Gigs of ram and Solid State hard drive. It must be that the computer is running out of resources because it happens after I have opened and closed a couple of years and several 1040 returns. Quote
TAXMAN Posted February 18, 2021 Author Report Posted February 18, 2021 I have a similar setup but I only had 2019 and 2020 open. Close most everything else when working on returns. Quote
Randall Posted February 18, 2021 Report Posted February 18, 2021 I haven't gotten this in awhile. Usually with a big print job. Recently someone suggested stop and start the print spooler. I did and haven't had this message since. I also have a new printer. I don't know if that it or what. Quote
Abby Normal Posted February 18, 2021 Report Posted February 18, 2021 I got that message a couple times earlier this year but not recently. I just ignore it and keep working. 2 Quote
HV Ken Posted February 18, 2021 Report Posted February 18, 2021 I am seeing this more this year than in years past. I always have the Task Manager up to give me an idea of when I need to close the program to free up the memory issues inherent in ATX's lazy programming practices. Whatever you do, don't click on CLOST PROGRAM. This will cause you to lose any unsaved work. Instead, "X" the error window, save your changes, then close the program as you normally would. 1 Quote
Randall Posted February 18, 2021 Report Posted February 18, 2021 I've seen it in past years more. It's usually in big print jobs (lots of forms). I saw it earlier this year but not since doing the print spooler start and stop. Maybe later as my ATX files grow but so far so good. Quote
grandmabee Posted February 18, 2021 Report Posted February 18, 2021 3 minutes ago, Randall said: I've seen it in past years more. It's usually in big print jobs (lots of forms). I saw it earlier this year but not since doing the print spooler start and stop. Maybe later as my ATX files grow but so far so good. How do you "stop the print spooler" ? Quote
Pacun Posted February 19, 2021 Report Posted February 19, 2021 net stop spooler from CMD as admin. net start spooler to put it back in action. 1 Quote
Pacun Posted February 19, 2021 Report Posted February 19, 2021 I usually change printer on ATX and continue working and printing. Today, I couldn't print, so I click OK to the printing error and I printed a single pay. It went through, so I thought the issue was over. I sent the big print job and this time ATX crashed. So, maybe the issue is not ATX but the printer. Blaming the printer makes sense because this is issue is not widespread. I am using M670 HP print, I THINK. 1 Quote
BobbyCPA Posted February 19, 2021 Report Posted February 19, 2021 5 hours ago, HV Ken said: I am seeing this more this year than in years past. I always have the Task Manager up to give me an idea of when I need to close the program to free up the memory issues inherent in ATX's lazy programming practices. Whatever you do, don't click on CLOST PROGRAM. This will cause you to lose any unsaved work. Instead, "X" the error window, save your changes, then close the program as you normally would. I've been doing the same: "X" the error window, save the tax return, close ATX, restart ATX. Clicking OK on the error window prevented ATX from restarting until I rebooted my computer. 1 Quote
Slippery Pencil Posted February 19, 2021 Report Posted February 19, 2021 It's a new feature they implemented 4 or 5 years ago. I think they felt they needed to add something to compensate for the excessive price increase each year. Quote
Randall Posted February 19, 2021 Report Posted February 19, 2021 13 hours ago, grandmabee said: How do you "stop the print spooler" ? Someone suggested it in an earlier post. Type Services in MS search box. Page down to Print Spooler. Right click and click on stop. Repeat and click on start the 2nd time. I also got a new printer, HP Neverstop 100 (with a new computer). A small end printer. I don't know which one actually helped. The verdict is still out as I do more returns. 2 1 Quote
Abby Normal Posted February 19, 2021 Report Posted February 19, 2021 15 hours ago, Pacun said: net stop spooler from CMD as admin. net start spooler to put it back in action. You could put this in a bat file and put a shortcut to it on your desktop. Or even this more complete version that clears the cache too: You can clear the print queue using commands like this. Select Start. Type Command. Right-click “Command Prompt” and select “Run as administrator“. Type net stop spooler then press “Enter“. Type del %systemroot%\System32\spool\printers\* /Q then press “Enter“. Type net start spooler then press “Enter“. I found a batch file you can download: https://www.tenforums.com/tutorials/90615-reset-clear-print-spooler-windows-10-a.html 1 Quote
Randall Posted February 19, 2021 Report Posted February 19, 2021 It seems easier to just go straight to 'Services' Quote
Pacun Posted February 19, 2021 Report Posted February 19, 2021 35 minutes ago, Randall said: It seems easier to just go straight to 'Services' Abby's suggestion also include deletion of any print jobs that might interfere. 1 Quote
Abby Normal Posted February 19, 2021 Report Posted February 19, 2021 1 hour ago, Pacun said: Abby's suggestion also include deletion of any print jobs that might interfere. Correct. It clears the print queue in addition to restarting the spooler service. Quote
Randall Posted February 20, 2021 Report Posted February 20, 2021 15 hours ago, Abby Normal said: Correct. It clears the print queue in addition to restarting the spooler service. I usually just do one thing at a time. That is print job. Is there anything in the print queue when I do this? Something behind the scenes so to speak? Quote
jklcpa Posted February 20, 2021 Report Posted February 20, 2021 This discussion comes up often enough that I copied the instructions for solving this error and put it in "Tips, Tricks and Workaround" that is part of the pinned topics at the top of General Chat. That is why the old (linked) topic was revived and appears in the list of current topics. Quote
Jack from Ohio Posted February 24, 2021 Report Posted February 24, 2021 Just reboot your computer every 3-4 hours. ATX programmers ARE lazy. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.