The lines here that appear to be the error, may well not be:
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 196 | CDmcrypt :: ~CDmcrypt - would call etpki_lib_term()
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 204 | CDmcrypt :: ~CDmcrypt - etpki_lib_term() return code : 1
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 196 | CDmcrypt :: ~CDmcrypt - would call etpki_lib_term()
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 204 | CDmcrypt :: ~CDmcrypt - etpki_lib_term() return code : 1
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 196 | CDmcrypt :: ~CDmcrypt - would call etpki_lib_term()
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 204 | CDmcrypt :: ~CDmcrypt - etpki_lib_term() return code : 0
Notice the last item ends in return code 0. This typically means the attempt at whatever it was doing, did eventually work. The actual error probably lies elsewhere.
I would collect the following info:
1. ITCA product version at both ends of the connection
2. Screenshot of 'DSMVER' or run "DSMVER -F C:\DSMVER.txt" and copy paste the output.
3. Zip up all RC logs with a time stamp matching the day the test was done an NOTHING OLD.
4. The output of "camping -a <target machine name>" from the Remote Controlling system.
5. The output of "camping -a <remote controlling system>" from the system you are trying to control.
6. The operating system running on both ends.
Thanks,
Joe Puccio
Senior Engineer, Software Support