Updating quickbooks on a server
These tips may help you solve those issues before you lose your hair or your money. When you are upgrading Quick Books from one version to the next, sometimes the earlier version's data file can't be read by the newer version. Usually this will happen during the installation process and will require you make a backup first.
However, to avoid any issues with the data file, make sure you run a verification on that file before you uninstall the old version or install the new version.
Close out Quick Books, click Start | Run, enter , look for the Quick Books services, and stop those two.
Once the services are stopped, you should be able to copy and paste that file.
If the rebuild simply won't work, you might want to make sure that data file is located on the local machine.
Quick Books is insistent that the data file be located on the C:\ drive.
He’s an avid promoter of open source and the voice of The Android Expert.
If you've lost your documentation and can't find your license/product numbers, you can always locate them by hitting either [F2] or [Ctrl]1 when Quick Books is open (and you're logged into your data file). If you have to reinstall, you'll have to re-register (unless you wrote that validation code down... Have you ever tried to copy that Quick Books data file from your hard drive to a removable drive (for backup or migration purposes), only to find out the file is locked? Quick Books Server Manager and Directory Monitor have that file locked down.
Better yet, install the new version side by side with the old version so you will always have a fallback.
Sometimes, that verified data still will not upgrade to the newer version.
This complexity means that Quick Books is prone to having problems.
I do a lot of work on Quick Books and have gathered some of the common issues I deal with almost daily.