"Failed to initialize SQL PI engine" for SQL Server agents that have special characters in the display name on systems with log4j 2.17.1 or higher prevents SQL PI from functioning for the agent and data is not collected.
An error in the database similar to the following may appear where in this example AGENTNAME (*\EXAMPLE) is the display name of the database agent.
ERROR [AGENTNAME (*\EXAMPLE)]lowPriorityPool-1[DBSS_PI_Engine_Maintenance][2022/05/04 04:44:52]] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine
java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@ada7e93] unable to create manager for [D:\Quest\Foglight Agent Manager\state\default\agents\fb8be857-fbcf-4747-973d-295a8570e581\DB_SQL_Server\6.1.0.10*/AGENTNAME (*\EXAMPLE)_sql_pi_statistics.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@1d49dda1[pattern=D:\Quest\Foglight Agent Manager\state\default\agents\fb8be857-fbcf-4747-973d-295a8570e581\DB_SQL_Server\6.1.0.10/AGENTNAME (*\EXAMPLE)_sql_pi_statistics.log-%d{MM-dd-yy}.log.gz, append=true, bufferedIO=true, bufferSize=8192, policy=SizeBasedTriggeringPolicy(size=20971520), strategy=DefaultRolloverStrategy(min=1, max=10, useMax=true), advertiseURI=null, layout=%d{yyyy-MM-dd HH:mm:ss.SSS} %p [%t] - %m%n, filePermissions=null, fileOwner=null]]