The detect EXEC command is stopping the detect service in VigilEnt Security Agent for Windows. (NETIQKB31692)

fact
VigilEnt Security Agent for Windows 3.x

symptom
The detect EXEC command is stopping the detect service in VigilEnt Security Agent for Windows.

cause
Once the Detect Service issues the EXEC command, the service does not execute additional EXEC commands or take additional actions until that command exits. If the EXEC command does not exit, the Detect Service will not read from the log that triggered the EXEC command. The Detect Service continues to process events from other Event Logs and respond to them.


fix

To determine whether the command has halted the Detect Service:

1. Check the command in the Task Manager.
2. In the Task Manager, find the processes tab, and look for the command name followed by a CPU value of 00. The Value "00" indicates that the command is idle.
3. The incomplete EXEC command can be ended by either using the End Task button on the Task Manager, or click the Save option in the Detect Service Configuration utility.
• The End Task button stops the invocation of the EXEC command and restores the Detect Service to full operation.
• The Save option in the File menu in the Detect Service Configuration utility stops all threads monitoring the individual events logs, then restarts the threads.

This restores the monitoring of all the logs.

Formerly known as NETIQKB31692