Data Recovery

QuickBooksRepair.com offers the best data recovery service available.

QuickBooksRepair.com repairs files from any version of QuickBooks from version 1 for DOS to the current Enterprise 2015. Our techs use tools which have evolved over the last 20 years that are specifically designed for repairing damaged QuickBooks files.

Our recovery success rate is over 95%!

This is how we are able to offer our
100% money-back guarantee
if your data is unrecoverable.

The risk is ALL ON US!

Our repair process does not require you to upgrade your file to the latest version.  You don’t need to worry about having to purchase additional software that you don’t need.

We frequently recover files that other companies, including Intuit, are unable to repair!

We also work with all the international versions of QuickBooks so it doesn’t matter if your version is from the US, UK, Canada, Australia, New Zealand, or Singapore!

Here are just some of the most common problems that we resolve and other services we provide.

  • Any of the series -6000 error codes when opening or using your data file such as but not limited to the following examples. (-6000, -30), (-6000, -82), (-6000, -301), (-6000, -305), (-6123, -xxx), (-6150, -1006), (-6177, 0), (-6189, -82), (-6210, 0)
  • QuickBooks has experienced a problem and must be shut down.
  • An error occurred when QuickBooks tried to access the company file.
  • Any C = ERROR you may encounter.

FREQUENT C = ERRORS

C=43

Can’t read transaction

C=53

List item still exists after being deleted

C=225

Error reading transaction

C=44

Can’t write transaction

C=79

Problem with inventory data

C=315

Error reading transaction

C=47

Can’t find transaction

C=88

Problem reading one or more of the data trees in the file

C=342

Often followed by an IPF in APPCORE.DLL – damaged data tree

CLICK TO SEE ALL C = ERRORS
C=# Title Description Alternate Description Action Extra Info
1 Can't find form resource Could not load the resource that describes the layout of a form Form (or register) is too big to fit in the window. Quickbooks is unable to display the information requested. Non-Standard video display or resolution. Try changing resolution or video driver. For Mac monitor may not be large enough. This error should normally only happen during development. Maybe a damaged copy of QBWIN.DLL.?
2 Can't find table resource Could not load the resource that describes the layout of a table or table footer. Most likely problem displaying something on the screen. Reinstall Quickbooks. Check the video display or resolution. This error should normally only happen during development. Maybe a damaged copy of QBWIN.DLL.?
3 Unable to open file Unable to open a Quicken file on the MAC (but the file exists). The file is possibly damaged Unable to open a Quicken file on the MAC (but the file exists). The file is possibly damaged. Also seen as QBM restore problems with multiple disk backup and when creating file in QBM. Open the file in Quicken and resave it to a new name, check to make sure the quicken file integrity is good. If unable to restore backup - check to make sure files are all named the same including entire path on disks. If having problems creating new company most likely files needed are not in directory - reinstall QBM. V= OS Error
4 Unable to create file Unable to create a file in places like backup and restore Unable to create a file in places like backup and restore this error should only occur in older (2.0 - 3.1) version of QBW - check hard drive space, read-only access
5 Unable to seek in file Unable to seek (reposition) to a specific part of a file.Possibly damaged file. Not used for .QBW file. Could be backup file during restore Unable to read part of the file possibly damaged c-index Copy the file to a new location and try again. If you get an error during copy, data is damaged. Verify, rebuild if necessary. V=OS Error on Mac
6 Unable to skip in file Attempt to jump forward in file failed.Damaged backup file? Unable to read part of the file possibly damaged c-index. Might be a damaged mac backup file. Use a different backup or data file. Treat as a damaged backup. File will most likely have to come in house for Data Recovery called from SquashProc. V= OS Error on Mac
7 Unable to go to end of file Unable to seek to end of file. Used during company startup when reading COA.DAT. Maybe damaged charts.dat file? the "default" COA (COA.DAT) used when creating a company maybe damaged. Reinstall Quickbooks. Try creating another company. V= OS Error on Mac
8 Unable to tell position of file Unable to find current location in file. Backup file, image file, qbw file, or coa.dat file may be damaged. Unable to read part of the file possibly damaged c-index Treat a normal data damage - verify rebuild if necessary - if unable to open file - restore backup or send file in for Data Recovery
9 Unable to read file Unable to read from an auxillary file Often problem backing up and restoring the file - media problems. Mac - problem with PC Exchange unable to backup on PC formatted diskettes. Possibly a damaged disk. Try copying the file to see if the disk is damaged. Mac, upgrade the Mac PC exhange program to 2.0.3 or higher.
10 Unable to write file Unable to write to an auxiliary file. Should only happen during backup/restore, export, mail merge or other operation which write to the date file When backing up a file onto a disk with little or no space warning then c=10 error. Mac - program is not able to create startup files on hard drive or problem with PC Exchange. Damaged floppy disk or not enough free disk space on hard drive. Check to see if customer is accessing across network may not have rights to write to the server, check to see if the files are locked or drive is locked by third party software such as norton> Mac - check version of PC change upgrade to at least 2.0.3.
11 Unable to close file. Unable to close the file (MAC only). Unable to close the file (MAC only). Verify file rebuild if necessary - will most likely have to make copy of file and rebuild bypassing the backup
12 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
13 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
14 Unknown Key Tried to sort a transaction list by an unknown category. Report or register is unable to sort or total information correctly verify file - rebuild if necessary - resort lists close and reopen file - try again Unable to build sort key for txList because it is not a valid sort type
15 Error in dsetKey Could not set the key to find a particular transaction or list element Could not set the key to find a particular transaction or list element Please report the error. V= value has C-Index error code. Find out steps and get data so we can reproduce C-Index dsetkey function failed
16 Attempting link to target with 0 amount Should never try to link to a 0 amount target, but we did anyway. should only occur in v2 debug Trying to link to a 0 amount target this error should only occur in QBW2.0 - should not be occuring in shipped product - verify - rebuild if necessary
17 Unable to link Error creating link Error creating link between trasactions Verify file rebuild if necessary - check for link damage - open invoice, unpaid bills, undeposited funds. Memorize and delete the problem transactions. V contains link type. Only avaiable in debugging Should never be seen in shipping code.
18 Unable to create TxList for Paying Bills Probably not enough memory to create list of transactions for paying bills unable to display the information in the paybills Try to free up some memory. Verify file, rebuild if necessary - look for any link damage with a/p - unpaid bills report compaired to account balance.
19 Shrinking single target Condense unable to shrink transaction data (probably data error). Condense unable to shrink transaction data (probably data error). Verify file rebuild if necessary - check for link damage - open invoice, unpaid bills etc. Memorize and delete the problem transactions. There is only one target and its amount is not zero
20 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
21 Closing data file while in a transaction (caching). An attempt to close the data file, while performing an operation that is being cached. May result in data loss. Trying to close file when transaction is cached in memory. Release issue with 4.0 corrected in latest release - occurs when editing paychecks. Release issue with v3r6 occurs when converity DOS file - pressing escape while QBW3r6 is converting links from QBD.
22 Exceeded Capacity of Item History Table There is too much historical information for one inventory item. Could possibly be data damage. Could possibly be a damaged item or list. Could be a faulty converty from Mac. Try rebuilding file. Find which item is causing error - create new item merge old into new. If customer just converted from Mac to QBW 5.0 (or higher) instruct customer to export and import the item list.
23 Error opening data file. Can't read header information Damaged file header Possibly damaged data file - restore backup if unable to get into file have file come in for Data Recovery V contains C-Index error code
24 Unable to compress a record Update failed while writing a record (one of several types) when updating from previous version. This is problem while writing to the file, so data or disk damage is possible, as well as bugs. Error updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= size returned by builddrec
25 Invalid rCrit Invalid Information sent to CreateTxList Problem displaying report this error should only occur on older (2.0 - 3.1) version of QBW - verify rebuild if necessary
26 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
27 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
28 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
29 Unknown Key type Unknown key type when decompressing a C-index record Record (target, master, list, etc) contains a invalid key This error should only occur in older (2.0 - 3.1 )version of QBW - Verify, rebuild if necesssary
30 Can't get volume information Can't identify volume or folder that QB is installed in (mac only) during startup. The hard disk probably has problems. Can't identify volume or folder that QB is installed in (mac only) during startup. The hard disk probably has problems. Try reinstalling QBM
31 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
32 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
33 Can't make Virtual target of given type Internal Error -- trying to create Vat or Cogs target with an unknown target type Problem recording part of transaction - usually associated with the cogs account or inventory try to create transaction again - try with just 1 item to detemine which item is causing problem - create new item merge old item into new - file in house regenerate item history - try to record transaction again. V= bad ftarg type value
34 Empty crit bit array Internal error Internal error Unclear. Free more memory. Try in new company. Reinstall program is necessary
35 Not enough memory to grow transaction list Not enough memory to GrowTxList or CreateTxList Problem displaying report This error should only occur in older (2.0-3.1) Not enough memory. Try again with more memory available.
36 Not enough memory to edit list item Not enough memory to edit object in list problem editing a item/account/name any list item this error should only occur in older (2.0-3.1) versions of QBW. V has which list. Try again with more memory available
37 Error writing item history record File Error qbw was unable to write the inventory item history record Check for hard drive space, read-only access, low-memory, etc. Verify, rebuild if necessary. Create a new item merge old into new V=item ref number V=item ref number
38 Error in dfnd (TBYITEM) unknown unknown This error should only occur in older (2.0-3.1) versions of QBW.
39 Error in cnextrep. Error when getting history of an item. Error in cindex file or internal error in Quickbooks Usually problem with inventory - generating the history if able to determine what item is giving error create new item merge old with new. Rebuild should address and correct this in later (3.1) versions of qbw V=Cindex error code
40 Error in dsetkey Error returned by dsetkey in SearchTxListByName Problem displaying report Verify rebuild if necessary - V has C-index error code or return value from builddrec. Get setps and data so we can reproduce
41 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
42 Error writing master record Either error writing master record OR error compressing and record. May happen when merging names QBW was unable to write to the master record of a transaction verify rebuild if necessary V= contains C-Index error code or return value from builddrec
43 Error reading target Error reading target OR memorized tx target Error reading target (individual line on a transaction) OR memorized tx target May be due to bad data or may be due to invalid txList. Try closing company and repeating steps. If further problem was txList problem, Run Verify & Rebuild. Check KB - there are some release issues in early versions that will cause c=43 and some issues where it is not data damage, but caused by transacations being deleted V contains C-Index error code (or for memorized tx, record number we were reading).
44 Error writing target Error writing target Error writing target (individual line on a transaction) Verify Rebuild if necessary. If that doesn't work, try freeing memory and resources. If error occurs in rebuild try to go to the transaction that is causing error - if unable to go to transaction the file may need data recovery V= contains C-Index error code Log file will also display the record that is causing the problem
45 Unable to allocate the txList sort array Not enough memory to allocate sort array for transaction list Problem displaying report Try again with more memory - close TSRs and any windows within QB
46 Unable to reallocate the txList sort array Not enough memory to grow the sort array for a transaction list Problem displaying report Try again with more memory - close TSRs and any windows within QB
47 Can't find target in txList Trying to remove a target from a txList or locate a target that has been modified, but could not find it. Error generating report. Report is trying to remove or change the amounts and it is not able to display the information correctly. Try again with other windows closed such as reports, registers receive payments, etc. See KB for various ways to reproduce the error Due to a problem updating transaction lists
48 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
49 Invalid auto link type specified Internal Error -- attempting to link two txs with non-existant link type problem creating link delete both transactions you are attempting to link - verify and rebuild if necessary - re-enter transactions and try linking again V = requested link type
50 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
51 Can't find TxList Trying to remove txList from list of txLists (closing the list), but we can't find it. error trying to remove a transaction from a report. Close all the reports, shut down QBW if necessary and try again
52 Invalid field specified to position by Internal Error -- Table footer has an illegal field definition unsure - most likely unable to display a form because of a invalid field Verify rebuild if necessary. If error is occuring on a templete - try defaulting that templete. Get steps to reproduce - see if occurs in sample company. Report where error occurs. ABORTs
53 Empty Index entry points to a used edlist item Some entry in a list should be deleted, but for some reason did not get deleted Resort all the lists close and re-open the file try again, verify file and rebuild if necessary V= item being used (hiword) and list type (loword). ABORTs. Essentially, the last item in the edlist or index points to a used edlist item instead of a deleted one. Somehow the index and the edlist got out of synch.
54 C-Index returned failure (dsetKey) A call to C-Index's "dsetkey" routine returned that it failed most likely qbw is trying to create a key for record, but is unable to Report steps. Exit Quickbooks and then retry. If problem continues, try rebuild. If problem still continues, contact ICU
55 Form field types don't match some field type on a form is invalid or unexpected A field on a form is invalid or unexpected. If it is on a invoice or customizied templete try to default the templete. If it is a form you cannot edit try in another company - reinstall Quickbooks. V=objID in most cases. The DLLs resource is probably hosed
56 Can't select new field Unable to select a field on some form Unable to select a field on some form If occurs on customized templete try defaulting. Try in another company - attempt to reinstall.
57 Can't find pick resource Unable to load a resource for a drop down list. problem reading information from a drop down list See if problem happens in a new company. Reinstall Quickbooks.
58 Error computing avg cost in inventory history Divide by zero in item history calc.- problem recording the history for inventory item try to determine which item is causing error - check inventory valuation detail for item - see if cost is showing correctly - create new merge old with new - on newer version verify and rebuild should also address the issue
59 Can't find pop resource Unable to load a resource for a popup window Unable to load a resource for a popup window reinstall QBW - see if error occurs in other files…
60 Filtered edlist message error Unknown message when processing the filtered list proc. problem displaying a list resort all the lists make sure show all is selected - if error is occuring with a pick list or a list that cannot be resorted - try in a new company - reinstall if needed The Proc received an unknown message type
61 Unable to allocate memory Unable to allocate memory for hList.g in an EdListType Probably out of memory. Close some applications and try again.
62 Unable to allocate memory unable to re-allocate memory for an hList.g in and EdListType Probably out of memory. Close some applications and try again.
63 Unable to reallocate memory Unable to re-allocate memory for an hList.g in an EdList Type Probably out of memory. Close some applications and try again.
64 Table field types don't match Internal error regarding tables Problem displaying information from a table Report where the error is occuring. Try exiting out of qb and trying again, try reinstalling, try a new company While creating a table field.
65 Can't find original target QB was trying to return to a spot in the file after performing some other operation which removed the desired target QB is trying to display information from a transaction is not in the file close all the reports and other windows within QB and try again. V= cindex error returned from cfind
66 Can't select next/prev table field Unable to select some field in a table Unable to select some field in a table If on a templete try defaulting. See if occurs in new file - reinstall if needed. The next or prev table field is invalid.
67 Invalid index detected in an EdList. Memory has become corrupt or some internal coding error List damage resort all lists - exit qb and go back in. Verify file rebuild if needed. V= index # (hiword) and listType (loword).
68 Unable to allocate memory for register We're probably out of memory Probably out of memory. Close some applications and try again. See if it occurs in another file. Which register is causing problem - see if they are reaching the max number of lines (windows limitation of 65535 per window)
69 Unable to allocate memory We're probably out of memory Probably out of memory. Close some applications and try again.
70 Unable to allocate or re-allocate memory We're probably out of memory Probably out of memory. Close some applications and try again.
71 Error setting number of targets. Target number is greater than the number of allocated targets (only debug version). This error should only occur in the debug version - most likely trying to capture the record jumps in targets Report steps to reproduce. File may need data recovery
72 Unable to allocate history update action buffer We're probably out of memory Probably out of memory. Close some applications and try again. See if it occurs with another file. Make sure file is local.
73 Unable to allocate memory for PO selection list We're probably out of memory unable to display the PO list Free more memory. Run the open PO report - see how many PO are open for the vendor. Try to close several and try again - if this works please Report the number of PO s for vendor.
74 Error deleting master record C-Index was unable to delete the master record of some transaction Unable to delete part of a trasanction. Most likely there is some type of data damage verify file - rebuild if necessary - try deleting transaction again V= Cindex error. ABORTs
75 Error deleting target record C-Index was unable to delete a target record Unable to delete part of a trasanction. Most likely there is some type of data damage verify file - rebuild if necessary - try deleting transaction again V= Cindex error. ABORTs
76 No proc given in UndoAddItem Probably a coding error. Next candidate would be a memory problem Most likely a memory problem Exit Quickbooks and try again.
77 No proc given in SelListCreate Probably a coding error. Next candidate would be a memory problem Most likely a memory problem Exit Quickbooks and try again.
78 Negative open quantity detected Negative open quantity detected Negative open quantity detected Delete the trasanction and re-enter.
79 Error reading item history record Error trying to read item history record (duh) Unable to read the inventory history for the item Note the v= number (V = item reference, 7.0 and later divide v number by 256 to get the item reference number) create a new item merge the old into the new. Rebuild will correct in some cases - if error is occuring during rebuild try merge - if error is still occuring restore a backup or file will need to come in for Data Recovery V = item, 7.0 and later divide v number by 256 to get the item reference number
80 Couldn't create buffer for new trans when trying to autofill NewTrans, which allocates memory for a new transaction faild Probably out of memory. Close some applications and try again. Try another vendor or account. Turn off the auto fill preference and turn it back on.
81 No size specified for field on form. A field has no spaces specified to store data. Perhaps out of memory but more likely coding error problem displaying or recording a form Get steps to reproduce (which form) and report. Try defaulting the templete. See if occuring in new file. Exit out of QB and try again. Reinstall if necessary. ABORTs
82 Unable to record a non-sibling link C-Index faild to write a link to disk Most likely data damage - problem recording a link Verify file, rebuild if necessary - check for link damage (open invoice, unpaid bill, cbbs etc.) delete and re-enter the problem transactions - if still unable to correct check for backups or file may have to be sent in for data recovery ABORTs
83 Unable to record a sibling link C-Index faild to write a sibling link to disk Most likely data damage - problem recording a link Verify file, rebuild if necessary - check for link damage (open invoice, unpaid bill, cbbs etc.) delete and re-enter the problem transactions - if still unable to correct check for backups or file may have to be sent in for data recovery ABORTs
84 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
85 Unable to locate program code to handle a table on a form Perhaps memory is corrupt, coding error problems displaying a form Exit Quickbooks and try again. Get steps to reproduce (what form they are having the problem with) and report ABORTs. No table proc was passed to TableCreate
86 Field type inside table is invalid Perhaps memory is corrupt, coding error problems displaying a form - also seen with the wrong tax table update installed Exit Quickbooks and try again, try same steps in new company. Check the tax table according to related KB. V= field #, usually. ABORTs
87 Error reading from C-Index C-Index returned a failure when reading an edlist record problem reading a list record verify the file, rebuild if needed. Resort all the lists - exit out of QB and go back in - try again. If unable to open file try restoring backup or file will have to be sent in for Data Recovery FATAL
88 Error writing to C-Index C-Index returned a failure problem writing to file Verify rebuild if needed. Check resources - reboot in safe mode if necessary. If unable to get into file - restore a backup or send file in for data recovery - Check KB for further troublshooting information v= CIndex return from csave.Could not write some kind of data in DBRecord::Write.
89 Error Writing wndow positions QBW was unable to save window positions to disk Error should only happen in 2.0 - QBW was unable to write window positions to file - would occur when closing a window in QBW check disk space. Verify file, rebuild if necessary
90 Field or other object on form has an invalid height or width. Occurs on Macs with small screens; may also occur if a window can not be placed on screen (large pick lists for example?) Occurs on Macs with small screens; may also occur if a window can not be placed on screen Make sure that screen is at least a 13" monitor, especially on Macs Essentially a formobj is being placed outside the bounds of the window.
91 Not a form window (expected one) QBW requested form window information for something that was not on a form problem displaying a window or read from the templete on later versions default templete if you are trying to open a invoice or other customized form also look at c=291. If it is another window close all other windows and try again.
92 No field size specified Unable to create a field on a form because the size of the buffer to hold input data was unspecified; coding error. problem displaying a form Close applications to free memory close QB and try again. Try defaulting the templete. See if problem occurs in sample company reinstall if needed. Please Report the form that this error is occuring on.
93 Unable to allocate memory for specific pick lists Out of memory unable to display a pull down list because system is out of memory Close some applications and try again. Reboot if needed.
94 Error getting pick string Quickbooks did not recognize a pick string. Check options (payroll, inventory) and types of elements expected in pick list. Pick list will display a smiley face :-> Unable to read all the information from a drop down list. List will most likely display a :-) where it is unable to read. Review KB for various program related issues. If error is occuring at another place please Report the steps to reporduce.
95 Error allocating memory for table footer Out of memory problem displaying a form or report because the system is out of memory close all applications, shut down qbw and try again. Reboot if needed.
96 Expected a table part to be active Some part of a table was inactive unexpectedly problem displaying a form or report Exit Quickbooks, Close some applications, and try again. Review KB for some program related issues with QBM and earlier versions of QBW on a invoice when selecting tax item and customer is taxable. ABORTs
97 Table not open Trying to close a table but it was not open, unexpectedly when trying to close a window qbw it is unable to close a table because never opened but it should have been Report steps to reproduce and what window they are trying to close ABORTs
98 RecordLinks unable to get next record number Unable to get next record number while recording links QB is unable to read what the next record number in the file should be when trying to record some links. Verify, rebuild if needed. Delete the transactions causing problem try to record again. Restore backup or contact ICU for further options of data recovery ABORTs
99 Unable to begin transaction C-Index was unable to a begin transaction; "transbeg" routine failed Most likely data damage - problem recording a trasnaction Verify rebuild if needed. Try a different type of trasanction. Restore a backup or refer to ICU. V=CIndex error. ABORTs
100 Unable to end transaction C-Index was unable to end a transaction; "transend" routine failed Most likely data damage - problem recording a trasnaction Verify rebuild if needed. Try a different type of trasanction. Restore a backup or refer to ICU. V=CIndex error. ABORTs
101 No table footer defined Quickbooks attempted an operation on a table footer but the table had no footer problem displaying a form or report Report what form or window error is occuring. Try defaulting the templete see if error occurs in sample reinstall if needed. ABORTs
102 Unable to decompress record Index into file or record is damaged; "putdrec" routine failed. usually indicates damage to a list If error is occuring when opening file - lists are unable to load into memory - restore backup or refer to ICU. If you are able to get into file - try restorting all the lists look for any problems on the lists (KB 102684 has good troublshooting suggestions) V=CIndex error code
103 Unable to create data file Quickbooks was not able to create a new data file "dbcreate" routine failed. The number will help PD determine why Quickbooks was not able to create a new data file Make sure the file they're trying to create does not already exist. There may be a problem with the hard drive. Try another file name. Also try another drive location for the file. V= CIndex error from create
104 Unable to add root nodes to data file Quickbooks had a problem initializing a data file Quickbooks had a problem initializing a data file or adding information to the file structure Make sure the user has enough disk space. If a network is present, make sure the file is not in use by another task. Close down QB and try adding information again. Verify file rebuild if necessary. V=CIndex error from addroot
105 Unable to open data file (2) Quickbooks tried and failed to open what is already a suspicious data file (The data is in a state indicating it may not have closed properly) Quickbooks tried and failed to open what is already a suspicious data file (The data is in a state indicating it may not have closed properly) If unable to open file using the troubled company steps - restore a backup or contact ICU for further options V=CIndex error from CI_bopen
106 Can't clear write from previous session Quickbooks was unable to restore the state of the data file based on the image file. The data could be fine, or could have a partially recorded transaction hanging around System crashed while QB was open. QB was not able to pull information from the image file to restore the data. The data could be fine, or could have a partially recorded transaction hanging around Run verify data. If it succeeds, the file is probably okay If it fails, there's a good chance rebuild can fix it. If rebuild does not correct problem - check the log file, try to correct the problem manually by deleting the transaction causing the problem. V=CIndex error from imagerest
107 This file was not closed in the previous session QuickBooks was unable to close the data file in previous session. The data should be fine. System crashed while QB was open. If unable to open file try copying file file and see if able to open file or try renaming the qbi file. V=CIndex error from DIdbopen
108 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
109 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
110 Could not read the previous audit trail list. This should only be found in the international version of 3.1. It occurs when a problem with the audit trail information is detected while building the audit trail report. The problem is in changes or deletions to one of the lists. Error has only been seen in internation verion of 3.1 when trying to build the audit trail report Try condensing the file removing the audit trail information - if this works please report steps you took to correct problem.
111 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
112 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
113 Invalid size for a pick list item Memory is corrupted or coding error unable display the information from a pull down list Close QB, check resources - reboot if needed try again if sill occuring - try same steps in sample company.
114 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
115 List item merge faild Quickbooks could not merge two list items. Both items still exist, but it may be that some transactions were changed to refer to the target of the merge Quickbooks could not merge two list items. Both items still exist, but it may be that some transactions were changed to refer to the target of the merge Rebuild should fix the problem. Resort the lists - exit out of qb and try again. If unable to merge existing items try to create new list element and merge old with new - if able to narrow to any transaction or list element causing problem - deleting and re-enter information. V=listType
116 Restore encountered a RLC block which it did not recognize QuickBooks was unable to restore the backup file. Most likely due to a corrupted backup file. QB was unable to restore a backup file - most offen occurs with a mac file. Go back to QBM make sure the preferences for reporting is defaulted (not set to description only)> make another back and try again. Could also be a corrupted backup - if first suggestion does not work - try backing up onto hard drive then restoring (if unable to restore might be something wrong with file - trouble shoot like it is data damage) try backing up onto floppy and restore on same system if unable to restore might be something wrong with the floppy drive. V= RLC mode
117 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
118 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
119 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
120 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
121 Invalid account or item type An invalid account or item type was passed into Quickbooks account or item compare function. List damage Resort lists - check for any problems (KB 102684 good suggestions). If error is occuring on a customized template - try defaulting the template - in QBM might occur when trying to edit the account - condense file prior to start date. ABORTs. V= itemType or accntType
122 Invalid quicken file Account headers in the quicken file appear to be inconsistent (debug version only) Account headers in the quicken file appear to be inconsistent> Verify that the data can be read and used in Quicken refer customer to Quicken support if necessary to make sure file is stable. Please report this it should not occur in the shipped product
123 Error reading Quicken file Quickbooks faild to recognize a record from a Quicken data file. If Quicken (and any add on products) can read and manipulate the data, this may indicate a bug QB failed to read a record from a Quicken data file Verify that the data can be successfully read and manipulated in Quicken (and any add on products whose data is being converted) If so, restart the convert.
124 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
125 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
126 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
127 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
128 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
129 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
130 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
131 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
132 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
133 Transaction remarked during convert QuickBooks tried to convert a transaction in a QBDOS file incorrectly problem converting a QBDOS file Verify integurity of file in QBDOS, qbutil Should only occur in debug builds, not in shipping releases
134 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
135 Invalid Qcard operand read An operation on a Qcard could not be completed Problem displaying a Qcard A harmless problem with the program. Turn off the qcards exit the program and turn on the qcards again
136 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
137 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
138 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
139 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
140 Can't find row Data needs to read into a report which has not allocated a row for it. problem displaying a report Try regenerating the report, changing date ranges. Try with different filters exit QB and restart. See if able to reproduce in sample - Report what report error is occuring on.
141 Can't find column Data needs to read into a report which has not allocated a column for it. problem displaying a report Try regenerating the report, changing date ranges. Try with different filters exit QB and restart. See if able to reproduce in sample - Report what report error is occuring on.
142 Error in dfind (TBYNAME) An error occurred while searching problem performing a find If this is the only error, it simply indicates a harmless bug. Verify file rebuild if needed. Try same steps in sample company - Report what was being performed.
143 Error in IHA convert An error accurred while converting data from In-House-Account (QB4.0 and later does not convert it any more) An error accurred while converting data from In-House-Account (QB4.0 and later does not convert it any more) Make sure the file in IHA can be successfully read and manipulated. Try starting the convert process again. All the version of QBW that converted the file are now sunset so further options for customer are limited to working within current QBWs which means creating a new file.
144 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
145 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
146 Criteria bits set with single item An error occurred while preparing for search problem doing find This should be a rather harmless bug. Report steps to reproduce.
147 Error encountered while creating a report An error occurred while creating a transaction history report problem reading/displaying inventory item history information see if you can narrow down the item causing the problem - create a new item merge old into new.
148 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
149 Error reading Quickbooks file During convert, Quickbooks for windows failed to recognize a record from a Quickbooks for DOS data file. If Quickbooks for DOS can successfully read and manipulate the data, this may indicate a bug in QBW restart the convert During convert, Quickbooks for windows failed to recognize a record from a Quickbooks for DOS data file. If Quickbooks for DOS can successfully read and manipulate the data, this may indicate a bug in QBW restart the convert Verify the file is okay in QBD. This is also a release issue for 5.0r5 - have customer update their program to r7 (r6 won't convert at all)
150 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
151 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
152 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
153 Invalid account criteria type An error occurred during a search problem doing find Exit qb try find again. Attempt same steps in sample. Report steps to reproduce.
154 Unknown axis type Reports bug problem displaying a report exit qb try report again. Try sample company - get steps to reproduce with exact report they are trying to reproduce
155 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
156 Unable to save budget C-Index was unable to write a budget record to disk Unable to record budget Possible resource issue. Check resources, reboot computer and restart QB. End task on non-essential applications. QuickBooks should try to roll back. If not, verify, try rebuild if necessary
157 Can't find column in tx dictionary Reports bug. Column ID was missing problem displaying a report exit qb try report again. Try sample company - get steps to reproduce with exact report they are trying to reproduce
158 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
159 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
160 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
161 Damaged budget. Not enough room in the buffer when converting the Quicken or QuickBooks Dos budget problem converting budget information from Quicken or QB DOS. Possible resource issue. Check resources, reboot computer and restart QB. End task on non-essential applications. Is source file healthy? Verify or validate data in source version. If damaged, repair and convert again. Should happen only in debug version
162 Damaged account. Problem when converting QuickBooks Dos account Problem converting QBD account information. Is source file healthy? Verify or validate data in source version. If damaged, repair and convert again. If unable to correct file in QBD restore a backup or refer customer to ICU. Should happen only in debug version
163 Damaged transaction. Problem when converting QuickBooks Dos transaction Problem converting QBD transactions. Is source file healthy? Verify or validate data in source version. If damaged, repair and convert again. If unable to correct file in QBD restore a backup or refer customer to ICU. Should happen only in debug version
164 Damaged transaction Normaly happens during a Quicken DOS convert Problem converting Quicken DOS transactions. Seen with sales tax line items on the invoices conflicting with the default sales tax item. Is source data file healthy? If not, repair and convert again. For sales tax line - edit the problem invoices and reconvert. Try converting to a lower version of QB - 3.0)> If unable to correct in quicken refer to ICU for further options.
165 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
166 Damaged category. Problem when converting Quicken or QuickBooks Dos category Should only appear in association with conversion from Quicken or QB DOS. Is source file healthy? Verify or validate data in source version. If damaged, repair and convert again. If unable to correct file in QBD restore a backup or refer customer to ICU. Should happen only in debug version
167 Problem with Quicken or DOS Quickbooks file during convert A bad trailer record was found during convert Should only appear in association with conversion from Quicken or QB DOS. Is source data file healthy? If not, repair and convert again. If unable to correct submit to ICU for further options.
168 Damaged name record. Converting from QuickBooks Dos; the length of the initials or last name is too long. Should only be seen Converting from QuickBooks Dos; having problems converting a employee Employee name has not been converted - customer will have to enter employee and edit the transactions associated with employee to the correct name. If a rebuilt name was created edit the rebuild name to be the employee
169 Damaged serial number. Converting from QuickBooks Dos; the length of the serial number is too long. Should only appear in association with conversion from QB DOS. Should not affect the conversion of the file.
170 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
171 Bad name type Converting from QuickBooks Dos; the type of the name is unknown (no customer neither vendor). Should only appear in association with conversion from QB DOS - problem converting the names Is source data file healthy? If not, repair and convert again. If convert completed look for a possible rebuilt name correct as needed. If unable to correct submit to ICU for further options.
172 There is a running balance while sorting Transaction list bug Problem displaying report Try in safe-mode. Attempt same report in sample company. Verify rebuild if needed. Try other reports. Report what report the error is occuring on.
173 SORTBY_REG in this type of search is disallowed (search by date, or name, or item) Transaction list bug Problem displaying report - also seen when trying to view a memorized statement charge with no source account attached. Try in safe-mode. Attempt same report in sample company. Verify rebuild if needed. Try other reports. Report what report the error is occuring on. If error is occuring with memorized transaction - delete transaction and enter again.
174 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
175 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
176 Error reading Quicken or QuickBooks Dos data file Quickbooks faild to recognize a record from a Quicken or QuickBooks DOS data file. If Quicken (and any add on products) can read and manipulate the data, this may indicate a bug. Should only appear in association with conversion from Quicken or QB DOS. Problem reading a record in Quicken or QBD Verify that the data can be successfully read and manipulated in Quicken or QuickBooks (and any add on products whose data is being converted) If so, restart the convert. If unable to correct contact ICU for further options
177 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
178 DeleteAny() failed cindex failed to delete a record Transaction record could not be deleted. Close file. Opend file - QBW should try to roll back. If not, try verify data and rebuild if necessary V is the cindex error
179 Link not found in ReadLinksTrans2Targ() QuickBooks failed to find the link for a target. Problem locating a link for the transation Verify rebuild if necessary. Check for link damage - open invoice, unpaid bills, cbbs, undeposited funds, etc. Delete the problem transactions and re-enter. V= the source target number
180 Targ not tax item in TaxTargNumToRevenue() A target that is supposed to be a tax line is not a Tax line A target that is supposed to be a tax line is not a Tax line Verify and Rebuild if necessary. Delete thr problem transaction and re-enter.
181 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
182 Tried to read from a virtual txList We tried to do an illegal operation on virtual transaction list, i.e. cogs and inventory problem displaying report that contains "virtual" transactions Try another report. See if same problem occurs in sample company. Verify rebuild if necessary. Narrow down items on report - see if able to determine inventory item causing problem - create new item, merge old item into the new. We tried to read rom a virtual txlist
183 Tried to read from a virtual txList We tried to do an illegal operation on a virtual target, i.e. cogs and inventory problem displaying report that contains "virtual" transactions Try another report. See if same problem occurs in sample company. Verify rebuild if necessary. Narrow down items on report - see if able to determine inventory item causing problem - create new item, merge old item into the new. We tried to read rom a virtual target
184 A target was outside the date range A report bug occurred such that it selected a target that was outside the user specified date range. problem displaying report See KB for some known causes of this error. Most common fix it to make sure there is a date in the from and to of the customize report screen V = 0 or 1>
185 Unable to open mirror file CIndex could not open the mirror file CIndex could not open the mirror file Try the same steps in sample company. Reinstall if necessary. Report steps to reproduce. Supposedly we don't support mirror files anymore, so something really weird happened.
186 Pick list item text too long. QuickBooks tried to add a new item to a pick list but the item text was too long problems adding information to a pick list try adding name again this time make name shorter.
187 EdListUndoProc called without a list QuickBooks is trying to process an 'Undo' message for one of the lists, but we don't know which one. Problems displaying message on one of the lists. Try same steps in sample company - reinstall if needed. Report steps customer was doing. pEdList is zero
188 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V= and activity which lead to error. Can you duplicate?
189 bit string > 64K QBW tried to allocate a bit map (an array of bits) that is more than 64K long QBW had problem allocating memory Exit out of the program - close all other programs - reboot if necessary - try safe mode - see if same error occurs in sample company - reinstall if necessary
190 Error encounted while replacing memorixed report QBW couldn't allocate memory for the new report to replace an existing report Problem memorizing a Memorized Reports Data is fine. Report was not memorized. Need to make some more memory available. End task on extraneous avtivities. Safe mode a possibility.
191 Unable to build transaction lists for statements Probably due to allocation failure. ? Problem displaying statement Need to make more memory available. End task on extraneous avtivities. Safe mode a possibility. See if same problem occurs in sample company. Verify rebuild if necessary.
192 Not enough memory for statement edit form Can't print statement because memory allocation failure Problem printing statement Need to make more memory available. End task on extraneous avtivities. Safe mode a possibility. See if same problem occurs in sample company. Verify rebuild if necessary.
193 No string defined for preference ID or bad prefid QuickBooks is asking for a preference from QBW.INI but the preference ID is unknown. Possibly QBW failed to load a resource string because the qbwin.dll has been corrupted. QB had problem pulling information from QBW.INI Try rebooting and restart QB. See if same problem occurs in sample company. Reinstall if necessary.
194 Unable to build the toolbar QuickBooks tried to build the toolbar but was unable to finish because of a corrupted resource file or lack of memory. Problem displaying toolbar Try sample company. Close all programs - reboot if necessary - try safe mode. Reinstall if necessary The call to Toolbar(...) returns NULL
195 Reminders memory error No memory to create tCrit. problem displaying reminders Close all programs - reboot if neceaary - try safe mode. See if error occurs in sample company. Verify rebuild if necessary GetTCrit returns NULL
196 Reminders transaction list error An error occurred while creating transaction lists for reminders problem displaying reminders Close all programs - reboot if neceaary - try safe mode. See if error occurs in sample company. Verify rebuild if necessary V = ID indicating which transaction list indicated the failure
197 Unable to create reminders window An error occurred while creating a reminders window. problem displaying reminders Close all programs - reboot if neceaary - try safe mode. See if error occurs in sample company. Verify rebuild if necessary CreateRemindPopup returned NULL
198 SearchTxListForTarg() sortby NOTHING QuickBooks is trying to search a transaction list with no sorting criteria problem displaying a report Close all programs - reboot if neceaary - try safe mode. See if error occurs in sample company. Try another report - if it is a memorized report create a new report. Verify rebuild if necessary ABORTs
199 Purchase orders memory error No memory to create tCrit problem displaying purchase orders Free more memory. End task on extraneous activities. Try safe-mode. Verify rebuild if necessary.
200 Purchase Orders transaction list error Couldn't create tx list of purchase orders Problem generating report on Purchase Orders, such as, Open Purchase Order report. Free more memory. Verify the file, rebuild if indicated. Try generating a Transaction Report filtered for Purchase Orders.
201 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
202 Unknown tx list in reminders QuickBooks tried to find a position in the reminder list, but could not identify the txList. Problem displaying the reminders list. report immediately! Include full error message I.e., L=, M=, C=. Note what action generated error. Verify file, rebuild if indicated. Check QBWINLOG. V is code indicating which function had error.
203 Insufficient memory to print mailing labels Insufficient memroy to print mailing labels Problem printing mailing labels Make more memory available. End task on non-essential routines. May require system re-boot. Check Printer memory settings. Try same steps in sample company, try with smaller number of lables.
204 Can't find list print resource QuickBooks is trying to print one of the lists but was unable to load necessary information from resource file. Problem printing a list such as COA, Items, etc. If possible, resort troubled list (show-all marked). Examine list for any anomolies (blank spaces, garbled text, etc.). Test in sample company. Verify file, Rebuild if indicated. Reinstall if necessary
205 There is not enough memory to complete the export Ran out of memory during export Export fails due to lack of sufficient virtual memory. With QBM - the QB application icon had been moved into the components folder. Free up memory - exit program re-enter - reboot if necessar. Check free space on HD. Try sample company - reinstall if necessary. With QBM - move the QB application icon back into the main folder and try exporting again.
206 Couldn't write a data line to the import file QuickBooks was exporting the line into the IIF file and could not complete the operation due to the low memory or not enough disk space. Import fails. Typically related to media error or lack of space. Disk may be full, or some other media problem. Check drive free space. If adequate, run chkdsk. Verify file & rebuild if indicated.
207 Couldn't write a definition line to the import file QuickBooks was exporting the line into the IIF file and could not complete the operation due to the low memory or not enough disk space Problem exporting lists. Disk may be full, or some other media problem. Check drive free space. If adequate, run chkdsk. Verify file & rebuild if indicated. Look for any possible problems on the lists that you are trying to export.
208 Can't open file for export QuickBooks can't open the .IIF file to begin exporting data Unable to open export file Is the destination disk full? Path and filename okay? If floppy disk, has it been formatted on this machine? Will export execute to HD? Try in sample company.
209 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
210 No String Defined for ini ID or bad ini ID QBW is looking for an item in the QBW.INI file which it hasn't even defined. QBW had problems reading information from QBW.INI file - often customer number Action depends on the V number. The program is looking for information that we didn't define. How does customers QBW.INI file compare to yours? Significant omissions. Make sure the customer number is showing correct. Rename QBW.INI and reinstall QBW. V= reside
211 Not even enough memory to allocate list of txLists QBW keeps a master list containing lists of transactions that are currently in use. There isn't enough memory to create this list May be encountered if user is sequentially entering huge amount of transactions. Occurs when system memory is depleted Memory is very low, exit as many applications as you can and try again. Try restarting windows, ending task on extraneous applications. Check virtual memory management; is Windows managing? Check free space on HD. If low, have customer clear up space. Try sample company - reinstall if necessary. Aborts
212 Unable to read version number QB can't read the file version number from the QBW file QBW does not recognize the version number of the file. (example - open a QBW 4.0 file in 3.0) Check to see if sample company opens, if sample opens QB installation is OK and problem is related to the data file. What version of QB was file created in - has customer upgraded program - check their registration. Copy file to new location on local HD and try to open. If open fails again and customer had not upgraded most likely header damage. Restore a backup or contact ICU for options of Data Recovery
213 unknown unknown unknown Please report the error. include full error message i.e. L=, M=, and V=. Verify QB version and release.
214 String Bucket:> Too many rows or columns The report cannot be generated because there is not enough meory to hold all the text required to display the report Problem displaying report Close other applications and try again. Restart system. Check TSR's, end non-essential applications. Try another report - with less information filtered
215 Report string bucket locked The memory that holds the text for the report being generated cannot be moved in memory and therefore cannot grow to hold more text Problem displaying report Close other applications and try again. Restart system. Check TSR's, end non-essential applications. Try another report - with less information filtered - smaller date range - etc.
216 Report string moved during really The memory holding the text for the report being generated was moved in memory, the report will be really messed up so we abort Problem displaying report Close other applications and try again. If this fails, restart windows and end task on non-essential applications. Check free space on HD. If this doesn't work there is nothing we can do to enable this report to run. See if error occurs in sample - reinstall if necessary. Verify rebuild if necessar.
217 Realloc of report strings failed QB has partially completed the generation of the report and run out of memory. Rather than jeopardize the data, QB will stop generating the report. Problem displaying report Close other applications and try again. If this fails, restart windows and end task on non-essential applications. Check free space on HD. If this doesn't work there is nothing we can do to enable this report to run. See if error occurs in sample - reinstall if necessary. Verify rebuild if necessar.
218 Unable to find transaction in either axis This is a debugging message which cannot appear in the release product Should not be encountered in released version of QB. Please report the error.. include full error message i.e. L=, M=, and V=
219 Unknown tx list The location in memory of the list of transactions for the report being generated is not what QBW expects it to be therefore we can't use it problem displaying report Check system resoucres - reboot if necessary - try file local. Try in sample company - reinstall if needed. Try changing the filters - different date range etc. Report what report they are trying to run.
220 Unable to find transaction in sub-column axis Only in debug version Should not be encountered in released version of QB unless customer has gottten into DeBug accidentally. Check for DeBug options - help debug at bottom. If present, restart QB. If DeBug not present Please report the error.. include full error message i.e. L=, M=, and V= and activity that lead to error.
221 unknown unknown Should not be encountered. Please report the error.. include full error message i.e. L=, M=, and V=
222 Unable to delete link QBW is unable to delete a record which links two transactions from the data file Problem deleting a link attached to the transaction Verify data and rebuild the file if verify fails. Attempt to delete transaction again. If message persists when deleting transaction check QBWIN.LOG. If verify is clean and still unable to delete the transaction restore from a backup or contact ICU for further options V=Cindex code returned from cdelete
223 unknown unknown unknown Please report the error.. include full error message i.e. L=, M=, and V=
224 Trying to read target number zero QBW tried to read an invalid split line for a transaction or a memorized transaction. The data file may or may not be damaged. It may just be QBW has a bug which causes it to look for an invalid split line QBW is having a problem reading part of the target split. This error will sometimes also occur when trying to look at a transaction history because the transaction it is linking to is gone or damaged. This is a non-fatal error and you should be able to continue working in the file. Memorize, delete and re-enter the problem transaction. Verify file - rebuild if necessary. Check for any link damage - open invoice, unpaid bills, undeposited funds, cbbs. Review KB for some examples known problem and further troublshooting
225 Trying to read invalid master record QBW tried to read an invalid transaction or memorized transaction. The data file is most likely damaged QBW is having a problem reading the master of the transaction. This error will sometimes also occur when trying to look at a transaction history because the transaction it is linking to is gone or damaged. This is a non-fatal error and you should be able to continue working in the file. Memorize, delete and re-enter the problem transaction. Verify file - rebuild if necessary. Check for any link damage - open invoice, unpaid bills, undeposited funds, cbbs. Review KB for some examples known problem and further troublshooting
226 Insufficient memory to build missing check form The system is REALLY out of memory The system is REALLY out of memory Close other applications and try again. Restart system. Check TSR's, end non-essential applications. If error persists check Virtual Memory management, is Windows managing? Check free space on HD. See if error exists in sample company - reinstall if necessary.
227 Report line is wider then maximum allowed One of the lines in the report being printed is wider then the maximum QBW can print across the defined page. This is coding error. Problem printing a report QB has made a mistake in figuring out how to do the printing. The user could try making the margin smaller or changing the font to a smaller size. Try printing with default fonts. Check paper size. Please report the error with all details, report being printed (details), font, printer model and driver version. Include system info.
228 Setting key in IsDupDoc If QBW was recording a transaction, this is a coding error in the code which searches for duplicate document numbers. If QBW was verifying the data, this is a coding error during the verification of account or name balances Problem recording transaction and searching for duplicate document numbers If we were recording the transaction, the user could try and turn off duplicate document number checking for the document type they are recording. If it was during verify data there isn't much they can do. Restore a backup or contact ICU V= CIndex error from dsetkey
229 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
230 Couldn't put link because one of the transactions does not exist During import QBW encountered where one transaction was supposed to be linked to another and one of them or both of them didn't exist. This could be because they were not in the import file or QBW encountered an error when saving them. QBW does not import links only transactions and lists Check the import file. Make sure it is in the correct format. Try importing into sample or new company - delete the bad transaction from the import file and try again.
231 Error encountered while clearing old window positions While saving the users desktop QB tried to save the same windows trice QBW had a problem saving the windows positions. Have the user close and open QBW again if they are using the save desktop on start up preference. If they are using the save this desktop preference, have them resave it. Should go away if preference reset to Don't save desktop.
232 Error encountered while loading saved window positions While restoring the users desktop during startup QBW tried to restore the same window twice. This is a coding error or a datafile error QBW had a problem loading the windows positions Open file supressing the desktop. Have the user close and open QBW again if they are using the save desktop on start up preference. If they are using the save this desktop preference, have them resave it. Should go away if preference reset to Don't save desktop. V=nextrec value
233 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
234 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
235 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
236 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
237 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
238 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
239 BalType attempt to divide by zero QBW tried to divide an amount or quantity by 0 with an undefined mathematical operation. This is a coding error. QBW tried to divide an amount by 0 known problem with Progress Invoicing from an estimate - this is a none fatal error message - click ok on error. If occuring in different area - verify rebuild if necessary - try sample company - reinstall is needed - Report steps.
240 Can't open file for import The IIF file specified cannot be opened QBW had a problem opening the import file The file may be in use by another application, for example a word processor or the file may not be an IIF file or hard drive problem. Can you copy file to new location?
241 Can't open default chart of accounts file during the creation of a company the user specified a preset chart of accounts to use. When we tried to open the CHARTS.IIF file within QB> failed When trying to create the file QB is unable to open the default COA information to create a file. File has most likely been deleted by the user from the QB directory. If it is there it may be used by another applications. If none of the above is true have them close windows and reboot their computer. Try in sample company. If it is still not working reinstall QBW
242 No sort specified for tx report During the creation of the report QBW tried to create it without a sort order. This is a coding error problem displaying a report The action to take depends on which report caused the problem. Try to find another way of getting the data they are looking for. Are resources OK. Can the report be filtered for a small date range or fewer names?> Verify file - rebuild if needed. see if able to get same error in sample - Report what report is causing the error
243 FindTarg in transaction failed QBW was searching for a particular split line and could not find it. This means data file may be corrupted Running a find, getting transaction history, or detail report where split is required and it is unable to locate the split information Resort COA, Names, and Items (show-all marked). Can the transaction be accessed from another source (register, QR, etc) Have the user free up some memory and try again. If it still fails, run verify data and try rebuilding the data file if necessary. V=targnum
244 Insufficient memory for resetting header, footer information to default values QBW requested memory to reset the header and footer in a report to the default and we could not get the memory Problem displaying report because of memory issues Memory is very low, exit as many applications as you can and try again. Try restarting windows, ending task on extraneous applications. Check free space on HD. See if error occurs in sample company - reinstall if necessary.
245 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
246 QuickZoom on an 'other' name type is not fully supported yet QBW allowed the user to QuickZoom on a report that doesn't support QuickZoom. This is a coding error Customer did a quickzoom on a report but should not have See if problem happens in a new company. Reinstall Quickbooks if necessary. If able to reproduce - Report steps.
247 Attempt to Quickzoom in an unknown name type axis QBW allowed the user to QuickZoom when it doesn't know how to create the QuickZoom report the user would expect Customer did a quickzoom on a report but should not have See if problem happens in a new company. Reinstall Quickbooks if necessary. If able to reproduce - Report steps.
248 Unable to memorize this transaction The user is trying to memorize a transaction and QBW doesn't know what type of transaction it is. This is a coding error. When trying to memorize a transaction QBW is not able to read what typd of transaction it is Verify rebuild if necessary - Delete and recreate transaction attempting to memorize - try memorizing again - if still unable to memorize - try in new a company reinstall if necessary
249 invalid memory handle This is a debuging message. If you see it there is a real problem Should not be encountered in a publicly released version. Check version and release information. If this is a valid consumer release of QB, Report full error message and steps leading to error generation.
250 No message ID specified QBW was trying to put up a warning message of some type and the text it is supposed to display is undefined. This is a coding error. QBW is unable to display warning message check system resoucres - reboot if necessary - try file local. Try in sample company - reinstall if needed. Report steps to reproduce is error still occurs
251 SortTxList() with unknown key sort QBW was creating a list of transactions and there was no sort order specified. This is a coding error. problem displaying report Try another report. See if same problem occurs in sample company Verify rebuild if necessary. Verify file rebuild if necessary
252 SearchTxListForTarg() with unknown key sort. QBW was searching a list of transactions and the list is not sorted in a known way. This is a coding error. problem displaying a report verify rebuild if necessary - try another report - try changing the filters or customizing to change information changing sort by etc. Try same report in sample company - reinstall if necessary
253 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
254 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
255 TxListGetItem() without fo range Item number This is a debuging message. If you see it there is a real problem unknown Check the ctrl-1 screen for what version are they using - if it is a normal version of QB Report all system information and steps to reproduce
256 TxListGetNextItem() without the range item pointer This is a debuging message. If you see it there is a real problem unknown Check the ctrl-1 screen for what version are they using - if it is a normal version of QB Report all system information and steps to reproduce
257 Freeing Locked memory Memory must be "unlockec" before QB can tell Windows it isn't using it anymore. This is a case where QB is trying to give it back to Windows with it "locked" QB did not release the memory correctly back to windows See if you can reproduce the problem without changing any of the settings. Please report exact steps to reproduce and what programs are also running.
258 BuildFonts() - hFont non-zero (Please Continue) When creating the fonts used in a report we encountered one which had not properly been disposed of the last time. This is probably a coding error. Problem displaying the report with the current format. See if you are able to reproduce. Does the error occur with other reports?> Try changing the format of the default font on the reports - note what fonts were selected before you change. See if error occurs in sample.
259 Glue Free (NULL) Qb thought it needed to give some memory back to Windows, but thendidn't specify which piece of memory QB did not release the memory correctly back to windows See if you can reproduce the problem without changing any of the settings. Please report exact steps to reproduce and what programs are also running.
260 Unable to close data file! C-Index had a problem closing the data file. The file might be corrupted. Qb had a problem closing the data file because of a problem in the file structure (C-Index) Make a copy of the file - go into the copy of the file. Rebuild, bypassing the backup (which will first close the file) by holding down the control key when clicking on rebuild. V= CIndex error from dclose
261 Do Working total is 0 When the program went to put up a thermometer, QB told the window that there were zero steps to complete. Depending on the operation it could mean that there's some problem with the data file (giving us zero items) or a simple programing error. QB is unsure of where to set the Progress meter for the action. The progress meter is showing on step 0 of 0. Try to reproduce the error. See if error occurs in sample. Reinstall QBW if necessary. Try to reproduce on different system. Report all system information
262 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
263 Mmaulreg() unexpectedly received TLP_TXLIST_REGEN message the register was sent a message it doen't understand A 'regen' should only be sent to a txlist in pay bills or receive payments. This could be caused by internal memory corruption. The register was sent a message it doen't understand. Message should only occur on pay bills or receive payments. Close the register. Try same steps again. See if error just occurs with one account - create a new account merge old into the new. (same steps if only occurs with one name)> See if error occurs with other files. If error is still occuring - restart windows try once more. Reinstall QBW if necessary
264 Link already has record number in RecordLinks() QBW attempted to assign a duplicate record number to link. The link was not recorded and we stopped trying to link the transactions together. QBW did not link the trasactions together correctly. Memorize and delete the transaction which was added or edited. Verify file, if verify fails, rebuild file as necessary. Re-enter the transactions trying to link them together again. If error still occurs complete delete both transactions and re-enter fresh.
265 Unable to delete sibling link. Each link has two records in our data file. This error means that while deleting a link, we couldn't find the related link. QBW did not find the second half of a link pair it was trying to delete. It is usually because there is either a transaction that is damaged or the linke is gone. Memorize and delete the problem transactions. When you are looking for link damage - this is a good error to find because you have found the source of the reports not matching. After various link reports are clean verify might still fail with "orphan" links - there will not be any transaction information - a rebuild should clean these up. V= CIndex error from cdelete
266 RecordLinks (2) unable to get next record number. C-Index was unable to assign a record number to the link we were generating. QBW did not correctly record the link that is being generated. Memorize and delete the transaction which was added or edited. Verify file, if verify fails, rebuild file as necessary. Re-enter the transactions trying to link them together again. If error still occurs complete delete both transactions and re-enter fresh. ABORTs
267 SelList - trying to restore parent window proc but there isn't one. QB was tring to hide a drop-down list but couldn't find a parent window QB was tring to hide or close a drop-down list but couldn't find the window where the list was being displayed from. Data should be fine. Quit QB and restart see if you can reproduce the error. If you can try in the sample reinstall if needed. Report the steps.
268 SelListShow() - reentered We interrupted ourselves while trying to show a drop-down list. A bug in the program, combined with some aspect of the users data and system setup has caused a possible endless loop. QBW is having a problem showing a drop down list. Try to reproduce the error. See if error occurs in sample. Rebuild if necessary. Reinstall QBW if necessary. If error still occurs Report steps to reproduce. ABORTs. Probably to prevent an endless loop.
269 SelListShow() called while in SelListHide() We were trying to hide and show a drop-down at the same time QBW is having a problem displaying a drop down list. We are trying to close and open the list at the same time. Try to reproduce the error. See if error occurs in sample. Rebuild if necessary. Reinstall QBW if necessary. If error still occurs Report steps to reproduce. ABORTs. Probably to prevent an endless loop.
270 SelListHide() Called while in SelListShow() We interrupted ourselves while trying to hide a drop-down list. QBW is having> a problem closing a drop down list. Try to reproduce the error. See if error occurs in sample. Rebuild if necessary. Reinstall QBW if necessary. If error still occurs Report steps to reproduce. ABORTs. Probably to prevent an endless loop.
271 GetBitN - Range error Bitmaps are mostly used for selected items in report filters. Here we're trying to set a bit that is out of bounds of allocated memory. Each target has a series of flags (called bitmaps) that can be set for faster reporting. (example> if it is paid, or marked to print are flags). We are trying to set this to something that is not possible. Try to reproduce the error both in their file and in sample. Verify the file and rebuild if necessary. Try to narrow down to the transaction that is causing the problem and delete it.
272 SetBitN - range error Bitmaps are mostly used for selected items in report filters. Here we're trying to set a bit that is out of bounds of allocated memory. Each target has a series of flags (called bitmaps) that can be set for faster reporting. (example> if it is paid, or marked to print are flags). We are trying to set this to something that is not possible. Try to reproduce the error both in their file and in sample. Verify the file and rebuild if necessary. Try to narrow down to the transaction that is causing the problem and delete it. If same error occurs in sample - get exact steps and report
273 ClearBitN - range error Bitmaps are mostly used for selected items in report filters, but are also used during verify/rebuild. Here we're trying to clear a bit that is out of bounds of allocated memory. Each target has a series of flags (called bitmaps) that can be set for faster reporting. (example> if it is paid, or marked to print are flags). We are trying to set this to something that is not possible. Try to reproduce the error both in their file and in sample. Verify the file and rebuild if necessary. Try to narrow down to the transaction that is causing the problem and delete it. If same error occurs in sample - get exact steps and report
274 FormMgrAddObj() called before FormMgrSetWindow() Internal problem while trying to display a form QBW had a problem displaying a form. Try to reproduce the error both in their file and in sample. Verify the file and rebuild if necessary. Reinstall QBW as necessary. If error still occurs Report exact steps. ABORTs
275 FormMgrSetWindow - bad window Internal problem while trying to display a form. Tried to use a non-Quickbooks window to display Quickbooks data. QBW had a problem displaying a form. Try to reproduce the error both in their file and in sample. Verify the file and rebuild if necessary. Reinstall QBW as necessary. If error still occurs Report exact steps. ABORTs
276 Out of string buckets Internal error while generating a report. Getting this message means that we've trashed memory. Error ususally occurs when trying to generate a report and there is some corrupt memory. What report were they running - try different report. Try same report again with different filters (smaller date range) Try same report in the sample company. Reboot system and reinstall QB is necessary. Report steps to reproduce.
277 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
278 Invalid bucket ID. Internal error while generating a report. Getting this message means that we've trashed memory Error ususally occurs when trying to generate a report and there is some corrupt memory. What report were they running - try different report. Try same report again with different filters (smaller date range) Try same report in the sample company. Reboot system and reinstall QB is necessary. Report steps to reproduce.
279 BucketGetPtr - Bad offset The report corrupted itself in memory Error ususally occurs when trying to generate a report and there is some corrupt memory. What report were they running - try different report. Try same report again with different filters (smaller date range) Try same report in the sample company. Reboot system and reinstall QB is necessary. Report steps to reproduce.
280 Could not create a vendor name during rebuild. QuickBooks tried to create the vendor for Sales Tax payable target during rebuild. QBW unsuccessfully tried to create a vendor for Sales Tax Payable during rebuild. Try to add some names to the other names list (the number will depend on how large the reference numbers are) Try rebuilding again. If you are unable to add the names to the other name list - restore a backup or submit for data recovery
281 Insufficient memory to complete operation The report is out of memory The report is out of memory Exit QBW and try again. If error still occurs try with less columns or rows. Try different report.
282 hmemcmpSO of different offsets Currently this can only happen when we're trying to determine if a transaction has changed. Something's corrupted in memory but the data file should be okay. A Windows only problem QBW is having a problem determine if the transaction has changed. Close all windows restart QBW and try again. Reboot system if needed.
283 Uneven Begin/End transaction This is a logic error in the program or the user has found a new path that we weren't aware of. Detected when closing the data file. Problem closing the datafile, customer might have run the payroll checkup in multiuser mode Close file and restart QBW. Verify file to assure data is not damaged. V=the current write count, which is supposed to be zero
284 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
285 Duplicate serial number Duplicate serial number encountered while converting Quickbooks/Dos data Problems converting a QBD file Quit convert go back into DOS run QBUTIL, check associated KBs>
286 Invalid window in GetWindowState() While saving the desktop we ran across a window that wasn't a window. Windows only, not Mac Problem saving the desktop, or displaying the saved desktop If error is occuring when opening file - saved desktop might be damaged. Try opening file holding down the alt key to bypass loading the desktop. Save a new desktop (in 6.0 and later the desktop preference is user specific - error might happen for just one user)
287 Mismatched calls to QBWAllowDrawing() In order to speed up screen refreshes sometimes we turn off drawing when we know we're going to draw something again anyway. This error is telling us we turned drawing on or off too many times without a matching call to turn it back on or off. Problem with screen refresh/draw. Please report the error. Internal logic error or data problem. Restart Quickbooks. The screen might look garbled though.
288 Warning: overwriting existing font handle We forgot to free the old fonts before trying to create the new ones while processing the report format dialog. Windows only Problem displaying the fonts while processing report format dialog Restart Quickbooks, reboot is system resources are low. Report steps including report and any special formating or fonts V= font number
289 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
290 Link type >=32. Too many bits for SetLinkTypeCritBits() We have the ability internally to search for specific type of links. This error is telling us that we're searching for too many types (32 is the max) but since we have fewer then 10 types this shouldn't arise. If it does, we've corrupted memory. QBW is trying to search for something in the file it should not be able to search for. We should not have more than 32 link types, in this case QBW is trying to search for more that 32. Find out which customization is causing the problem, or which aspect of Find and report. Verify, rebuild if necessary. Delete any transactions that might be causing the error to occur.
291 No memory for style for invoice, credit memos etc. We ran out of memory when trying to create a customized form. Otherwise, an unspecified error. Problem displaying a customized form Free up memory and restart Quickbooks. If working with templates, edit the offending template and save changes. Default the templetes causing problems (review c=91 and associated KBs) ABORTs
292 EL_ACCNT: EP_CRITAND, unknown combination. In Quickzoom(tm) we AND together two separate report filters. Here the account filters are not andable. This might happen if you were trying to and "Payroll Accounts" with "All A/P and Sales Tax" Problem displaying transactions or report from a quickzoom Please report the error, recording which report is being run, and which filters and customization has been chosen. Don't QuickZoom in this instance. V= crit1 (hiword) and crit2 (loword).
293 This is a problem with the DOS quickBooks list file We detected some sort of damage in the QB/DOS QMT file problem converting a QBDOS file Run QBUTIL, try converting again - submit case for data recovery
294 Error reading QuickInvoice file. C-Index couldn't read the QI file for some unknown reason Problems reading the QuickInvoice file index There could be a .QID file thats not a QuickInvoice file. Rename it to something else so we don't try converting it.
295 Can't release Quick Tour Close Windows and restore While quiting we had a problem "letting go" of the quick tour Problem completely exiting the quick Tour (only occurs in older version of QBW) close all programs exit windows and try again.
296 If you are doing a normal import, this is a drat. If you have fiddled with the import file this message is not a drate this is a debug message Something is wrong with the IIF file or there is a bug in import Something is wrong with the IIF file or there is a bug in import Run verify, rebuild if necessary. What type of information was being imported into the file - might have to delete some of the information that was being imported in.
297 Unexpected error: missing 1099 resource or wrong ID for an invoice window. If processing 1099s, a resource could not be read due to a lack of memory or corrupt program file. If showing a sales form, for some reason QB thought a purchase order was being shown, but using non-PO code to do it. Problem running the program because of lack of memory or corrupt program. Reboot system try again. Reinstall if necessary. Make sure the QBW installing in the correct directory (review KB) Should probably be two different errors.
298 wrong index number or key count problem. The program was confused about an index or a key count The program was confused about an index or a key count Verify, rebuild if necessary. Try to delete transaction causing error. Restore a backup or send to Data Recovery For the GetIndexList, V= index and ABORTs. Should probably be two different errors.
299 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
300 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
301 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
302 Insufficient memory for edlist disk buffer We ran out of memory starting up. The data is fine Not enough memory for one of the qbw buffers Free memory reboot system if necessary try to launch another file.
303 Display index corrupted The data was corrupted either on disk or in memory List is showing on the screen incorrectly Resort all the lists close and re-open the file try again. Check lists for any incorrect sorting (bank account with expense sub)
304 Unable to create Image file C-Index couldn't create the Imaging file. Disk might be full? The data file will not be opened. Program is not able to create startup files on the hard drive. check hard disk space. Check to see if customer is accessing across network may not have rights to write to the server, check to see if the files are locked or drive is locked by third party software such as norton V= CIndex error from CIdbcreate
305 Error in dsetkey (TBYITEM) Error in creating a cindex search key. The routine "dsetkey" failed when using "item" key. Problem could be in several locations. Error trying to create a search for part of the index Verify, rebuild if needed. Remove transaction causing the problem. Restore backup or contact ICU for further options of data recovery V= CIndex error
306 Error in dsetkey (TBYDATE) See 305 (used "date" key) Error trying to create a search for part of the index Verify, rebuild if needed. Remove transaction causing the problem. Restore backup or contact ICU for further options of data recovery V= CIndex error
307 Error in droproot. When updating, if the version is less or equal than 14 (Kremlin) we need to rebuild any index which contains a BalType. The routine "droproot" failed during that process. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= CIndex error
308 Error in droproot. When updating, if the version is less or equal than 14 (Kremlin) we need to rebuild any index which contains a BalType. The routine "droproot" failed during that process. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= CIndex error
309 Error in addroot When updating, if the version is less or equal than 14 (Kremlin) we need to rebuild any index which contains a BalType. The routine "addroot" failed adding new date key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= CIndex error
310 Error in addroot When updating, if the version is less or equal than 14 (Kremlin) we need to rebuild any index which contains a BalType. The routine "addroot" failed adding new name key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= CIndex error
311 Too many lines in reminder list. QuickBooks could not display the reminder list because there were too many lines. QBW is not able to display the reminders list because there are too many lines Limitation should be 32,000 reminder lines. What has customer used reminders for in past?> How did information display before error started occuring? Report steps customer might have taken to max out the list.
312 Unable to correct rounding errors in budgets. QuickBooks tried to fix the rounding for the given time period when building a report but could not find the amount with rounded amount. QuickBooks tried to fix the rounding for the given time period when building a report but could not find the amount with rounded amount. Try changing the amounts. If changing the budget amounts works Report date range and amounts customer had budgeted.
313 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
314 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
315 Assertion failed. This is a miscellaneous error. It is used all over the program, so it is hard to say how bad it is, or what the root cause of the problem is. This is a miscellaneous error. It is used all over the program, so it is hard to say how bad it is, or what the root cause of the problem is. This is often a harmless error message, but often follows or ipfs. Verify, rebuild if necessary. Try same steps in sample company. Review KBs for know problems when error would occur Should make the "a" value the V in the error code.
316 Transaction buffer not allocated for Qty trans most likely out of memory A internal buffer is not correctly allocating memory for a transaction Verify, rebuild if necessary. Try to delete transaction causing error. Restore a backup or send to Data Recovery
317 Invalid index type in Write and Read low level code. Error when trying to write or read data. Error when trying to write or read data. Verify, rebuild if necessary. Try to delete transaction causing error. Restore a backup or send to Data Recovery Its not just WriteAny. Its all over diskio.c
318 Unable to create temporary window. Only on MAC. Due to a resource or memory problem Error should only happen in QBM. Unable to create window because or resource problem Try freeing some memory. If that doesn't work, reinstall QB.
319 Wrong button style. MAC only. QB tried to create a button, but the button type was a bad value. Error should only happen in QBM. Unable to create a button. Restart and try again. Try sample company, reinstall if necessary. If it is occuring on just that file restore a backup or submit to Data Recovery
320 Error creating popup menu for pick list Error creating popup menu for pick list Error creating popup menu for pick list Exit QBW and try again. Try same steps in sample company. Reinstall if necessary. If problem is data related verify, rebuild if necessary - submit for Data Recovery.
321 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
322 Insufficient memory for update Insufficient memory for update Insufficient memory for update free memory reboot system if necessary and try update again
323 Error dropping accnt key (7to9Targets) When updating we need to rebuild an index. The routine "droproot" failed removing account key Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again. V= CIndex error code
324 Error dropping item key (7to9Targets) When updating we need to rebuild an index. The routine "droproot" failed removing item key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
325 Error adding new accnt key (7to9Targets) When updating we need to rebuild an index. The routine "addroot" failed adding new account key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
326 Error adding new item key (7to9Targets) When updating we need to rebuild an index. The routine "addroot" failed adding new item key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
327 Error adding new audit trail index root When updating from Maui (QBW2.0) we need to rebuild an index. The routine "addroot" failed adding new audit trail key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
328 Error dropping window positions root When updating we need to rebuild an index. The routine "droproot" failed removing window position key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
329 Error adding window positions root When updating we need to rebuild an index. The routine "addroot" failed adding new window position key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
330 Error during update QuickBooks failed when opening a company during updating indexes. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
331 Error recording deleted transaction in the audit trail QuickBooks failed storing the transaction being removed into the audit trail. May not be enogh memory or disk space to complete the operation. QBW failed to record a transaction that was deleted in the audit trail Free up disk space. Reboot system if necessary. File should be fine (audit trail just did not get recorded), might want to verify and rebuild if needed
332 Memorized object too big. When converting Quicken or QuickBooks Dos data file - memorized object appears to be too big, it will not be converted. Problem converting file from DOS or quicken because of a "large" memorized object restore file in original program. Check memorized transaction, reports etc. Delete unused or unnecessary memorized information try converting again. Run correction utility in original program. Attempt to convert file again.
333 Not an error code. This is a string id, not an error code. This is a string id, not an error code. No action should be necessary should be able to ok pass message. Report where error occurred.
334 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
335 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
336 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
337 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
338 Bad Index in DBKey search functions, or internal error We tried to lookup information from an invalid index, or, some other kind of error occurred, maybe while printing lists. Memory is probably trashed, but it could be file related. QBW tried to lookup information from a invalid index. Restart QBW. Reboot system is necessary. Try same action again. Verify and rebuild if necessary. ABORTs. These two error message codes overlapped.
339 Cannot show the message, or unknown QuickBooks failed when tried to show the message. Most likely very low memory. Possible low memory or problem installation. Review KB for various program related issues. If error is occuring at another place please Report the steps to reporduce. ABORTs. These two error message codes overlapped
340 Not enough memory to complete operation. Exiting the program. QuickBooks' general message when it failed to allocate / reallocate the memory. There was not enough memory to complete the operation or need to allocate memory differently Free up memory - exit program re-enter - reboot if necessar. Check free space on HD. Try sample company - reinstall if necessary.
341 Error adding new time activity index root When updating we need to create a new index. The routine "addroot" failed adding new time activity key. Problem reading the file index when updating the file restore file in original version of QBW - verify rebuild if necessary - check lists for any problems - attempt to convert file again.
342 QBW is trying to read some data that has been partially deleted. QBW is trying to read some data that has been partially deleted. QBW is trying to read some data that has been partially deleted. If unable to open file using troubled company steps restore a backup or send to Data Recovery.
343 Cannot show the message. We encountered an error trying to show the real message QBW is unable to display the real message Unknown. Report steps. What was customer doing when they received error
344 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
345 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
346 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
347 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
348 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
349 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
350 Missing special payroll item. QuickBooks was looking for a special payroll item (like FUTA, FWH, etc) and could not find one. QuickBooks was looking for a special payroll item (like FUTA, FWH, etc) and could not find one. Most likely some type of list damage to the payroll item list Turn off the payroll options, turn back on. Verify and rebuild if necessary. If the "Special" payroll item is not showing as a rebuilt item, escalate call to Data Recovery
351 No "state" payroll item. Internal error - wrong parameters to the call to return the "state" payroll item. Problem reading the "state" payroll item Turn off the payroll options, turn back on. Verify and rebuild if necessary. Is there a state payroll item on the list? Do the employees have the correct payroll item selectioned on their profile? Reselect if necessary. If the state item is a rebuilt item, restore a backup or submit to Data Recovery
352 W-2 interface problem. This error should never happen. This means we are attempting to retrieve W2 information for an employee we don't think exists. If this happens, either the program or the data file has a problem QBW is trying to retrieve W2 information for an employee who doesn't exist. Resort the names list. Try editing the employees to make sure they have valid information in the payroll screen. Verify, rebuild if necessary.
353 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
354 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
355 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
356 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
357 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
358 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
359 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
360 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
361 Attempted to create a window or icon without a window handle Internal error. Internal error attempting to create a window. Unknown. Report steps and when error occurred. V is just the FORM_TITLE constant
362 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
363 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
364 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
365 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
366 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
367 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
368 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
369 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
370 Can't open file for Mail Merge. After asking for a mail merge file name, QuickBooks failed to open it. Windows only. Problem opening a file for mail merge Check for the proper name and path. Does the file already exist, rename.
371 Error saving reconcile report to disk When the user finishes reconciling an account QB saves the reconcile report as it is to disk so it can reprint it at a later time if the user chooses. This error occurs if QB is unable to save part or all of the report. Problem saving the reconcile report. Might be a low memory issue. The actual data should not be effected, you will just loose your last reconcile report. If it is not low memory the last reconcile report may be corrupted, verify rebuild if necessary. The V= is the record number that can not be written.
372 Error reading last reconcile report An error occurred trying to read the last reconcile report. This report is separate from the rest of the users data so it should not effect it Problem displaying or printing the past reconcile report Might be a low memory issue. If it is not low memory the last reconcile report may be corrupted, verify rebuild if necessary. You will most likely lose your report (even if the file was sent in for data recovery, if the report is damaged it would be lost) The V= is the record number that can not be read.
373 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
374 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
375 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
376 Problems with custom fields dictionary. QuickBooks could not create the custom field dictionary record. This message follows C=379. QuickBooks could not create the custom field dictionary record. This message often follows C=379. If error is occuring when opening file - lists are unable to load into memory - restore backup or refer to Data Recovery. If you are able to get into file - try restorting all the lists look for any problems on the lists. Run verify and rebuild if necessary
377 Problems with custom fields dictionary QuickBooks could not write the changes to the custom field dictionary record. QuickBooks could not write the changes to the custom field dictionary record. check disk space. Verify file, rebuild if necessary. Try editing a different custom field.
378 Problems with custom fields dictionary. There is a mismatch in the expected version number of the custom field dictionary and the read one. There is a mismatch in the expected version number of the custom field dictionary and the read one. If error is occuring when opening file - lists are unable to load into memory - restore backup or refer to ICU. If you are able to get into file - try restorting all the lists look for any problems on the lists. Run verify and rebuild if necessary.
379 Problems with custom fields dictionary. QuickBooks could not create the custom field dictionary record. QuickBooks could not create the custom field dictionary record. If error is occuring when opening file - lists are unable to load into memory - restore backup or refer to ICU. If you are able to get into file - try restorting all the lists look for any problems on the lists. Run verify and rebuild if necessary.
380 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
381 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
382 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
383 Error when updating an edlist. QuickBooks was updating an edlist record and an error happen. It may follow another message. QBW had a problem updating a list element. Resort the lists - make sure show all is displayed. Makre sure all the types are grouped together correctly. If still unable to change element - create a new record and merge the old into the new. Verify rebuild if necessary. Verify if problem occurs in sample company - if problem doesn't occur in sample and still receiving error restore backup or submit for data recovery.
384 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
385 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
386 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
387 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
388 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
389 Unable to create txlist for paying liabilities. QuickBooks failed to create a txlist for a liability report. Check for low memory. QBW was not able to display the list of information in the pay liabilities window. Try a different date range. Try the liabilities report. Verify file rebuild if necessary.
390 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
391 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
392 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
393 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
394 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
395 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
396 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
397 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
398 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
399 unknown unknown unknown Unknown. Please report the error.. include full error message i.e. L=, M=, and V=
400 Error writing reconcile report An error occurred trying to save the reconcile report to disk An error occurred trying to save the reconcile report to disk When the user finishes reconciling an account we save the reconcile report as it is to disk so we can reprint it at a later time if the user so chooses. This error occurs if we are unable to save part or all of the report. Might low disk space. There shouldn't be anything wrong with the file, you might be missing the last reconcile report. V=the record number that cannot be written

  • Connection to company file has been lost
  • This is not a QuickBooks data file or is damaged
  • Conversion from Enterprise to Pro or Premier – (This is a full conversion including payroll data!)
  • Conversion of Accountant’s copy to a regular data file.
  • Errors restoring a backup or portable file such as Error in reload.sql at line X. Sybase message: cannot convert to a timestamp. The bad value was supplied for column ‘db_created_tms? on row X of the data file.
  • Problems while running verify, rebuild, backup, archive, condense, or upgrading.
  • Errors while upgrading a QuickBooks company file such as Sybase message: Invalid option ‘ISQL_command_timing’ — no PUBLIC setting exists.

HOW OUR DATA RECOVERY SERVICE WORKS

Upon completion of the data recovery service request page, you will be sent a link to upload your files to a secure server. After receiving your data we will perform an evaluation on it.

If there is any significant data loss, we will contact you with the projected outcome of your data. Based on that information you may let us know whether or not to continue with the recovery process. In most cases there is no data loss and prepaid repairs that have no data loss are returned immediately upon completion.

STANDARD DATA RECOVERY SERVICE

Standard service has an average turnaround time within two business days.
Guaranteed success or no charge

PRIORITY DATA RECOVERY SERVICE

Priority repair has an average turnaround time within 6 to 12 hours and includes weekend service.
Guaranteed success or no charge

If you don’t see your problem listed here and want to know if we can fix it before sending your data, just send us an email describing your problem to info@quickbooksrepair.com and we will get back to you as soon as we can. You may also use the link below for a free quote.

Testimonials

Click here to add your own Testimonial

  • Service was fantastic. Lead time was faster than quoted. They resolved my issue with no lost data and were pretty quick emails.

    ★ ★ ★ ★ ★

  • Thank you so much!
    We think it's good to go, upgraded to 2013 no problem as well :)
  • ITS ABSOLUTELY COOL!

    ★ ★ ★ ★ ★

  • Great service. I was very happy that all my data was recovered.

    ★ ★ ★ ★ ★

  • Good service

    ★ ★ ★ ★ ★

  • Everything went well. Thanks so much for your quick service and I will recommend you to anyone that needed that conversion in the future.

    ★ ★ ★ ★ ★

  • Excellent service! Responded to my email inquiries within minutes. I had 2 QuickBooks files to convert from Enterprise to Premier and it only took about 4 hours from the time I uploaded them.

    ★ ★ ★ ★ ★

  • I can't thank you enough.  This appears to have worked flawlessly and you saved me tons of money.

    ★ ★ ★ ★ ★

  • The service was so quick, I was amazed, and all work out very well. I would definitely use this service again, thank you so very much!

    ★ ★ ★ ★ ★

  • Great service. Very fast. Would definitely use and refer.

    ★ ★ ★ ★ ☆

  • The best and easy to deal with!

    ★ ★ ★ ★ ★

  • Great experience! Fixed by QB file in less the 8 hours on a day before a holiday! What a life saver! Worth every penny!

    ★ ★ ★ ★ ★

  • Thank you for the quick turnaround on this conversion. I got this file back to my client and everything was just as it was before in the Enterprise version of the file. Thanks again for your help, I will definitely use your services again in the future.

    ★ ★ ★ ★ ★

  • The files look great. It’s frustrating that we had to spend the money for something that Intuit should provide automatically, but given that it must be done your service is fantastic.

    ★ ★ ★ ★ ★

  • They appear to only communicate by email but turnaround time was great ... and the job was done successfully.

    ★ ★ ★ ★ ★

  • Overall, an excellent service. The webpage seems kind of out-dated and the uploading process didn't work the first time. You can only upload 1 file at a time, though the site indicates otherwise. However, they converted my files perfectly. I will use them again in the future.

    ★ ★ ★ ★ ★

  • We wanted to downgrade from Enterprise to Pro as it was just more than we needed and was more cost effective for us to use. We contacted thus company. After getting our questions answered and making our payment we heard back from them and within 24 hours we had our converted files back and we were up and running on our Pro version with no errors to be found. Everything was there and worked perfectly. Thanks again for prompt and courteous service.

    ★ ★ ★ ★ ☆

  • i should have gone to you first instead of wasting my money on other "data file transfer utilities".
    THANKS SO MUCH - you saved me hours of time.

Don’t send your file to some other company to have them “try” and fix it.
Cut
out the middleman and save time and money!

QuickBooksRepair.com experienced technicians do the work – no subcontractors!
We offer
you the highest quality, the fastest service AND the lowest prices available.
Check
our rates against the competition and see for yourself.