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.

In reply to the problem experienced in this thread, I too am experiencing the same problem. Running 365 in a local environment. 3048 and the lockfiles don't close on closing the database. I am running the 32 bit version of Office 365. So the problem is not confined to the 64 bit version. To delete the lockfiles without restarting the computer: Scroll down in task manager until the MSAccess.exe is found and close the application. The lockfiles can then be deleted. This does not solve the problem, but at least the database can be restarted and the problem reincountered. Background information: The problem came out of the blue upon which I deinstalled and reinstalled office, to no avail. Microsoft stated that this bug had been fixed with an earlier release of 365. Evidently not! My question: can I return to an earlier version of 365 and how to do this? Hopefully Microsoft will come up with a solution soonest. Thank you.

Servus Karl, JA, es sind noch viele schwerwiegende Bugs enthalten. Bugs, die das Laufen einer Access-App unmöglich machen. Hatten wir auch schon vor einigen Jahren, jetzt wieder: Unerklärliche Fehlermeldungen an diversen Stellen: "... Mehr Datenbanken können nicht geöffnet werden". Hat nichts mit nicht geschlossenen Recordsets zu tun, meine App läuft seit 10 Jahren stabil.

Thanks, but I've already used task manager to end the process and manually delete the file. That closes the database. But it still doesn't fix the other error which caused the lock in the first place. I hope that Microsoft fixes this issue soon. Because I cannot roll back to a prior version as suggested by others. And I'm already past my deadline for the reports generated by the broken database.

You don't have to completely logoff to be able to delete the .laccdb file. If you end the main Microsoft Access task from the Task Manager, you can then delete the .laccdb file without logging all of the way out. Its a small thing but it will prevent you from logging off and closing down all of your applications

One more issue I have noticed with 2408 (and possibly 2407)... When I make an .accde from my .accdb, the 'save as' dialog will open to 'My Documents' no matter what. Previously, it would open to the location of the .accdb which is exactly what I needed. With 2408, I have to navigate every time to the proper location before saving, or save and move the .accde after the save. I reverted to 2406 and now when creating .accde the 'save as' opens to the parent .accdb location again. Hoping that 2408 will be fixed so that it will behave this way in the future.

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-31T15:34:41+00:00

In reply to the problem experienced in this thread, I too am experiencing the same problem. Running 365 in a local environment. 3048 and the lockfiles don't close on closing the database. I am running the 32 bit version of Office 365. So the problem is not confined to the 64 bit version.

To delete the lockfiles without restarting the computer: Scroll down in task manager until the MSAccess.exe is found and close the application. The lockfiles can then be deleted.

This does not solve the problem, but at least the database can be restarted and the problem reincountered.

Background information: The problem came out of the blue upon which I deinstalled and reinstalled office, to no avail. Microsoft stated that this bug had been fixed with an earlier release of 365. Evidently not!

My question: can I return to an earlier version of 365 and how to do this?

Hopefully Microsoft will come up with a solution soonest.

Thank you.
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-31T15:13:40+00:00

Servus Karl,

JA, es sind noch viele schwerwiegende Bugs enthalten. Bugs, die das Laufen einer Access-App unmöglich machen.

Hatten wir auch schon vor einigen Jahren, jetzt wieder:
Unerklärliche Fehlermeldungen an diversen Stellen: "... Mehr Datenbanken können nicht geöffnet werden".
Hat nichts mit nicht geschlossenen Recordsets zu tun, meine App läuft seit 10 Jahren stabil.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-08-31T13:44:05+00:00

Thanks, but I've already used task manager to end the process and manually delete the file. That closes the database. But it still doesn't fix the other error which caused the lock in the first place. I hope that Microsoft fixes this issue soon. Because I cannot roll back to a prior version as suggested by others. And I'm already past my deadline for the reports generated by the broken database.
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-31T11:33:02+00:00

You don't have to completely logoff to be able to delete the .laccdb file. If you end the main Microsoft Access task from the Task Manager, you can then delete the .laccdb file without logging all of the way out. Its a small thing but it will prevent you from logging off and closing down all of your applications
Was this answer helpful?

0 comments No comments
Anonymous

2024-08-30T23:21:17+00:00

One more issue I have noticed with 2408 (and possibly 2407)... When I make an .accde from my .accdb, the 'save as' dialog will open to 'My Documents' no matter what. Previously, it would open to the location of the .accdb which is exactly what I needed. With 2408, I have to navigate every time to the proper location before saving, or save and move the .accde after the save.

I reverted to 2406 and now when creating .accde the 'save as' opens to the parent .accdb location again. Hoping that 2408 will be fixed so that it will behave this way in the future.
Was this answer helpful?

0 comments No comments