CTRA Server: no transports available, ffffffff. Server shutting down

We run into the CTRA Server: no transports available, ffffffff Server shutting down issue recently on both our Windows and Linux servers. This might happen when the agent starts and the only communication protocol enabled is ip.spipe. The agent doesn’t connect in fact it shuts down after this error message like in this example:

(59D09A0D.0077-1:kraaumsg.cpp,107,"CTRA_msg_no_transports") CTRA Server: no transports available, ffffffff. Server shutting down
(59D09A0D.0078-1:kraafmn.cpp,787,"kglpsrvr") RegisterHandlers() returned error code: -1!
(59D09A0D.0079-1:kraafmn.cpp,788,"kglpsrvr") Ignoring server start-up request!
(59D09A0D.007A-1:kraaumsg.cpp,143,"CTRA_msg_server_exit_status") CTRA Server:  exit status, ffffffff
(59D09A0D.007B-B:signalmanager.cpp,524,"managerThread") Termination signal received.  Exiting...
(59D09A0D.007C-B:khdxprts.cpp,1760,"KHD_stopStatusMgr")  CTExporterStatus object is unavailable!
(59D09A0D.007D-B:kscqueue.cpp,200,"stop") Successfully stopped Audit worker thread
(59D09A0E.0000-C:kcacmdunx.cpp,273,"executeCmd") Shutdown -- before sleep.
(59D09A0E.0001-C:kcacmdunx.cpp,364,"executeCmd") Shutdown processing.
(59D09A0E.0002-C:kcacmdunx.cpp,264,"executeCmd") Shutdown -- before sleep.
(59D09A0E.0003-C:kcacmdunx.cpp,364,"executeCmd") Shutdown processing.

In both cases the solution is very simple.

Linux / Unix

The issue was due to the fact that our custom certificates expired, once the certificates were re-created, copied across and both the remote TEMS and the Linux OS agent restarted, the problem went away.

Windows

On windows the issue was a missing file after upgrading to Fixpack 7. Once the kdebe.dll file is copied from ITM\TMAITM6_x64 to ITM\GSK8_x64\lib64
the problem was solved.

Leave a Reply

Your email address will not be published. Required fields are marked *