QuickBooks 2009 Release R6
Just a quick note. Intuit released the R6 update of QuickBooks 2009 today, with little advance notice. There are only two fixes listed for this release:
- If your company file is located in certain locations (some network locations, the root folder of a drive) you would get an error (-6177, 0) when trying to open it. This wasn’t a common problem, and if you ran into it you should have already found that you could move the file to a different location.
- In some cases a sales order would be marked as closed when you used group items or items with different units of measure. If you ran into this problem it was a major hassle, so I’m glad to see that they fixed this.
If you have had either of these problems, OR if you work with sales orders and group items (or multiple units of measure) then you should install this update soon. If you don’t have these problems, you can wait to do the update at a convenient time. I should note that I have only used this update for a couple of days – I’ve not seen any new problems introduced, but that isn’t a guarantee. By this stage in their development cycle I don’t expect new major problems to be introduced.
Update later in the day on Feb 6 2009: I’m seeing several messages in the Intuit Community forum from people who got the update and are having problems with printing or the PDF driver. I should note that in MY installation I have NOT run into either of these problems. I have not worked with a system that shows the problems that some are reporting, so I don’t have any fixes for them at this point.
Category: General Tips, Program Updates, QuickBooks 2009
About the Author (Author Profile)
Charlie Russell is the founder of CCRSoftware. He’s been involved with the small business software industry since the mid 70’s, focusing on inventory and accounting software for small businesses. Charlie is a Certified Advanced QuickBooks ProAdvisor.
Subscribe
If you enjoyed this article, subscribe to receive more just like it.
Unfortunately, I started QB2009 this morning and the R6 update window popped up, so I let it install. That was before I saw the email alert about your comments here. Oh, well. As expected, the PDF Converter didn’t work (as you’ve said here). Luckily, I remembered you saying previously that this would happen. Fortunately, I had printed out a copy of the instructions to fix the problem (for Vista 64)and things are back working properly now. It is unbelievable that Intuit can’t fix this so you don’t have to do this every time you install an update. You’ve fully detailed how to change the settings, so they shouldn’t have any excuses for not using your instructions to map a fix for the problem.
Vernon, based on some conversations I’ve had with some people with more detailed technical knowledge than I have, there apparently is a three way “discussion” on this. Intuit says the problem lies with the Amyuni driver being incompatible. Amyuni says that it is a problem with Vista 64 not working the way it is advertised. Microsoft – well, Microsoft hasn’t said anything about this that I’m aware of. I’m not sure that in this case we can lay the blame entirely at Intuits feet. But, that is something beyond my level of technical expertise to evaluate. I’m told that Amyuni is working with them to fix this issue, if possible.
Any issues with scheduled backups and the R6 update? We had just installed 2009 on 2/7. I scheduled a weekly backup and it ran fine on 2/14, the R6 update was installed automatically on 2/16 and now the 2/21 weekly backup did not complete. It created a tmp file called “QBTempBackup.tmp Sat, Feb 21 2009 01 00 14 AM” so it looks like it tried but failed.
Also, I’m not seeing a log file like it used to keep for the backups. Any idea where I can look that up?
Tom: I haven’t seen this issue myself. You might check in the Intuit Community forum…
I cannot update R6 because it says something is missing in the Quickbooks program. HELP
Update FROM R6 or TO R6? The current release for QB 2009 is R11. Are you manually updating or using automatic update? What QB product do you have? What operating environment? What is the exact error message, and what are you doing at the time it appears?