When adding Risk Exception, duplicate policy entry noticed and cannot add Risk Exception to either policy
Last Updated May 07, 2019
While attempting to apply a Risk Exception from Symantec Endpoint Protection Manager (SEPM) console and adding to an existing exception policy, you noticed there are two duplicate policies. When selecting one of the policies and clicking “Save Changes”, you get following error: “Number of policies successfully updated: 0. There was an error: Database error.”
From SEPM > Monitors > Logs > Risk > Past Month > View Log
Different SHA-1 for same SHA-256, so cannot query the distinct SHA-1 row.