I am experiencing a sudden shutdown of QuickBooks Enterprise Solutions Version 12.0 when saving record deposits.
Our QuickBooks is set up in a client-server environment. Clients are Windows 10 Pro and Server is Windows Server 2012. QuickBooks is R16 Updated.
We don't have any issue with Record Deposit on the server side. We have issues on the client side. This issue started on Windows 7 so we updated our windows to Windows 10 Pro hoping that the issue will be resolved but no avail.
These are the thing I already did:
2. Update windows to Windows 10
3. Re-install QuickBooks
4. Update Windows
5. Tried the Server and it okay. No problem at all.
6. Tried in other computers some works some did not work.
There is one client that at least resolved partially through debugging. We need to run the Microsoft Visual Studio 2018 while doing the deposits which is weird. We do not yet how to make it a permanent solution.
I will appreciate any help from your end.
Thanks, BRC for this response. But I disagree to agree with Intuit not supporting Windows 10. I bought that software in 2012 based on the premise that I could use it perpetually or at least in 15 to 20 years. I presumed that it covers updates which what most big software companies do.
It would be unfair to us, buyers, to receive a very convenient response, that Intuit is no longer working due to not supporting the present windows platform. On the other hand, Windows is not selling anymore lower than Windows 10 version or at least Windows 8.
Another thing, this issue started in Windows 7. I did not upgrade until recently because I know Windows 10 at its inception has bugs issue with QuickBooks. But after some time, I was made to believe that they have fixed the issue. So I was hoping that I could resolve the "Record Deposit Sudden Shutdown Issue" by upgrading my computers to Windows 10 will solve the problem.
This is so absurd. Intuit cannot do this to their customer!
Pardon me, but I need to be clarified about this.
Hi there, Ciodensky.
I just want to add to what BRC had previously shared. QuickBooks 2012 is not tested on newer OS because it's an old version, way before Windows 10 was released.
Once a QuickBooks version is discontinued, software and maintenance updates are no longer available. Because of this, the troubleshooting steps may or may not work if you're using QuickBooks on a non-compatible Operating System.
For more details about the Disco policy, please see this article: QuickBooks Desktop service discontinuation (Disco) policy and upgrade information.
You can always reply to this tread if you have follow-up questions. The Community is always here to guide you.
I agree with the Customer, that stopping support for QB 12, is to soon. Windows 10 is supposed to have Windows 7 compatibility. I have been using QB Enterprise 12 since 2012 and started with QB around 1994 without much need for support since then. Even in version 11, I only needed once instance of help when the program would not install from the CD. I really like the program and have spent over $6000 on QB software over the years. I am not ready to spend $2000 a year for the online version. I will use something else instead.
With Windows 7 support to soon end I am force to get QB t o work with Windows 10. MY only pro problem so far in testing is emailing receipt, PO's etc. Some error about PDF files. It works once then gives and error until you close the program ans reopen it. It will then work one more time before it happens again. I have yet to make a deposit but will soon try that too.
I wish I could sell you one of my products then tell you a couple of years later you cannot use it anymore.
Hi there, @etsgary.
I appreciate you for sharing your thoughts and opinion here in the Community. Other applications were built with secure and latest smart updates, because of that, our product keeps up with trends in technology because of added features in QuickBooks.
To learn more about what operating system best works with QuickBooks Desktop, here's an article you can read for reference: System Requirements for QuickBooks 2020 and Enterprise Solutions 20.0.
Then, in case you want to learn how to remove a credit from an invoice, you can refer to this article for the details: Remove or Unapply a Credit from an Invoice or Bill.
As always, keep me posted if you need further assistant. I'm always here to help.
That might solve this problem, but I wold then be stuck with the customer limitation of Pro. That's why I upgrade to Enterprise. I currently have over 17,000 customer entries. I believe Pro maxed out at 3000. I would delete the old customers inactive customers but that would e a real chore in QB. We attempted to do that 10 years ago. As we are National Retailer to businesses our potential is a million or more. I am not willing to pay Intuit some $1800 per year, which is mostly for support, as I have needed little support in the last 25 years. It will probably be the end of QB Enterprise at least for me. The only issue I still have run across with QB 12 and Windows 10 is email sales receipt and PO's. It works one time than you must close the program and open it again. IT will then work one more time. I will just make Outlook signature templates to substitute for the QB templates, lookup the attachments, and enter the person name. Plus, half our business is now from Amazon, so we don't even have to email them. I am going to peruse other complaints of Windows 10 errors with QB to see if they are a problem for me. I am using a test version of my data on a Windows 10 PC before upgrading the work PC's.
I looked into that on the Intuit Site. It shows 14, 500 items. As I already said I have 17,250 custom res, 2400 inventory items, 280 Vendors. 210 chart of account items, plus myriad other items in memorized reports, memorized transactions, payment items, shipping items, and other lists. Plus Pro is still a yearly price structure, albeit with support, but I would be ahead paying once for the product and paying hourly support when I need it. So thanks, but no thanks. I will live with it not emailing PDF files. If I can't I, will look elsewhere.