Server Migration: Troubleshooting Error 6000 When Moving Company Files

Migrating QuickBooks Desktop company files to a new server frequently triggers 6000-series errors (such as Error 6000, -83 or 6000, -77) when workstations attempt to access the new location. This error occurs because legacy Network Data (.ND) files retain outdated server paths, folder permissions fail to grant access to QuickBooks database services, or the Database Server Manager has not scanned the new directory. You can fix Error 6000 after a server migration by deleting old .ND and .TLG files, assigning full folder permissions, and rescanning with Database Server Manager on the new server.

Fast-Fix: The 45-Second Solution

To fix Error 6000 after moving company files to a new server, delete old network support files and rescan the directory. On the new server, delete all .ND files in the company folder. Open QuickBooks Database Server Manager on the new server, scan the shared folder to build fresh .ND files, and ensure the folder’s Sharing and Security tabs grant Full Control to Everyone, SYSTEM, and the local QBDataServiceUser## account.

---

Quick Status & Triage Snapshot

• Primary Error Codes: Error 6000, -83, Error 6000, -77, or Error 6000, -107 occurring immediately following server migrations or folder relocation.
• Data Risk Tier: Low. The accounting records inside .QBW are intact; the error stems from network misconfigurations and stale configuration files.
• Multi-User Impact: Complete lockout across all workstations connecting to the migrated file path.
• Estimated Fix Time: 10 to 20 minutes.

---

Technical Anatomy: Why Server Migrations Trigger Error 6000

When moving company files from an older server (e.g., Windows Server 2016 or 2019) to a new host (e.g., Windows Server 2022 or 2025), administrators typically copy the entire company folder structure. While this preserves files, it also transfers hidden environmental conflicts:

1. Stale .ND Network Pointers: The .ND file created on the old server contains the old host’s static IP address, machine name, and port allocation. When workstations open the file on the new server, QuickBooks reads the old .ND file and tries to connect to the decommissioned server, throwing Error 6000, -83.
2. Missing Service Permissions: On the new server, the Windows user accounts that run the database daemon (QBDataServiceUser##) do not inherit permissions automatically. If the service account cannot write lock files to the folder, multi-user hosting aborts.
3. Unregistered Database Manager: If the company folder on the new server has not been explicitly scanned by the QuickBooks Database Server Manager, the Sybase SQL engine will refuse incoming network connection requests.

---

Diagnostic Flowchart: Post-Migration Error 6000 Workflow

Start: Error 6000 appears after migrating files to a new server
 │
 ├──> Did you copy the old .ND and .TLG files over with the .QBW?
 │     ├── YES ──> Delete all .ND files in the migrated folder immediately.
 │     └── NO  ──> Proceed to Database Server Manager setup.
 │
 ├──> Is the matching QuickBooks Database Server Manager installed on the new server?
 │     ├── NO  ──> Install the Database Server Manager version matching your client year.
 │     └── YES ──> Open QBDBSM and scan the new company folder.
 │
 ├──> Verify Windows Sharing & NTFS Security on the new host folder:
 │     └── Grant Full Control to Everyone, SYSTEM, and QBDataServiceUser##.
 │
 └──> Test connection from client workstation using direct UNC path (\\NewServer\Share\).

---

Step-by-Step Server Migration Fix Guide

Work through these steps directly on your new host server to resolve post-migration errors.

Step 1: Install the Matching QuickBooks Database Server Manager

Workstations cannot connect to files on a new server if the server is acting as a passive file share without the active database engine.

1. On the new server, run the QuickBooks Desktop installation package.
2. Choose Custom and Network Options, then select:
   I’ll be using QuickBooks Desktop on this computer, AND I’ll be storing our company file here so it can be shared over our network, or I will NOT be using QuickBooks Desktop on this computer… (Database Server Manager Only).
3. Finish the installation to ensure the Windows service (e.g., QuickBooksDB34 for 2024 or QuickBooksDB35 for 2025) is created and set to Automatic startup.

For detailed operating system requirements on newer hosting platforms, consult our deployment guide on Windows Server 2025: Installing QuickBooks Database Server Manager.

Step 2: Delete Stale .ND Files Inherited from the Old Server

Purging old network files forces the database manager on the new server to build configuration files with current network parameters.

1. Open File Explorer on the new server.
2. Navigate to the migrated folder containing your company file (.QBW).
3. Make sure file extensions are visible (click View > Show > File name extensions).
4. Locate any files ending in .ND (e.g., CompanyFile.qbw.nd).
5. Right-click and Delete these .ND files.
6. (Optional) If you also encountered log mismatch errors, rename CompanyFile.qbw.tlg to CompanyFile.qbw.tlg.old as outlined in Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.

Step 3: Configure Windows Share and NTFS Folder Permissions

Permissions do not automatically transfer between servers. You must configure access rights for both network sharing and the local file system.

1. Right-click the folder containing your company files and select Properties.
2. Go to the Sharing tab and click Advanced Sharing.
3. Check Share this folder, click Permissions, and grant Full Control to Everyone (or your designated Domain Users group). Click OK.
4. Switch to the Security tab (NTFS permissions) on the Properties window.
5. Click Edit and verify that the following accounts have Full Control:
   • SYSTEM
   • Administrators
   • Users (or Domain Users)
   • The specific database service account: QBDataServiceUser## (where ## matches your version year, such as QBDataServiceUser34).
6. Click Apply, then click OK.

For a complete checklist of folder security settings, see Multi-User Access: Verifying Folder Sharing & Network Permissions.

Step 4: Scan the Migrated Directory with Database Server Manager

Scanning mounts the company file directory into the database engine registry and generates a clean, authoritative .ND file.

1. On the new server, open the Windows Start menu, type QuickBooks Database Server Manager, and launch it.
2. Click the Scan Folders tab.
3. Click Add Folder and browse to the local drive path of your migrated company folder (e.g., D:\QuickBooksData\).
4. Click Scan.
5. Ensure the scan completes with a status of “Complete” and confirms your company file is found.
6. Check your company folder in File Explorer to verify that a fresh .ND file was created with the new server’s name and dynamic port.

Step 5: Update Workstation Mapped Drives and UNC Paths

Workstations will trigger Error 6000 if they attempt to open recent file shortcuts pointing to the retired server.

1. On each client workstation, open QuickBooks Desktop to the No Company Open screen.
2. If your old company file appears in the recent files list, do not click it.
3. Click Open or restore an existing file, choose Open a company file, and click Next.
4. In the address bar, type the direct UNC path to the new server:
   \\[NewServerName]\[ShareName]\(Example: \\FS01\QBData\)
5. Select your company file and click Open.

If your workstations rely on mapped drive letters, remap the network drive to the new server share before opening files. Follow our guide on File Access: How to Map a Network Drive for QuickBooks Company Files.

---

Differential Diagnosis: Post-Migration Error 6000 Codes

• Error 6000, -83 Post-Migration vs. Standard Error 6000, -83: A standard 6000, -83 error often points to hosting conflicts on workstations. Post-migration 6000, -83 errors are almost always caused by stale IP addresses inside copied .ND files or missing QBDataServiceUser## NTFS permissions on the new server drive. Review our dedicated guide on QuickBooks Error 6000, -83: Expert Guide to Host Configuration & Setup Errors.
• Error 6000, -77 Post-Migration: This error indicates that the company file is located in a folder with incorrect permission structures, or that the path references an external drive letter or non-standard storage location that QuickBooks treats as restricted.

---

Hard Stop: Domain Controller and Subnet Isolation

If Error 6000 persists after deleting support files and confirming folder permissions, check your network infrastructure:

• Subnet Mismatch: If the new server was placed on a different corporate VLAN or subnet (e.g., server on 10.0.1.x, workstations on 192.168.1.x), routers may be filtering broadcast packets required for database discovery.
• Domain Controllers: If the new server is an Active Directory Domain Controller, QuickBooks Database Server Manager cannot run under standard local service accounts. You must adjust the service configuration to run under a domain user account with appropriate directory rights.