QuickBooks Error 6060: Company File Authentication Failure

Error 6060 means QuickBooks refused to authenticate a request to open your company file; here is what causes it, what to check yourself, and when the file needs repair.

Error 6060 stops a request to open the company file at the authentication step. QuickBooks has found the file and knows it is there; what failed is the handshake that admits your session, or an application's session, to the data. That distinction matters, because most authentication failures trace to the setup rather than the file.

The handshake that fails

Desktop editions of QuickBooks do not read the company file directly. Every open request is handed to a database service, which authenticates the requesting user, workstation, or integrated application before granting access. Error 6060 is what comes back when that authentication is refused. Because the refusal happens before any transaction is read, the dialog tells you almost nothing about the state of your data.

The same checkpoint governs applications that connect through the QuickBooks Web Connector. When a sync trips it, the connecting software may show its own message, commonly 'Object reference not set to an instance of an object'. That text belongs to the application, and it points at the connection rather than at your books.

Common causes, ranked

The likeliest cause depends on when the code appears. During a scheduled sync, the prime suspect is the application's connection definition, and its developer can switch the declared style between RPC and DocWrapped values. If the code appears for one Windows user only, suspect folder permissions on the machine hosting the file. If it appears for everyone after a reboot, suspect the database service being stopped or running under an account that lost its rights.

Genuine damage sits last on the list, but it does occur. The service reads parts of the file header and the transaction log while validating a session, so corruption in either can fail the check. Damage announces itself by failing everywhere: locally, remotely, and for every account.

Safe checks in order

Start local. Open the file directly on the machine where it is stored, in single-user mode, signed in as the QuickBooks administrator. If that succeeds, your data is intact and the fault sits in the connection layer. Next, confirm the folder grants full control to your Windows account and to the database service.

Then rescan the folder with the QuickBooks Database Server Manager on the host, which refreshes the network descriptor. Once the file opens, run Verify Data from the File menu to test the data itself. If the file refuses to open at all, restore your newest backup onto the same machine and try that copy. A backup that opens cleanly while the live file refuses is the clearest damage signal you can produce on your own.

Damage or environment?

Environment failures are selective. Permissions errors follow one account, service errors follow a reboot, and sync errors follow an application; in each case the file opens for somebody, somewhere. Damage is universal. The same file, opened locally as administrator with the service running, still refuses, and Verify Data reports problems or will not finish.

If QuickBooks opens the file cleanly and Verify passes, the file is not your problem. An application that still cannot connect is pointing at its own configuration. That question belongs to the application's developer, and it is not a repair we perform.

Our file repair service

When the evidence points to damage, our engineers evaluate the file at no charge. You receive a firm, fixed quote before any repair work begins, and there is no fee unless we return a working file. The work is guaranteed, and it covers the company file itself: the header, the lists, and the transaction data inside it.

You can browse the full <a href="/Quickbooks-Error-Codes.aspx">QuickBooks error code reference</a> for related file access and damage codes. If your checks have already pointed to the file rather than the setup, start at our <a href="/contact-quickbooks-recovery-pro.aspx">QuickBooks file repair contact page</a> and we will begin the evaluation.

Frequently asked questions

Does error 6060 mean my company file is corrupted?

Not by itself. The code reports a failed authentication, and damage is only one of several possible causes. The local open test described above separates them quickly.

Where does the 'object reference' message come from?

From the integrated application, not from QuickBooks. Its developer can adjust the style declared in the application's connection file, switching between RPC and DocWrapped. We do not repair third-party applications.

Will restoring a backup solve it?

Only if the live file is damaged. A backup that opens while the live file refuses confirms damage; if neither opens, look at permissions and the database service first.

Do you repair Web Connector or permissions problems?

No. Those are environment and third-party software issues outside our service. We repair damaged company files, with a free evaluation and a fixed quote before any work begins.

All QuickBooks error codes we repair

The track record

Twenty years of files
brought back to life.

95%+ recovery success rate

20+ years with QuickBooks files

1000s of businesses served worldwide

5 regional editions, PC and Mac

What you get

Every service.
The same promises.

Free evaluation first.

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.

No fix, no fee.

Every service is guaranteed. If we cannot resolve your issue, there is no charge - you pay nothing at all.

Data-level engineering.

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.

Every version from QuickBooks 1 for DOS through the current Pro, Premier, Accountant and Enterprise releases.

Private, then deleted.

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.

Pricing

Transparent pricing

QuickBooks File Repair / Data Recovery. We resolve your issue, or you pay nothing.

Standard

Turnaround 48 hours (business days)

US$275Under 1 GB

US$4131 - 2 GB

US$5502 - 3 GB

US$825Over 3 GB

Free evaluation before you pay
Firm fixed quote, agreed up front
Guaranteed: no fix, no fee
All editions, PC and Mac

Buy now

Expedited

Turnaround 8-12 hours

US$449Under 1 GB

US$6741 - 2 GB

US$8982 - 3 GB

US$1,347Over 3 GB

Everything in Standard
Priority place in the queue
Same guarantee: no fix, no fee