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

Anonymous
2010-11-02T01:50:09+00:00

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

Microsoft 365 and Office | Access | For home | Windows

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

91 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-08-20T00:29:08+00:00

    I now get the message when trying to open the file.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-11-11T11:12:18+00:00

    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 ...

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2015-10-02T16:05:49+00:00

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

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-09-16T07:29:42+00:00

    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 ...

    Was this answer helpful?

    0 comments