Troubleshooting
Problem
Sterling Control Center Lost Connection to Connect:Direct Server after Keycert Change
Symptom
We just updated our keycert on Connect:Direct UNIX via Sterling Control Center. Shortly afterwards we found we were unable to make further updates to the C:D server via SCC. The SCC connection properties now show error: CNCD022E
Sterling Control Center 5.2.xx
Error Message
CNCD022E Error connecting to server. Server ID: name-server Host Name: ip-address API Port: 1363 Source Port: User ID: profile-name Details: Error: Connection Exception! Unexpected IOException in CommunicationBuffer::Send(). sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Resolving The Problem
You should add the new certificate to the Sterling Control Center before pushing it out to the Connect:Direct node if this is the same keycert used by .client in SPADMIN or SPCLI.
Update the trust store file that was setup for secure connections as outlined in 'Creating a Secure Connection between the Engine and a Managed Connect:Direct Server' within the 'Sterling Control Center Getting Started Guide'.
Historical Number
NFX11571
Product Synonym
[<p><b>]Function Area[</b><p>];secure+;[<p><b>]Escalation ID[</b><p>];00330699;[<p><b>]Severity[</b><p>];Normal
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg21559896