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

flawed_81
Tera Guru

‎07-03-2024 02:59 AM

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! 

 

0 Helpfuls
  • 2,670 Views
11 REPLIES 11

Wimsnow
Tera Contributor

‎08-13-2024 02:44 AM

Same issue here, did you find any solution?

I have the latest ODBC driver version 2.0.0 April 2024 installed.

Strange enough, the documents don't mention changing the DataSourceIPClass. (only DataSourceIPProperties must be changed)

It is filled by default with the value 'oajava/service_now/IP' but that class could not be found....

Configure the ODBC driver (servicenow.com)

0 Helpfuls

Bobby4
Tera Contributor

‎08-22-2024 06:57 AM

Any solution for this?  I'm getting the same thing as @Wimsnow.

0 Helpfuls

Rebecca Bailey
Tera Contributor

‎09-10-2024 07:32 AM

Any solution for this issue?  I have had to reinstall the ODBC driver after my laptop had be reimaged, this setting previously worked fine, I previously installed it back in 2023.  I have tried everything, but cannot get past this issue of the classpath. 

0 Helpfuls

Rebecca Bailey
Tera Contributor

‎09-10-2024 09:03 AM

Ok, solution found... well kind of... this error only appears with the ODBC connector v. 2 onwards (I used ServiceNow-ODBC_2.1.1).  Luckily I did have a previous version (ServiceNow-ODBC_1.0.15) and once I removed v.2.1.1 and then reinstalled v.1.0.15 all worked fine.  Hope you all managed to work it out like I did.