Are you ready to take your data science career to the next step, or break into data science? With Springboard’s Data Science Career Track, you’ll master data science topics, have personalized career guidance, weekly calls with a data science expert, and a job guarantee.
Intercepting SQL Server connection errors in Access VBA code, over a VPN
I have an Access application that is running on the computers of numerous individuals at one of my clients, running various different versions of Windows and Office. We have migrated a number of tables to SQL Server but the connection strings for the different computer configurations are different, so I have a function which attempts to open a pass-thru query that selects the first record from one of the tables on the SQL server. If that process raises an error, the error handler attempts several other connection strings until it finds the proper one for the current users computer; that part works fine.
However, some of the users of the application do so over a VPN, with the application on their home or laptop and if they have failed to open the VPN connection prior to running the application, the receive the following error message:
However, some of the users of the application do so over a VPN, with the application on their home or laptop and if they have failed to open the VPN connection prior to running the application, the receive the following error message:
Connection Failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB][ConnectionOpen(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or access is denied.
Asked:
Who is Participating?
here you are:
Potential causes of the "SQL Server does not exist or access denied" error message
http://support.microsoft.com/kb/328306
looks like you are using DSN ODBC that may need to be checked with potential adjustment of uid\pwd sql server name there and verification of the sql uid\pwd sql server name by attempt to login on sql server via ssms to make sure that "sql server exists and used sql login has access to sql server\DB there"
Potential causes of the "SQL Server does not exist or access denied" error message
http://support.microsoft.com/kb/328306
looks like you are using DSN ODBC that may need to be checked with potential adjustment of uid\pwd sql server name there and verification of the sql uid\pwd sql server name by attempt to login on sql server via ssms to make sure that "sql server exists and used sql login has access to sql server\DB there"
Take one of the machines home with you and set it up on your home network. You'll get an IP something like 192.168.0.4 or 192.168.1.5. There's a list available of class C addresses that can be used by anyone because they're kept behind a NAT and not seen by the outside world - hence lots of people have the same IP addess but don't collide.
Anyhow, then open up the VPN and everything and get into your work network. At this point you'll be on another network and you'll probably have a different address range - 10.something, in all likelihood.
Anyhow, have a server in work that Access can try to find: if it does then it's operating via the VPN, and if not it can tell the user to open up the connection.
hth
Mike
Anyhow, then open up the VPN and everything and get into your work network. At this point you'll be on another network and you'll probably have a different address range - 10.something, in all likelihood.
Anyhow, have a server in work that Access can try to find: if it does then it's operating via the VPN, and if not it can tell the user to open up the connection.
hth
Mike
I think I would simply take the server name from the connect string and try to ping it. That will tell you if the network is up or not.
Jim.
Jim.
Have not been able to pursue this as I've been working several other short suspense tasks. Hope to get back to this soon.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month9 days, 3 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
in all connection strings always use the FQDN (full qualified domain name) and not only the name of the server. As an alternative you can also use the IP address but it's better to use the FQDN as an IP address could change sometimes (not very often in case of servers).
Sometimes a big network is divided into several subnets and without the FQDN it only searches in the direct reachable subnet and not all the others (depending on your network configuration).
Cheers,
Christian