After upgrading to Spectrum 10.3 various CORBA errors present in control panel

Document ID : KB000112340
Last Modified Date : 28/08/2018
Show Technical Document Details
Issue:
After upgrading to 10.3 from 10.2.x the following messages in the VNM.OUT/Spectrum Control Panel:

ERROR TRACE at CsCorbaMgr.cc(1254): Failed to connect to CORBA Naming Service on corbaloc::SERVERNAME:14006/NameService, will retry in 5 seconds.

ERROR TRACE at CsCorbaMgr.cc(1260): Could not create a root naming context. Maximum number of retries exceeded.
CORBA exception: Exception: CORBA::NO_PERMISSION
    Minor: 1447174771 
    Completion Status: NO
Cause:
This is caused by improperly configured CORBA files.
Resolution:
The following line in the $SPECROOT/.jcorbarc file must be false:

vbroker.security.alwaysSecure=false

Also, the following lines should be set properly:

vbroker.security.client.socket.enabledProtocols=TLSv1.2
vbroker.security.server.socket.enabledProtocols=TLSv1.2

Also in the .corbarc in the same location, the line must also be false:

vbroker.security.alwaysSecure=false

After changes are made the SpectroSERVER must be shutdown, and processd restarted.
For details on restarting Processd, please see this link:

https://docops.ca.com/ca-spectrum/10-3-0/en/administrating/distributed-spectroserver-administration/setting-up-a-distributed-spectroserver-environment#SettingUpaDistributedSpectroSERVEREnvironment-StopandRestartProcessd