Fix a QuickBooks Company File Copy or Upload That Fails Partway
A QuickBooks company file copy or upload that dies partway usually has one quiet cause, and two small steps get you one clean, complete transfer.
You start copying a QuickBooks company file to an external drive, or uploading it to a service, and the transfer dies partway. Sometimes it stalls at 40 percent, sometimes at 90. The browser reports a network error, the copy dialog freezes, or the archive that arrives will not open. The network is rarely at fault. Something on the machine that hosts the file is holding it open while you read it.
Why does the transfer fail partway?
On the computer that hosts the file for multi-user access, the Database Server Manager runs as a Windows service. Its job is to keep the live QBW file open around the clock so every workstation can reach it. That means constant reads and writes on the same bytes your copy is trying to read. When the two collide, the transfer stalls, resets, or yields a copy that will not open. No dialog explains it, because from the operating system's view, nothing failed.
Two habits prevent nearly all of these failures. Zip the file before moving it, or stop the database service for the few minutes the copy needs. Both are safe with a little preparation, and both are covered below.
Before you touch the file
Preparation matters more than the fix itself. Confirm that a recent backup exists, because the next steps briefly interrupt everyone's access to the data. Ask all users to close QuickBooks, then check that nobody is still signed in. If QuickBooks must stay open on the host, switch it to single-user mode first so nothing writes to the file while you copy. Note the exact name of the database service before stopping it, so restarting it later involves no guesswork.
Zip the file before you move it
- Close QuickBooks on every workstation, or put the host into single-user mode.
- In Windows Explorer, right-click the QBW file, choose Show more options if your menu shows it, then Send to and Compressed (zipped) folder. Wait for the archive to finish; a large file takes minutes.
- Copy or upload the ZIP, never the live file.
- Leave the original QBW exactly where it sits.
The archive gets written once, quickly, and after that the upload never touches the live file. It is also far smaller, so it finishes inside timeouts that a multi-gigabyte raw file would blow past. Zip only the QBW itself. The helper files stored beside it belong to that machine and are not part of a clean copy.
Stop the service for a byte-exact copy
Use this route when zipping fails too, or when the destination needs the raw file. Press the Windows key and R together, type services.msc, and press Enter. Find the service named QuickBooksDB followed by two digits that track the release year, QuickBooksDB31 for the 2021 edition, for example. Right-click it and choose Stop. Copy the file while nothing holds it open, then right-click the same service and choose Start.
While the service is stopped, no workstation can open the file in multi-user mode, so pick a quiet window and give users notice. The monitoring service listed nearby, QBCFMonitorService, does not need stopping. A reboot of the host also brings the database service back if you forget to restart it.
Split a large archive into 500 MB parts
An archive of a big company file can still run to several gigabytes, and some upload pages refuse files past a certain size. A free archiver called 7-Zip splits the finished ZIP into parts that each arrive intact:
- Select the finished ZIP.
- Right-click it, choose 7-Zip, then Add to archive.
- In the Split to volumes, bytes field, type 500M.
- Click OK. The result is a set of parts named .001, .002, .003 and onward, beside the original.
Upload every part. One missing piece makes the whole set unreadable, and renamed parts will not rejoin, so leave the names alone. To reassemble, put all parts in one folder, right-click the .001 part, and choose 7-Zip, then Extract Here. The tool stitches the parts back into one archive and unpacks it.
Signs the copy is good
- Every part except the last is exactly the size you set; only the final piece is smaller.
- Extraction finishes with no CRC or checksum error.
- The extracted QBW matches the source file's size to the byte.
- QuickBooks opens the extracted copy without complaint.
Test the extracted copy, not the original. A byte-for-byte size match between the two is the quickest proof that every part survived the trip.
If the problem runs deeper
Two failures sit below this workaround's reach. If the copy halts with a cyclic redundancy check error, the drive itself is struggling where the file lives, and no transfer technique repairs that. It becomes recovery work, the kind our QuickBooks data recovery service handles when a file will not open. The other limit is size: an archive that uploads cleanly today still grows with the books. Condensing an oversized QuickBooks Desktop company file attacks the size at the source. Solve that, and the next transfer stops being an event.