Problems With Office Version 2201 (1 Viewer)

[TonyPWalker]

Hello All,
Our works PC's were automatically upgraded to Office version 2201, which has caused havoc with our in-house database.
Even with only a couple of forms open, we were getting "Cannot open any more databases."
The cure was to revert back to version 2112.
Has anybody else experienced the same problem?

 

[Ranman256]

you must roll the update back. its a bug in MS.
it screwed up all our databases. (well not db, its Access where the problem is)
Rolling back the update fixed it.

 

[TonyPWalker]

you must roll the update back. its a bug in MS.
it screwed up all our databases. (well not db, its Access where the problem is)
Rolling back the update fixed it.

That's exactly what I did, but I couldn't find anything about this bug beforehand. :-(

 

[theDBguy]

Hi Tony. Was this you?

https://answers.microsoft.com/en-us/msoffice/forum/all/is-cannot-open-any-more-databases-what-we-can-now/ef6313e2-ee71-4286-8b4d-8ab9dd7e337d

 

[wildidee]

Same problem (MS Access front-end connecting to SQL server). Unable to exit MS Access after closing application + "Cannot open any more databases" error with performance loss, unable to save changes, ...)

 

[theDBguy]

Same problem (MS Access front-end connecting to SQL server). Unable to exit MS Access after closing application + "Cannot open any more databases" error with performance loss, unable to save changes, ...)

Hi. Let's hope MS acknowledges it soon and comes up with a fix right away.

 

[wildidee]

Hi. Let's hope MS acknowledges it soon and comes up with a fix right away.

It might be related to reconnecting the front-end to back-end tables in an automated way.

Microsoft mentions

"We fixed an issue that could cause an application to stop responding when connecting to an Access or Jet database using multiple threads in rapid succession."

That is exactly what I am doing in that application (automatic reconnect to a back-end file to dump data)

 

[wildidee]

It might be related to reconnecting the front-end to back-end tables in an automated way.

Microsoft mentions

"We fixed an issue that could cause an application to stop responding when connecting to an Access or Jet database using multiple threads in rapid succession."

That is exactly what I am doing in that application (automatic reconnect to a back-end file to dump data)

answers.microsoft.com/en-us/officeinsider/forum/all/office-for-windows-beta-release-notes-version-2201/5d72172e-4277-4c04-a534-9fb658575f4d

 

[Gasman]

No need to copy and paste.
answers.microsoft.com/en-us/officeinsider/forum/all/office-for-windows-beta-release-notes-version-2201/5d72172e-4277-4c04-a534-9fb658575f4d

 

[wildidee]

Adding the folder where the Access application resides (front-end + back-end) to the Office trusted zones is confirmed to be a successful workaround.

 

[wildidee]

techcommunity.microsoft.com/t5/access/access-doesn-t-close-properly-a-remaining-background-process-can/m-p/3103807/thread-id/4640

 

[jdraw]

More info at https://www.devhut.net/another-access-bug-cannot-open-any-more-databases/

 

[GK in the UK]

This fixed it for me. Perpetual Access 2016. I was on build 14827.20158 but this link reverted to 14701.20206. Lock file no longer remains on closing Access.

Link: Lock File Problems with Access 16.0.13801.21086 - Microsoft Community

The reply 4th February listing 5 steps to download 16.0.14701.20226

Incidentally, as well as the lock file problems, forms opened in my application as instances were failing to close even though they were removed from the collection. Reverting fixed this issue.

 

[Minty]

There appears to have been a further update to finally fix this;

https://docs.microsoft.com/en-gb/officeupdates/current-channel
2201:Feb 08 Build 14827.20192