Steven Moody

QuickBooks Error 6190: Expert Fix for Multi-User File Access

The important point is that Error 6190 is a company-file access problem, not automatically evidence of permanent data loss. Several conditions can produce the error, including problems involving the company file, transaction log, hosting configuration, network communication, or an incomplete QuickBooks session.

This expert guide explains what QuickBooks Error 6190 means, why it happens, how to troubleshoot it safely, how the 6190, 816 variant fits into the problem, and how to distinguish it from other QuickBooks 6000-series errors.

What Is QuickBooks Error 6190?

QuickBooks Error 6190 is a company-file access error that can occur when QuickBooks Desktop cannot properly access or open a company file, particularly in a multi-user environment.

A common message is similar to:

“QuickBooks is unable to open this company file. It may have been opened by another user.”

The exact cause can vary. A mismatch involving the .QBW company file and .TLG transaction log can be involved, but 6190 should not automatically be diagnosed as a TLG mismatch without checking the surrounding environment.

Other contributing factors can include:

• A company file being opened by another user
• Incorrect hosting configuration
• A workstation attempting to host the file
• Network communication problems
• QuickBooks Database Server Manager issues
• Damaged or outdated .ND network configuration data
• An interrupted QuickBooks session
• File permissions problems
• Version or release inconsistencies
• Company-file corruption
• A company file stored in an unsuitable location

Because multiple causes can produce similar symptoms, troubleshooting should start with the simplest access and hosting checks before moving to file repair.

Quick Facts About Error 6190

• Product: QuickBooks Desktop
• Error family: 6000-series company-file errors
• Primary symptom: Company file will not open
• Common environment: Multi-user and networked installations
• Potential causes: File access, hosting, network, .ND/.TLG configuration, permissions, or data issues
• Data risk: The error itself does not prove that accounting data has been lost
• Recommended approach: Diagnose the hosting and file environment before performing repair operations

Why Does QuickBooks Error 6190 Occur?

Error 6190 can have more than one underlying cause. Understanding the environment helps prevent unnecessary changes to the company file.

1. Company File and Transaction Log Are Not Consistent

The QuickBooks company file uses a .QBW file, while the transaction log uses a .TLG file.

After an unexpected interruption, crash, forced shutdown, or other abnormal event, QuickBooks may encounter an inconsistency between the current company file state and supporting file information.

This is one reason the .TLG file is frequently discussed when troubleshooting Error 6190.

However, renaming the .TLG file should be treated as a targeted troubleshooting step rather than an automatic first response.

2. QuickBooks Was Interrupted During an Active Session

A computer shutdown, application crash, power interruption, or forced restart can leave the QuickBooks environment in an incomplete state.

When QuickBooks starts again, it may have difficulty determining whether the company file is still being used.

3. Another User Has the Company File Open

In a multi-user environment, another user may already have the company file open.

Before modifying files, confirm that:

• All users have closed QuickBooks.
• No workstation is still connected.
• No remote session is keeping QuickBooks open.
• The server is correctly configured for hosting.

This simple check can prevent unnecessary troubleshooting.

4. Incorrect Hosting Configuration

QuickBooks Desktop multi-user environments rely on proper hosting.

A common configuration principle is:

Server = hosts the company file

Workstations = access the hosted company file

If hosting is incorrectly configured, users may experience company-file access errors, including 6000-series problems.

5. QuickBooks Database Server Manager Problem

The QuickBooks Database Server Manager provides important functionality for accessing company files stored on a server.

If the appropriate database service is stopped, improperly configured, or unable to communicate with the company-file folder, workstations may fail to access the file.

6. Network Communication Failure

A weak or interrupted network connection can prevent a workstation from communicating correctly with the company file.

Potential causes include:

• Network interruptions
• Incorrect firewall configuration
• DNS or connectivity problems
• Server availability problems
• Incorrect shared-folder permissions
• Wireless instability
• Incorrect hosting configuration

7. Damaged .ND File

The .ND file contains network configuration information associated with a QuickBooks company file.

If this file becomes damaged or contains outdated configuration information, QuickBooks may have trouble communicating with the company file over a network.

Renaming the .ND file allows QuickBooks to create a new one.

8. Version or Release Differences

Different QuickBooks Desktop installations should be maintained appropriately across the server and workstations.

If one computer has an incompatible or outdated release, multi-user connectivity can become unstable.

Always check the actual product version and release before assuming that every installation is identical.

9. File Permission Problems

Windows permissions can also interfere with company-file access.

The QuickBooks user account and database service need appropriate access to the folder containing the company file.

Permission problems become especially important after:

• Moving a company file
• Changing Windows accounts
• Migrating to a new server
• Restoring a backup
• Changing folder structures
• Reconfiguring network shares

Symptoms of QuickBooks Error 6190

You may be dealing with Error 6190 when you notice one or more of the following:

• QuickBooks cannot open the company file.
• An error message says the file may already be open.
• Multiple users cannot access the company file.
• QuickBooks repeatedly switches between single-user and multi-user mode.
• A workstation cannot connect to the company file.
• QuickBooks becomes unresponsive while opening the file.
• Transactions cannot be saved.
• The company file opens on the server but not on workstations.
• The company file works locally but fails through the network.
• A 6000-series error appears when opening the file.

These symptoms are useful clues, but the exact error code and environment should always be confirmed before choosing a repair method.

Before Fixing Error 6190: Protect Your Accounting Data

Before performing file-level troubleshooting, take a cautious approach.

Create a backup when possible

If you can access the company file from any computer, create a current backup before making significant changes.

Close QuickBooks Everywhere

Ask all users to exit QuickBooks.

Do not rename company-file support files while another user is actively working in the company file.

Identify the Company File Location

Determine whether the .QBW file is:

• On the local computer
• On a dedicated server
• On a shared Windows folder
• In a hosted environment
• On another networked computer

This distinction is critical because a local-file problem and a network-hosting problem require different troubleshooting.

How to Fix QuickBooks Error 6190

Work through the following methods in order. Stop once the problem is resolved.

Method 1: Confirm Nobody Else Is Using the Company File

This is the safest first check.

1. Ask every QuickBooks user to close QuickBooks.
2. Check the server and workstations.
3. Confirm that no remote desktop session is still running QuickBooks.
4. Wait briefly for all QuickBooks processes to close.
5. Reopen QuickBooks on the computer where the company file is stored.
6. Try opening the company file.

If the file opens locally but not from workstations, move your investigation toward hosting and network configuration.

Method 2: Check Hosting Settings

Incorrect hosting is a common source of multi-user problems.

On the computer that stores the company file:

1. Open QuickBooks Desktop.
2. Open the File menu.
3. Select Utilities.
4. Review the hosting-related option.
5. Confirm the server is configured to host the company file.
6. On workstations, verify that they are not unnecessarily configured to host the file.
7. Close and reopen QuickBooks.
8. Test the company file again.

The exact menu wording can vary by QuickBooks Desktop edition and setup, so use the hosting option displayed by your installed version.

Method 3: Restart the QuickBooks Database Service

If the company file is hosted on a Windows server, check the relevant QuickBooks Database Server Manager service.

1. Close QuickBooks on the affected computers.
2. Open Windows Services on the server.
3. Locate the QuickBooks database service associated with the installed version.
4. Check whether the service is running.
5. If appropriate, restart the service.
6. Reopen QuickBooks.
7. Test the company file from a workstation.

If the service repeatedly stops, investigate the server configuration instead of repeatedly restarting it.

Method 4: Rename the .ND File

If the network configuration file is damaged or outdated, rebuilding it can help.

First, close QuickBooks on all computers.

Then:

1. Locate the folder containing the company file.
2. Find the .ND file associated with the company file.
3. Right-click the file.
4. Select Rename.
5. Add .OLD to the filename.
6. Do not delete the original file.
7. Reopen QuickBooks.
8. Allow QuickBooks to recreate the network configuration file.
9. Test multi-user access.

For example:

CompanyName.qbw.ND

can become:

CompanyName.qbw.ND.OLD

Renaming rather than deleting gives you a safer rollback option.

Method 5: Rename the .TLG File

If the problem appears related to the transaction log, renaming the .TLG file can allow QuickBooks to generate a new transaction log.

Important precaution

Only perform this after closing QuickBooks on every computer using the company file.

Steps:

1. Open the company-file folder.
2. Locate the .TLG file associated with the company file.
3. Right-click it.
4. Select Rename.
5. Add .OLD to the filename.
6. Reopen QuickBooks.
7. Allow QuickBooks to create a new transaction log.
8. Test the company file.

Do not claim that renaming a .TLG file guarantees that no data can be lost. A transaction log may contain information associated with activity that had not yet been committed to the company file.

For this reason, preserve the original file rather than deleting it.

Method 6: Use QuickBooks Tool Hub and File Doctor

QuickBooks Tool Hub can be useful when the problem involves company-file or network configuration.

A typical workflow is:

1. Close QuickBooks.
2. Open QuickBooks Tool Hub if it is already installed.
3. Select the Company File Issues section.
4. Choose the available File Doctor option.
5. Select the affected company file.
6. Follow the diagnostic prompts.
7. Allow the scan to finish.
8. Reopen QuickBooks.
9. Test both local and multi-user access.

File Doctor is a diagnostic and repair utility, not a guarantee that every company-file problem will be fixed.

If it reports that a problem cannot be repaired, avoid repeatedly running the same repair without identifying the underlying cause.

Method 7: Test the Company File Locally

This is one of the most useful diagnostic tests for a multi-user problem.

If the company file is stored on a server:

1. Close QuickBooks.
2. Make a safe working copy or use an appropriate backup.
3. Test the company file from a local location when practical.
4. Open it in QuickBooks.
5. Compare the result with opening the same company file through the network.

What the result tells you

If the file opens locally but not over the network:

Investigate:

• Hosting
• Database Server Manager
• Firewall configuration
• Folder permissions
• Network connectivity
• .ND configuration
• Server availability

If the file does not open locally either:

The problem may involve:

• Company-file integrity
• .TLG or .ND configuration
• QuickBooks installation
• File permissions
• File location
• A broader company-file problem

This simple test can prevent you from spending hours troubleshooting the wrong layer.

Method 8: Check QuickBooks Version and Release

On the server and affected workstations:

1. Open QuickBooks.
2. Press F2 to view product information.
3. Record the product year, version, and release information.
4. Compare the installations.
5. Apply available updates where appropriate.
6. Restart the affected computers.
7. Test multi-user access again.

Do not assume that every 6000-series error is caused by a version mismatch. Use version checking as part of the diagnosis.

Method 9: Check Windows Folder Permissions

If the company file was recently moved, restored, or migrated, verify that the relevant Windows users and QuickBooks database services can access the folder.

Check:

• Folder sharing
• Security permissions
• Read/write access
• Server account permissions
• Company-file folder ownership
• Network-share accessibility

Avoid making broad permission changes to the entire computer. Adjust access only where necessary.

Method 10: Review Firewall and Security Configuration

Security software can interfere with communication between QuickBooks workstations and the server.

Instead of permanently disabling security protection, check whether the required QuickBooks applications and communication paths are permitted by your organization's firewall configuration.

Pay particular attention to:

• QuickBooks executable files
• Database Server Manager components
• The Windows Firewall profile
• The network used by the server and workstations
• Any third-party endpoint-security rules

If you test with security software temporarily paused, restore protection immediately afterward and create an appropriate exception only when necessary.

Method 11: Verify and Rebuild Company Data

If the company file can be opened but behaves abnormally, QuickBooks' built-in data utilities may help determine whether there is data integrity damage.

Use:

File → Utilities → Verify Data

If Verify Data identifies a problem, follow the available Rebuild Data workflow after creating an appropriate backup.

Do not use Rebuild Data simply because Error 6190 appeared. First establish whether there is evidence of company-file data damage.

Method 12: Check the Company File Location

The location of the .QBW file matters.

For a traditional multi-user setup, keep the company file in a properly configured folder on the intended server.

Avoid casually storing active company files in:

• Random desktop folders
• Downloads
• Removable drives
• Unreliable network locations
• Folders with restricted permissions
• Unsuitable synchronization folders

If the file was recently moved, confirm that every workstation is opening the correct company file.

Method 13: Restore a Known-Good Backup When Necessary

If the company file remains inaccessible and you have a reliable recent backup, restoring a backup can become a recovery option.

Before doing so:

• Identify the correct backup.
• Confirm its date.
• Preserve the current company file.
• Avoid overwriting the original unnecessarily.
• Record which transactions may have occurred after the backup date.

A backup restoration is a recovery decision, not simply another routine Error 6190 fix.

QuickBooks Error 6190, 816: What Does It Mean?

The 6190, 816 combination is often encountered in discussions of QuickBooks company-file access problems.

Rather than treating the -816 portion as proof of one specific internal cause, use the displayed error message and environment to determine whether the problem involves:

• Another user accessing the company file
• Single-user versus multi-user mode
• Hosting configuration
• Company-file access
• Network communication
• Supporting .ND or .TLG files

If users see a message indicating that the company file is already in use or unavailable, first make sure every QuickBooks session has been properly closed.

How to Troubleshoot QuickBooks Error 6190, 816

For a 6190, 816 situation, use this order:

Step 1: Close every QuickBooks session

Make sure nobody is actively using the company file.

Step 2: Check the server

Confirm that the computer storing the company file is powered on and accessible.

Step 3: Review hosting

Confirm that the intended server is hosting the company file and workstations are accessing it correctly.

Step 4: Restart the database service

Restart the appropriate QuickBooks database service if it is not functioning correctly.

Step 5: Check .ND configuration

Rename the .ND file only after closing QuickBooks everywhere.

Step 6: Investigate .TLG consistency

If the troubleshooting evidence points toward a transaction-log issue, preserve the original .TLG and rename it rather than deleting it.

Step 7: Test locally

Determine whether the company file opens locally on the server.

Step 8: Check network and permissions

If local access works but network access fails, concentrate on the network layer.

Error 6190 vs. Other QuickBooks 6000-Series Errors

QuickBooks has numerous 6000-series company-file errors. They should not all be treated as identical.

• QuickBooks Error 6000:- Generally associated with problems opening or accessing a company file.
• QuickBooks Error 6130:- Can occur when QuickBooks has difficulty accessing a company file, particularly in networked environments. Hosting, permissions, and file-access conditions should be investigated.
• QuickBooks Error 6143:- Can indicate difficulty opening or accessing a company file and may require investigation of the file location and network environment.
• QuickBooks Error 6147:- Can be associated with problems opening a company file or restoring a backup, depending on the circumstances.
• QuickBooks Error 6150:- Can appear when QuickBooks encounters difficulty opening or creating a company file.
• QuickBooks Error 6000-82:- Often points toward company-file or network access problems in a multi-user environment.
• QuickBooks Error 6000-83:- Can involve company-file access, network configuration, permissions, or hosting.
• QuickBooks Error 6123:- Can occur during company-file access, backup restoration, or related file operations.

The key lesson is simple:

Do not apply one generic fix to every 6000-series error.

The exact error code, message, file location, and whether the problem occurs locally or across the network should determine the troubleshooting path.

Quick Diagnostic: Local File or Network Problem?

This decision process can significantly narrow the problem.

Scenario A: Server can open the file, workstations cannot

Focus on:

• Hosting
• Database Server Manager
• Network connectivity
• Firewall
• Permissions
• .ND file
• Server configuration

Scenario B: Nobody can open the file

Focus on:

• Company-file integrity
• .TLG and .ND configuration
• File location
• Permissions
• QuickBooks installation
• Backup recovery options

Scenario C: Only one workstation cannot connect

Focus on:

• That workstation's QuickBooks installation
• Network connectivity
• Firewall
• User permissions
• Version/release
• Local configuration

Scenario D: File opens locally but fails from the shared location

The network or hosting environment becomes the primary area of investigation.

Common Mistakes When Fixing Error 6190

Several troubleshooting habits can make the situation worse.

Deleting .ND or .TLG Files

Renaming is generally safer than deleting because it preserves the original file for reference or rollback.

Changing Multiple Settings at Once

If you change hosting, firewall, permissions, file names, and installation settings simultaneously, you may not know which change solved or caused the problem.

Change one logical area at a time.

Disabling Security Software Permanently

Do not leave antivirus or firewall protection disabled simply to make QuickBooks work.

Investigate the required exception or communication rule instead.

Running Rebuild Data Without Evidence of Data Damage

Rebuild Data is a data-integrity operation. It should not be treated as a universal solution for every company-file access error.

Restoring an Old Backup Too Quickly

An old backup can remove access to more recent accounting activity if you replace the current file without understanding the consequences.

Assuming Error 6190 Means Data Loss

The error indicates an access problem. It does not, by itself, prove that the company file is permanently damaged or that accounting data has disappeared.

How to Prevent QuickBooks Error 6190

A well-maintained QuickBooks environment can reduce recurring company-file problems.

Use proper shutdown procedures

Close QuickBooks normally rather than forcing the application or computer to shut down.

Maintain reliable backups

Use a consistent backup strategy and periodically verify that backups are usable.

Keep installations maintained

Keep the server and workstations appropriately updated for the QuickBooks environment you operate.

Maintain one intended host

For traditional multi-user installations, clearly identify the computer responsible for hosting the company file.

Monitor the server

Unexpected server restarts, storage problems, and network interruptions can affect QuickBooks availability.

Protect the company-file folder

Use appropriate Windows sharing and security permissions.

Avoid unnecessary file movement

Moving an active company file without updating the related configuration can create additional access problems.

Document your environment

Record:

• QuickBooks version
• Server name
• Company-file location
• User access
• Hosting configuration
• Backup location
• Database service configuration

Good documentation makes troubleshooting considerably easier when an error occurs.

Frequently Asked Questions About QuickBooks Error 6190

What is QuickBooks Error 6190?

QuickBooks Error 6190 is a company-file access error that can prevent QuickBooks Desktop from opening a company file. It is frequently encountered in multi-user environments and can involve hosting, network, file-access, .ND, .TLG, or company-file conditions.

Does Error 6190 mean my QuickBooks data is lost?

No. The appearance of Error 6190 does not automatically mean that your accounting data has been lost. Diagnose the company file and environment before considering recovery procedures.

Is Error 6190 caused by the .TLG file?

A mismatch or problem involving the transaction log can be associated with Error 6190, but it should not be assumed to be the only possible cause. Hosting, network, permissions, and company-file access should also be checked.

Can renaming the .TLG file fix Error 6190?

Renaming the .TLG file can help when the transaction log is part of the problem. Close QuickBooks everywhere first, preserve the original file, and allow QuickBooks to generate a new transaction log.

Should I delete the .TLG file?

Avoid deleting it as a first step. Renaming it with an .OLD extension preserves the original file and is a more cautious troubleshooting approach.

Can QuickBooks Tool Hub fix Error 6190?

Tool Hub and its File Doctor utility can help diagnose certain company-file and network problems. However, not every Error 6190 situation has the same cause, so additional investigation may still be necessary.

Why does QuickBooks Error 6190 happen in multi-user mode?

Multi-user environments add network communication, hosting, database services, shared-folder permissions, and workstation configuration to the troubleshooting equation. A failure in any of these areas can prevent access to the company file.

What is QuickBooks Error 6190, 816?

6190, 816 is another form of the company-file access problem associated with messages indicating that a company file may be in use or unavailable. The displayed message and actual environment should be used to determine the appropriate fix rather than assuming a single cause.

What should I do if the company file opens on the server but not on workstations?

Focus on the network environment. Check hosting, Database Server Manager, firewall configuration, folder permissions, .ND configuration, and connectivity between the workstation and server.

What if nobody can open the company file?

Start by confirming the company-file location, checking whether the file can be opened locally, reviewing supporting files, and checking for signs of data integrity problems. If a reliable backup exists, keep recovery options available before making major changes.

Can Error 6190 damage my company file?

The error itself does not establish that permanent damage has occurred. However, if the underlying cause is a damaged file or an interrupted write operation, additional investigation may be necessary.

When should I seek professional help?

Consider professional assistance when:

• Multiple users are locked out
• The company file will not open anywhere
• A backup restoration is being considered
• Data-integrity problems are reported
• The error repeatedly returns
• The server has multiple QuickBooks installations
• The network environment is complex
• Payroll or critical accounting operations are blocked

Expert Troubleshooting Workflow for Error 6190

For a structured diagnosis, use this sequence:

1. Confirm the exact error message

Do not troubleshoot from the code alone.

2. Close all QuickBooks sessions

Eliminate an active-user conflict.

3. Identify the file location

Determine whether the problem is local or network-based.

4. Test local access

This separates many network problems from company-file problems.

5. Verify hosting

Make sure the intended server is hosting the file correctly.

6. Check Database Server Manager

Confirm the relevant database service is functioning.

7. Check .ND configuration

Rebuild the network configuration file when appropriate.

8. Investigate .TLG consistency

Rename the transaction log only when the troubleshooting evidence supports it.

9. Check firewall and permissions

Verify that communication and folder access are configured correctly.

10. Run diagnostic tools

Use available QuickBooks diagnostic utilities when appropriate.

11. Verify company data

Use Verify Data and Rebuild Data when there is evidence of data integrity problems.

12. Consider recovery

If the file remains inaccessible, evaluate a known-good backup or professional data-recovery workflow before making irreversible changes.

QuickBooks Error 6190 Prevention Checklist

Before an error becomes an accounting emergency, make sure your environment has:

• A reliable company-file backup process
• A clearly identified QuickBooks host
• Correct multi-user configuration
• Working Database Server Manager
• Appropriate Windows folder permissions
• Stable network connectivity
• Proper firewall configuration
• Consistent QuickBooks maintenance
• Documented company-file location
• A tested recovery plan
• Proper shutdown procedures
• Regular monitoring of the server

Related QuickBooks Error Keywords and Topics

Error 6190 belongs to a much larger QuickBooks troubleshooting ecosystem. Users searching for related company-file problems may also encounter:

QuickBooks Error 6190, QuickBooks Error 6190 816, QuickBooks 6190 fix, QuickBooks 6000 series errors, QuickBooks Error 6000, QuickBooks Error 6130, QuickBooks Error 6143, QuickBooks Error 6147, QuickBooks Error 6150, QuickBooks Error 6123, QuickBooks Error 6000-82, QuickBooks Error 6000-83, QuickBooks company file won't open, QuickBooks company file access error, QuickBooks multi-user mode not working, QuickBooks hosting error, QuickBooks network error, QuickBooks Database Server Manager, QuickBooks File Doctor, QuickBooks Tool Hub, QuickBooks TLG file, QuickBooks ND file, QuickBooks company file corruption, QuickBooks company file recovery, QuickBooks server error, QuickBooks firewall issue, QuickBooks permissions error, QuickBooks multi-user access, QuickBooks Desktop troubleshooting, QuickBooks company file network problem.

These related terms are useful because people experiencing Error 6190 may describe the problem differently even when the underlying issue is connected to company-file access.

Final Takeaway

QuickBooks Error 6190 is primarily an access problem that requires diagnosis—not a reason to immediately assume that your accounting data is gone.

The most effective troubleshooting strategy is to identify where the failure occurs and then work from the least invasive solution toward more advanced repair.

Start by confirming that nobody else is using the file. Check hosting and the QuickBooks Database Server Manager. Determine whether the company file opens locally. If network access is the problem, investigate connectivity, permissions, firewall configuration, and .ND settings. If the evidence points toward a transaction-log problem, preserve the existing .TLG and rename it rather than deleting it. Use diagnostic and data-repair utilities only when they fit the symptoms.

For QuickBooks Error 6190, 6190, 816, and related 6000-series company-file errors, a structured diagnosis is more reliable than repeatedly applying random fixes.

If Error 6190 is preventing your accounting team from accessing an important company file, the Data Service Team can help diagnose the QuickBooks Desktop environment, company-file access, multi-user configuration, network issues, and related accounting software problems.

Need help with QuickBooks Error 6190? Call Data Service Team at +1-(888)-718-7888.

Terpopuler di

Uang Jangan Cuma Disimpan, Yuk Kenalan dengan Dunia Pasar Modal!

Bukan Sekadar Taktik: Mengasah Daya Pikir dan Strategi Siswa Tunanetra Melalui Permainan Catur

Memahami Murid Pendiam tetapi Rajin Mengerjakan Tugas

Public Speaking Sebagai Keterampilan Penting dalam Meningkatkan Kualitas SDM

Meneropong MBG dan Belajar Dari Kelembutan Hati Umar bin Khattab

Membangun Human Capital yang Adaptif di Era Disrupsi Digital