Solved

Losing connection to access database located on cloud server

Posted on 2014-10-06
9
242 Views
Last Modified: 2014-10-14
I am getting the attached error message when accessing an access 2010 database that is located on a cloud server.  It happens intermittently.  Other applications, can be accessed with no problems.  The problem seem limited to Access.  This is the only Access database that is located on the cloud server and multiple users access it.  I'd like to get some ideas of what could be causing this problem.  The network guys are stumped and I am looking for fresh ideas on what could be causing this problem.  The error message does not appear to be an Access error message.
disconnect.jpg
0
Comment
Question by:chtullu135
9 Comments
 
LVL 22

Expert Comment

by:Kelvin Sparks
ID: 40364751
You haven't described how you connect. It is typical of a remote desktop disconnect.

I use these regularly, and usually only see this if a VPN is in place and that disconnects. It can be momentarily - other internets sessions will reconnect, but a VPN one will need the VPN to re-establish itself.

Alternately, the cloud provider may have a firewall or similar plan in place that drops connections after a set amount of time. This can be quite common for RDP sessions (typically between 30 and 120 minutes).


Kelvin
0
 
LVL 57
ID: 40364765
<<I am getting the attached error message when accessing an access 2010 database that is located on a cloud server.  It happens intermittently.>>

 Your problem is not Access; it's RD (Remote Desktop).    

 You've got a logon to a remote server through RDP and that's what's getting disconnected.  You may be using Access, but this has nothing to do with Access.

Jim.
0
 

Author Comment

by:chtullu135
ID: 40364868
Thanks Jim,  I haven't noticed that problem occurred with other applications.  However, since the problem is intermittent, it could very well be happening with other applications..  Kelvin's point about a firewall dropping connections after a set time may also be contributing factor.  It may be that the users are using accessing the access database and not closing the connection when they are done.  I'll ask the users.
0
 
LVL 34

Expert Comment

by:PatHartman
ID: 40364917
Access is the canary in the coal mine so to speak when it comes to flaky connections.  Access has a very close connection with it's BE and can't recover gracefully from intermittent drops.

You might have to convert the BE to SQL Server.  Since Access expects to connect and disconnect to a SQL Server BE, it is more stable in this situation.
0
Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 
LVL 49

Expert Comment

by:Gustav Brock
ID: 40365566
Jim is right. This has nothing to do with Access as it runs at the remote site.

It is solely a loss of connection between the user's Remote Desktop client and the remote server. The client is quite sensitive to drops of connection, and you'll see the message; however, it is also quite good to regain normal operation once the connection is reestablished.

/gustav
0
 

Assisted Solution

by:chtullu135
chtullu135 earned 0 total points
ID: 40370999
Hello Pat,  
Why would using a SQL server backend make the connections more stable.  I mean it sounds right.  I imagine since SQL server is designed from the get-go to be used as a backend, it is inherently more stable than an Access backend
0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 40371018
@chtullu,

  The connection Access has with a DB file is not the issue here, it's your connection to a remote desktop server that is getting cut off.  As Kelvin said, that may be by design.    RDP sessions can be set to disconnect or log off after a certain amount of time or a certain amount of time of inactivity.  Then on top of that is all the usual stuff, like an actual flaky connection over a VPN.

  But yes, SQL Server is by far more robust because it has a server side process that acts as a door man for the DB.   No one gets to the DB otherwise and all connections run through the door man.

  in contrast, with a JET or ACE DB (the default DB for Access), every client reaches out to the DB file and manipulates it directly.   There is no server side process.  The server acts as nothing more than a file sharing device.

Jim.
0
 

Author Comment

by:chtullu135
ID: 40371040
That makes a lot of sense Jim.  Thanks.
0
 

Author Closing Comment

by:chtullu135
ID: 40379400
Thanks for the help.  I am advising the client to migrate the backend to sql server
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Steve Terp was featured in a video created by CRN about how "Channel Is Crucial To Market Disruption". Click on View source to see the video and article
Describes a method of obtaining an object variable to an already running instance of Microsoft Access so that it can be controlled via automation.
Familiarize people with the process of utilizing SQL Server views from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Access…
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now