Re: Driver class not found: net.sourceforge.jtds.jdbc.Driver
Hi Sven, When MCF is built, two entirely distinct versions of the examples are created -- a standard version, and a "proprietary" version. The proprietary version does not in general include any proprietary jars and leaves connectors that depend on them disabled in the connectors.xml file. The proprietary version is not included in the shipping binary. If you want everything to automatically be put together for you and you rely on proprietary jars you will need to build yourself. However, it's easy to add root-level proprietary jars to the non-proprietary binary. The start options in the examples directories all include references to root-level proprietary jars; you just have to add your JDBC driver to those options files and you should be good to go. Karl On Thu, Aug 16, 2018 at 11:36 AM Farrenkopf, Sven wrote: > Hi there, > > > > I'm trying to get the JDBC-Connector to work with the provided example. > Target database is MSSQL. The JDBC-Connector seems to be registered > successfully. > > > > But every time I configure the JDBC-Connector via web-interface, the > connection-status shows "Threw exception: 'Driver class not found: > net.sourceforge.jtds.jdbc.Driver'" > > > > While several sources (including Manifold-Website) state that third party > libraries are required to BUILD the connectors, I have downloaded the > binary version and I thought there was no need to build anything there. (Am > I wrong?) > > > > So do I have to put a required jar-file within the folders somewhere? I > tried several jtds-jars in several folders with no luck. I simply want to > test an sql-connection with manifold within the example. > > > > Sven >
Driver class not found: net.sourceforge.jtds.jdbc.Driver
Hi there, I'm trying to get the JDBC-Connector to work with the provided example. Target database is MSSQL. The JDBC-Connector seems to be registered successfully. But every time I configure the JDBC-Connector via web-interface, the connection-status shows "Threw exception: 'Driver class not found: net.sourceforge.jtds.jdbc.Driver'" While several sources (including Manifold-Website) state that third party libraries are required to BUILD the connectors, I have downloaded the binary version and I thought there was no need to build anything there. (Am I wrong?) So do I have to put a required jar-file within the folders somewhere? I tried several jtds-jars in several folders with no luck. I simply want to test an sql-connection with manifold within the example. Sven
Re: Documentum indexing issue
Hi Sharnel, (1) I cannot create a patch unless you create a ticket I can attach it to. (2) I can easily recognize this kind of corruption and allow MCF to skip the document, and I've committed that change (r1838171). However, partially indexing a document that is partially corrupted like this is not something that is straightforward to do; the connector currently skips corrupted documents entirely. Karl On Wed, Aug 15, 2018 at 11:54 PM Sharnel Merdeck Pereira < spere...@worldbankgroup.org> wrote: > Hi, > > > > I am using MCF v 2.9.1 with dfc 7.1 > > > > On indexing there are documents which are corrupt . The metadata to these > objects are fine but only the file content is corrupt. > > > > Indexing stops with below : > > > > org.apache.manifoldcf.crawler.common.DCTM.DocumentumException: > [DM_STORAGE_E_BAD_TICKET]error: > "Use of invalid ticket for storage object with name ifcdocs_store_01; > storage may be improperly configured. > > Ticket was 8007b986. Data Ticket was 1." > > at > org.apache.manifoldcf.crawler.common.DCTM.DocumentumObjectImpl.getFile(DocumentumObjectImpl.java:375) > ~[?:?] > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:1.8.0_181] > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[?:1.8.0_181] > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:1.8.0_181] > > at java.lang.reflect.Method.invoke(Method.java:498) > ~[?:1.8.0_181] > > at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > ~[?:1.8.0_181] > > > >- there are many such corrupt docs which is breaking indexing. >- No errors on dfc logs > > > > Kindly help with a patch fix so that we can extract the metadata , ignore > file content if the above exception occurs and continue indexing. > > > > Thanks > > Sharnel > > >
