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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-09-12T01:51:53+00:00

    You can try running the Task Manager and terminate any MS-Access instance. This is due to network interruptions why it did not terminate gracefully.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2011-04-21T16:09:02+00:00

    Has anyone tried this? http://forums.iis.net/t/1071472.aspx

    In the file ApplicationHost.Config (c:\windows>\System32\InetSrv\config) the section where:

    <applicationPoolDefaults>

      <processModel identityType="NetworkService" />

    </applicationPoolDefaults>

    Change to:

    <applicationPoolDefaults>

      <processModel identityType="NetworkService" loadUserProfile="false" />

    </applicationPoolDefaults>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-04-15T14:22:14+00:00

    I have the exact same issue and its been driving me nuts! Like you steve im hoping someone will come back with a sucess story!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-03-21T06:52:31+00:00

    I'm also interested in hearing if this worked. I have the same problem on all our new Win 7 machines, while the XP ones remin unaffected. I can also add that the network shares don't appear to be disconected when this error occours and I also tried all new wiring and various other measures to overcome this problem to no avail (although un-installing HP's security tools stops other fatal crash errors when openting tables in table view).

    Hopefully now a few months have passed since these previous posts someone can confirm weather these measures seem to work (or not)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2011-01-26T22:23:34+00:00

    Hi HKoehn,

    Thanks for the reply. The reason I said it normally is related to a network problem is because this error is usually directly related to some sort of networking issue, such as mapped network drives disconnecting, outdated drivers, or a machine being disconnected from the network (not just SMB 2.0 traffic, though lately this has been more and more common). In the scenario you bring up, I believe the SMB 2.0 problem doesn’t present itself on Windows XP machines because I don’t think this networking protocol was introduced until Windows Vista.

    Best Regards,

    Nathan Ost

    Microsoft Online Community Support

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Was this answer helpful?

    0 comments