Get a free evaluation Error 6010, 2 usually appears beside -6094, 0, under the message "An error occurred when QuickBooks tried to start the database server." Your company file is a database, not a document, and the engine meant to open it never started. Most of the time the cause sits on your machine, and you can fix it yourself.
A QuickBooks Desktop company file is a SQL Anywhere database. When you open one, QuickBooks starts a database engine, the QuickBooksDB service, and that engine hosts the file while you work in it.
This code means the start attempt failed outright. The engine never came up, so QuickBooks had nothing to open the file with. The second number is internal to QuickBooks, not a database engine code, so engine error tables will not explain it.
Intuit links this code to security program updates, and that is the most common trigger: antivirus or firewall software updates overnight and starts blocking the database service. Close behind are a stopped or missing QuickBooksDB service, another computer already hosting the file, and a damaged QuickBooks installation.
Do not confuse this with -6010, -100. That sibling means a computer that is not the server is hosting the file, a hosting conflict. Here the local start itself failed, so the fixes target the service and the software around it, not hosting mode alone.
Run the cheap checks first. Start the QuickBooksDB service and set it to automatic; review your security software's update history against the day the error began; confirm only the server carries hosting.
Then scan the folder with Intuit's Database Server Manager, open a different company file on the same machine, and try this file from a local copy, not the network. Each result tells you something: if another file opens, or this one opens locally, the file is fine and the problem is your environment.
Genuine damage is the less common cause here, and the pattern is distinct. The service runs, security software is satisfied, other files open on the same machine, and this one file still fails with the same code on every computer you try.
That points at the file itself, usually a crash or interrupted save that left it truncated. The engine cannot start on a database it cannot read, so no service restart or firewall rule will change the outcome. That is where repair, not troubleshooting, is the answer.
We rebuild damaged company files and return your data in a clean, working file. The file gets a free evaluation first, you receive a firm fixed quote before any work begins, and there is no fix, no fee.
If your checks point to damage, our <a href="/Quickbooks-Error-Codes.aspx">QuickBooks error code reference</a> covers the rest of the -6000 family and related codes. You can also <a href="/contact-quickbooks-recovery-pro.aspx">contact our QuickBooks repair team</a> to start the evaluation.
No. The -100 variant is a hosting conflict: a computer that is not the server is hosting the file. With 6010, 2 the local database start failed outright, which points at the service, security software, or the installation.
It is internal to QuickBooks rather than a code from the database engine, so looking it up in engine documentation will mislead you. Read the pair as one signal: the engine did not start.
Often, yes. Restarting the QuickBooksDB service, allowing it through your security software, and correcting hosting mode clear most cases. If one of those works, you never needed a repair, and we are glad the page saved you the money.
When the environment checks pass and this one file still fails everywhere while other files open. That is the pattern of a damaged database, and it is worth the free evaluation before you restore an old backup.
That is your decision and your accountant's, because it sets how much recent work you lose. If the gap is too large, repairing the damaged file is the alternative.
We look at your file before you pay anything, then give you a firm fixed quote. Nothing starts until you accept it, so there are no surprises and no diagnosis fee.
Every service is guaranteed. If we cannot resolve your issue, there is no charge - you pay nothing at all.
When Verify, Rebuild and File Doctor loop or fail, the file needs engineering work rather than another pass of the built-in tools. That is what we do.
Every version from QuickBooks 1 for DOS through the current Pro, Premier, Accountant and Enterprise releases.
Your company file is used only for the work you asked for, never shared, and deleted 14 days after the job. Immediate deletion on request.
QuickBooks File Repair / Data Recovery. We resolve your issue, or you pay nothing.
Pick the bracket that matches your company file. If you are unsure, request a free evaluation and we will confirm before you pay.
Turnaround 48 hours (business days)
Turnaround 8-12 hours
Not sure which applies? Send us the file for a free evaluation and we will confirm the price before you pay.
Every service is guaranteed. If we cannot resolve your issue, there is no charge - you pay nothing at all.
Get a free evaluationThere is no charge to look at your file. Send the details and we will tell you what can be recovered before you pay anything.
Send us the file and we will tell you what can be recovered. We resolve your issue, or you pay nothing.
Independent service provider. Quickbooks Repair Pro is operated by E-Tech. Our repair, data recovery and conversion services are our own work, and are not affiliated with or endorsed by Intuit Inc. “QuickBooks”® and “QuickBooks Desktop”® are registered trademarks of Intuit Inc., used here only to identify the software we work on.
QuickbooksRepairPro.com is an independent service provider of QuickBooks Accounting Migration, Condense/SuperCondense, and Repair services, and is not affiliated with Intuit.