Forum Discussion
Access doesn't close properly. A remaining background process can only be terminated in task manager
- 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
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 DevCon
Ciao
Davide
Downgrading 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@lease forward instructions on how to revert to previous Office 365 version. Thanks.
- Tiger7663, I used this link, but it is in Italian:
https://support.microsoft.com/it-it/topic/come-ripristinare-una-versione-precedente-di-office-2bd5c457-a917-d57e-35a1-f709e3dda841
Gommacri How do I downgrade my version in more simple terms? It's killing my productivity. I presume Microsoft will deploy a fix fairly swiftly.
I find that closing it and then rebooting the machine helps until the next time the DB is closed.BTW I'm in England, and have been suffering this since about 1pm our time (7 hours ago) - having changed nothing, installed nothing, and have been blamed for corrupting the database ever since.
- I see a better solution than downgrade has been provided, good to know
Ciao Davide,
I've never done it myself. So, if somebody has been successful with the Runtime, please report/confirm it here for others.
Personally I would assume the same procedure as desribed in the linked articles also for the Runtime, i.e. with
TargetVersion="16.0.14729.20260"
I would expect to revert the installation back to the previous build of the Current Channel.
Servus
Karl
************
Access News
Access DevCon- I tried the procedure with the target version "16.0.14729.20194".
It worked fine on every full version, but nothing changed on runtime versions, they still remain 16.0.14827.20158...
I'm searching for any solution
Ciao- Well, it worked.
The procedure is the same, just you cannot force the update after setting the version.
at the last step you have to wait that the runtime update by itself.
Ciao
