company file size is 68MB

Your file size is fine. Create the backup of your file and restore it with a new name. Ask your team to use the restored file. If the same error persists, your file is damaged. Chat Support and ask them to check your file. Another option, purchase a 3rd party service to repair your file.

@Fiat Lux - ASIA  thank you so much for the realistic and practical steps to hopefully determine the source of the errors. I will try this overnight tonight or tomorrow give it a day or so and advise back. One thing weird from yesterday that I cannot explain... Tuesday is our busiest day in this company database, I had five people in and out all day making changes and not one problem. Typically I have to re-scan the folders several times a day to keep everybody able to access but yesterday zero problems for the first time in weeks. This morning one person had an issue but the others have reported no problems. did a re-scan and that one person go in instantly. QUESTION: what does this mean and how does it happen when one of the users is listed as SearchIndexUser. See screenshot.

For the last two months, we were having terrible problems with this issue, spent about 20 man hours trying to fix it. Followed every single recommendation, test and database fix. Finally we just decided to upgrade to 2024, thinking that surely QB would have fixed the problem in the new release.

We successfully upgraded to 24.0 last Monday, and for Monday, Tuesday and Wednesday everything worked as expected.

Today however, our secondary computer was unable to open the QB company file at all. We kept getting 6190 and 816 errors.This despite the fact that the primary user had logged out of the system altogether! So it could not have been a problem where the other user was logged in under single user mode, they were not logged in at all.

Under the previous version, we could always fix the problem by having the primary user log off. Then the secondary user could log in. Even though both were in multi-user mode, the system would only work for one at a time. But at least we could get people working.

Now it will not work for the secondary user at all. 

No one was here over the holidays, and no changes were made.

So, I am wondering if the problem of the old QBDSM getting left behind in the upgrade is happening for upgrades to 2024?

If so, how do we identify and deleted the "old" QBDSM?

Thanks for sharing complete details of your concern and what you've done to fix this, @square1 comp.

I understand the significance of accessing your company file for your business and would like to provide further steps to resolve the error you're experiencing.

QuickBooks error codes 6190 and 816 can occur if multiple users use QuickBooks Desktop in multi-user mode or someone else is logged into the company file in single-user mode. 

To fix the issue, the first thing we need to do is to ensure that your QuickBooks desktop is updated then rename .ND and .TLG files. Renaming these will not cause you to lose QuickBooks data. These files are automatically re-created when you open your company file.

Here's how:

1. Open the folder that contains your QuickBooks company file.

2. Look for the same file name as your company files but with extensions .ND and .TLG.

     a. company_file.qbw.nd.

     b. company_file.qbw.tlg.

3. Right-click each file and select Rename. Add the word OLD at the end of each file name (Example: company_file.qbw.nd.OLD).

4. Reopen QuickBooks and try to sign in to your company file.

If the issue persists, download QuickBooks tool hub then run quick fix my program.

Here's how:

1. In the QuickBooks Tool Hub, select Program Problems.

2. Select Quick Fix my Program.

3. Start QuickBooks Desktop and open your data file.

If the previous step fails to resolve the issue, we can try fixing company file and network issues with QuickBooks File Doctor.

Furthermore, you can restart your computers and servers and move your company files to your local hard drive.

If the issue persists, you can refer to this article for additional troubleshooting steps (Proceed to solutions 3-7 under You open the file over a network Fix error -6000 when opening a company file.

The Community is always here to help if you need further assistance with errors -6190 and -816. 

@square1 comp 

How big is your file size?

Have you run the Verify/Rebuild Data utility?

I get this error frequently as well. It started about a year ago and persists through all the updates and releases. The only way I've found to fix it is to log out and restart the host computer. I only have two users and one background process that accesses the database.  I hope you find a solution, I have not.

Thanks.  This is my experience too.  I haven't had the nerve yet to start messing with the database and going thru the boilerplate fixes offered in this thread.  I need a day of 2 when my wife (the main user) is out of the office and I have time to recover if the troubleshooting makes things worse.  Sad that "live with it" is sometimes the easier solution.

@Natvilcius 

You can ask a 3rd party service provider to check your file.