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?