Contents x
    How do I Diagnose ODBC Connection Errors?
    • 01 Jun 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    How do I Diagnose ODBC Connection Errors?

    • Updated on 01 Jun 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article summary

    This article will go over methods of troubleshooting ODBC connection errors, such as module not found.

    Answer:
    Often, users have difficulty getting ODBC connections to work properly. There are many possible problems and variables but there are steps that can be done to find the issue and resolve.
    1. Confirm which version of Windows is being used on the machine in question. Do this by clicking the Start button, right-clicking on "computer" or "This PC" and choosing "Properties."
    2. Verify the system type to determine if the machine in question is a 64 bit or a 32 bit operating system. This can also be found in computer properties as well.
    • If the machine in question is 64-bit
    a. The ODBC Administrator is located in C:\Windows\SysWOW64\odbcad32.exe or can be accessed in Control Panel\System and Security\Administrative Tools
    b. Run the odbcad32.exe and click on the System DSN tab.
    c. If you do not  see "FoundSQL92," this means that the connection has not been configured yet or that is it configured in the wrong place.
    •  If the machine in question is 32-bit
    a. The Administrator is in C:\Windows\System32\odbcad32.exe and can also be found in the Control Panel under Administrative Tools.
    b. Run it and look at System DSN, as above. Select "configure."
    c. An error message of some type may occur.
    d. If you see a message saying that the the module could not be loaded, and a path for example like "n:\found\fims\pgoe1024.dll," see the following article which will outline what DLLs are needed for each version of Progress:

    https://knowledgebase.progress.com/articles/Article/000032523
     
    • Check the Progress version being used. The ODBC driver needs to correspond to the correct version of Progress that has been installed. This is found in a file in the ..npo\dlc directory. The file's name is "version" and it has no extension. Open it in notepad and confirm which version you are working with. See the article above after verifying the Progress version in use to see what DLLs are needed for your version of Progress.
    • Make sure that you have the correct driver in n:\dlc\bin, then make sure that the registry is pointing to that driver by going to regedt32, HKEY_LOCAL_MACHINE, SOFTWARE, Wow6432Node, ODBC, ODBC.INI and checking the FoundSQL92 key.
    • For the Driver value you should see the path to the relevant driver.
    • Then, check ODBCINST.INI, Progress OpenEdge 10.2B Driver (if you are on Progress 10) and ensure the Driver and Setup values also have the right path. 
    One tool that can be useful is the Microsoft ODBC test tool that can be used to test ODBC drivers for issues. Please see the attached file which contains the executable and documentation on the tool. See also the following:

    https://docs.microsoft.com/en-us/sql/odbc/odbc-test?view=sql-server-2017

    Note: We provide links to third-party websites in an effort to help you resolve your issue. We are not responsible for the information on third-party websites, and we cannot assist with implementing the resolution from these websites.
    Attachments
    odbctest.zip
    348.62 KB
    Was this article helpful?
    What's Next