QuickBooks Error 6175, often shown as Error -6175,0, appears in QuickBooks Desktop when QuickBooks cannot access the company file through the database server. In plain terms, the workstation is trying to open a company file over the network, but the server component that manages multi-user access is not responding correctly.
This error does not apply to QuickBooks Online. QuickBooks Online does not use local .QBW company files or QuickBooks Database Server Manager. If you are seeing Error -6175,0, you are working with QuickBooks Desktop or a Desktop-based environment.
The good news is that this error is often fixable without touching the accounting data itself. Most cases involve hosting settings, QuickBooks Database Server Manager, Windows services, network configuration files, folder permissions, or firewall rules. The steps below walk through the safest order to troubleshoot the problem.
Quick Answer
To fix QuickBooks Error 6175, close QuickBooks on all computers, update QuickBooks Desktop, run QuickBooks File Doctor, scan the company file folder with QuickBooks Database Server Manager on the server, make sure only the server is hosting multi-user access, restart the QuickBooksDBXX and QBCFMonitorService services, then test the company file from a workstation. If the error continues, review firewall and security software settings.
What QuickBooks Error 6175 Means
QuickBooks Desktop uses a company file, usually ending in .QBW, to store your accounting data. In a multi-user setup, that file is commonly stored on a server or host computer. Workstations do not directly manage the file on their own. Instead, they communicate with QuickBooks Database Server Manager, which allows multiple users to access the file safely.
Error -6175,0 usually means QuickBooks Desktop cannot communicate properly with that database server component. The file may be fine, but QuickBooks cannot reach it in the way multi-user mode requires.
Common causes include:
- QuickBooks Database Server Manager is not running on the server.
- The company file folder has not been scanned by Database Server Manager.
- More than one computer is set to host multi-user access.
- A workstation is trying to open the file from the wrong network path.
- Windows Firewall or security software is blocking QuickBooks communication.
- The QuickBooksDBXX service is stopped or set to manual startup.
- The .ND network data file is damaged or outdated.
- QuickBooks Desktop is not updated consistently across the server and workstations.
- Windows folder permissions do not allow the user to access the company file location.
Before You Start: Important Safety Checks
Do not begin by deleting files or moving the company file. Error 6175 is usually a network and hosting issue, not a reason to edit the main .QBW file. A safer troubleshooting process starts with access, services, and configuration.
Before making changes, confirm the following:
- You can access the server computer where the company file is stored.
- You have Windows administrator rights on the server and affected workstations.
- QuickBooks Desktop is installed and updated on the computers used to access the file.
- QuickBooks Tool Hub is installed on the affected computer or server.
- You have a recent backup of the QuickBooks Desktop company file.
- The company file is stored on a local server drive, not only on a removable drive or unsupported shared location.
- All users have closed QuickBooks before you change hosting, services, or network settings.
- The server and workstations can communicate over the network.
Professional caution: If you suspect company file damage, stop and create a backup or copy before running repair utilities. Do not keep working in a file that may be damaged.
Step-by-Step Fix for QuickBooks Error 6175
Work through these steps in order. If all workstations are affected, start your troubleshooting on the server. If only one workstation is affected, check that workstation first, especially its network path, firewall, and hosting setting.
1. Close QuickBooks on every computer
Before changing hosting settings, restarting services, or renaming support files, make sure all users are out of QuickBooks Desktop. This matters because QuickBooks network files and services can remain active while users are connected.
Ask each user to close the company file and exit QuickBooks Desktop. If your office uses Remote Desktop or a hosted Windows environment, confirm that users are fully signed out of QuickBooks, not just disconnected from a session.
Expected result: No users are actively connected to the company file.
If this does not work: Restarting the server later in the process may clear stuck sessions, but do not restart a server without confirming it will not interrupt other business operations.
2. Update QuickBooks Desktop on the server and workstations
QuickBooks Desktop versions and releases should be consistent across the computers using the same company file. An outdated workstation or server installation can contribute to multi-user issues.
Update QuickBooks Desktop on the server first, then update the affected workstations. The exact update process can vary slightly by version, but the goal is to install the latest available release for your supported QuickBooks Desktop product.
Why it matters: Updates can include program fixes and components needed for stable multi-user access.
Expected result: The server and workstations are running current QuickBooks Desktop releases for their installed year.
3. Run QuickBooks File Doctor from Tool Hub
QuickBooks Tool Hub includes QuickBooks File Doctor, which can help diagnose company file and network access issues. This is a useful early step because it checks common problems without requiring you to manually edit QuickBooks support files.
Open QuickBooks Tool Hub, select Company File Issues, and run QuickBooks File Doctor. Choose the affected company file. If File Doctor asks for the QuickBooks admin password, enter it.
Why it matters: File Doctor can identify and repair certain file and network problems that may trigger Error -6175,0.
Expected result: File Doctor completes its scan and repair attempt.
If the error remains: Do not keep rerunning the same tool repeatedly. Move to the server-side database and hosting checks.
4. Scan the company file folder in QuickBooks Database Server Manager
QuickBooks Database Server Manager must be installed and configured on the computer that stores the company file. If the company file was moved, restored, or migrated to a new server, Database Server Manager may not be watching the correct folder.
On the server, open QuickBooks Tool Hub, select Network Issues, and open QuickBooks Database Server Manager. Scan the folder that contains the company file. Use the server local path when scanning, not a workstation shortcut or mapped drive path.
Why it matters: Database Server Manager creates and maintains the network information QuickBooks needs for multi-user access.
Expected result: The folder containing the .QBW company file appears in Database Server Manager after the scan.
If the folder does not appear: Confirm you are on the actual server that stores the company file and that you have administrator rights. Also confirm the file is not stored only on a removable drive or unsupported shared location.
5. Confirm only the server is hosting multi-user access
This is one of the most important checks. In a proper QuickBooks Desktop multi-user setup, the server that stores the company file should host multi-user access. Workstations should not host the same company file.
On the server, open QuickBooks Desktop and check the hosting setting under the QuickBooks utilities area. If the server is not hosting, enable hosting there.
On each workstation, open QuickBooks Desktop and confirm hosting is turned off. If a workstation is set to host multi-user access, turn hosting off on that workstation.
Why it matters: Multiple computers trying to host the same company file can confuse QuickBooks network communication and trigger access errors.
Expected result: The server hosts multi-user access. Workstations access the file over the network without hosting it.
Common mistake: Turning on hosting on every workstation feels logical to many users, but it is usually wrong. Hosting belongs on the server, not on every computer that opens the file.
6. Restart QuickBooks database services on the server
QuickBooks Database Server Manager depends on Windows services. If these services are stopped, disabled, or set incorrectly, workstations may not be able to connect to the company file.
On the server, open Windows Services. Look for the QuickBooksDBXX service, where XX represents the QuickBooks Desktop version year. Also check QBCFMonitorService. Restart the QuickBooksDBXX service and confirm the startup type is set to Automatic if it is not already.
Why it matters: The QuickBooksDBXX service handles database access for multi-user mode. If it is not running, QuickBooks may display Error -6175,0 when a workstation tries to open the file.
Expected result: QuickBooksDBXX and QBCFMonitorService are running on the server.
If the service is missing: QuickBooks Database Server Manager may not be installed properly on the server, or the installed QuickBooks components may not match the company file environment. A repair or reinstallation of the server components may be needed.
7. Restart the server and affected workstations
If you changed hosting settings, restarted services, updated QuickBooks, or rescanned the folder, restart the server and affected workstations. This clears old network sessions and lets QuickBooks services start fresh.
Why it matters: Some service and hosting changes do not fully apply until Windows and QuickBooks components restart.
Expected result: The server comes back online, QuickBooksDBXX starts automatically, and workstations can reach the shared folder.
If workstations still cannot reach the file location: Check basic network access before opening QuickBooks. The workstation must be able to reach the server folder that contains the company file.
8. Test the company file from the server, then a workstation
Open the company file directly on the server first. This confirms that the file itself can open in QuickBooks Desktop. Then test from one workstation using the correct network path.
If the file opens on the server but not from any workstation, focus on Database Server Manager, network sharing, Windows permissions, firewall rules, and QuickBooks services. If only one workstation fails, focus on that specific computer.
Expected result: The company file opens from the server and from at least one workstation. Multi-user mode works without Error -6175,0.
9. Rename the .ND file if network data appears damaged
The .ND file is a QuickBooks Network Data file. It stores information QuickBooks uses to open the company file across the network. If it is outdated or damaged, QuickBooks may fail even when the company file itself is not damaged.
Only do this after all users are out of QuickBooks. In the folder that contains the company file, locate the .ND file associated with the company file. Rename the .ND file by adding a safe ending such as .old. Do not rename or delete the main .QBW company file. After renaming the .ND file, rescan the folder using QuickBooks Database Server Manager.
Why it matters: Rescanning the folder allows Database Server Manager to recreate network configuration data.
Expected result: A fresh network data file is created and the workstation can connect.
If you are unsure: Get help before renaming QuickBooks support files. Renaming the wrong file can create unnecessary confusion.
10. Review firewall and security software settings
If hosting, services, and Database Server Manager are correct but Error 6175 continues, the connection may be blocked by Windows Firewall or another security product.
QuickBooks Desktop uses program components and database server ports for multi-user access. The specific port requirements vary by QuickBooks Desktop year. Do not permanently turn off firewall protection. Instead, configure the firewall to allow the appropriate QuickBooks Desktop programs and database server communication.
Why it matters: A firewall can allow normal internet browsing while still blocking QuickBooks database traffic between a workstation and server.
Expected result: QuickBooks programs and database communication are allowed, and the company file opens from the workstation.
If your business uses managed antivirus or IT security tools: Coordinate changes with your IT provider. Security rules may be controlled centrally and can override local Windows settings.
Troubleshooting Logic: Where to Look First
Error 6175 becomes easier to diagnose when you separate server-wide problems from workstation-specific problems.
| Situation | Likely Area to Check | Practical Next Step |
|---|---|---|
| All workstations get Error -6175,0 | Server, Database Server Manager, QuickBooksDBXX service, firewall | Start on the server and confirm services, hosting, and folder scan |
| Only one workstation gets the error | That workstation network path, hosting setting, local firewall | Turn off hosting on the workstation and verify it can reach the shared folder |
| File opens on server but not over network | Network sharing, permissions, firewall, Database Server Manager | Confirm the folder is scanned and accessible from the workstation |
| Error began after moving the company file | Database Server Manager scan and network path | Scan the new folder from the server and update workstation shortcuts |
| Error began after server migration | Server components and hosting configuration | Reinstall or reconfigure Database Server Manager on the new server |
How to Verify the Fix
Do not assume the issue is resolved just because the file opens once. A proper verification checks the server, workstation access, services, and backup ability.
| Check | How to Verify | Expected Result |
|---|---|---|
| Company file opens on server | Open the .QBW file directly in QuickBooks Desktop on the server | The file opens without Error -6175,0 |
| Company file opens from workstation | Open the file using the correct network path | At least one workstation opens the file successfully |
| Database Server Manager is scanning the right folder | Open Database Server Manager on the server | The company file folder appears in the scanned folder list |
| Hosting is correct | Check hosting settings on server and workstations | Only the server is hosting multi-user access |
| QuickBooks services are running | Check Windows Services on the server | QuickBooksDBXX and QBCFMonitorService are running |
| Backup works | Create a company file backup after repairs | QuickBooks creates the backup successfully |
Common Mistakes That Make Error 6175 Worse
Many Error -6175,0 cases take longer to fix because users change too many things at once. Keep the troubleshooting controlled and document what you change.
- Trying to fix it in QuickBooks Online: This is a QuickBooks Desktop error. QuickBooks Online does not use Database Server Manager.
- Turning on hosting everywhere: Only the server should host multi-user access in a standard setup.
- Moving the company file without rescanning: Database Server Manager needs to scan the folder where the file actually lives.
- Skipping the backup: Always protect the company file before repair work.
- Deleting support files blindly: The .QBW file is your accounting data. Do not delete or rename it during network troubleshooting.
- Ignoring permissions: Even if QuickBooks is configured correctly, Windows user permissions can still block access to the folder.
- Running File Doctor only on a workstation: If the server is the problem, server-side checks are necessary.
- Leaving firewall protection off: Temporarily testing security settings is different from permanently disabling protection. Configure exceptions instead.
Best Practices for Preventing QuickBooks Error 6175
A stable QuickBooks Desktop multi-user setup depends on consistency. Small environment changes, such as moving a file or replacing a server, can break access if the QuickBooks database components are not updated afterward.
- Keep QuickBooks Desktop updated on every computer in the setup.
- Store the active company file in a dedicated shared folder on the server.
- Use QuickBooks Database Server Manager on the server that stores the file.
- Allow only the server to host multi-user access.
- Create regular QuickBooks backups and verify that backups complete successfully.
- Use Windows user accounts with appropriate folder permissions.
- Restart QuickBooks database services after major QuickBooks updates when needed.
- Document the server name, shared folder path, QuickBooks version, and hosting setup.
When Professional Help Makes Sense
Many Error 6175 cases can be fixed with the steps above. Professional help becomes worthwhile when the troubleshooting affects the server, multiple users, or the integrity of the company file.
Consider getting QuickBooks support if:
- All workstations are locked out of the company file.
- The error started after a server migration or file move.
- QuickBooks services are missing, damaged, or will not stay running.
- Firewall or security software rules are managed by an IT environment.
- You are unsure which computer should host the company file.
- The company file may be damaged or backups are failing.
- The business cannot afford extended downtime while users are unable to work.
From a bookkeeping and accounting perspective, the biggest risk is not the error message itself. The larger risk is making rushed changes to the wrong file, using an unsupported storage location, or creating a network setup that causes recurring access issues. If the standard steps do not resolve the problem, it is usually more efficient to have someone review the environment directly.
Frequently Asked Questions
Does QuickBooks Error 6175 affect QuickBooks Online?
No. QuickBooks Error -6175,0 applies to QuickBooks Desktop company file access. QuickBooks Online is browser-based and does not use local .QBW files or QuickBooks Database Server Manager.
Why does Error 6175 happen in multi-user mode?
Multi-user mode depends on QuickBooks Database Server Manager and the QuickBooksDBXX service. If the workstation cannot communicate with the server component, QuickBooks may display Error -6175,0.
Should every workstation host multi-user access?
No. In a standard QuickBooks Desktop multi-user setup, only the server that stores the company file should host multi-user access. Workstations should have hosting turned off.
Can QuickBooks File Doctor fix Error 6175?
It can help with some company file and network issues, so it is a good early troubleshooting step. If the underlying problem is server hosting, services, folder scanning, or firewall rules, you may still need to correct those settings manually.
What is the QuickBooksDBXX service?
QuickBooksDBXX is a Windows service used by QuickBooks Database Server Manager. The XX represents the QuickBooks Desktop version year. This service should be running on the server that hosts the company file.
Is it safe to rename the .ND file?
Renaming the .ND file can be safe when QuickBooks is closed for all users and you rename only the network data file associated with the company file. Do not rename or delete the main .QBW company file.
What if the company file opens on the server but not on workstations?
That usually points to a network, hosting, Database Server Manager, firewall, or permissions issue. Confirm the folder is scanned on the server, the services are running, the workstation can reach the shared folder, and only the server is hosting.
Can firewall settings cause QuickBooks Error 6175?
Yes. Windows Firewall or third-party security software can block QuickBooks database communication. The correct fix is to allow the needed QuickBooks programs and ports, not to leave firewall protection turned off permanently.
Key Takeaways
- QuickBooks Error 6175 is a QuickBooks Desktop company file access error, not a QuickBooks Online issue.
- The problem usually involves Database Server Manager, hosting settings, Windows services, firewall rules, or network configuration files.
- Only the server should host multi-user access in a standard QuickBooks Desktop setup.
- QuickBooksDBXX and QBCFMonitorService should be running on the server.
- If the company file was moved or the server changed, rescan the folder in QuickBooks Database Server Manager.
- Back up the company file before repair work and avoid editing or deleting the main .QBW file.
Conclusion
QuickBooks Error -6175,0 is usually a sign that QuickBooks Desktop cannot reach the company file through the database server. Start with the server, confirm Database Server Manager is scanning the correct folder, make sure hosting is enabled only where it belongs, restart the QuickBooks services, and then test from a workstation.
If the error continues after those checks, the issue is often deeper than a simple QuickBooks setting. Firewall rules, Windows permissions, damaged network data, or an incomplete server migration may be involved. At that point, careful troubleshooting matters because the wrong change can create more downtime or put the company file at risk.
Need Expert Help with QuickBooks?
If QuickBooks Error 6175 is keeping your team out of the company file, Databrax can help you review the server setup, Database Server Manager, hosting configuration, QuickBooks services, network access, and related company file issues. We provide practical QuickBooks Error Resolution and QuickBooks Support so you can get back to working in the file with less guesswork and less risk.