• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Customer Support? TRIGGERcmdAgent keeps stopping

General Discussion
2
30
2.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    Frank Malczewski @Russ
    last edited by Sep 5, 2023, 7:43 PM

    @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: 68245a65-975b-4b72-a531-56a31c084510-image.png
    If you remember, I set it up to restart every week on Sunday.
    95addac3-06dd-4e1b-b51c-b3fa45065408-image.png

    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

    R 1 Reply Last reply Sep 5, 2023, 9:16 PM Reply Quote 0
    • R
      Russ @Frank Malczewski
      last edited by Sep 5, 2023, 9:16 PM

      @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.

      Russell VanderMey

      F 4 Replies Last reply Sep 6, 2023, 12:35 AM Reply Quote 0
      • F
        Frank Malczewski @Russ
        last edited by Frank Malczewski Sep 6, 2023, 12:38 AM Sep 6, 2023, 12:35 AM

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

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

        1 Reply Last reply Reply Quote 0
        • F
          Frank Malczewski @Russ
          last edited by Sep 6, 2023, 12:41 AM

          @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>

          1 Reply Last reply Reply Quote 0
          • F
            Frank Malczewski @Russ
            last edited by Sep 6, 2023, 1:02 AM

            @Russ Will see if that helped. Thanks.

            1 Reply Last reply Reply Quote 0
            • F
              Frank Malczewski @Russ
              last edited by Sep 7, 2023, 7:27 PM

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

              dfea67c8-e07a-4b7b-b344-c8fd957ed4c3-image.png

              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...

              R 1 Reply Last reply Sep 7, 2023, 7:59 PM Reply Quote 0
              • R
                Russ @Frank Malczewski
                last edited by Sep 7, 2023, 7:59 PM

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

                Russell VanderMey

                F 1 Reply Last reply Sep 10, 2023, 1:23 AM Reply Quote 0
                • F
                  Frank Malczewski @Russ
                  last edited by Sep 10, 2023, 1:23 AM

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • F
                    Frank Malczewski
                    last edited by Oct 27, 2023, 9:46 PM

                    @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 inconvenience2023-10-27 17_40_37-Server - AnyDesk.jpg .

                    Thanks.

                    R 1 Reply Last reply Oct 27, 2023, 10:21 PM Reply Quote 0
                    • R
                      Russ @Frank Malczewski
                      last edited by Oct 27, 2023, 10:21 PM

                      @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.

                      Russell VanderMey

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post