|
|
|
|
|
|
|
Quickbooks Database Errors
These error codes and the information provided below gives you a bit of
insight about the error codes you may encounter while working with Quickbooks, how they relate to your database and
possible solutions for your problem. This is not a complete list of problems, it is just a place to start and is provided to help you diagnose your Quickbooks problem. Anytime you receive an error in Quickbooks there is a possibility it is
related to corruption within the main database file. In most
cases this is the *insert company name*.QBW file. However, it is
possible that this file could also have the .QBB, .QBA or .QBM
extension. depending on what version of Quickbooks you are using. In almost every case of database corruption we are able to successfully repair your database and return your company file to a working state.
Help is available 24/7 for any Quickbooks Error.
1-877-230-3282
Newer versions of Quickbooks such as 2005 -
2011 Pro, Premier and Enterprise editions use a Sybase
database in an effort to increase size limitations, and allow for more
database growth. For the users this is a good thing, it provides a more
stable environment with more potential for future growth. It has however
changed many of the error codes that used to be used by Quickbooks to
alert us of a problem with functionality. Below is a list of common
error codes you could expect to see due to damage in a database or
Quickbooks environment. If you experience one of these errors and have expended all of your options for a self recovery, contact us and we will consult with you about sending your database out for repair.
Common Quickbooks Database Related Errors:
3371, Status
Code -11118: Could not initialize license
properties.
3371: Quickbooks could not load the license
data.
-6000, -77 when opening a company file.
-6000, -82: An error occurred when trying to
open the
file or An error occurred when Quickbooks tried to
access the
company file.
-6000, -301: An error occurred when Quickbooks
tried
to access the company file.
-6000, -305 occurs when trying to open a
company file.
-6000, -816: Quickbooks was unable to open the
company
file because the file is in use.
-6010, -100: Your Quickbooks installation may
have been
modified.
-6032, -158: An error occurred when Quickbooks
tried
to access the company file.
-6085, 0 when restoring a backup after entering
an incorrect
password.
-6098, 5 when opening up a data file from the
server.
-6123
-6130
-6123, 0: Connection to the Quickbooks company
file has
been lost.
-6129, -101: An error occurred when Quickbooks
tried
to access the company file.
-6150, -1006: An error occurred when Quickbooks
tried
to create, open, or use the company file.
-6175.
-6189: Quickbooks is unable to determine the
cause of
the error on the local file.
80070057 parameter is incorrect, when clicking
on a
QBB, QBM, NT, or TLG file from a Google Search Timeline.
80070057, the parameter is incorrect. There
was an unexpected
error reported while trying to run Quickbooks with
company file
|
Common Quickbooks Upgrading Errors:
- Error -6000,
-82: An error occurred when trying to open the file, or
An error
occurred when Quickbooks tried to access the company
file.
-
Error -6032,
-158: An error occurred when Quickbooks tried to access
the company
file.
|
Versions of Quickbooks made prior to 2005 and
some non-US versions of Quickbooks are more likely to suffer one of the
following error codes, The new versions of Quickbooks use a different
database structure and most of the old error codes are not used as
often.
Error Codes - C =
C=1 |
For example, M=1028, L=1743, C=1,V=0 [0], in Quickbooks V5.0/R4, after a backup and
restore
to a new system. This may involve non-standard video
settings.
|
C=3 |
According to one report this means the program
is
unable to open a Quicken file on a Mac. This should happen
only on Mac
versions. Free up HD space. Reopen and close the file
using Quicken for
the Mac. Then try again. However, a second source says this
relates
to QB having a full or nearly full hard drive. |
C=9 |
Unable to read from an auxiliary file at the
OS file system level.
Copy the data file to another disk or drive. Possible
damaged disk. |
C=10 |
Unable to write to an auxiliary file at the OS
file system level.
Should only happen during backup/restore, export, mail merge
or other
operation which write to a data file. Free up hard disk
space and try
again. Possible damaged disk. |
C=19 |
Unable to delete
a transaction, because it is incomplete (probably data
error). Happens during Condense Data and will require manual repair of the database. |
C=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. |
C=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 cannot be used after conversion in a new
version of the
program. (not used since version 4.0). |
C=38 |
Unknown, but related to backup, as in V7.0D
R1 (M=1352 L=968 C=38 V=30 (FFFFFFE2) |
C=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. |
C=44 |
Error writing a transaction. Possible data
damage or out of memory.
Restart Windows and try again. If error persists you may need our data repair services. |
C=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, Contact us. |
C=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. |
C=53 |
Some entry in a
list should be deleted, but for some reason
was not
deleted. Rebuild data may be tried, but don't expect much. If it
does not work, Restore last backup. If
you get this on a regular
basis it may be time to contact our file repair service. |
C=55, C=64 |
The network temporarily went down. It then
probably came back before it was noticed, except for QB,
which
cannot handle that. |
C=88 |
Error writing to the QB file on the
QB file level.
Rebuild. If the problem persists try to free memory and try again. |
C=147 |
Benign
error ( keep working). |
C=184 |
Unexpected Error - February report days
mismatch (28 & 29) |
C=210 |
Appears in files with Error C=53
(also Error 210, -210) |
C=212 |
File has been used in later version. Comment at C=32. |
C=224 |
QB tried to read an invalid split line for a
transaction or
memorized transaction. The data file may be damaged or QB
may be confused. Delete the first split transaction
error, in the QBWIN.LOG file. |
C=225, C=260, C=265 |
Try Rebuild. If that does not work, Contact us and allow us to do a Free Evaluation of the database.
|
C=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. |
C=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.
If all else fails you may need a file repair
|
C=339 |
Memory is too
full to send any other message.
See C=47. | |
Error Codes - Other:
117
or 146 |
Unknown Client-Specific Tax Form
Printing Error.
Uninstall and reinstall Quickbooks |
80004003 |
This is a Windows error number.
It means
Invalid Pointer. In QB2000 it related to an error when
clicking
an icon in the opening splash screen. All 8xxxxxxx numbers
are Windows
error codes (in hex). |
Balance sheet out of balance |
If unexplainable from an accounting standpoint, This is almost always due to data
corruption. Contact us and find out how we can help!
|
Balance sheet net income not equal
to Profit & Loss
net |
If the balance sheet alone is in
balance then one
statement is on the Cash Basis and the other is on the
Accrual
Basis. Modify or Customize memorized reports, depending on
the
version of QB. Also Edit (File) | Preferences | Reports |
Cash (or
Accrual) to set the default Preference for future reports. |
Chart of Accounts delete error |
See list item delete error below. |
Cursor, letters in title bar
yellow, faint, hard to
see |
Some say the Windows color definitions change. Due
to WordPerfect 6. Apparently fixed
in WordPerfect 7. The solution is to exit
and re-start
Windows without using WordPerfect or to use WordPerfect 7. |
Data from
new QB version, cannot use |
This big problem is easy to fix.
Each QB (QB 4, 5, 6,
99, 2000, 2001...) upgrades data files so you cannot use it
with older
program versions. All you need is the new QB
version. Users who think they have the same QB version may
be very confused by this. That is because free Releases may
update formats in a version. QB6 R3, QB99 R3 and
QB2001 R2 upgraded file formats. This causes
problems for QB Pro Advisors who deal with
many QB versions, releases and clients, so Intuit tries to
minimize
it. |
Erroneous
credits in A/R Aging report |
See Unexplained Errors below. |
IE
(Internet Explorer problems) |
Installing
some versions of QB try to get you to install a version of
IE
earlier than the one you have. You can add this to the top
of the
qbw.ini file for some systems and operating systems:
[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. |
OL-2XX |
These errors relate to remote
network/server problems
(despite saying contact Intuit). QB2000 correctly says
contact
Financial Institution. The key is how often they occur. It
may be a
transient problem (delays in the Internet between you and
your bank
or a problem with the bank server). Try again, preferably at
a
"less busy" time. QB2000 OL-206 says "try again
later. If it still fails, contact the financial institution. If they cant help it may be a damaged file.
|
Other program busy |
For example, "This action
cannot
be completed because the other program is busy. Choose
'Switch to'
to activate the busy program and correct the problem. Doing
so may
result in this error message, "QBDagent.exe, MrtInitialize
failed - 7." Clicking OK makes this go away for the moment.
Usually not related to Quickbooks damage
|
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.
There is a good chance you will need to have the file repaired.
|
Spool32 |
This may occur when printing. Usually not related to Quickbooks damage
|
Trans
# |
This
appears in messages like:
Trans # Type Date Num Name
Payroll Item Wage Base Amount
37922 Paycheck 03/30/2001
9093 ... (cont.)
It usually relates to transactions that must be found
and
deleted to fix QB files. |
Unexplained Errors |
Many unexplained errors relate to
corrupt data, which we can usually fix. | | |
|
|
|
Top 10 Reasons Why You Should Choose our Quickbooks Repair Service
- Strict non-disclosure agreement, Your privacy and security
are guaranteed
- Friendly technicians standing by 24/7 to speak
with you one on one
- No-Repair, No-Charge policy
- Free evaluation for all standard level services
- Swift standard repair turn around, usually 1-3 days.
- Firm upfront pricing, no surprises here.
- Expedited Emergency services 12-24 hour turn around.
- Most advanced techniques available.
- Over 10 very successful years of experience.
- Over 90% Success rate.
© 2011 Data Recovery USA, Inc
repairquickbooksdata.com is not affiliated with Intuit in any way. The Quickbooks software
is a registered trademark of Intuit.
|
|
|
|
|
|
|
|
|
|