SUMMARY
Dec 02, 2016
To further investigate your issue, it is helpful if the Support team is provided with the debug log for your agent. This will log information on objectives that are targeted and for Epilog, any filename and new log records it has detected.
Snare Agent for Windows
Start a command prompt on the machine where Snare is installed, as Administrator and change directory to your Snare installation (e.g. c:\Program Files\Snare).
Execute the following:
...
| Code Block |
|---|
> net start snare |
Snare Epilog for Windows
Start a command prompt on the machine where Epilog is installed, as Administrator and change directory to your Epilog installation (e.g. c:\Program Files\Epilog).
Execute the following:
...
| Code Block |
|---|
> net start epilog |
Snare Agent for MSSQL
Start a command prompt on the machine where Snare MSSQL is installed, as Administrator and change directory to your Snare MSSQL installation (e.g. c:\Program Files\SnareMSSQL).
Execute the following:
...
| Code Block |
|---|
> net start snaremssql |
Snare Agent Manager (SAM)
Again start an admin cmd prompt on the system. Stop the existing SAM service then run the in debug mode from the command line. Be sure to cd to the install folder being C:\Program Files\Intersect Alliance\Snare Agent Manager
| Code Block |
|---|
> net stop snaream.exe
> snareAM.exe -c -d9 > 2>&1 my-samdebug.log
> net start snaream.exe |