QuickBooks Error messages

Most error messages list numerical values for several letter coefficients. Most of the letters have a meaning only for programmers, but the first two and one in the middle are useful for debugging:

V=4 Version of QuickBooks

R=11 Maintenance release. While one version of QuickBooks is current, several updates may be released. The releases and their meaning are listed somewhere in http://www.quickbooks.com. Release notes there list "most" of the problems fixed by one release. If you release is not the latest, installing the latest release may possibly be the fix.

C=43 Error code number. Some error codes numbers are below. If you get another arror code, back up or copy your file, and be sure the backup is good. Then try Verify Data and Rebuild Data.

Error Codes

At one time, Intuit representatives participated directly in a forum in Compuserve. They posted these meanings for some error codes:

C=3, C=9, or C=10

1. Hard drive full or nearly full.

2. When backing up, disk is not usable

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

C=19

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=21

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.

C=32, 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.

C=43 or 44

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

C=47

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.

C=51

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.

C=53

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.

C=88

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.

C=147

Benign error. Apparently, you can keep working.

Error -210

Has appeared only in files that also gave Error C=53.

C=212

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

C=225, C=260 or C=265

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

C=304

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.

C=315

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.

C=339

Memory is too full to send any other message. Read text at C=47.

One other thing...

Mouse pointer XE "mouse pointer:faint" (cursor) (or letters in title bar) become yellow XE "title bar:faint letters" or faint and hard to see: This has been attributed to WordPerfect? 6, and apparently was fixed in WordPerfect? 7. If it appears, the only solution is to exit and re-start Windows, without using WordPerfect? , or to buy WordPerfect? 7. People commenting on this have said that the definitions of Windows colors have been changed.