Customer Support? TRIGGERcmdAgent keeps stopping

[Frank Malczewski]

@Russ Hi Russ. Yes, we did that a while back.
This is under the AntiVirus scan section. Is there another area to look as well?

[Russ]

@Frank-Malczewski , thanks for showing me the config.

Yes, please try excluding the whole C:\Users\Home\AppData\Local\TRIGGERcmdAgent folder. I suspect Norton is blocking something in there besides the .exe.

[Frank Malczewski]

@Russ OK. I just made that change. Lets see if the recent changes helps. I'll be in touch...

[Frank Malczewski]

@Russ Hi Russ. Well, its been a couple of months without any issues UNTIL yesterday, when I noticed I couldn't trigger any lights and checked my server to find:
If you remember, I set it up to restart every week on Sunday.

I also saw that multiple (3) TRIGGERcmdAGents were showing in the system tray. I had to acknowledge the error and manually restart it.
Was wondering if you had any other users seeing this happen since spring.

Thanks

Frank

[Russ]

@Frank-Malczewski, no, I don't know of anyone else who's had that error yet.

When I googled for that error I saw multiple suggestions to use this command:

sfc /scannow

It might be worth a try.

I've seen that issue with multiple TRIGGERcmd tray icons - that's from killing the agent and re-running it. When you hover over the icon for one of the processes that was already killed, the icon disappears.

[Frank Malczewski]

@Russ Use that command where? In the scheduled task?

UPDATE - never mind - you meant to run it from a CMD prompt

[Frank Malczewski]

@Russ results:

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\windows\system32>

[Frank Malczewski]

@Russ Will see if that helped. Thanks.

[Frank Malczewski]

@Russ Well, for some odd reason Triggercmd stopped today and I found the following error message which was nothing like the previous failures:

Might this have been a fluke with Triggercmd stopping or is it related?

I also think I am going to increase my task scheduler (to stop and restart TRIGGERcmd) to run every day instead of once per week...

[Russ]

@Frank-Malczewski, that one is for a different process, so probably not related to the triggercmd agent.

[Frank Malczewski]

@Russ OK. Thanks. As previously mentioned, I am now running that script nightly. Hopefully, even if I get a failure it will be short-lived.

[Frank Malczewski]

@Russ Just an update - I have not 'noticed' TRIGGERcmd failing since I started running the script daily. I do occasionally see multiple icons in the system tray that vanish if I hover over them - not sure if they stay after I run the script or if TRIGGERcmd crashed, then my script ran within that 24 hr window and started TRIGGERcmd back up but whichever it is, it has not been an inconvenience .

Thanks.

[Russ]

@Frank-Malczewski, thanks for letting me know. Sorry that's necessary but I'm glad it's working for you. I've seen those extra tray icons before - the icon doesn't get removed when you kill the agent without using the Quit function.