[Discovery] Linux / Unix Server fails generating this error com.snc.automation_common.integration.exceptions.UnknownExceptionDescription <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size: 14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> From attempting to discover Linux or Unix servers noticed this error message "SEVERE *** ERROR *** com.snc.automation_common.integration.exceptions.UnknownException This is basically stating its attempting to talk to the target from the MID Server host but it seems to be unrecognizable using the default SNCSSH. Steps to Reproduce From the MID Server Properties verify if mid.property.ssh.use_snc is true. From the filter navigator: Run a discovery from a Linux machineLook in the Discovery logs. Also, from the MID Server parameters you can add mid.ssh.debug and a value as the 'IP address’. Then go to the ssh probe to run a test probe to the target, and investigate in the Agent logs. Workaround From the MID Server Parameters add mid.ssh.use_snc set to false. Additional InformationMID Server parametersMID Server Properties