Your network access was interrupted. To continue close the database and then open it again. Windows 7

Anonymous
2011-01-12T01:03:48+00:00

I've got a new problem that cropped up some time ago and only today did I find some critical information about this problem. Every once in a great while, with no consistency, a user will come back to their workstation and find the following error message on their screen:

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

We have our 2002/2003 format MS Access database backend stored on a shared drive on our SBS 2008 server. All the workstations are connected to the domain and they each have a local copy of the 2002/2003 format MS Access database frontend on their own hard drive. The server is a high performance dell with (4) 15K RPM hard drives in RAID 5, 12GB of memory, (2) Xeon processors, and gigabit wires to an unmanaged Netgear switch. All the workstations are gigabit as well. The server does file sharing, printer sharing, DHCP, DNS and MS Exchange on our small network. We have 8 workstations in use on a daily basis and two workstations that get used occasionally.

All the workstations are running Office 2007 or Office 2010. This problem affects both 2007 and 2010. All workstations have MS Updates turned off but we do bring them up to date every few weeks.

All of our Windows 7 workstations are having this problem andonly our Windows 7 boxes are having this problem . These Windows 7 workstations are all 32 bit Dell Optiplex 760 or 780 minitower desktops. The machine I'm currently investigating has a built-in Intel 82567LM-3 Gigabit network adapter with driver version 11.6.92.0 from 4/12/2010.

We are using MS Server Backup on the server. I'm fairly sure that this problem is not related to the backup because the problem does not correspond at all with our designated backup times.

I'm quite sure there is no interruption in network access. All of our XP workstations do not have this problem, including both those that are heavily used and those that are used lightly. I've checked for errors in the event log on the server and the Windows 7 workstations and there are no related errors logged on either one. There are no distantly related errors. Nothing is logged around the time of the so-called "disconnect". I'm quite positive the network is not dropping connection at all, and if it is, it has to be the sort of hiccup that is so brief that there are no popups, warnings, errors, etc., other than this MS Access problem.

Our network is a controlled environment. We have content filtering using OpenDNS and we have Norton Antivirus 2011 installed on every workstation. We haven't had viruses on any of our workstations in a couple years, maybe more. We don't have any other applications giving any error messages remotely similar to this.

I do not believe this is a problem with our network as it is fast and rock solid. Our server is very clean and never needs rebooting unless we are installing some kind of updates or software that requires it. I do see a lot of other posts online about this problem but so far there don't appear to be any solutions, only the standard rhetoric of "check your network" which is clearly not doing anything to escalate and solve this issue.

I did have to make some changes in the registry on our server right after we rolled out the new server. The changes I'm talking about are specifically "Turning off the sharing violation notification delay". You'll see this documented on Microsoft's website at http://support.microsoft.com/kb/889588 . We made these changes because there was a very long delay when more than one user was using the database. This was also true of our 2003 Server and we had made those same changes on there as well.

How would you recommend troubleshooting this issue? I can probably do wireshark if necessary although the problem is fairly infrequent, maybe once or twice per day. It will require running any analysis tool for many hours in hopes that the problem occurs.

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

45 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2013-04-16T11:49:24+00:00

    Yesterday I faced this misleading error message, and I was not able to find anything useful in the Internet. I got it SOLVED! so I write here to share my case and solution:

    Finally, the reason why I was getting this error message was THE USER running my application: My application is a SERVICE, so user is not the one logged on the computer, but, according to the task manager, user is SYSTEM.

    My service is written in Java, and it was trying to connect to a MS Access 2007 .accdb database, getting the error message "Your network access was interrupted. To continue close the database and then open it again".

    If I run my service changing "log on as" from "local system account" to "this account" and I enter the user & password used to log on Windows, the problem disappears! As you see, it has nothing to do with closing database and opening it again, and it has nothing to do with network access interruption. An ERROR_ACCESS_DENIED (0x5) would have been much much clearer...  ;-)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-01-01T21:23:40+00:00

    on the client (win 7) machines while database is open.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-12-26T15:39:40+00:00

    Hello Steve,

    I have a win 2008 server with an Access database that 20 users connect to remotely. This frontend database is linked to tables in an Access backend on a 2nd win 2003 server. I am experiencing the same 'your network access was interrupted' message that others have. Can you clarify exactly where I should open a Windows Explorer window in order to resolve this issue?

    Also, have other users following this thread reported that they have resolved this problem with your work around?

    Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-27T05:01:06+00:00

    UPDATE: I think I have found a simple work around for this - you just leave a Windows Explorer window open in the same network share as the database! I have found that this also works with the win7 task scheduler which otherwise fails to open the database overnight if you schedule it to do so.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2012-08-15T17:32:03+00:00

    I've been having the same problem but mine is a WinXP system.  This is a large network with several thousand users.  I keep the database on a network drive but the drive is not shared with anyone else. 

    I update a database once a year, with some minor modifications to the data structure and the form each year, and never had a problem before this (last year I was using Access 2003 but this year I'm using 2007).  This year I redesigned the form more substantially and reset the data but fundamentally it's the same.  Last year's db opened in 2007 hasn't given me the error yet but I get it intermittently on the new version.  No one has any idea why.

    Was this answer helpful?

    0 comments