Exceptions created on SEP 11.x based on TruScan detection (file hash) are not compatible with SONAR exception (New proactive engine)
When migrating from SEP 11.x to SEP 12.x some applications (usually In-House Application) start to be blocked again
TruScan exceptions created on SEP 11.x are based on SHA-1 so when migrating to SEP 12.x those exceptions won't be compatible with the new proactive engine (SONAR) that use SHA-2
A new exception to the blocked file need to be created again through SEPM 12.x console. The link below show how to create the new exception
Migration from SEP 11.x to SEP 12.x using the same environment
Did this article resolve your issue?
Did this article save you the trouble of contacting technical support?
How can we make this article more helpful?
Email Address (Optional)
Login to Subscribe
Please login to set up your subscription.
Get support for your product, with downloads, knowledge base articles, documentation, and more.
Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
Submit a suspected infected file to Symantec.
Report a suspected erroneous detection (false positive).
Create and manage cases, manage licensing and renewals, submit threats, and enroll with Symantec Rewards.
Customer and Technical Support phone numbers and hours of operation.
User-to-user forums, blogs, videos, and other community resources on Symantec Connect.
Set default language
Do you wish to save this as your future site?