QuickBooks Error -6144, -103 -- Damaged Network Descriptor File

QuickBooks error -6144, -103 blocks company file access over a network, but our engineers can resolve the damaged database service configuration causing it.

QuickBooks Error -6144, -103 is a multi-user company file access failure that occurs when the network descriptor (.ND) file references a damaged or incorrect QuickBooks Database Service account. When this configuration data is corrupted, the workstation cannot establish a proper connection to the host system, blocking access to the company file entirely.

What the Error Message Says

When opening a company file in multi-user mode, QuickBooks displays one of the following messages:

An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6144, -103).

or

Error -6144, -103: "There was an unexpected error reported while trying to run QuickBooks with company files [path and filename]."

What the Code Means

The 6000 series of errors generally indicates that QuickBooks cannot reach the company file across a network connection. The specific -6144, -103 variant points to a failure in the database service layer. Every QuickBooks company file in a multi-user environment is paired with a corresponding .ND file. This descriptor file tells the QuickBooks Database Server Manager how to route traffic between the host and workstations. When the .ND file points to a wrong or damaged database service account, the connection handshake fails before the file can open.

What Triggers It

Our engineers most commonly see this error caused by:

• A corrupted .ND file left behind after a QuickBooks update or reinstall
• The QuickBooksDBXX service (where XX corresponds to your QuickBooks version) running under an incorrect Windows user account
• A server crash or improper shutdown that damaged the database service configuration
• Multiple versions of QuickBooks Database Server Manager installed on the same host, causing routing conflicts
• Antivirus or firewall software quarantining components of the database service account

How to Fix It

Scenario 1: Corrupted .ND File (Most Common)

1. On the computer hosting the company file, close QuickBooks on all workstations.
2. Open the folder where your company file is stored.
3. Locate the file ending in .ND that shares your company file's name (for example, CompanyFile.QBW.ND).
4. Right-click the .ND file and select Rename. Add .OLD to the end of the file name.
5. Open the Windows Start menu, locate the QuickBooks folder, and open QuickBooks Database Server Manager.
6. Select the Scan Folders tab and browse to the folder containing your company file.
7. Click Start Scan. The Database Server Manager will generate a fresh, undamaged .ND file.
8. Open QuickBooks on a workstation and attempt to access the file.

Scenario 2: Incorrect Database Service Account Configuration

1. Press Windows Key + R, type services.msc, and press Enter.
2. Scroll through the list and locate the service named QuickBooksDBXX (for example, QuickBooksDB33 for QuickBooks 2023).
3. Right-click the service and select Properties.
4. Select the Log On tab.
5. Verify that the service is set to run under the Local System account or the correct Windows admin account. If the account listed is incorrect or shows as an unknown SID, select Local System account.
6. Click Apply, then OK. If prompted, enter the valid Windows administrator password.
7. Right-click the QuickBooksDBXX service and select Restart.
8. Attempt to open the company file from a workstation.

Scenario 3: Conflicting Database Server Manager Versions

1. Open the Windows Control Panel and navigate to Programs and Features.
2. Search the installed programs list for multiple instances of QuickBooks Database Server Manager.
3. Uninstall all versions except the one matching your current QuickBooks Desktop version.
4. Run a clean install of the matching Database Server Manager.
5. Open Database Server Manager and perform a full folder scan on the directory holding your company file.

How to Prevent It Recurring

To keep the database service configuration stable, our engineers recommend designating a single dedicated host machine for the company file and avoiding installing multiple QuickBooks versions on that server. Always shut down QuickBooks and the server through the proper operating system commands rather than forcing a hard shutdown. Configure your third-party antivirus software to exclude the QuickBooks installation directory and the company file folder from active scanning, which prevents the security software from severing the database service account connection.