Company file access and damage

A hosting conflict usually explains error -6120, 0; here is how to separate setup trouble from real file damage.

QuickBooks raises -6123, 0 when its database engine cannot finish attaching to a company file during an open, upgrade, or restore; here is how to sort environment problems from real damage.

Error 6129, 0 is a failed lock check inside the company file, usually left behind by a crashed session or mismatched permissions.

QuickBooks cannot open the company file and shows 6130, 0: what the code means and what to check before paying for repair.

Error 6131 blocks the company file open; most cases trace to hosting or network setup, and a few to real file damage.

The wrong computer is hosting your company file: what -6138, -105 means, what to check yourself, and when the file needs repair.

The 6000-family code that also blocks restores, and what that tells you about the file itself.

Error 6147, 0 usually follows a restore onto a network path; test the file locally before you assume damage.

QuickBooks locates your company file but cannot open it: causes, the local copy test, and when the file needs repair.

QuickBooks cannot reach the database service that serves the company file; most cases are hosting or firewall settings rather than damage.

Error -6176, 0 usually means a firewall is blocking the connection between two computers, not that your file is broken.

Most 6177, 0 cases are a stale file location rather than damage; here is how to tell which one you have.

Error 6189, 816 is usually a network configuration problem, not file damage, but a failed restore can make it the real thing.

Error 6190, 816 usually means something else already has your file open, not that it is broken.

Error 6200 means the receiving company file refused hours dated inside its closed period; the usual fix is a closing-date decision, not a repair.

Error -6210, 0 is a hosting conflict, and most of the time the file is fine. Here is how to prove it.