QuickBooks Error 8007000e: Out of Memory in a Large Company File

QuickBooks Desktop shows error 8007000e when Windows runs out of memory on a large company file; here is what the code means and how to clear it.

Error 8007000e stops QuickBooks Desktop in the middle of ordinary work: opening a large company file, saving a transaction, or running a heavy report. The code comes from Windows, not from your data by itself. It means the operating system refused a memory request from QuickBooks, and the causes are usually ordinary and repairable.

What does the error message say?

The dialog usually shows the bare code with a short line of text. Common forms include "Error 8007000E", "Error 8007000E: out of memory", and the Windows line "Not enough storage is available to complete this operation." QuickBooks sometimes closes after the message. At other times it keeps running but refuses the one task that failed, such as opening the file or finishing a report.

What does the code mean?

8007000e is a Windows code, not a QuickBooks one. Read it in two parts. The 8007 prefix says the failure came from the operating system. The ending, 000e, is Windows error 14, which means out of memory. QuickBooks asked Windows for memory, and Windows said no.

One constraint matters here. QuickBooks Desktop is a 32-bit program, so one QuickBooks process can address only a limited block of memory. The ceiling is roughly 2 GB on 32-bit Windows and up to about 4 GB on 64-bit Windows. A very large company file can exhaust that ceiling even when the machine has RAM to spare. Extra memory still helps, because it keeps other programs from squeezing QuickBooks, but the per-process limit is the wall this error describes.

What triggers the error?

  • A company file that has grown very large. Verify, rebuild, condense, and search operations load much of the file at once, and oversized lists add to the load.
  • Heavy reports and many open windows. Long date ranges, wide custom reports, several files open at once, and a long audit trail all raise the peak demand.
  • A machine that is short on resources: too little RAM, many programs running, a paging file fixed too small, or low free disk space.
  • A damaged data file. Damage can make a verify or rebuild loop and consume memory until Windows cuts the request off.

How do you fix error 8007000e?

Work through the scenarios in order. In our engineers' experience, the first one resolves most reports of this code.

Free memory on the machine

  1. Save your work where possible, then close QuickBooks.
  2. Close other heavy programs: browsers with many tabs, spreadsheets, other accounting tools.
  3. Restart Windows rather than only logging off. A reboot releases memory that closing the program may not.
  4. Reopen the company file before anything else, then retry the task that failed.

Reduce the load inside QuickBooks

  1. Close windows you are not using; every open window holds part of the file in memory.
  2. Keep one company file open at a time.
  3. Break long reports into smaller date ranges and run them one at a time.
  4. If the failure strikes during a payroll or product update, run it right after a restart with nothing else open.

Shrink the company file

  1. Run Verify Data from the File menu, under Utilities. If it reports problems, follow with Rebuild Data; the rebuild re-indexes the database and can lower the memory the file demands.
  2. Create a portable company file (.QBM), then restore it to produce a fresh working file. Restoring a portable rebuilds indexes and often yields a leaner copy. Test on a copy, never on your only original.
  3. Use the Condense Data utility to strip old, closed transactions before a date you choose. Try it on a copy first; results vary with file content and edition.
  4. Trim lists you no longer need: inactive customers, vendors, and items.
  5. Match the machine to the file. Add RAM, move to 64-bit Windows if the PC still runs 32-bit, keep disk space free, and let Windows manage the paging file.

Handle a damaged file

  1. Install the latest QuickBooks release, because updates have carried memory-handling fixes in the past.
  2. If Verify keeps failing after a Rebuild, restore a recent backup and work forward from it.
  3. If no backup restores cleanly, the file can go to our engineers for a direct repair instead of a rebuild from scratch.

How do you keep it from coming back?

  • Keep the file lean. Condense or archive closed transactions on a schedule, trim inactive list entries, and keep the audit trail from growing without end.
  • Reboot on a schedule, not only when something fails. Memory pressure builds quietly over days of uptime.
  • Verify data monthly and rebuild as soon as verify flags anything. Small damage is cheap to clear.
  • Install new releases when they appear, and size the machine for the file you actually have: 64-bit Windows, adequate RAM, and free disk space.
  • Keep open windows few and one company file open at a time.
Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.