Hi,
When did you download the 2.3.1.7 release? This issue was identified soon after the release and has since been fixed and the release package was updated with the fix. I recommend download 2.3.1.7 again and redeploy, it should solve this problem.
Hope it helps,
Joe