MS Access-Error Executing command prevents multiple users

Topic

New Reply

We have an Access database in Office 365. The database is used by approximately 30-40 users. The database resides on a Shared server.  We have the front end separated from the backend data.
Approximately 2 weeks ago, the database started giving us this error message: “There was an error executing the command” whenever we try to open any of the forms we have to enter the data.  It will allow one or two users to access the database, but after that it won’t let anyone else use it.  They get the error message.  If we wait for a period of time, allowing someone to exit, then another person can get in.
We didn’t have this issue prior to a couple of weeks ago.

Reply | Quote

Replies

https://www.askwoody.com/newsletter/ms-defcon-2-batten-down-the-hatches-for-january/

“Speaking of Access, Microsoft has finally fixed a problem created with the December updates, where two or more people couldn’t open an Access database. The issue was already fixed in click-to-run versions. In KB2965317, released on December 29, Access 2013 finally received its update to fix this problem. You’ll have to manually install that update in order to fix your file-access issue because the patch has not yet been released to Windows Software Update Services or Windows update.”

You’l need to kick an update to the click to run to get on the latest version.   It’s now been fixed.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

This issue is still present for Office 2016 msi install, where databases are stored on a network share that uses DFS namespaces. In January, Microsoft released KB5002115 to fix KB4484211, which fixes KB5002099 that initially broke multiuser access. Still not a fix for DFS namespaces. They are supposed to release a fix for us DFS folks (or what they call “everything else”) Feb 1. We have had to block all of these updates in Configuration Manager on our ADRs. This has had real business impact and a simple UNC path for end users doesn’t work with these large databases that have internal links to backend databases all using DFS. Its also tricky to track down the culprit when the database is locked. After this last year of patching, Microsoft tells us we are out of support hours…awesome!  While they used to be good about not charging us hours for their mistakes, their support seems to be reeling from the past year of bad patches. Contiue to find Askwoody and other resources helpful each month to avoid the nasty stuff.

Reply | Quote

I don’t do much with Office but just in case there’s some Excel in the mix there I saw this recently:

https://www.bleepingcomputer.com/news/microsoft/microsoft-disables-excel-40-macros-by-default-to-block-malware/

 

Reply | Quote

It’s been a month since this thread was updated. Does anyone know if (or when) this is supposed to be fixed?

Reply | Quote

https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc

”

• All remaining network paths – This fix corrects the issue for all other network paths, such as: DFS Namespaces, Short file names, and Mapped drives.

See if that helps.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote