Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

ODBC driver IPclass could not be found - error [10200]

flawed_81
Tera Guru

odbc IPclass error.png

I've installed ODBC driver yesterday and I'm getting this error when I test the connection. I've checked the service_now path and effectively the IP folder is not there. Not sure how to resolve this and cannot find anyone having the same problem.

I've tested in two different Win 10 laptops connected to different networks, I've tried connecting to different SN instances (one PDI and one Sandbox from work), I've got JRE and the dependency jar files, I've created a local odbc user.

I'm lost! 

12 REPLIES 12

johnbyram
Tera Contributor

Does anyone know of a fix for this item?

Brian S5
Kilo Sage

Looking for a fix for this as well, and any information that can be provided. 

JoeSkaggs
Tera Contributor

In case anyone finds this down the line, here is the fix.  
I downloaded the latest ODBC driver from the store
I downloaded and installed JDK 11.0.31 64 bit
I downloaded the ODBC dependencies from the store and put them in the program files / servicenow / odbc folder.  
In the servicenow odbc manager ip parameters I set servicejvmlocation to c:\programfiles\java\jdk-11.0.31\bin\server
ServiceJVMClassPath to C:\Program Files\ServiceNow\ODBC

C:\Program Files\ServiceNow\ODBC\ip\oajava\service_now\glide-odbc.jar;C:\Program Files\ServiceNow\ODBC\bc-fips-1.0.2.4.jar;C:\Program Files\ServiceNow\ODBC\bcpkix-fips-1.0.3.jar

I then pointed the windows sys odbc 64 bit at my instance

JoeSkaggs_0-1783467568543.png

 

, and used my creds and it connected.  
Only took me 4 hours of trouble!