Forum Discussion
Access doesn't close properly. A remaining background process can only be terminated in task manager
Since yesterday I noticed that in all my Access databases there is a problem when I close them.
When I close a database, it leaves a background process that can only be terminated in Task Manager. Without this, it is not possible to (re)open databases!
I have already checked some possible causes. It also concerns databases that I have not changed at all in recent months and that worked fine until this week. Therefore, I have to assume that it is a bug in an automatic update!
It seems that it has to do with a malfunction in the deallocation of allocated memory in VBA source code.
Did anyone experience the same problem? Are there already fixes or solutions available?
- Yes, here also the update available (Europe). Tested en fix the problem. Trusted Location not necessary any more. But I highly recommend it. Otherwise you will have problem starting from April. MS is blocking marcos. Check https://techcommunity.microsoft.com/t5/microsoft-365-blog/helping-users-stay-safe-blocking-internet-macros-by-default-in/ba-p/3071805
189 Replies
- Same issue. QuitAccess macro close the access file, but the access program with blank screen still is open, and the linked text file is still shown as open and another job that is supposed to delete the linked text file cannot delete the file. When I rename the file with suffix, the access program is closed by the QuitAccess macro. And there are other files that I have QuitAccess macro because I run all my access files by schedule, and they all seem working. Only one file is having this issue. I am going to try trusted folder option I read earlier on this thread.
- Somehow I was not able to add a network folder as trusted location. I moved the file to C drive, and the file was closed properly. For now, this is the answer.
Hi,
You are not alone. There are reports about it in all Access forums of the world. I answered it like this several times:
According to many posts in the last days M365 Current Channel version 2201 build 16.0.14827.20158 of Jan 26 causes
- a persistent .laccdb, an Access ghost process
- error 3048 cant open any more databases- other errors like "already in use by Admin"
The only remedy so far is to revert back to an older build of M365. See also the M365 version history.
I've reported it to Microsoft, too.
Servus
Karl
************
Access News
Access DevConIf by now you don't know, the solution is simple: add the folders where the front and backend are located to Trusted Locations. AND You have to do it for every single user in your network, a step I missed doing the first time and the other two users kept having the problem.
- Keep in mind, though, that there have been reports where the Trusted Location workaround wasn't effective. See this note, for example, on the MS site:
https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da
Note: This workaround will not work if AMSI (Antimalware Scan Interface) is enabled for all documents. More information about AMSI can be found here: Office VBA + AMSI: Parting the veil on malicious macros - Microsoft Security Blog
Also, it's not always clear that people are fully implementing this, but one has to be cautious.
Hi,
The Microsoft Access team has published a first version of a support article about this update bug: https://support.microsoft.com/en-us/topic/b2dce32b-b8b0-41f1-ba40-7876e524d9da
In it a fix is announced, but so far without a date. Until then, the workaround recommended is to put the database in a trusted location.
Servus
Karl
************
Access News
Access DevConHi,
Since we've seen a lot of positive reports about it and the trusted location is now also the officially recommended workaround by MSFT: In order to keep the thread readable, I think it would be good to especially post here when the workaround does NOT help or other new findings.
Servus
Karl
************
Access News
Access DevCon
- What about downgrading runtime versions?
Ciao
DavideDowngrading Office 365 to previous version solved
- error 3048 cant open any more databases
for me!
I didn't try for Run-time version
Thanks a lot
Cristian
