This was initially addressed by SSLV-1955 in SV 3.9.3.1. If you are running a version older than SV 3.9.3.1, update to the latest SV version.

If the problem happens in SV 3.9.3.1 or newer versions, a Technical Case should be opened with Symantec Support for further investigation.