How to Troubleshoot QuickBooks Error code 6190 and 816?

by Joey Williams QBS Enterprise Support

QuickBooks is the most efficient business accounting software of the rapidly growing business organizations around the globe. It also helps in various operations that are necessary for effective business working throughout such as accounting, payroll, bookkeeping, invoice generation, and other. But due to some or the other issues QuickBooks generally face a common error code that is – QuickBooks Enterprise Error 6190, -816.


In this technical post, we are going to focus particularly on QuickBooks Error 6190, -816 and its solution. If you see the message “An error occurs when QuickBooks tried to access the company file (-6190, -816),” don’t worry. There’s an issue with your multi-user network, not your accounting data.



This error code signifies that the QuickBooks user is unable to access the company file. Usually, this error code appears with a warning message that is – “QuickBooks was unable to open the file [path] on the host computer”. If you require immediate help for the Error 6190, -816 under the guidance of experts –you need to speak with the team anytime.


Reasons of QuickBooks Error Code 6190, -816

Here are some of the causes due to QB Error 6190, -816 appears: -

  • If the QuickBooks Company file is open on multi-user environment.
  • If you are trying to access the company file place in single-user mode via other system or network at the same time.
  • In case, the company files are under the Read-only mode.
  • This error can also arise in a situation where the company files are updated but not the transaction files.


Solutions to fix QuickBooks Enterprise Error 6190, -816

Checkout the possible fixes to resolve the QB Error Code 6190, -816:-

Method 1: Downloading and running QuickBooks file doctor tool

  • The user should log in as admin, if not already.
  • The user will get two options displayed on the screen namely, Network Connectivity Only and Both File Damage and Network Connectivity.
  • The user is recommended to opt for the first option. The reason behind this can be that this will detect all the corrupted and damaged files.
  • After that, the user is supposed to enter the admin password, when needed.
  • In the last step, the user will be asked whether the file is on workstation or server. Then in that case, the user needs to opt for the option as the case may be and hit Proceed.


Method 2: Fix the Discrepancy

In order to get rid of the error, the user can rename the files. Renaming the file would not cause any no data loss. The steps to be followed in this process are as follows:

  • First of all, the user needs to open the company folder and then find the company file.
  • The next step is to right click the company file and then select the rename option.
  • Now, rename the transaction log file.
  • And then exit the system, followed by opening the QuickBooks and logging in the company file and you are good to go.


Method 3: Single User-Mode check 

  • Sign-out QuickBooks for all the servers. Later, restart it and copy or replicate the QB data files to some other location different than the original source. Afterward, paste it to the original location & log-in the QuickBooks application.
  • You need to change the file mode other than read-only mode.
  • In the server, install the QuickBooks Database Manager (QBDSM) that stores all the Company files. Then, after the installation process completed- restart the server...!



Get Instant help and support by experts

It is very difficult for a business to run properly without the services of QuickBooks desktop. Moreover, it may also lead to loss of crucial data and information associated with the business. In order to rectify this error with the assistance of QuickBooks desktop support professionals – dial the toll-free helpline number of our Intuit certified technician’s i.e., 1-800-615-2347.

Sponsor Ads

About Joey Williams Advanced   QBS Enterprise Support

20 connections, 0 recommendations, 106 honor points.
Joined APSense since, April 20th, 2022, From San Francisco, United States.

Created on Feb 20th 2024 00:06. Viewed 57 times.


No comment, be the first to comment.
Please sign in before you comment.