QuickBooks Error 6175, 0 occurs when QuickBooks Desktop cannot start the database server manager service needed to access a company file in multi-user mode. The error message typically reads: "An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit." followed by error code -6175, 0.
This error is specifically related to the QuickBooks Database Server Manager (QBDBMgrN) service, which handles multi-user file access. When this service fails to start or loses communication with the company file, QuickBooks cannot open the file and displays the 6175 error. The issue can affect both the server computer hosting the file and workstations trying to connect to it.
The good news is that this error is well-documented and has several proven solutions. The most common causes are a stopped or corrupted database service, firewall blocking QuickBooks ports, incorrect hosting configuration, or a damaged company file. Follow the steps below in order to resolve the issue.
Restart the QuickBooks Database Server Manager service. Press Windows+R, type services.msc, find "QuickBooksDBXX" (where XX is your version year), right-click it and select Restart. Then try opening your company file again. This resolves the error in approximately 50% of cases.
Error -6175, 0: QuickBooks is trying to access the company file but cannot communicate with the database serverBasic Troubleshooting
Step 1: Restart the QuickBooks Database Server Manager service. Press Windows+R on the server computer, type services.msc, and press Enter. Scroll down to find "QuickBooksDBXX" (the XX corresponds to your QuickBooks version — for example, QuickBooksDB33 for QuickBooks 2023). Right-click the service and select Restart. If the service is stopped, click Start. Wait for the service status to show "Running" before attempting to open your company file again.
Step 2: Verify the hosting configuration is correct. On the server computer (the one where the company file is stored), open QuickBooks, go to File > Utilities, and make sure "Host Multi-User Access" is selected. On all workstation computers, go to File > Utilities and ensure "Stop Hosting Multi-User Access" is selected. Only the server should host — if a workstation is accidentally set to host, it causes conflict errors including 6175.
Step 3: Run the QuickBooks File Doctor tool. Download the QuickBooks Tool Hub from the official Intuit website. Open the Tool Hub and select "Company File Issues." Click "Run QuickBooks File Doctor." Select your company file (browse to it if it does not appear automatically). Choose "Check your file and network" and click Continue. The tool will diagnose and attempt to repair both file and network issues that cause the 6175 error.
Step 4: Check Windows Firewall settings. Open Windows Defender Firewall > Advanced Settings. Click Inbound Rules and look for rules allowing QuickBooks programs (QBW32.exe, QBDBMgrN.exe, QBDBMgr.exe) and the QuickBooks ports (8019, 56728, 55378-55382). If these rules do not exist, create new inbound rules for each program and port. Repeat for Outbound Rules. Third-party firewalls and antivirus software may also need exceptions configured.
Advanced Solutions
Step 1: Configure QuickBooks Database Server Manager manually. Open the QuickBooks Database Server Manager from the Windows Start menu (it installs separately from QuickBooks). Click the "Scan Folders" tab and add the folder containing your company file. Click Scan. The tool will create the necessary network descriptor files (.ND) that allow multi-user access. After scanning, restart the database service and try opening your company file.
Step 2: Delete and regenerate the network descriptor (.ND) file. Navigate to the folder containing your company file (typically something like C:\Users\Public\Documents\Intuit\QuickBooks\Company Files). Find the file with the same name as your company file but with an .ND extension (for example, MyCompany.qbw.nd). Delete this file. Open QuickBooks Database Server Manager and rescan the folder to generate a fresh .ND file. Corrupted .ND files are a common cause of error 6175.
Step 3: Verify Windows user permissions on the company file folder. Right-click the folder containing the company file and select Properties > Security tab. Ensure the QBDataServiceUserXX account has Full Control permissions. Also verify that the Windows user account running QuickBooks has Read/Write access. Click Edit to modify permissions if needed. Insufficient folder permissions prevent the database server from accessing the company file.
Step 4: Reinstall the QuickBooks Database Server Manager. Open Control Panel > Programs and Features. Find "QuickBooks Database Server Manager" and uninstall it. Download the latest QuickBooks Database Server Manager installer from the Intuit website. Install it on the server computer and run the initial scan to register your company files. Restart the computer after installation before testing.
Step 5: If the error persists, try opening the company file in single-user mode first. On the server computer, open QuickBooks and select File > Open or Restore Company > Open a company file. Navigate to your file and open it. Once open in single-user mode, go to File > Utilities > Host Multi-User Access to switch back to multi-user mode. This can reset the hosting state and resolve persistent 6175 errors.
Why Does This Problem Happen?
Error 6175, 0 is fundamentally a communication failure between the QuickBooks application and the database server that manages multi-user file access. The QuickBooks Database Server Manager runs as a Windows service in the background and must be active whenever multiple users need to access the same company file. When this service crashes, is blocked by a firewall, or loses access to the company file, error 6175 appears.
Common triggers include Windows updates that reset firewall rules or service configurations, antivirus software quarantining QuickBooks components, power outages that corrupt the network descriptor file, and incorrect hosting settings where multiple computers are trying to host the same company file simultaneously. Regular maintenance of the server environment and keeping QuickBooks updated helps prevent this error.