The QuickBooks 2014 R6 update was released to manual update on June 12, and as I described in this article, it fixed a lot of problems. Unfortunately, we are finding that it also introduced some new problems.
7/3/2014: Intuit has released QuickBooks 2014 R7 to address some of the problems outlined in this article. Information on this can be found in my article at https://www.accountexnetwork.com/blog/2014/07/quickbooks-2014-r7/
This article was updated on 6/20/2014, 6/23/2014, 6/26/2014 and 7/7/2014 as we learned more about the issues.
Intuit typically releases an update like this as a manual update first, where you have to go to the Intuit support site and manually download a patch file. A week later, the update switches to an automatic update, where it is pushed out to users automatically if they have enabled this feature. I usually recommend waiting to update until we see if there are errors that the manual updaters report. Unfortunately, this time, it was not apparent that there were problems until the first wave of automatic updates were installed.
In any release, we expect that some people will see problems because there are so many variables involved. Different operating systems, different versions that you are updating from, different levels of “health” of the database being installed, different versions of Microsoft Office installed, and many variables in the “Windows registry” that can affect things. I tend to avoid writing about these kinds of bugs unless I can see them in my test system, and we see that they are widespread.
There are a number of reports of problems in the R6 update. Here are the ones I am seeing most commonly reported, and that I have run into myself on one of my test systems. I am just sorry that these did not show up before the automatic update phase.
QuickBooks Has Stopped Working
Ouch. In some cases people are seeing an error “QuickBooks has stopped working” when you open your company file. I am not seeing this happen consistently. Of three installations, only one shows this problem. Intuit acknowledges that this is happening in KB article SLN86691.
Intuit lists three steps to resolve the problem: Reboot your computer. If you are using an Intuit payroll product, rename the Paysub.ini file and download your payroll update again (the KB article provides a batch file to help with the renaming). Perform a “clean install” of 2014 R6 if the first two steps do not work.
My one test system that failed had a test payroll subscription, the ones that did not fail did not. The Intuit process seems to have resolved the problem for me.
Update late on 6/20: Intuit has created an off-cycle update, which is kind of a stealth background update, that should fix this particular issue. KB article SLN86691 has been updated to show this, and describes how to ensure that you get the update.
Names Truncated in Reports
Here’s my Unpaid Bills Detail Report when viewed on screen (Figure 1).
Figure 1: Unpaid Bills Detail – On Screen and Correct
Figure 2 is the same report printed; note the truncation of the vendor name. Just one of them is truncated in this case, but some people report that it is more widespread.
Figure 2: Unpaid Bills Detail – Error
This problem may be showing up in other reports, such as the Unbilled Time report, perhaps in the Inventory Stock Status by Item report.
I missed this early on because I was always looking at the screen, where it shows correctly.
QBSDK-Based Add-ons Fail
I develop some add-on products that work with QuickBooks, and I knew there was a problem when I started getting a number of tech support calls for my products later in the day when the automatic update was released. If you are running Windows XP then you will get one of several odd errors if you are using an add-on product that uses the QBSDK (which most apps are using for QuickBooks on Windows).
In some cases you may get a Windows error dialog like the one shown in Figure 3:
Figure 3: Add-on Error
In other cases, your add-on application may generate an error about a “missing component.” The problem is that every add-on product will probably show you a different error, as they try to interpret what QuickBooks is telling them. This will happen when the add-on tries to connect to the QuickBooks database.
I do have a fix for this one, but you have to be cautious. If you can find an R5 installation, you can locate the QBXMLRP2.dll file (usually in C:\Program Files\Common File\Intuit\QuickBooks, or C:\Program Files (x86)\Common File\Intuit\QuickBooks on 64-bit systems) and copy that over to your R6 installation; that seems to fix the problem. I have tested this on my system and it resolves that problem, but I am not sure what side effects it will cause. So far I have not seen any problems, but note that this might remove the SDK bug fixes that were included in the 2014 R6 update (as I describe in my 2014 R6 article).
The good DLL has a file version of 184.108.40.20605, the bad one has a file version of 220.127.116.1106 (Figure 4).
Figure 4: 2014 R5 DLL
There may be other problems, but I have not been able to duplicate any of those that I see reported.
- If you are running on Windows XP and using an add-on, consider trying this fix. However, a better answer is that you should not be running on Windows XP due to the security issues and loss of PCI compliance (see this article).
- If you are running on any 2014 version earlier than R6, you might want to wait on updating until we see what the full extent of the problem is.
- If you have already moved to 2014 R6, please let Intuit know about the problems using the Send Feedback Online option in your Help menu. The more they hear about this, the faster they should respond.
I have no idea if they are working on a fix for any of these at this time. Update late on 6/20/2014: Intuit says that they are working on these issues and hope to have a fix soon. Update 7/3/2014 – 2014 R7 has been released, which addresses some of these issues. See https://www.accountexnetwork.com/blog/2014/07/quickbooks-2014-r7/
This is an “evolving story” as more info comes out about this problem. Here are some updates added after the article was initially posted.
- Intuit pulled the R6 automatic and manual patches from distribution the morning of June 20. The full product download still includes the R6 information because some people need it to fix these problems: SLN86334 (crashing when working with Bank Feeds); SLN76905 (crashing with emailing/mailing invoices through QuickBooks Billing Solutions or Webmail); and SLN77622 (unexpected crashes due to various causes).
- Another error, again only on Windows XP, the Record Deposit option for Merchant Services may not work correctly. I have not run into this myself, but I have confirmation that it is an issue with R6.
The longer we look at this release, the more problems we hear about. There are a lot of errors that people are trying to attribute to R6 – I can’t confirm many of them as I don’t see all these problems on any of my test systems. I suspect some of the problems that people report after upgrading to R6 might not be new problems due to R6, but problems that have been around for awhile that just happen to be showing up at this time.
At this time (6/26/2014) we still don’t have a “fix” for the 2014 R6 problem other than to roll back to R5. Intuit has added links to installers for R5 in KB article SLN86786. They are working on a comprehensive fix, but it isn’t ready yet. I’m happy if they take time to work on this and get the errors all resolved.
Here are some additional KB articles from Intuit that relate to R6 (on top of the ones I’ve already listed above):
- Errors with SDK Apps, Accountants Copy File Transfer or QuickBooks Statement Writer: SLN86786 (they recommend moving back to R5 and provide links for the installers).
- Subitems missing from reports: SLN86719
- Fuzzy or blurry logos when emailing, saving or printing transactions like logos: SLN86785
- Report section headers are truncated: SLN86630
Intuit releases QuickBooks 2014 R7 to address some of these issues. See: https://www.accountexnetwork.com/blog/2014/07/quickbooks-2014-r7/
There is still a confirmed problem with both the R6 and R7 release – The message “QuickBooks needs to update your company file” loops over an over when you open your company file or switch between single and multi user mode. Intuit KB article SLN86901.