Domino server crash or DLL error using Domino Change Detector

[Don Mottolo]

I'm new to TDI and trying to use the Domino Change Detection
connector on TDI 7.0 (with all Fix Packs installed from 1 to 7 ) for
the first time. TDI is installed on the Domino 8.5.3 server. I am
remoting in to the server, starting TDI, and trying to create an AL
using the Domino Change Detection connector as a feed source using
IIOP.

I can set up a regular Lotus Notes Connector using IIOP on this same
server to this same Notes database successfully to read or write
data. The ncso.jar has been copied to the \TDI\V7.0\jars\Domino
folder.

When I set up the Domino Change Detection connector and click
"Connect" I get:
"Error: java.lang.UnsatisfiedLinkError: C:\Program Files\IBM\TDI
\V7.0\libs\domchdet.dll (JVMPORT015E Unable to resolve DLL references
- a prerequisite DLL may be missing."

After searching I saw it recommended to add the path to the Domino
server DLLs to the Windows system Path variable. So, I tried adding
that, but now then clicking "Connect" cause both TDI CE and the Domino
Server to crash immediately! (and unfortunately, the server crash
is consistently reproducible.)

What am I doing wrong here?

[Eddie Hartman]

TDI is pure Java, Don. So when you see error message in logs, they are
often the same ones Java developers see. So oftens Google may have
suggestions if you replace the word 'TDI' in your search with
'Java'. :)

Your error in particular is:  java.lang.UnsatisfiedLinkError:  C:

\Program Files\IBM\TDI\V7.0\libs\domchdet.dll (JVMPORT015E Unable to
resolve DLL references

The java bit is that some library file is missing (domchdet.dll). And
from the error I see it's looking in the TDI installation folder. It
could be that you did not include the path to your Domino installation
in the system PATH. This will be to your Notes Client Installation in
the case you're using the Client Connection option for the Domino
Connectors; or your Domino Server installation for DIIOP. See if that
helps.

-Eddie

> - a prerequisite DLL may be missing."

TDI is like a Java 4GL where you tied Java objects together using
script. Even interactively.

In addition to being java related

[Don Mottolo]

Hi Eddie,

Thanks for the reply... I'm reading the error as saying that
domchdet.dll is unable to find other DLLs that it needs. So, I did
already try putting the Domino Server directory in the Windows System
Path, which would seem to make sense, but after that THE DOMINO SERVER
CRASHES if I try to connect.

If I take the Domino directory out of the path, I get the error; if I
put it in the path, it immediately crashes the Domino server when I
connect with the TDI Domino Change Detection connector.

Is it not meant to run on the same machine as the Domino server?
Any ideas?

[Don Mottolo]

To use the Domino Change Detection Connector, TDI needs to make a
LOCAL Notes client connection EVEN if you specify IIOP. So, the
Notes client must be installed on the same machine. (Normally, for
security it is recommend that a Domino server not also have a Notes
client installed on it.).

I was attempting to do it on a single Domino server that did not have
a Notes client, and because I did not understand, was pointing to the
Domino server path. The Domino server and TDI crashed because they
were both trying to use the same files directly.

The solution in this case was to install TDI on a different machine
that did have the Notes client installed.