QuickBooks 2017 R5 Problems
Update: R5 Problem Resolved
Originally found on Accountexnetwork.com | Written by
I’m seeing reports of QuickBooks 2017 R5 problems that occur if you are using certain kinds of QuickBooks add-on programs. Poor performance and even QuickBooks crashes. If you are using any QuickBooks add-on product I recommend that you don’t install the QuickBooks 2017 R5 update at this time, until Intuit resolves the problem.
QuickBooks 2017 R5
Intuit released the QuickBooks 2017 R5 update last month, and it has one big change and several small corrections. Most changes were minor bug fixes and spelling corrections. The main change, however, is the update to the security update that modifies how password management works, allowing you to stay “logged in” for a specific period of time without having to reenter your password. This is the same update that Intuit included in QuickBooks 2015 R13 and QuickBooks 2016 R10 (see details in this article).
QuickBooks 2017 R5 Crashes and Slowdowns
If you are using a QuickBooks add-on product then you might see this problem. What I’m seeing reported is that performance of the QuickBooks add-on product gets slower and slower, as the data flow from the QuickBooks database slows down. Eventually QuickBooks itself will crash (several different error messages have been reported).
This doesn’t affect all QuickBooks add-on products. It isn’t clear what exact activity triggers this, although there are some clues. Each of the products that has reported this problem, as far as I’ve seen it, is one that is used to access large volumes of transaction data. There is a generic Transaction Query that many database tools use, and this might be the common thread, although it is too early to tell. I’ve tested my own QuickBooks SDK products and they don’t run into this problem, but my products aren’t using this kind of transaction query.
FLEXquarters is reporting issues with the QODBC driver, which many people use to access data from QuickBooks desktop (see this support article).
Clearify also is reporting similar issues with their very popular QQube reporting tool.
I see reports that this also is a problem with Synergration’s tools that extract data from QuickBooks, but I haven’t confirmed that this is a 2017 R5 issue (but I suspect that it is).
This is not the fault of the add-on developers, this is an issue on the QuickBooks side of things.
What Can You Do?
At this point, if you have not updated to QuickBooks 2017 R5, I would definitely hold off updating.
If you have already updated, you have two options.
Roll back to 2017 R4, which can be complicated. You have to uninstall what you have, and locate the install files that can update you to 2017 R4. You will have to talk to Intuit support for help with this (or a very knowledgeable QuickBooks ProAdvisor).
Wait for Intuit to issue an update that fixes this. I know that they are aware of the problem, but they have to pin down what the error is and come up with a fix that doesn’t create additional problems. It is hard to say how long that might take.