Version
6.0.2.x & 7.x.
Issue/Symptoms
Receiving an event for "Data is bad for config list entry".
Cause:
"Data is bad for config list entry" means that an agent received config list change and the instruction or details on the config list was mostly likely corrupted that the agent didn't know how to apply it. Config list entry is created whenever you may a system config change or rule change or file state change (like ban or approval, etc.).
Solution
On Events page, check how many machines under the Source column are reporting the "data is bad for config list entry". If it's less than 5 machines, please use solution Agent cache corruption to fix the cache as there is some entries on the cache's file inventory that is reporting a bad hash to the server.
If it's more than 5 machines reporting this event, it means that there's a CL entry that agents are unable to process due to the configlist.xml getting corrupted. The errors.bt9 file on the agents will show a message of being unable to process some CL version(s). To resolve this, go to the Bit9 server and browse to %Program Files%\Bit9\Parity Server\Hostpkg and %Program Files%\Bit9\Parity Server\configxml. Make a backup of the configlist.xml file outside of those folders. Delete the configlist.xml file and restart the Parity Server service. A new configlist.xml file will get created.
