Unsolved
This post is more than 5 years old
2 Posts
0
288200
July 20th, 2007 15:00
MS Access 2007 error: Your network access was interrupted.
I have an MS Access 2007 database that is located on a network drive. If I leave the database open for any length of time and often while I'm editing a record, I receive the following error and all the editable fields change to #name: "Your network access was interrupted. To continue close the database, and then open it again." I can close the database and then open it up immediately again without a problem until I receive the same error again later. Thanks to anyone who has insight to this problem.
Jason
0 events found
No Events found!
gothamww
1 Message
0
April 1st, 2008 14:00
post the resolution here.
jasperpc
2 Posts
0
April 1st, 2008 16:00
I initially tried disabling the TOE on the server, but that did not help. I then edited the registry key on the server (windows server 2003):
(Typical disclaimer for editing the registry applies here... I do not endorse it, make a back up first, etc... :-)
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\autodisconnect"
was f (15) changed it to FFFFFFFF (4294967295)
This has fixed the problem.
HKColorado
20 Posts
0
January 26th, 2011 12:00
It appears this problem may be related to an SMB 2.0 issue if you are using Windows 7 or Vista to connect to Sever 2008. Please see this related post:
http://social.answers.microsoft.com/Forums/en-US/addbuz/thread/61ed2ca6-ec77-40dd-8251-6f453a6ecb85
cp03
1 Message
0
December 13th, 2011 08:00
Did you have to do this on each user's workstation?
keithmast
1 Message
0
June 27th, 2012 07:00
6/27/2012
It's been a while since you posted this solution. Do you still recommend this change to the restistry to correct the "Your network access was interrupted. To continue, close the database, and then open it again." error? I have Win Serv 2008 SP2.
Keith
HKColorado
20 Posts
0
June 27th, 2012 08:00
I know that not everyone can do this, but we moved to SQL Server, partly to get away from this problem. We still use Access 2007 but now use ODBC linked tables.
jvthree
1 Message
0
July 19th, 2012 14:00
Disabling SMB in XP does not solve this problem.
HKColorado
20 Posts
0
July 23rd, 2012 08:00
I don't think disabeling SMB in XP is recommended at all. I think the proposed solution was to disable SMB 2.0 on Windows 7 machines that were having this problem. As I best recall, we actually tried this and it didn't help. Moving to SQL Server 2008 Express is the only thing we found that alleviated this problem. Using SQL Server Express is quite easy, and a tremendous improvement over an Access database backend. At this point I don't think I would ever using Access database backends anymore except for prototyping or for something extremely trivial that will not be shared or used across a network.
Jellis33
1 Message
0
October 5th, 2013 10:00
I have the same issue but the MS Access database back end resides on a Linux server running Samba 3.6.1-34.3-1-2691-SUSE-SL12.1-x86_64
Does anyone know of SAMBA or Linux settings to prevent the dropped connection.
Issue occurs on forms bound to linked tables
It seems sporadic (can happen quickly upon entry into form or after a period of time)
I made the registry setting that JASPERPC recommended on the workstations that experience the issue as it is mentioned in other forums as a recommended change on workstations.
Issue occurs on XP and Win 7 PCs
I have set SAMBA parameters OPLOCK and OPLOCK2 to no (although I don't think this should impact connection timeouts)
Issue occurred as soon as I upgraded the databases to Access 2010 from Access 97.
Using same server, folders, user logins as before.
The Access 97 DB had been running for 13 years. (2 - 3 years on this server)