Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from RGaley on Oct 6 at 1:01 PM In our scenario, it turns out that the act of deploying the jar file with NWA is what corrupted the jar file. After deploy, we opened the folder where NWA stored the jar, and replaced it with the source jar. This had to be done on each instance (server) where deployed.
| | | ---------------Original Message---------------
From: Rich Galey
Sent: Tuesday, September 20, 2016 3:26 PM
Subject: SAP UCES 6.35 and JDBC Drivers
Did I miss a step in loading the .jar files to the system? I'm getting these two errors anytime I try to ping a JDBC custom DataSource from NW 7.45.
1)
readResourceFromJar(String fileName)
[EXCEPTION]
java.util.zip.ZipException: invalid code lengths set
at java.util.zip.InflaterInputStream.read(InflaterInp utStream.java:147)
at sun.misc.IOUtils.readFully(IOUtils.java:48)...
2)
DataSourceManagerImpl.ping1xDSConnection(), Class 'com.microsoft.sqlserver.jdbc.SQLServerDriver 9; cannot be found in the driver JAR for driver SQLSVR_6.42. Check the class name spelling.
[EXCEPTION]
java.rmi.RemoteException: Class 'com.microsoft.sqlserver.jdbc.SQLServerDriver 9; cannot be found i
I have done an identical setup in a brand new installation using NW 7.0, and all works fine. SAP has verified the SDA file I had to create for 3rd party JDBC.
Has anyone run into this kind of problem before? |
| Reply to this email to post your response. __.____._ |    _.____.__ |
