Forum Discussion
Solved
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 Mana...
- 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
Performed a local and online repair of office. Issue still persists. Hopefully a fix will be released soon.
Thank you for including the video! That might be very helpful in figuring out the problem. There is one other recent report of a similar problem, but nothing widespread yet. I hope someone from MS sees the report soon this morning.
- Thanks for passing that info along. I did actually try turning the compact on close on/off. No effect. I'm good for now. I've been using Access for 20 years and am used to dealing with all these types of issues. In this case, since uninstalling Grammarly I've had no issues.
- FWIW: the feedback I'm getting from the MVP group would suggest that this is more likely to be a problem in the time (and time delays) involved in starting and shutting down accdbs, especially if the accdb has "Compact on Close" set to on. It's not a breach, in that sense, if by breach the implication is that somehow the third-party software is actually intruding into the running code.
- I donnt reallly neeed grammmarllie aniway. Im justt glad i have a viabul worc around!!! Kind of scary that MSAccess is so fragile that it can be breached by a 3rd party app like Grammarly.
- By the way, not to be unsympathetic, but Grammarly is not a Microsoft product, so fixing the problem is probably in the court of Grammarly more so than on Microsoft.
- Microsoft has not been able to replicate the problem, unfortunately, with or without Grammarly running. If the problem returns, please follow up so we can provide additional input.
- I think I found the culprit. I turned off Grammarly from the system tray and now MsAccess no longer get stuck as a background process. When I turn Grammarly back on the problem immediately returns. What's interesting is that Grammarly does not activate when I use MsAccess. (Apparently its still listening). I tried turning off Grammarly for all my Office Apps but no effect on MsAccess. This seems like a serious security issue. I hope MS locks this down fast.
- Yes i have the latest update. Im now on Version 2201 (Build 14827.20192) and issue is still happening.
- First, you're replying to me, not to the poster with the problem. Also as I stated, he reports the versions he installed in his post and linked video.
There is now a second report on a different forum of the same set of circumstances. A recent update (today) didn't fix the problem after all. We're still waiting confirmation of the exact version in that report, though.
I'm keeping my fingers crossed that it's a coincidence, but recent history advises us to be wary nonetheless. - What version are you running? Everything solved on our end and Access is functioning normally again.
- What is the version? Everything solved on our end and Access is functioning normally again.
- The OP reported that he DID install both the update which was supposed to provide the fix and one subsequent update. That's why this is a bit unsettling, in fact.
- ummm, the issue was resolved last week with an O365 update. Did you apply the most current update? What version do you have?
