Forum Discussion
Microsoft Access Database App Error 3046
We experience the exact same issue at one of our clients. They are using Access 2016 64 bits and first had the query issue, the update did fix that, but it seems as if the extreme amount of locking issues appeared shortly after.
They use a frontend separated from the backend.
- Repairing the databases does not help;
- Setting the registry key (lease time) as suggested as a work-around on the database server has no effect;
- Increasing the retry attempt from 2 to 20 has no effect.
- Disable opening the database in lock mode even does not resolve anything.
If the error occurs they could go to debug mode, wait a couple of seconds and resume by pressing F5, the "lock" then probably resolved and execution continues, but only for a while until the next lock hits.
This client is unable to work with more than 1 client at the moment. Any help or update on this will be highly appreciated.
I have myself experienced it quite regularly since December 10, 2019. I am in a multi-user environment, each user having its own copy of the same ACCESS 2016 program on his desktop running WINDOWS 10 while the data is in a separated ACCESS 2016 database on a server. The problem happens when the program just loaded tries to do a very simple update to one record of a table. This ACCESS program has been working fine for years and all of a sudden, the error 3046 appeared on December 10 exactly as described by others above. I have no idea if any patch has been developped for this but would like to know if any..