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.

My data base has had quite a few problems with the latest MS Office Version. Tables not being able to be written to due to open already when they are not. Closing the data base I get error that I'm trying to open the data base that's already open. The shift key plus open does not work. Sometimes it will not open at all. until I go in the Task Manager and close all processes still running. I cannot roll back here so I am stuck until MS fixes the bug!

No, I use the 32bit version and have most of the symptoms described above, including yours. Mine does not run out of databases immediately, though. It takes a while with lots of SQL queries going to a linked ODBC database before it starts to complain. Another issue I get often is an error when I close down Access. The error states that: You attempted to open a database that is already open by user 'Admin' on machine 'nnn'.

I'm having the same issue, plus it runs out of tables after a while of running, where it opens and closes recordsets properly. When I try to go back to the previous build, the update process is broken, so a full repair is needed to get the updates running again. Only this time it finds no new updates. I have a client whose Microsoft Office 365 just upgraded to 2048 Build 17928.20114 on August 26th. Since that time they have been getting "Error 3048 cannot open any more databases" I just checked the Task Manager and found 5 ghost processes of MSACCESS.EXE. I FYI, this is the 32bit version of M365. Am I the first encounter this in the 32bit version?

Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here: BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com) Juan Soto 14x Access MVP AccessExperts.com

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-08-30T19:09:51+00:00

My data base has had quite a few problems with the latest MS Office Version. Tables not being able to be written to due to open already when they are not. Closing the data base I get error that I'm trying to open the data base that's already open. The shift key plus open does not work. Sometimes it will not open at all. until I go in the Task Manager and close all processes still running. I cannot roll back here so I am stuck until MS fixes the bug!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-08-30T18:19:02+00:00

No, I use the 32bit version and have most of the symptoms described above, including yours.

Mine does not run out of databases immediately, though. It takes a while with lots of SQL queries going to a linked ODBC database before it starts to complain.

Another issue I get often is an error when I close down Access. The error states that:

You attempted to open a database that is already open by user 'Admin' on machine 'nnn'.
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-30T18:03:47+00:00

I'm having the same issue, plus it runs out of tables after a while of running, where it opens and closes recordsets properly.

When I try to go back to the previous build, the update process is broken, so a full repair is needed to get the updates running again. Only this time it finds no new updates.

I have a client whose Microsoft Office 365 just upgraded to 2048 Build 17928.20114 on August 26th.

Since that time they have been getting "Error 3048 cannot open any more databases"

I just checked the Task Manager and found 5 ghost processes of MSACCESS.EXE.

I

FYI, this is the 32bit version of M365.

Am I the first encounter this in the 32bit version?
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-30T17:04:48+00:00

Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here:

BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

Juan Soto

14x Access MVP

AccessExperts.com
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-30T17:04:25+00:00

Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here:

BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

Juan Soto

14x Access MVP

AccessExperts.com
Was this answer helpful?

0 comments No comments