Agent Manager fails to start with error "attempted duplicate class definition" (4370250)

The FglAM (Foglight Agent Manager) fails to start.

In the FglAM logs an error can be seen before it quits:

ERROR   [Startup Thread] com.quest.glue.core.Glue - Unable to start. Cause: loader (instance of  sun/misc/Launcher$AppClassLoader): attempted  duplicate class definition for name: "com/quest/glue/core/agent/AgentInteractionHandler$1"
java.lang.LinkageError: loader (instance of  sun/misc/Launcher$AppClassLoader): attempted  duplicate class definition for name: "com/quest/glue/core/agent/AgentInteractionHandler$1"

On FglAM version 7.1, the error message is:

ERROR   [Startup Thread] com.quest.glue.core.Glue - Unable to start. Cause: loader 'app' attempted duplicate class definition for com.quest.glue.core.agent.AgentClassLoader. (com.quest.glue.core.agent.AgentClassLoader is in unnamed module of loader 'app')
java.lang.LinkageError: loader 'app' attempted duplicate class definition for com.quest.glue.core.agent.AgentClassLoader. (com.quest.glue.core.agent.AgentClassLoader is in unnamed module of loader 'app')

SentinelOne Protection tools may negatively impact the FglAM (Foglight Agent Manager).

To resolve the issue it is required that users exclude directories from being scanned by the Sentinel One Protection tools, these are common installations directories:

But installations could be located in a different directory.

Refer to AntiVirus exclusion settings for Foglight and Agent Managers (4271242) for additional information.

SentinelOne has an Exclusion Mode called Interoperability, which we have found resolves this issue when applied.

Once (Interoperability) exclusions are in place, restart the FglAM (Foglight Agent Manager) service.

Remove additional VM options from 3rd party applications that may conflict with the FglAM startup; for example:

vmparameter.X = "-javaagent:/path/to/application-agent.jar";