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.

Thank you so much Karl! I did have to manually use the Update Now feature and I'm ecstatic to say the issue has been resolved for me!

I'm on Current Channel Preview, and today's update has removed the two issues I had, not closing and running out of databases. I currently have the following versions: C:\Program Files (x86)\Microsoft Office\root\Office16\MSACC.OLB Version: 16.0.17830.20056 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL Version: 16.0.18025.20024 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL Version: 16.0.18025.20024 Well done to all for reporting and keeping this issue on top of the agenda.

Hi Kal, I have just re-rolled forward to 2408 to create you a test scenario. Microsoft® Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 32-bit If you run the ReproduceError() function on an affected system then it will output as follows : "Open Databases : 1" "Open Databases : 2" "Open Databases : 3" etc. When it reaches 504 it is game over. On an un-affected system Microsoft® Access® for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 32-bit it will output "Open Databases : 1" "Open Databases : 1" "Open Databases : 1" 5000 times, as it should. Function OpenDatabaseCount() Dim td As TableDef For Each td In CurrentDb.TableDefs 'Do nothing Next OpenDatabaseCount = DAO.Workspaces(0).Databases.Count End Function Function ReproduceError() Dim i For i = 1 To 5000 Debug.Print "Open Databases : " & OpenDatabaseCount Next End Function

Kari, thanks for your reply. If the process remains, there is no response even if you double-click the same MDB or ACCDB again. If I force-terminate the Microsoft Access process in Task Manager and try to open the same file again, it asks if I want to open it in safe mode. The problem does not occur with 32-bit Access; it only occurs with 64-bit Access. I have confirmed that this issue occurs in the following environments: ・Win11 21H2 22000.2538（64bit）・Win11 24H2 26100.1457（64bit）

Hi, So you see the usual consequences of a hanging process. I just wanted to make sure. As you tested it with very "distant" Win11 builds, it shouldn't be that what plays a role here. Maybe sth else that's in your environment but not in mine. Several others were able to replicate the problem which was also reported at SO . It's already reported to Microsoft. I'll let you know when there's news. So far, it only happens in the beta versions/channels, not in the Current Channel version 2407. That would be the masses and the point where we would write a documenting article on AFo . 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-10T15:08:41+00:00

Thank you so much Karl! I did have to manually use the Update Now feature and I'm ecstatic to say the issue has been resolved for me!
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T14:03:05+00:00
I'm on Current Channel Preview, and today's update has removed the two issues I had, not closing and running out of databases. I currently have the following versions:
- C:\Program Files (x86)\Microsoft Office\root\Office16\MSACC.OLB Version: 16.0.17830.20056
- C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\ACEDAO.DLL Version: 16.0.18025.20024
- C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE16\MSO.DLL Version: 16.0.18025.20024
Well done to all for reporting and keeping this issue on top of the agenda.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T08:38:18+00:00
Hi Kal,

I have just re-rolled forward to 2408 to create you a test scenario. Microsoft® Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 32-bit

If you run the ReproduceError() function on an affected system then it will output as follows : "Open Databases : 1" "Open Databases : 2" "Open Databases : 3" etc. When it reaches 504 it is game over.

On an un-affected system

Microsoft® Access® for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 32-bit

it will output "Open Databases : 1" "Open Databases : 1" "Open Databases : 1" 5000 times, as it should.

Function OpenDatabaseCount() Dim td As TableDef
For Each td In CurrentDb.TableDefs
```
    'Do nothing
Next
OpenDatabaseCount = DAO.Workspaces(0).Databases.Count
```
End Function

Function ReproduceError() Dim i For i = 1 To 5000
```
Debug.Print "Open Databases : " & OpenDatabaseCount
```
Next End Function
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-08-20T13:19:22+00:00

Kari, thanks for your reply.

If the process remains, there is no response even if you double-click the same MDB or ACCDB again.

If I force-terminate the Microsoft Access process in Task Manager and try to open the same file again, it asks if I want to open it in safe mode.

The problem does not occur with 32-bit Access; it only occurs with 64-bit Access.

I have confirmed that this issue occurs in the following environments:
・Win11 21H2 22000.2538（64bit）
・Win11 24H2 26100.1457（64bit）
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-08-20T13:41:34+00:00

Hi,

So you see the usual consequences of a hanging process. I just wanted to make sure.

As you tested it with very "distant" Win11 builds, it shouldn't be that what plays a role here. Maybe sth else that's in your environment but not in mine. Several others were able to replicate the problem which was also reported at SO.

It's already reported to Microsoft. I'll let you know when there's news.

So far, it only happens in the beta versions/channels, not in the Current Channel version 2407. That would be the masses and the point where we would write a documenting article on AFo.

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