Forum Discussion
Microsoft Access Database App Error 3046
Help!!! I have a multi user (front end / back end) access application. My users are now receiving intermittent 3046 record currently locked error messages. I have tried various regedit su...
Shane Groff
Microsoft
MicrosoftJulian-Cooper-KPP There was no build update that would impact this, but there were configuration changes (each time Access starts, it downloads configuration changes that may change behavior) that were made on Jan 3 that might impact this.
Are there any details on the actual changes as its almost impossible to test this issue without doing it in a live environment due to the irregularity of it. At present, I have moved the back end db to the rds session host where the front end app launches from as the assumption is its network related and this overcomes this but this limits all users onto a single session host so load balancing goes out the window.
- Shane Groff
Julian-Cooper-KPP There was a significant change to address some of the issues around the errors with corrupt/inconsistent databases, which was being rolled out to production, but we have turned back off, and it is possible that this change could cause the 3128/3046 errors. That change has been turned off via configuration so if users are still seeing this issue after restarting Access, then there must be some other cause. As many posters have pointed out, this may legitimately be a case where there is locking contention (multiple users trying to modify the same data at the same time), so it may just be an application error or appropriate behavior, it is hard to say without access to the application reporting the error. We do not have evidence that this is an issue being experienced broadly.
Shane Groff We work in a live environment. Since the new configuration, the errors occur less frequently. So it had to have an impact.
Our code has not changed in 6-8 weeks. So that we can rule out that it is a programming error. The hardware has also not changed.
- Hi Shane
Thanks for the update.
If it helps to identify the cause.
I was seeing the 'corrupt database' issue being caused by the windows 10 latest release. The disableleasing workaround had sorted this for the most part. However, when the build that caused the corrupt query error was rolled out, it was roughly this point where I started seeing the error locking issue.
I moved all users front ends to an rds session host and rolled back office 365 to until three fixed build was released.
It is since this point that the record locking issue has started and happens from anywhere the front end app is located.
Having now moved the back end to a vhdx and attached directly to the session host, thus avoiding network comms altogether, this seems to have resolved the issue further.
I still have another session host running the same front end and communicating over the network but doing less heavy processing and this also seems ok since 3rd January so something has improved although not sure if it would reoccur if I tried to do heavy transactions over the network again.
I have never had a 3046 error on this network with this application (or any of my many apps to be honest on other networks) so I am confident that it's nothing to do with the programming.
I have even gone as far as to double check no connections after left open any longer than necessary within the code.
Hope that helps.
