Your browser version is outdated. We recommend that you update your browser to the latest version.

   This information has been provided as a way for you to research any Quickbooks error codes you may have encountered. Below you will find a list of many common error codes and their meanings. In most cases if you are receiving one of these error codes will be able to help you repair your company file. If you have questions regarding one of these errors, we suggest contacting one of our recovery specialists and discussing your situation with them. The phone consultation is completely free and you are under no obligation to use our service. Our goal is to help users of Quickbooks solve data issues and keep their Quickbooks environment running as smoothly and efficiently as possible and we look forward to serving you should you have need...

These errors will pertain to most versions of Quickbooks from 2005 to current. These databases utilize a Sybase database structure. 

  •  3371, Status Code -11118: Could not initialize license properties.
  •  3371: QuickBooks could not load the license data.
  • -6000, -77 when opening a company file.
  • -6000, -82: An error occurred when trying to open the file or An error occurred when QuickBooks tried to access the company file.
  • -6000, -301: An error occurred when QuickBooks tried to access the company file.
  • -6000, -305 occurs when trying to open a company file.
  • -6000, -816: QuickBooks was unable to open the company file because the file is in use.
  • -6010, -100: Your QuickBooks installation may have been modified.
  • -6032, -158: An error occurred when QuickBooks tried to access the company file.
  • -6085, 0 when restoring a backup after entering an incorrect password.
  • -6098, 5 when opening up a data file from the server.
  • -6123, -xxx
  • -6130, -xxx
  • -6123, 0: Connection to the QuickBooks company file has been lost.
  • -6129, -101: An error occurred when QuickBooks tried to access the company file.
  • -6150, -1006: An error occurred when QuickBooks tried to create, open, or use the company file.
  • -6175. QuickBooks has a problem in reading this registration file
  • -6189: QuickBooks is unable to determine the cause of the error on the local file.
  • -6147,0: This is not a QuickBooks data file or there is a problem with the data file
  • 80070057 parameter is incorrect, when clicking on a QBB, QBM, NT, or TLG file from a Google Search Timeline.
  • 80070057, the parameter is incorrect. There was an unexpected error reported while trying to run QuickBooks with company file
  • "Connection to company file has been lost" Quickbooks must close immediately. Any unsaved data will need to be re-entered.
  • "File may be damaged"
  • "System Maintenance in progress"
  • "Internal database error *** ERROR *** Assertion failed errors"
  • "This is not a Quickbooks data file or the file is damaged" 

The next list of errors are typically seen in older versions of Quickbooks made prior to 2005. These versions of the software utilized a cIndex database. This database was also used in some of the non-USA versions until about 2007, so users of any non-US versions of Quickbooks may encounter these error codes. 


C=1 For example, M=1028, L=1743, C=1,V=0 [0], in QuickBooks V5.0/R4, after a backup and  restore to a new system. This may involve non-standard video settings. 
C=3 According to one report this means the program is unable to open a Quicken file on a Mac. This should happen only on Mac versions. Free up HD space. Reopen and close the file using Quicken for the Mac. Then try again. However, a second source says this relates to QB having a full or nearly full hard drive.
C=9 Unable to read from an auxiliary file at the OS file system level.  Copy the data file to another disk or drive. Possible damaged disk.
C=10 Unable to write to an auxiliary file at the OS file system level. Should only happen during backup/restore, export, mail merge or other operation which write to a data file. Free up hard disk space and try again. Possible damaged disk.

Unable to delete a transaction, because it is incomplete (probably data error). Happens during Condense Data and will require manual repair of the database.


QB is trying to close a data file while the program thinks it is in the middle of recording a transaction, but probably isn't. Check to see that the last data you recorded is still in the file. Get the latest release of QB for your version.  Moving data, re-installing, and rebuilding has no effect on this.


Also Error -35. The file was used in a newer version of QB and cannot be used in an older one. Each new version (and some Releases) of QB has an updated data structure. QB files cannot be used after conversion in a new version of the program.  (not used since version 4.0).
C=38 Unknown, but related to backup, as in V7.0D R1 (M=1352 L=968 C=38 V=30 (FFFFFFE2)

Error reading a transaction or memorized transaction. This can be caused when QB is trying to navigate a report or report-like data, or by data damage. If restarting QB and repeating the action causes the error again, it is probably damaged data. Then rebuild. C=43 also occurs when printing 1099 and W2 forms (V6.OD R1 [M=1477, L5203, C=43, V=2(2)). If the font looks like Russian letters it often relates to losing the OCR-A font is by installing TurboTax (also from Intuit). You must delete all OCR-A fonts and reinstall QB.

C=44 Error writing a transaction. Possible data damage or out of memory.  Restart Windows and try again. If error persists you may need our data repair services.



Trying to remove a transaction from a report or report like feature.  Trying to locate a transaction that has been modified, but could not find it. Harmless. Close all windows and continue.If this does not work, Contact us


Appeared in QB 3.0 and was described as a benign error (keep going) or: exit QB, exit Windows, and start again; verify in release 7 or later; or Rebuild data.


Some entry in a list should be deleted, but for some reason was not deleted. Rebuild data may be tried, but don't expect much.  If it does not work, Restore last backup. If you get this on a regular basis it may be time to contact our file repair service.

C=55,C=64 The network temporarily went down. It then probably came back before it was noticed, except for  QB, which cannot handle that.

Error writing to the QB file on the QB file level. Rebuild. If the problem persists try to free memory and try again.


Benign error ( keep working).

C=184 Unexpected Error - February report days mismatch (28 & 29)

Appears in files with Error C=53 (also Error 210, -210)


File has been used in later version. Comment at C=32.

C=224 QB tried to read an invalid split line for a transaction or memorized transaction. The data file may be damaged or QB may be confused. Delete the first split transaction error, in the QBWIN.LOG file.

Try Rebuild. If that does not work, Contact us and allow us to do a Free Evaluation of the database.


QB could not create an image (.qbi) file, due to lack of disk space or network limitations. QB creates this file when a company file is opened and deletes it when the file is closed.

Assertion failed miscellaneous error. The program should not be here and is not sure what to do.  It is used lots of places so it is hard to say how bad it is or what is the root cause. If you get it in list activities or reports it indicates a list problem. Try to Re-sort the list. It also can be low memory or conflicts with other programs.  Shut down other programs & see if problems disappear. This error appears in older versions of QB and Windows.
If all else fails you may need a file repair 

Memory is too full to send any other message.  See C=47.


Here are a few other random errors that can be encountered in any version of Quickbooks. These may or may not be related to a damaged database, if you feel that your database is in fact corrupted, contact us and find out how we can help you recover.

117 or 146 Unknown Client-Specific Tax Form Printing Error. Uninstall and reinstall QuickBooks 
80004003 This is a Windows error number. It means Invalid Pointer. In QB2000 it related to an error when clicking an icon in the opening splash screen. All 8xxxxxxx numbers are Windows error codes (in hex).
Balance sheet out of balance  If unexplainable from an accounting standpoint, This is almost always due to data corruption. Contact us and find out how we can help!
Balance sheet net income not equal to Profit & Loss net If the balance sheet alone is in balance then one statement is on the Cash Basis and the other is on the Accrual Basis. Modify or Customize memorized reports, depending on the version of QB. Also Edit (File) | Preferences | Reports | Cash (or Accrual) to set the default Preference for future reports.
Chart of Accounts delete error See list item delete error below.
Cursor, letters in title bar yellow, faint, hard to see Some say the Windows color definitions change. Due to WordPerfect 6. Apparently fixed in WordPerfect 7.    The solution is to exit and re-start Windows without using WordPerfect or to use WordPerfect 7.
Data from new QB version, cannot use This big problem is easy to fix. Each QB (QB 4, 5, 6, 99, 2000, 2001...) upgrades data files so you cannot use it with older program versions. All you need is the new QB version. Users who think they have the same QB version may be very confused by this. That is because free Releases may update formats in a version. QB6 R3, QB99 R3 and QB2001 R2 upgraded file formats. This causes problems for QB Pro Advisors who deal with many QB versions, releases and clients, so Intuit tries to minimize it.
Erroneous credits in A/R Aging report See Unexplained Errors below.
IE (Internet Explorer problems) Installing some versions of QB try to get you to install a version of IE earlier than the one you have. You can add this to the top of the qbw.ini file for some systems and operating systems:
It works 
Illegal operation For example, "This program has performed an illegal operation and will be shut down. Details: QBW caused a general protection fault in QBWPR.DLL.Ô The Windows, Closeall, File, Utilities, Rebuild procedure may help. However, you also may get more information if you disable Dr.Watson (see top of this page). You also might uninstall and reinstall QB. 
Invalid page fault For example, "QBW32 caused an invalid page fault in module QBTXN32.DLL at 017f:0042f188." See above.
Link Error Code: 00001  This appears in messages like: Link Error Code: 00001(HEX), UNKNOWN (15), linkRecNum = 48387, sibling = 48386, key (m1) = 40518, tOne = 40524, mTwo = 48378, tTwo =48382
It usually relates to transactions to be found and deleted to fix QB files.
List Item delete error The error says something like, "This account is associated with an item. It cannot be deleted." This applies to Items, Customers, Vendors, Employees, Payroll Items and the Chart of Accounts. You cannot delete such items if referenced by transactions or other items. For example, you cannot delete an account that is referenced by an Item or Payroll Item, even if no transactions reference it. You can only delete or change such items (accounts, etc.) after removing all references to them. 
OL-2XX These errors relate to remote network/server problems (despite saying contact Intuit). QB2000 correctly says contact Financial Institution. The key is how often they occur. It may be a transient problem (delays in the Internet between you and your bank or a problem with the bank server). Try again, preferably at a "less busy" time. QB2000 OL-206 says "try again later. If it still fails, contact the financial institution. If they cant help it may be a damaged file.
Other program busy
For example, "This action cannot be completed because the other program is busy. Choose 'Switch to' to activate the busy program and correct the problem. Doing so may result in this error message, "QBDagent.exe, MrtInitialize failed - 7." Clicking OK makes this go away for the moment.
Usually not related to Quickbooks damage 

Make sure the printer works with Start | Settings | Printers | right click printer | Properties, Print Test Page (lower right). Then check print spool setting. If this fails install a new printer driver from Windows or e Internet sites.  If you still have problems  check File | Print Setup and Print Forms settings in QB. Also see errors 117 and 146 and next. 

Usually not related to Quickbooks damage

QB freezes when printing You may have a Print Reports or Print Lists window ( with a printer name & Portrait/ Landscape, etc.) off the screen. QB does not respond to a mouse after you print or Printer Setup. Rebuild has no errors and other programs run OK. The W2000 Task Manager does not show QB as Not Responding. A Processes view shows 9%+ idle and no CPU time for qbw32.exe. Reports that Preview will Print. The solution: hold down Shift & click File, Printer Setup. Print Reports, etc., screens are centered on the screen. Move them slightly by dragging the top blue bar to create a new on-screen default. 
Server busy

QB does not release its file lock as soon as you exit, so anyone trying to use the file too soon gets this message. 

There is a good chance you will need to have the file repaired. 

This may occur when printing.  Usually not related to Quickbooks damage

Trans # This appears in messages like:

Trans #  Type  Date  Num   Name   Payroll Item   Wage Base   Amount
37922   Paycheck   03/30/2001    9093    ... (cont.)

It usually relates to transactions that must be found and deleted to fix QB files.

Unexplained Errors

Many unexplained errors relate to corrupt data, which we can usually fix.


Contact a Service Technician

Toll Free: 1-877-230-DATA (3282)


Providing users a complete Database Repair, .QBW File Condense, Conversion and Optimization services for all of the following versions of Quickbooks. 

Basic 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 99
Pro 2015, 2014, 2013, 2012,  2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 99 
Premier 2015, 2014, 2013, 2012,   2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 99
Enterprise Solutions 15.0, 14.0, 13.0, 12.0, 11.0, 10.0, 9.0, 8.0, 7.0, 6.0, 5.0, 4.0, 3.0, 2.0, 1.0

USA, UK, Canadian, German or Australian/New Zealand Versions all supported.