Hi Chai CK,
I've seen exact same issue in our environment when we did not apply same SCU2016-2 on both CCS Application Server and dedicated CCS Manager in data collection role. We applied PU11.5/SCU2016-2 on Application Server but not on dedicated CCS Managers and the issue started appearing when we tried scanning Unix assets (in agent-less mode) that were scanning fine before the update.
Ensure you keep your CCS infrastructure servers (CCS Application server, CCS Manger, Evaluator, etc...) on the same PU/SCU level (note this does not apply to CCS Agents as there is backward compatibility to some point).
Best to view on which PU/SCU level are your infrastructure components is via LiveUpdate, however if you're not having it enabled then manually checking in:
Settings->GridView (or MapVew), right-click on component and select Health and Status Details, and under LiveUpdate observe:
- Product Update -> CCS_PU - this is PU level your component is running
- Security Content Updates -> CCS_SCU - this is SCU level your component is tuning
Here is info about latest PU/SCU numbers:
|
11.10.10500.1255
|
PU2016-1
11.5
|
|
11.10.10600.1090
|
SCU2016-1
|
|
11.10.10700.1100
|
SCU2016-2
|
|
11.10.10600.1013
|
PU2016-3
11.5.1
|
|
11.10.10800.1102
|
SCU2016-3
|
|
11.10.10700.1060
|
PU2017-1
11.5.2
|
|
11.10.10900.1130
|
SCU2017-1
|