CA Client Automation

While trying for infrastructure deployment, we are getting this error for almost all the machines(not for few).

All the firewall ports are opened as required.

We are getting the below error:

dmprimer.log file on one of the agents.

05/19/17 14:16:21 | 51844 | 56600 | ctrace.cpp | 848 | =======> Trace level = 5 <=======
05/19/17 14:16:21 | 51844 | 56600 | cdmprimer.cpp | 8805 | Unable to load CbbCore.dll!
05/19/17 14:16:21 | 51844 | 56600 | cdmprimer.cpp | 8850 | FIPS mode in dmprimer.cfg file: 2
05/19/17 14:16:21 | 51844 | 56600 | cdmprimer.cpp | 539 | Final FIPS mode : 2
05/19/17 14:16:21 | 51844 | 56600 | cdmcrypt.cpp | 323 | Install Path C:\Program Files\CA\DSM\DMPrimer\

05/19/17 14:16:21 | 51844 | 56600 | cdmcrypt.cpp | 328 | ETPKI Path: C:\Program Files\CA\DSM\DMPrimer\cryptocme.dll
05/19/17 14:16:22 | 51844 | 56600 | cdmprimer.cpp | 3603 | m_oDesKey.Create <0>
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 323 | Install Path C:\Program Files\CA\DSM\DMPrimer\

05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 328 | ETPKI Path: C:\Program Files\CA\DSM\DMPrimer\cryptocme.dll
05/19/17 14:16:22 | 51844 | 56600 | cdmprimer.cpp | 3606 | m_oPackageKey.Create <0>
05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 323 | Install Path C:\Program Files\CA\DSM\DMPrimer\

05/19/17 14:16:22 | 51844 | 56600 | cdmcrypt.cpp | 328 | ETPKI Path: C:\Program Files\CA\DSM\DMPrimer\cryptocme.dll
05/19/17 14:16:22 | 51844 | 56600 | cdmprimer.cpp | 3609 | m_oManagerPubKey.Create <0>
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 407 | Connected to CAM server.
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 410 | CAM queue name is CAI051844-00000
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 407 | Connected to CAM server.
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 410 | CAM queue name is CAI051844-00001
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 983 | CAM queue DMPRIMER on local host is running or startable
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 457 | CAI051844-00001 disconnecting from CAM server.
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 471 | CAI051844-00001 disconnected from CAM server.
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 457 | CAI051844-00000 disconnecting from CAM server.
05/19/17 14:16:22 | 51844 | 56600 | ccam.cpp | 471 | CAI051844-00000 disconnected from CAM server.
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

Please suggest.

It appears you forgot to include the actual error message you received.

Steve McCormick

Principal Services Consultant

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