ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Upgrade Secure Cloud On-Premise Connector Server Failed


Article ID: 109325


Updated On:


CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On


Upgrading the Secure Cloud On-Premise Connector Server from version 1.58 to version 1.60 failed.


As part of previous Secure Cloud 1.58 hotfix steps the eta2_server certificate was imported into the ssl.keystore used by the Secure Cloud On-Premise Connector Server. This certificate caused a conflict which caused the upgrade to fail.


Secure Cloud 1.60


1. Stop the on-premise Connector Server 

2. Take a backup of the existing ssl.keystore 

3. Remove the eta2_server alias from the ssl.keystore file being used via the following command: 
keytool.exe -v -delete -alias eta2_server -keystore ssl.keystore 

4. Start the on-premise Connector Server and verify that you are still able to see endpoint account details via the Secure Cloud Web UI even with the eta2_server removed from the ssl.keystore 

5. If everything is still working properly then proceed with trying to upgrade the on-premise Connector Server from version 1.58 to version 1.60