The Scenario
I have worked with a QuickBooks (Enterprise) customer for years. Not only did their company file grow in size to get quite large, but they were unable to upgrade to newer versions, still locked on 2019. So part of getting this backup problem fixed was cleaning up the company file. So a little digression on those fixes first.
The Fixes
Over the years and several different bookkeepers, several issues were created in the company file:
- When a tax rate changed, instead of creating a new sales tax item, the rate on the existing item was changed. This meant that all sales orders and invoices that had correctly used the original rate now were using a sales tax item rate that didn’t match.
- When a U/M change was required from an inventory item, the U/M was just changed for the item. What should have been done is to modify the U/M for the item to add the new measure.
- Especially for walk-in customers, when an item was out of stock – at least according to inventory on hand – it was invoiced anyway. Procedures were modified a while back to start with sales orders and only invoice for actual items on hand.
Utilities to the Rescue
Each month, there are hundreds of sales orders and invoices, so fixing items one by one would have been more than onerous. Fortunately, I found a handful of utilities from https://q22.us that were helpful if not essential. One in particular, their mass update utility, allowed me to make changes to a large number of records at once. So fixing the issues took days (still a lot of them) instead of months and months.
Next Steps
With the file’s data repaired, I was able to successfully rebuild then condense the data. Following that I was able to upgrade from 2019 directly to 2021. Yippee!
Not So Fast..
Unfortunately, backup stopped working. Whether trying to do a Save Now or schedule a future backup, it would fail without providing any detail: it just didn’t work. Finally, it occurred to me that there is a backup log, and I decided to look there. To get to it, I pressed F2 then F3 . On the F# screen, click on the Open File tab, select QBBACKUP.LOG file from the list that appears, and then open the file.
What I found was that the backups were failing with a SQL -82 error – invalid character in database name.
Humm, why had this been working for years but now wasn’t?
The company file name….
When the file was first set up (2005!), the name of the business was entered as <name> CO. What QB did was to add .qbw to that file name, producing <nameCO..qbw. Note the double periods. When backup tries to start the file, it actually creates an alias that puts a space between the two periods so the alias appears to have a space in it. Not allowed and creates the error.
How to Change the File Name
Open Windows File Explorer, then navigate to the location where the company file is stored. Right click on the .qbw file and choose rename; you can enter a completely different name or simply remove the extra period. The other files associated with the .qbw will have their names changed as well. From then on, backup should work just fine. Or if it fails, it is related to data in the file which can be rebuilt using the utilities.
Oh, just make sure QB is closed on all devices that access the company files. You do not have to stop the QB 31 service but if using !B 2019, you will have to stop the !B 29 service.