- The driver is not able to find the JVM library or the JVM library cannot find its dependencies.
For the 32-bit Salesforce driver, make sure the paths to the 32-bit JVM are on the system path, for example, C:\Program Files (x86)\Java\jre6\bin;C:\Program Files (x86)\Java\jre6\bin\client;
For the 64-bit Salesforce driver, make sure the paths to the 64-bit JVM are on the system path, for example, C:\Program Files\Java\jre6\bin;C:\Program Files\Java\jre6\bin\client;
If using SQL Server linked server, set the path as mentioned above and then restart SQL Server to pick up the path.
For any other application, make sure to restart the application after installing the driver.
- The incorrect ODBC Data Source Administrator is used.
Use the ODBC Administrator that matches the bitness (32-bit or 64-bit) of the driver. The 32-bit version of the ODBC Data Source Administrator is found at C:\WINDOWS\SysWOW64\odbcad32.exe. The 64-bit ODBC Administrator is found at C:\Windows\System32\odbcad32.exe. If the 64-bit driver is installed and the 32-bit ODBC Data Source Administrator is used, the 64-bit drivers are seen, but the test connection will fail.
Note that if you open the ODBC Administrator from the product's program group, the correct ODBC Administrator will be opened.
- If User Account Control is turned on (Applies to Windows Vista, Windows Server 2008, and Windows 7 at this time), reinstall Java and the Connect(64) for ODBC product with the correct permissions as follows:
a. Uninstall Java and the Connect64 for ODBC product and remove any remaining files under C:\Program Files\Progress\DataDirect\Connect64_for_ODBC_70.
b. Using Run As Administrator (right-click the executable and choose Run As Administrator), reinstall both products, Java first.
c. Check to make sure sure the system path includes the required Java paths C:\Program Files\Java\jre6\jre\bin and C:\Program Files\Java\jre6\jre\bin\client (or C:\Program Files\Java\jre6\jre\bin\server).
d. Restart the ODBC Administrator and retry the test connect.