Quickbooks 2006 Corrupt or Damaged File Repair

Jun 04, 2006 4 Replies

formatting link



Quickbooks Corrupt or Damaged File Repair/Recovery We offer the following services to users of QuickBooks®: Data Recovery including damaged media (backups made on bad floppy disks) Password Recovery Conversion or update of QuickBooks files to later versions If you're having problems with your QuickBooks data, we can fix it. Guaranteed!



Recoverable Quickbooks Error Codes : The codes below are the common Quickbooks Error codes that are repairable. This is not a comprehensive list and in most cases we can recover files with other related error codes. C=102 (list problems - usually version 5 and earlier) C=43 (can't read transaction - usually incomplete transaction) C=44 (can't write transaction - usually incomplete transaction) C=47 (can't find transaction - usually while running a report or opening a file



C=53 (list item still exists after being deleted) C=79 (problem with inventory data) C=88 (problem reading one or more of the data trees in the file - often occurs after error code 55 or 59 - loss of network connection)



C=121 (invalid account type) | C=225 (error reading transaction) | C=291 (problem with templates)



C=315 (a generic error that can occur anywhere within QuickBooks) C=342 (usually followed by an IPF in APPCORE.DLL - damaged data tree) with saved desktop)



Error c=43 when attempting to process online transactions Error Message: "An error has occurred. If this is the first time using this account, or you have manually modified your account data, please check your account setup, otherwise call tech support" EDLIST.C (retStatus.Succeeded()) is false LVL_ERROR; LVL_ERROR--Connection; LVL_ERROR--** Corrected ** LVL_ERROR--Warning: Verify Name list: totInList was xx. Should be yy Verify list index Name: Invalid index entry Verify Name List Item xx: View out of sequence. Error: Verify Name Estimate Balance failed. Name = xx LVL_FATAL_ERROR--Cannot Continue--check for pEdList->hView == 0 failed. (pEdList->hView == 0) is false LVL_ERROR--DMError "QBW - an error has occurred in your program... Close or Ignore" when closing a QBW file (close & ignore both result in GPF in module QBCHAOS.DLL).



"This is not a QB data file or data is from a newer version. Check to ensure that the path and file name of the QBW file are correct."



"File may be damaged"



Please restart QuickBooks and try again. If you continue to experience this error, please note the C= value and contact technical support.



Quickbooks Error "-6150 -1006", "-6177,0", "-1,0", "C=224".



Quickbooks Damaged or Corrupted File Recovery Rates



Standard Data Recovery:



Turnaround time is 48 hours US$299 flat fee Guaranteed success, or no charge Expedited Data Recovery:



Turnaround time is 12 hours.



US$425 flat fee Guaranteed success, or no charge QBWRecovery Standard Recovery Service



formatting link


Does this include Canadian editions with multiple currencies (and other non-US versions), or is it US editions only?

Quickbooks Corrupt or Damaged File Repair/Recovery We offer the following services to users of QuickBooks®: Data Recovery including damaged media (backups made on bad floppy disks) Password Recovery Conversion or update of QuickBooks files to later versions If you're having problems with your QuickBooks data, we can fix it. Guaranteed!

Quickbooks Damaged or Corrupted File Recovery Rates

Standard Data Recovery:

Turnaround time is 48 hours US$299 flat fee Guaranteed success, or no charge Expedited Data Recovery:

Turnaround time is 12 hours.

US$425 flat fee Guaranteed success, or no charge QBWRecovery Standard Recovery Service

formatting link

Error Codes - Introduction:

Most QB error messages say Fatal or Unexpected Error and things like: V7.0D R3P M=1153, L=133, C=43, V=28 (FFFFFFF4).

Many such codes are only useful to computer programmers. They put codes and related tests in programs to stop program crashes and make it easy to correct crash problems. Thanks to good programmers, effective quality control and extensive pre-release (beta) tests by people like us (we repeatedly win #1 national Intuit prizes) QB usually has few bugs. Most errors relate to problems with your data or system. You can fix many o them once you understand some of this. See the table below to understand: V7.0D This is the version of your QB program (V7=QB99). R3P This is the maintenance Release number of your QB program. QB usually releases several free updates for each version. The releases available and the problems they fix are sometimes listed at

formatting link
If you have QB problems check that you areusing the most current release. If not, download it. This may fix manyproblems. M=1153 Module number. L=133 Line number. C=43 This is an error code number. We list more below. If you get repeated error codes then back up or copy your file and confirm you have a complete backup (restore it). After restoring the backup, click Windows, Closeall, File, Utilities, Verify Data and Rebuild Data. V=28 (FFFFFFF4) Some debugging value, often in hex, that a programmer thought might be useful.

Error Codes - C =

0 This may be due to an outdated Wininet.dll file on your computer when trying to access the Internet Connection Setup. The .dll version should match or be later than your Microsoft Internet Explorer version. Run the Internet Explorer repair tool, which may detect the outdated version, or update to the latest version of Internet Explorer. In the Internet Explorer Help menu click the link pertaining to program updates.

1 For example, M=1028, L=1743, C=1,V=0 [0], in QuickBooks V5.0/R4, after a backup and restore to a new system. This may involve non-standard video settings. Check to make sure you are in a standard set (e.g. 640x480 or 800x600) and 256 colors. It also may involve custom invoice form that must be copied in addition to the data file.

3 According to one report this means the program is unable to open a Quicken file on a Mac. This should happen only on Mac versions. Free up HD space. Reopen and close the file using Quicken for the Mac. Then try again. However, a second source says this relates to QB having a full or nearly full hard drive. 9 Unable to read from an auxiliary file at the OS file system level. Copy the data file to another disk or drive. Possible damaged disk. 10 Unable to write to an auxiliary file at the OS file system level. Should only happen during backup/restore, export, mail merge or other operation which write to a data file. Free up hard disk space and try again. Possible damaged disk. 19 Unable to delete a transaction, because it is incomplete (probably data error). Happens during Condense Data. In later versions, rebuild the data file.

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

32 Also Error -35. The file was used in a newer version of QB and cannot be used in an older one. Each new version (and some Releases) of QB has an updated data structure. QB files can't be used after conversion in a new version of the program. (not used since version 4.0). 38 Unknown, but related to backup, as in

V7.0D R1 (M=1352 L=968 C=38 V=30 (FFFFFFE2)

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

44 Error writing a transaction. Possible data damage or out of memory. Restart Windows and try again. If error persists, Rebuild.

47 Trying to remove a transaction from a report or report like feature. Trying to locate a transaction that has been modified, but could not find it. Harmless. Close all windows and continue. If this does not work, try Verify and Rebuild. 51 Appeared in QB 3.0 and was described as a benign error (keep going) or: exit QB, exit Windows, and start again; verify in release 7 or later; or Rebuild data.

53 Some entry in a list should be deleted, but for some reason was not deleted. Rebuild data may work, but don't expect much. If it does not, Restore last backup. If you get this often it may be time to upgrade to a new version.

55, 64 The network temporarily went down. It then probably came back before it was noticed, except for QB, which cannot handle that. 88 Error writing to the QB file on the QB file level. Rebuild. If the problem persists try to free memory and try again.

147 Benign error ( keep working).

184 Unexpected Error - February report days mismatch (28 & 29) 210 Appears in files with Error C=53 (also Error 210, -210)

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

224 QB tried to read an invalid split line for a transaction or memorized transaction. The data file may be damaged or QB may be confused. Delete the first split transaction error, in the QBWIN.LOG file. 225, 260, 265 Try Rebuild. You will probably have to call the QB Support Network.

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

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

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

342 Please restart QuickBooks and try again, preferably with a new data file. In Microsoft® Windows XP users should verify compatibility settings . Scan your system for viruses. If you are able to open other data files: rebuild your company data file without opening it . If you continue to receive the error after completing these steps, restore a backup of your company file. 387 This may be an invoice template problem. Go to Lists, Templates, at bottom Show All in case a template is inactive. Select a template and click Open Form. Repeat until a template has an error (some templates show no name). Then close the form. In the Templates window, select the template with the error, click Templates, Edit and Default on the right. When you get "All your Header, Fields, Columns, and Footer Settings will be returned to their original default ... ", click OK. Click OK again to save changes. You should now be able to open an invoice with no error. Custom templates will need customizing again.

Error Codes - Other:

117

146 Unknown Client-Specific Tax Form Print Error. Uninstall and reinstall QuickBooks.

15212 Common payroll or program upgrade problem: a shared download location mapped to an unavailable drive; file opened from a non-mapped location while Shared Download is OFF; or hard disk does not have sufficient space. Restart computer and re-map data file to network drive (see Map Network Drive). If you still have the problem Update QuickBooks from the QB File menu. Click the Options tab. Share Download OFF and then ON. Click Save. If the problem persists it is likely that a hard disk you are trying to download to does not have sufficient space. 80004003 80004005 All 8xxxxxxx numbers are Windows error codes (in hex). In QB2000 it related to an invalid pointer.error when clicking an icon in the opening splash screen. Balance sheet out of balance This is due to data corruption. See the above File Repair procedures. Balance sheet net income not equal to Profit & Loss net If the balance sheet is in balance, but the income on it does not match the income of the P&L, then one statement is on the Cash Basis and the other is on the Accrual Basis. Modify or Customize memorized reports, depending on the version of QB. Also Edit (File) | Preferences | Reports | Cash (or Accrual) to set the default Preference for future reports. Chart of Accounts delete error See list item delete error below. Cursor, letters in title bar yellow, faint, hard to see Some say the Windows color definitions change. Due to WordPerfect 6. Apparently fixed in WordPerfect 7. The solution is to exit and re-start Windows without using WordPerfect or to use WordPerfect 7. Data from new QB version-cannot use

OR

Cannot upgrade some workstations for network data file This is easy to fix. Each QuickBooks version & some free interim releases upgrades data file formats so you cannot use the files with older programs. All you need is the new QB version or release. QB6 R3, QB99 R3 and QB2001 R2 upgraded file formats. The interim upgrades causes big problems for QB ProAdvisors dealing with many QB versions, releases and clients, so Intuit tries to minimize them. Note that once you upgrade a QuickBooks network data file you may not be able to get into it to upgrade all workstations. In this case open a QB Sample file in the local Intuit Program Files folder. Erroneous credits in A/R Aging report See Unexplained Errors below. IE (Internet Explorer problems) Installing some versions of QB try to get you to install a version of IE earlier than the one you have. You can add this to the top of the qbw.ini file for some systems and operating systems: [Misc] IE5Override=-1 It works Illegal operation For example, "This program has performed an illegal operation and will be shut down. Details: QBW caused a general protection fault in QBWPR.DLL." The Windows, Closeall, File, Utilities, Rebuild procedure may help. However, you also may get more information if you disable Dr.Watson (see top of this page). You also might uninstall and reinstall QB. Invalid page fault For example, "QBW32 caused an invalid page fault in module QBTXN32.DLL at 017f:0042f188." See above. Link Error Code: 00001 This appears in messages like: Link Error Code: 00001(HEX), UNKNOWN (15), linkRecNum = 48387, sibling = 48386, key (m1) = 40518, tOne = 40524, mTwo = 48378, tTwo =48382 It usually relates to transactions to be found and deleted to fix QB files. List Item delete error The error says something like, "This account is associated with an item. It cannot be deleted." This applies to Items, Customers, Vendors, Employees, Payroll Items and the Chart of Accounts. You cannot delete such items if referenced by transactions or other items. For example, you cannot delete an account that is referenced by an Item or Payroll Item, even if no transactions reference it. You can only delete or change such items (accounts, etc.) after removing all references to them. Map Network Drive (common problem) Within QB File, Open Company, Look in drop-down list - My Network Places. Double-click Entire Network and the QB file drive. Right-click the folder with it and select Map Network Drive. Select an unused drive letter, Reconnect at Logon and Finish. From the Look in drop-down list select the drive assigned, the main window, Open. the QB file name and Press Ctrl+1 for Product Information. The path in File Information : G:\QuickBooks Pro\[company name].qbw. Map Network Drive (common problem) In Windows Explorer On the Windows toolbar, right-click Start and then Explore. From the Tools menu select Map Network Drive. Click the Browse button. Click the plus signs until you locate the folder that contains the QuickBooks data file. Select the folder and click OK. Select an unassigned drive, Reconnect at Logon and Click OK. Start QuickBooks, and from the File menu, choose Open Company. From the Look in drop-down list, select the drive letter assigned, choose your company file name and Open. When the file opens, press Ctrl+1 to open the Product Information window. Look at the path under Location in File Information .The file location should be like:G:\QuickBooks Pro\[company name].qbw. OL-2XX These errors relate to remote network/server problems (despite saying contact Intuit). QB2000 correctly says contact Financial Institution. The key is how often they occur. It may be a transient problem (delays in the Internet between you and your bank or a problem with the bank server). Try again, preferably at a "less busy" time. QB2000 OL-206 says "try again later. If it still fails, contact the financial institution. Other program busy For example, "This action cannot be completed because the other program is busy. Choose 'Switch to' to activate the busy program and correct the problem. Doing so may result in this error message, "QBDagent.exe, MrtInitialize failed - 7." Clicking OK makes this go away for the moment. It relates to QB Marimba automatic background download capability, criticized as an invasion of privacy. Remove QBDagent from the Windows startup menu. Turn off automatic downloads in QB.

Printing Make sure the printer works with Start | Settings | Printers | right click printer | Properties, Print Test Page (lower right). Then check print spool setting. If this fails install a new printer driver from Windows or e Internet sites. If you still have problems check File | Print Setup and Print Forms settings in QB. Also see errors 117 and 146 and next. QB freezes when printing You may have a Print Reports or Print Lists window ( with a printer name & Portrait/ Landscape, etc.) off the screen. QB does not respond to a mouse after you print or Printer Setup. Rebuild has no errors and other programs run OK. The W2000 Task Manager does not show QB as Not Responding. A Processes view shows 9%+ idle and no CPU time for qbw32.exe. Reports that Preview will Print. The solution: hold down Shift & click File, Printer Setup. Print Reports, etc., screens are centered on the screen. Move them slightly by dragging the top blue bar to create a new on-screen default. Server busy QB does not release its file lock as soon as you exit, so anyone trying to use the file too soon gets this message. To avoid it use the Task Manager (Ctrl-Alt-Del) and Process to End these processes: Axelbridge, Axelbridge1, QBDagent, QBDagent, QBupdate and QBserver . Alternatively, open a Sample or dummy file before exiting. A QB2002 fix was to be available by 2/15/02. Spool32 This may occur when printing. Someone suggested typing Ctrl -1 in QB to get version and miscellaneous information. However, it probably relates to a printer not being properly set up.

There was a problem loading registration support c:\windows\temp\{2b02f82e-a9b9-458c-80e5-3ea8c0de8471} \mfc70.dll Error... This occurs if you are use Microsoft Windows 98 First Edition and did not install Microsoft Active Accessibility. Trans # This appears in messages like:

Trans # Type Date Num Name Payroll Item Wage Base Amount

37922 Paycheck 03/30/2001 9093 ... (cont.)

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

Unexplained Errors Many unexplained errors relate to corrupt data, which you (or we) can usually fix. See File Repair Procedures and Comments below. W32.Blaster.Worm "Error C=342," "RPC Server is unavailable," or "QBCenters could not find a critical file" Run a full dscan with your anti-virus program, after updating it.

snipped-for-privacy@yahoo.com wrote:

C=3, C=9, or C

  1. Hard drive full or nearly full.

  1. When backing up, disk is not usable

  2. When restoring, backup disk is bad (Ouch!) Try copying to the hard drive (do not overwrite anything) and restoring from there.

C

When running Condense Data, file is too large (reported from one user, with a file size of 52 MB. Other live with larger files.)

C!

This code appeared only after upgrading to a new version of QuickBooks, related to payroll operations. They suggested a fix of opening a new directory for QuickBooks, and installing the earlier version there. Then the backup of the earlier file was restored there, and Rebuild Data run on the restored file.

C2, or Error -35

File has been used in a later version of QuickBooks. Each new version of QuickBooks has used an updated data structure, and files can't be used in an earlier version.

CC or 44

QuickBooks encountered a problem in reading the file. These problems often can be relieved by running Rebuild Data one or more times.

CG

Attributed to to low memory. Try Clicking Window|Close All. Then open some windows. Look at the Preferences|View|Desktop. If the desktop is saved when closing the company, but never cleared, too many windows could be open. Also hit Control-Alt-Delete, and check the task list, to see if other programs could be terminated. If these do not help. try Verify and Rebuild.

CQ

Apeared in QuickBooks 3.0. Was described as a benign error (keep going) or various fixes prescribed. The first is to exit QuickBooks, exit Windows, and start again. Verify release 7 or later. More severe is Rebuild Data.

CS

Restore last backup. Rebuild may be tried, but don't expect much. Seen in earlier versions, and you may need to buy a later version.

Use Scandisk to clean up the file system, then restore recent backup. This error indicates that QuickBooks can't read the file, probably due to external damage to a file. If the file will load, Rebuild Data can be tried, but is not likely to work.

C7

Benign error. Apparently, you can keep working.

Error -210

Has appeared only in files that also gave Error CS.

C!2

File has been used in later version. Comment at C2.

C"5, C&0 or C&5

Try Rebuild Data, but you will probably have to call the "QuickBooks support Network."

C04

QuickBooks was unable to create image (.qbi) file, either due to lack of disk space, or network limitations. QuickBooks creates this file when a company file is opened, and deletes when the company file is closed.

C15

May be data related, fixed by Rebuild Data.

If you get this in list activities, such as a list report, it indicates a list problem, and Re-sort list is worth a try.

Other possibilities are low memory, or conflicts with other programs. The test is in shutting down other programs, and seeing if the problem disappears. This error appeared in older version of QuickBooks and of Windows.

C39

Memory is too full to send any other message. Read text at CG.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required