We have an issue with Access losing connection to Databases.
We have the same issue with multiple Access databases. Some databases use data sources from SQL, some do not.
To Simplify my question and provide as much detail as possible with keeping it simple, lets say;
I have "Access Database A" that resides on Server1, and uses SQL server 2008 as back end.
I have "Access Database B" that resides on NAS1, and does not use SQL.
Our existing terminal server (Server 2008 R2) does not have any issues, a user can open either of the two databases in Access, and work in them with no problems. Server is running Office 2013 x86.
Now, we stood up a new 2012 R2 Terminal server (RDS), also with Office 2013 x86, and users are getting disconnected from the databases. They get disconnected from either of the two databases, so I have ruled out SQL being an issue. ODBC connectors are set up identical on both terminal servers. I cannot find any data in the event log that is relevant to any Access disconnects.
Also, network connectivity is not the problem, when a user loses connectivity, their RDP session is not dropped, and they have mapped drives (that exist on server1 and NAS1) that are also not affected.
I am looking for a way to enable logging to determine why Access is dropping connections randomly. Is there an advanced logging feature? Are there any timeout or keepalive settings I can look for?
Some more information, it seams like Access loses connection to the databases after some time of inactivity (we are working on gathering this data too), but no users have yet been disconnected while actively working in Access.
Any help is appreciated. Thank you.
There is none for the JET/ACE (access) DB's.
For SQL, there is the SQL logs and event logs.
<<Are there any timeout or keepalive settings I can look for? >>
There's no keep alive for either. LANMAN parameters can get in the way of the JET/ACE DB's, but not SQL server.
Default in Win 7 is 10 minutes I believe, but you say the mapped drives are not disconnecting, so that would seem to nullify that. Also it works OK with one server, but not the other (although there are server side settings for that).
Perplexing problem...is the new server running in a VM?
Do these stations loose connectivity to the NAS as well?
What are you seeing when a disconnect occurs?