SOLUTION TO ERROR " Your network access was interrupted. To continue close the database and then open it again." __

I am not a system administrator just an end user. However, your above comment is not correct. I get this error on many different access databases. However, many times you are not allowed to close the database and reopen. You have to completely reboot the entire computer in order to reopen that access database. If you were working on a new query or macro then it is completely lost and you have to start again. This happens multiple times a week and multiples times on some days. There is no rhyme or reason to when it will happen. My IT guys have been unable to provide me with any help as they see no network issues. I am also not able to compact my databases as I have always been able to do. This issue started happening today shortly after getting the interrupted network message. I have rebooted twice today and continue to have issues with Access.

Hi @All

I have experience the same issue on Win server 2008 / Terminal Server.

We use an access database since 2003, based on the network (DFS).

Since last week (10th of Septembre), I got that issue.

I tried to compact / repair : no change.

I copied the database : works

I changed it to the original  name : doesn't work

Run the access from Desktop / laptop / other Terminal server : it works

I had to reboot the Terminal server ... but today, it comes again ... sic !

I first thought that KB3076895  was the reason.

I installed last week the KB3092627 to correct it ... Both are installed correctly.

I must reboot again now and check if it works.

I'm pretty sure that a Patch is the root cause. But, unfortunately, the issue doesn't come after reboot ... and so playing with patchs is not reliable to know if it solves or not ...

Please share your experience and  why not the solution you have found ...

Thanks in advance ...

Yes rebooting does help.  Like all thinks microsoft, when in doubt reboot.  I am sure glad they don't make aircraft.

Possibly in an AD environment this problem can occur if drive from which Access database was opened is mapped via GPP drive maps.

Additionally group policy background processing for drive maps is enabled and setting for drive is "replace".

In this case backgroundprocessing and replace do a short network disconnect.

This causes MSAccess to throw this error ...