Microsoft Access *.accdb files will not open after installing SOS 7

[JWinter95]

We have several databases on our system. Those ending with .mdb open with no issues. Those ending in .accdb will not.

[Sam M]

Same issue experienced here. Application/file exclusions do not seem to help. Only solution is pausing the protection, opening the database, then resuming protection.

[JWinter95]

I have found that if I split the database and execute the front end from the workstation drive and link the data on the network I have no problems.

[Sam M]

OK, thank you. We run the front and back ends on the server. Will try to split it up, thanks.

[Friend]

Hi, @Sam M , @JWinter95,
Do you have all the antivirus patches installed: https://support.kaspersky.com/15013#block0?

Try to diagnose which Kaspersky Small Office Security component causes the issue:

1. Open the main Kaspersky Small Office Security window and go to “Settings” –> "Protection". Here you will find the list of protection components in order. Turn off all protection components by clicking their switches to the left so that they become gray. Switch the first component (File Anti-Virus) 'ON' by clicking the switch to the right.
2. Check whether the issue persists.
3. If it doesn’t, turn the second component on (Mail Anti-Virus), but leave the first one enabled.
4. Keep turning components on one by one until the issue kicks in.

Specify which component caused the issue.

 

[Sam M]

Thank you, Friend.

It seems the File Anti-Virus is causing the issue.

It will not resolve even if I add the database file to the exclusion list.

[Friend]

What version of the Kaspersky Small Office Security is installed with you?

[Sam M]

20.0.14.1085 (b) on the two workstations which are having the issue

20.0.14.1085 ( e) on a workstation that has experienced the issue once before

[Friend]

To install the patch G:

1. Run the database update of Kaspersky Small Office Security. For instructions, see this article.
2. When the update completes, restart your computer.

To check if the patch was installed successfully, open the application and click Support in the lower-left corner. You will see the full version number of the application with letter g added at the end.
Then check whether the issue persists.

[Sam M]

Thank you! It seems version “e” and later have solved this issue. Both problem workstations have self-updated to “e” and do not have this issue. We will update to patch “g” today.

Thanks for the help!