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: Create a form named Form1. On Form1, create a command button named Command1. 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.

Quick note. We have found 2 clients today that had Macro setting in Trust Center set to disabled. We adjusted to Enabled all macros and also added Trusted location to program location. So far that has helped. Will report back if anything changes with the users adjusted.

Can confirm, having this problem on our Windows 2022 terminal server, Access v2048... thanks for rolling known issues out to production MS!

Our in-house program running on Access experienced the same issue with the 'process remains open after exiting' error after running a single query and trying to run the same query again. This prevented us from performing any function twice, displaying the message 'someone else is using the program or process,' which wasn't accurate. The issue was caused by the locked file Access creates. We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408.

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

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

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

Anonymous

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:

Create a form named Form1.
On Form1, create a command button named Command1.
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.

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

Anonymous

2024-09-04T15:21:07+00:00

Quick note. We have found 2 clients today that had Macro setting in Trust Center set to disabled. We adjusted to Enabled all macros and also added Trusted location to program location. So far that has helped.

Will report back if anything changes with the users adjusted.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-04T18:46:33+00:00

Can confirm, having this problem on our Windows 2022 terminal server, Access v2048...

thanks for rolling known issues out to production MS!
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-05T03:54:08+00:00

Our in-house program running on Access experienced the same issue with the 'process remains open after exiting' error after running a single query and trying to run the same query again. This prevented us from performing any function twice, displaying the message 'someone else is using the program or process,' which wasn't accurate. The issue was caused by the locked file Access creates. We found a workaround by reverting to build 2406, which worked perfectly. However, despite disabling updates both within Access settings and the system settings, it automatically updated back to build 2408.
Was this answer helpful?

0 comments No comments
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 No comments
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 No comments