i just bought Quickbooks 2013 Pro and I am already getting error messages ever since I installed it 4 days ago. QB32.EXE Fatal Application Exit. Quickbooks is now terminating. Have been entering all my customers and info and this error message comes up and terminates program about every 20 minutes. What is causing this and how can I fix it? Brand new computer also with Windows 7. I was using Peachtree but decided to switch to QuickBooks.
Thank you for the responses. I have tried them all and have all the updates but it is still aborting. Brand new computer and Quick Books 2013. Very frustrating.
I am also having this problem. Everything else on my computer is perfect. I subscript to Pro Plus, so I've spent hours on the phone with tech support (in India) trying to solve the problem. The technicians are friendly, but seem to alway read from a script. Most are NOT capable of listening and understanding the problem. I explain the problem ten times and they still answer in a way that shows that they don't understand what I'm describing. They have re-installed, repaired my file, etc, etc, all without any success. My QB still crashes multiple times daily. I was told that I should close all other programs when using Quickbooks. That is not how I work, so it is not an option. I wish that they could have been up front with me and told me that this is a known issue and QB is working on solving the problem. Hiding the issue forced me to spend my hours wasting my time.
Do you use Merchant Services or Online billing? If so, try this article:
Edit: This might help also:
Also, make sure you have the R3 update downloaded.
Does this Fatal Error (which I'm currently experiencing as well) occur when you are doing invoices or bill generally? I found in 2012 that Quickbooks Pro would crash if you have the "History Bar" open on the right side of then invoices and bills screens.
For some reason loading the older transactions, payments, etc. would cause Quickbooks to crash about 5 - 10% of the time. When I closed the window, by using the little arrow at the top, the crashes seemed to go away.
I bet that whatever caused that problem, which was never fixed, has somehow made its way into the code of Quickbooks 2013. I have a very simple Windows 7 network with (3) computers sharing from a central server. Hope this fixes your problem.
Michelle Long CPA
, International QB TrainerAllStar
Go to www.quickbooks.com/support and download & install the R5 update -- it fixes several problems.
Please click solved or ask more questions.
We expreienced a similar error but with QBW Enterprise 13 - This was caused by a known issue and will be experienced with users connecting via terminal server or using a remote application of QBW. The error was actually making the server go blue-screen.
The cause was related to the system file RDPWD.sys file being outdated. It is not outdated and most likely will never casue an issue until you install and try to run QBW Ent. 13.0
There is a hotfix for the file depending upon your machine - Updating to even R5 with QBW 13.0 will not fix the issue until you run the hotfix. Something in QBW 13.0 does not play well with this file and Server 2008.
Hi everyone, please see this article to sign up to be notified when this issue will be resolved.
It appears that the "March 2013 - R6 Update" for QuickBooks 2013 was released today (http://support.intuit.ca/quickbooks/en-ca/iq/Update-QuickBooks/QuickBooks-2013-Update/HOW19716.html)
Any word if this resolves the sporadic "Aborting Application: QuickBooks is now terminating" crashes? The R6 release notes are pretty weak...
People come to Small Business Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:
- Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
- Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
- Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
- Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
- Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.