That is windows saying that it can't find dtlscli.dll.
dtlscli.dll is the executable that PC calls to talk with PWX.
Make sure that the login running PC has read and execute permissions on dtlscli
I have the same problem here, but I don't think it is caused by this reason.
How have you created two Extraction Definitions from different DB tables with the same Instance?
The following 2 source databases that all publish to the same DistDB
I found there are two instances as below
And I've created two capture registrations as below by the PWX Navigator, both of them are Condense Type of Partial and Active.
the content of my configuration file is as follows:
/* Define a CAPX CAPI_CONNECTION statement if you use the PowerExchange Logger
/* and continuous extraction mode.
/* The directory that you created for the Logger log files.
I guess there should be a problem with the DFLTINST in Dbmover.cfg and the DBID setting in PWXCCL.cfg.
When there is only one Instance, DFLTINST in Dbmover.cfg and DBID in PWXCCL.cfg should be set to the name of the Instance. But now there are two Instances, how should DFLTINST and DBID be set?
When you are using Multipub=Y, the rules about DFLTINST and DBID change slightly.
However, DFLTINST always determines the CDCT that PWX Listener will read when it attempts to find captured data in CND files.
Likewise, DBID in PWXCCL.CFG is what will be used by PWXCCL when creating the CDCT.
So those two values always have to match.