There are scenarios where an ODBC Driver stops responding due to various reasons. When this happens all the connectivity related to that particular ODBC is lost and no data can be accessed through it.
This document helps in identifying if a specific ODBC connection is responding, if not how it can be fixed.
There are two reasons why the ODBC Driver might stop responding:
Due to a variation in the Path Variables.
Due to an outdated version of the ODBC Driver installed in the system.
This document aims at providing a resolution for the above mentioned problems.
Identifying the problem
The following steps have to be followed to identify the problem
Click on Start and type ODBCAD32.exe in Run and hit Enter.
Under System DSN, select the DSN name and click on Configure.
If nothing happens when you click on Configure it means the ODBC driver of the system is not responding.
Resolving the problem
There are two steps to resolve this issue:
Goto the Command Prompt and type Path at the Prompt and hit Enter. The below Screen will appear.
As seen in the screen shot if the PATH starts with PATH=C:\sybase it is correct and the path variables are fine.
Instead if PATH starts with PATH=W:\prod it means there is an issue and the PATH variables needs to be modified.
To modify this Right Click on My Computer:
Select Properties->Advanced->Environment Variables
Select Path under System Variables and click Edit.
Now edit the Variable Value and move the W:\prod to the end of the Variable value.
Once done save this and close the existing Command Prompt and reopen it.
In Path, W:\Prod should now be at the end of the Path. This should resolve the ODBC Connectivity issue. If this doesnt work then try STEP02.
If the above resolution doesnt work we need to verify the .dll file of the ODBC driver to check if version installed is not outdated.
To do this goto C:\WINNT\system32.
Select the file sqlsrv32.dll and check the timestamp of the file.
Compare this timestamp with the timestamp of the same file in a system where the ODBC works fine.
If the timestamp is older that means the system has an older version of the ODBC Driver installed.
To fix this copy the sqlsrv32.dll file from a working machine to the machine where ODBC is not responding.
This should fix the ODBC connectivity issue.
The above mentioned scenarios are some of the most common reasons for the ODBC to stop functioning. These problems might occur when a new patch is installed or some new upgrade is done to our system.