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

Bless you Kurt. I had an Access database running on a virtual Windows 10 box, and the virtual server was paused due to a disk error at the host. One of my access databases crapped out, several were fine, and was ok but had network access errors the four times I ran a macro that processed stuff within it. I did what you suggested and it processed with no errors. It will run many more times. Hopefully, it will continue to run without error.

Why did this fix it?

You have a bigger problem. Your solution indicates that your databases are a) not split or b) if split, the front end is being shared. In either case, this is a big nono. 

The proper configuration for a multi-user Access application is a shared back end on a network share containing ONLY the tables and a LOCAL front end installed on the user's PC. The linking in the front end can and should use UNC instead mapped drives.

If your users are all loading the same, non split, apps that is an invitation to corruption. It might cure the network access problem, but will cause other problems.

Hi after disableing smb2 and removing HP tools to no avail, i discovered i had two versions of office installed on my system, Office 2013 Home and Business and Office 2013 Professional, i removed Home and Business and his message disappeared instantly, hope this helps anyone else as it appears to be a long standing issue.

Sorry to Microsoft,

we need a solution since so long far away. The only wordaround is to disable SMB2 on the server. Enable SMB2 and the problem is here. Disable SMB2 no problems.

The same is in SMB3 with Windows 2012 R2.

Sorry, the same shi......

Very frustrating and no help or solution helps.

Thanks

I have a completely different solution...

Our network is running 3 Windows 7 PCs (no other O/S), this error just started happening randomly one day and then it became more and more frequent to the point that I was starting to wonder if I would have to replace Access with something else. Prior to this when we were running 3 XP PCs I never had this problem once in more than 7 years.

Worse than the lack of network access was the database corruption that often accompanied a network access interruption. I have no idea how but duplicate records were being introduced into the database as a result of the network interruption even though the tables had duplicates not allowed and I was always creating a new and unique ID as the primary key for each new record. Even more bizarrely the database would then drop the primary key on the table that had the duplicates. Once that happened the database would be unusable until I manually went through, removed all the duplicates and added the primary keys back on. Access should have blocked the duplicates completely, not let them in and drop the primary key (with no error or warning messages of course). This corruption was occuring 2-3 times a week!

Anyway that's the background to my problem. I tried EVERY single fix suggested here and on other sites, not one of them made the slightest bit of difference to the network access interruption. I also tried reinstalling Access, did not help, tried different A/V programs, that did not help either. I had also noticed that network copying had become very slow, I changed some network card parameters and solved this but it did not help the primary problem.

One day I found the answer purely by accident and here's what I did (note that this solution is appropriate for a single network environment, I cannot vouch for what you should do in a multiple network environment):

1. Go to the Network and Sharing Centre
2. On the left it side under the "View your active networks" section it will tell you what your active network is, click on the icon with the 2 blue blocks (that is the picture icon not the text), this will open the "Set Network Properties" dialog box.
3. On the "Set Network Properties" dialog box click on the "Merge or delete network locations" text, this will open the "Merge or Delete Network Locations" dialog box. Note that you may need to enter an administrator password.
4. On the "Merge or Delete Network Locations" if you see more than one network then you may have the same problem I did, merge or delete as appropriate until there is only one network and remember its name.
5. Repeat steps 1-4 for all computers on the same network ensuring they all use the same network name.

The above solved the problem for me permanently and ended months of frustration and wasted hours. In our network the 2 "client" PCs had Network, Network 2 and Network 3 defined. The "server" PC had only 2 of these 3 (I can't remember which 2). I can only guess that Windows 7 was trying to switch between these phantom networks and thus interrupting the network connection. Note that in our network all 3 PCs are running virtually identical software and hardware configurations, the server computer has all the Access tables and the 2 clients interface to these tables using their own copy of an Access database with forms, queries, reports etc.

I hope this post can help some people who are as stuck as I was :-)

Hi byronator,

I'm facing the same problems for some of my customers, especially with Server 2012.

I was really interested in your solution and wanted to test it, but i couldn't find the "Merge or Delete Network Locations" on Server 2012 (with domain).

Does someone know how to implement this solution in this environment?

Thanks