This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BladeLogic Server Automation Suite
BladeLogic Agent and NSH
BSA BladeLogic Server Automation Suite
When attempting to connect to a BSA Target Server, the following message is observed in the rscd log on the target system:
(Not_Available):(Not_Available): C:\Windows/rsc/secure is empty, proceeding ahead with the default secure settings
(Not_available): (Not_available): /etc/rsc/secure is empty, proceeding ahead with the default secure settings
This will likely be accompanied by the following:
(Not_available): (Not_available): TLS setup failed for agent: Protocol mismatch. Check that client and server "secure" files match. Exiting and terminating connection.
empty secure file
Check the contents of the secure file on target server for the rscd line. If not present, you will see this message and the rscd service will listen on 5750/tcp instead of the expected 4750/tcp. The default settings in the file should be: