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

Hi HKoehn,

Normally, when we see this type of error message, though it may not seem like a network problem, it actually is. Access depends on a stable network connection and when that connection is interrupted in any way, it will display this type of message. A common symptom we see when Access displays this error is when you look at your mapped network drives on the machine, they will show as disconnected. My recommendation would be to have the user look at their mapped network drive as soon as this error message is displayed and see if they are showing as disconnected.

I would assume the next question would be why is it only happening on your Windows 7 machines? Unfortunately, networking is not my specialty, but it seems like a lot of times this problem does occur with newer operating systems and SMB 2.0 traffic / settings. I have seen several different steps used by our networking and platforms teams to fix issues with mapped network drives disconnecting and it appears one of the fixes they try (besides updating NIC cards) is installing the hotfix(s) in KB 982860. Though it doesn’t list the exact symptoms you are experiencing, it appears it does update some files and SMB settings. If you have a test environment that you can reproduce the issue on, it may be worth trying to test this fix. If you need more information about the fix and / or the impacts it will have, then you may want to consider opening up a support ticket with Microsoft so they can look at your exact issue and discuss the impacts of this fix. But once again, I would first verify that your mapped network drives are showing as disconnected immediately after you see the error message.

982860           A computer that is running Windows 7 or Windows Server 2008 R2 takes four minutes to open a Microsoft Office 2003 document from a network share

http://support.microsoft.com/default.aspx?scid=kb;EN-US;982860

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.

This problem does indeed appear to be an MS issue related to SMB 2.0. Here's a post where the user came to the same conclusion:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_25594983.html

I'm currently testing a work-around on one workstation where I have disabled SMB 2.0. I think I will try applying the hotfix to another workstation so that I can compare the two "fixes" to see if both of them resolve the error.

If this is in fact an SMB 2.0 issue, as I presume it is, I'm quite miffed that the general reply is, in your own words, "though it may not see like a network problem, it actually is". I've read many other forums posts on this issue and the symptoms are always the same; it only affects Windows 7 workstations connecting to Server 2008 while the XP workstations continue to run without any problem. I believe this "check your network" approach closes the door for MS to find a resolution to the real problem.

I work from a remote location so I have not been able to check to see if the network drives are disconnected or not when this happens. If I do find out, I'll report back.

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.

I would be interested in hearing whether or not the hotfix helped with this issue. We have much the same issue, Vista and Windows 7 both have problems with network disconnects to databases stored on our servers. Multiple XP systems connected to the same network do not exhibit the same problem.

Until recently it was only an issue for one of our developers, and he had simply given up on using the Vista system on any Access database opened remotely. Before giving up on it though, we went through three network cards and completely replaced the wiring for the Vista system. Now we've added three new Windows 7 workstations and they are showing the same symptoms. The share is on a 2008 Server, so I am fairly certain this is the same issue.

I will be testing this evening after disabling SMB 2.0.

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)