Windows Server 2012 64-bit - SQLDriverConnect Failure
This section is applicable if you receive the below error on Windows Server 2012 64-bit while running porttest:
756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991000 Jdbodbc.c1339 ODB0000163 - SQLDriverConnect failure. rc=-1 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991001 Jdbodbc.c1339 ODB0000164 - DBC:00 [IM002][0] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991002 Jdbodbc.c1349 ODB0000010 - SQLDriverConnect failed. ODBC DSN: JDE920. 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.992003 Jdb_drvm.c909 JDB9920164 - Failed to connect to JDE920 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991004 Jtp_cm.c284 JDB9909103 - Could not init connect. 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991005 Jtp_tm.c1134 JDB9909100 - Get connect info failed: Transaction ID = 756\1640 MAIN_THREAD Mon Nov 16 03:05:13.991006 Jdb_rq1.c2432 JDB3100013 - Failed to get connectinfo
The likely cause of this error is because the ODBC datasources for JDE920, JDE_DEV, JDE_PROD, and so on were created with the wrong ODBC defined, such as this 64-bit directory and file:
\System32\odbcad32.exe
For 64-bit systems, the correct location from which these datasources should be created is in this 32-bit directory and file and directory:
\SysWOW64\odbcad32.exe
To remedy, launch the odbcad32.exe
as an Administrator from
C:\Windows\SysWOW64
and manually create the datasources.