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

Anonymous
2024-08-20T05:08:41+00:00

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.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

97 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-09-05T09:49:14+00:00

    Hi,

    thanks for rolling known issues out to production MS!

    The default setting Current Channel is susceptible to update bugs, as we have already seen in many cases. If possible, you should switch to a slower channel for productive purposes.

    The monthly and semi-annual channels are less frequently affected. When they are, they are usually caused by security updates that are so important to Microsoft that they are quickly delivered to the slower channels too.

    This AFo article describes how to set and change channels: Demystifying Microsoft 365 Update Channels

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-09-05T09:37:00+00:00

    Hi,

    the new office build 2410 (2410 18028.20004) was installed from 'Preview channel' this morning on my machine.

    That build did not correct the issues:

    ...

    Your version and build number are not from Current Channel Preview (the mild beta) but from Beta Channel (the wild beta).

    Unlike the Preview channel, the Beta channel has not yet received the fix. This is expected to happen next week, as with the Current Channel.

    You can find more information and the current status in our documenting AFo article. We haven't mentioned the beta channel there so that the text doesn't get too long and confusing. If we see more beta channel questions/reports like yours, we might change that.

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-05T07:49:57+00:00

    Hi all,

    the new office build 2410 (2410 18028.20004) was installed from 'Preview channel' this morning on my machine.

    That build did not correct the issues:

    • error 3037 cannot open more databases and table
    • When closing the background task does not terminate and locks access. The only way out is to kill the background process with task manager

    I also tried to go back to 2406 and after a few hours, the version was updated back to 2410.

    I wonder if Microsoft applied the right corrections

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-08-31T22:31:29+00:00

    MS Access 2019 Version 2408 (Build 17928.20114 Click-to-Run) not functioning properly, previous version of 2407 functioned correctly. Behavior started on 8/27/2024. I had another machine with MS Access Version 2019 and 2021 Version 2404 (Build 17531.20152 Click-to-Run) which do not experience the issues.

    It does the following:

    1. Opening the application with the shift key so no code executes on startup and exiting MS Access does not produce an error. Accessing only an internal Access table within the application and exiting MS Access does not produce an error.
    2. Opening a linked table in MS Access results in an error.
    3. Opening the application in the normal method which accesses a linked table to trigger the login screen to the external database always results in an error. There are two versions of the application. The older uses SQL Server Native Client 11.0 to SQL Server 2019. The newer version uses ODBC Driver 18 for SQL Server to Azure SQL Server.
    4. The error observed is on application close the application task terminates in Task Manager and a background task starts for MS Access. The background task never terminates. Unless the background task is manually terminated, MS Access will not restart the application and no error message is thrown.
    5. If the application is set to compact on close, once the application terminates, the background task attempting to compress the database throws an error that a user has already locked the application.
    6. Additional observations, after opening and "saving as" several queries, MS Access will no longer save the queries and throws no error.

    Running on Windows 10 Pro Version 1H1 OS build 19043.2364

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-08-31T22:00:37+00:00

    Hi,

    We have published a documenting article on AFo with information about the planned fix by Microsoft.

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments