After updating Access in Office 365 to version 2408, the MSACCESS.EXE process remains after exiting Access.

Question

After applying the quality update for the latest channel (preview version) of Microsoft Access (64-bit), version 2408 (build 17928.20066) dated 8/14, the MSACCESS.EXE process won't end even after closing Microsoft Access application.

The reproduction steps are as follows:

1. Create a form named Form1.
2. On Form1, create a command button named Command1.
3. In the Click event of Command1, write "Application.Quit".

Run the application, click Command1 on Form1 to close the application. Afterward, when you check the Task Manager, MSACCESS.EXE process won't end.

This issue does not occur in the 32-bit version. I believe this is a bug. Can you advise where I should report this?

Rolling back to version 2407 resolved this issue.

Answer 1

It's very annoying when this happens. Something similar happened a couple of years ago, a bad Access update caused all my clients to break at once. The solution then was to roll back. In the aftermath, I moved most of my clients onto the Semi-Annual update channel so the updates are not as frequent - this decision has really helped to limit the damage this time around, as most clients have not got the bad update published on the Current Channel.

I still have had to do a few issues though and need this fixing asap.

For anyone that doesn't know how to roll back, here is the easiest method I have found :

File->Account

Disable the updates :

      Dropdown the **Update Options**  and select Disable Updates.

Then, determine your Update Channel by pressing the About Access button, or read next to it.

It should be one of Current, Monthly Enterprise, Semi-Annual.

Locate the Click to Run folder, Open a Command Prompt (as Admin) and enter the command :

cd "C:\Program Files\Common Files\Microsoft Shared\Clicktorun"

Use the following to update to the July 9th 2024 version :

If you are in the Current Chanel then use the command :

OfficeC2RClient.exe /update user updatetoversion=16.0.17726.20160

If you are in the Monthly Enterprise Channel then use the command :

OfficeC2RClient.exe /update user updatetoversion=16.0.17628.20188

If you are in the  Semi-Annual Enterprise Channel (or Preview) then use the command:

OfficeC2RClient.exe /update user updatetoversion=16.0.17328.20452

The command should launch the installer and update your Office back to July 9th.

Once Microsoft have fixed the problem (typically in a couple of weeks), you can re-enable updates.

https://www.accessforever.org/post/roll-back-to-previous-versions-of-office

https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date

Answer 2

having the same issue. VBA code that has been running for years now will not run.

Answer 3

Today has not been a good day... Also getting the "Cannot open any more databases" error as well as those already mentioned here. Now seems that 2408 is started to be installed widely on the Current Channel and I have a number of clients with one or more of these issues. How did this get out of Preview? Any official confirmation from MS that they are aware?

Oh, and also showing on 32-bit clients as well as x64.

Answer 4

hi, yes, I returned from holiday today to find most of my databases would crash very soon after opening them. I suspect it is related.

I would receive a "too many databases open" message.

?DAO .Workspaces(0).Databases.Count

would return several hundred databases open, instead of just 1.

This also prevented the database from closing as mentioned in original comment.

I believe the issue maybe caused by garbage collection of Currentdb, not closing connections when destroyed. Possibly introduced after recent fix to Linked Tables ?

The issue must have been introduced very recently anyway, my version was 2408, build 17928.20114

I rolled back to the July 9th build (Current channel : 16.0.17726.20160) and that fixed it for me.

Answer 5

Hi,

I have just updated the status section in our documenting article.

The bad news is that the fix in the Current Channel is to be expected only next week.

The good news is that it has been available in the Current Channel Preview (CCP) since yesterday. That is the (beta) channel for which it was first mentioned in the initial posting of this thread and elsewhere.

See the AFo article for details. As written there, fix reports from CCP are welcome.

Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg