From Report Events, check how many machines under the Source column are reporting the "data is bad for config list entry"
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
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 App Control Server:
- Browse to App Control Server Installation:
- C:\Program Files (x86)\Bit9\Parity Server\hostpkg\
- C:\Program Files (x86)\Bit9\Parity Server\configxml\
- Make a backup of all "configlist..." files outside of those folders
- Removed all "configlist..." files from those folders and restart the App Control Server Service
- A new configlist files will get created