Access 2007 database. Linked tables to backend SQL Server 2008 server. Running under Terminal Services on Server 2008 x64. Each user has their own copy of the frontend mdb. This message happens frequently for all users.
This application was running with Access 2007, backend to SQL Server 2005, under Terminal Services on Server 2003. This problem only began occurring since the move to the new environment.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
SQL Server is NOT on TS box; it runs on an SBS 2008 box.
Event Logs on both boxes are pretty clean; no clues there.
GP's for users work in all respects. This database is the only app having a problem.
WRT running db locally. Currently running app from physical console (versus RDP connection). Will have results shortly. This app will get error just by being open and sitting idle. Not sure of mean time to failure.
lol, I always get the problems from hell. I agree that it seems to have something to do with my new TS platform and I'm glad to be experimenting on myself before deploying to clients.
Because this app uses linked tables, it is using 32-bit ODBC, which means that the SQL Driver is my one and only option. I've just gotten on SSMS and set the remote query timeout to 0 and if that fails, will upgrade to MDAC 2.8 ifnot already at that level.
As an Access developer I have recently experienced this problem at a client site mainly running Access 2007 on Vista.
The following fixed it!
Thanks to Pinpoint Computers Steve Gauci (Thornton Australia)
Reference - http://support.microsoft.c
Update registry keys on user PCs as follows
[HKEY_LOCAL_MACHINE\SYSTEM
"autodisconnect"=dword:fff
[HKEY_LOCAL_MACHINE\SYSTEM
"KeepConn"=dword:00003840
llewes...This is nice to know and I will try it if my SQL Server timeout fix does not work. Of particular interest to me was the second reg entry, which is not doucmented in the referenced KB article, that controls disconnects of UNC references. I use those a lot (prefer them to drive mapping) and that is essentially how the SQL Server is referenced by the ODBC driver.
I'll update here after testing the SQL Server timeout for a few more days.
I have the same problem but do not seem to have KeepConn in my HKEY_LOCAL_MACHINE\SYSTEM\
Should I make the same adjustments in the other computer (the PC on which I run the backend of the DB)?
Christina
Server=backend pc. You can create the KeepConn key, non-existance just means it uses the default value (http://technet.microsoft.
I'm going to be looking more closely at the following:
(http://www.brianmadden.co
I recently experienced this same issue where our FileServer (no terminal services) was producing the following errors:
1)Opening an 2007 Access file: Error-Your network access was interrupted. To continue, close the database and then try it again. 2) Copying the Access file off the share: Error-Cannot copy ____: not enough server storage is available to process this command. I used llewes suggestion by adding the following 2 edits to the server's registry and it worked immediately after!!!
[HKEY_LOCAL_MACHINE\SYSTEM
"autodisconnect"=dword:fff
[HKEY_LOCAL_MACHINE\SYSTEM
"KeepConn"=dword:00003840 (had to create this dword key)
Thanks!!
Business Accounts
Answer for Membership
by: LSMConsultingPosted on 2009-08-26 at 06:43:48ID: 25187547
I'm assuming that the SQL Server is NOT on the same machine as the TS ...
If that's the case, then the first thing to look at would be the connection between the TS and the machine running the SQL Server. Have you checked the event log of both machines to see if there's any clues?
Also check User and Group settings for policies that may cause this. I'm not sure exactly what those would be (the logs will likely give you a clue, if this is a problem).
If you run the db locally from the TS box (i.e. do a physical walkup and fire up a local copy of the FE) does the same thing happen?