When we run Symantec's on-demand scanner it does not flag any StreamBase executable as problematic. This is a false match and neither the StreamBase Plugin nor the StreamBase utilities carry the
SONAR.SuspScript!g3 risk.
The full
StreamBase Studio install does not have this conflict with Symantec Antivirus so you may use that instead. Using the full StreamBase Studio and not the plugin is the preferred solution.
If you must run the StreamBase Studio Eclipse Plugin and not StreamBase Studio and see this behavior from Symantec, the options are:
A. Follow the "REMOVING A FILE FROM QUARANTINE" steps from here:
https://www.symantec.com/security-center/writeup/2017-032722-1016-99B. Make sure the StreamBase Server is installed into the default location at
C:\tibco\sb-cep\ and not elsewhere on your system.
C. Disable Symantec Antivirus while running StreamBase applications from Eclipse.