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

    Can't enter token

    General Discussion
    3
    3
    432
    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.
    • D
      dennism
      last edited by dennism

      Whenever I enter my token in the tokenfield, it gives me a JS-ENOENT error as seen here. After that, everytime I open the program the same error appears. Re-installing doesn't remove it, but removing the .TRIGGERcmdData folder in my user folder does fix it.

      EDIT: Didn't really make it clear in the post, but my issue was solved when I deleted the .TIGGERcmdData folder and restarted the agent. Just a bug report

      D RussR 2 Replies Last reply Reply Quote 0
      • D
        dennism @dennism
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • RussR
          Russ @dennism
          last edited by Russ

          @dennism, thank you for reporting it. I confirmed this was a bug with version 20 of the Windows client. I pulled it off the site so the the link goes to version 19 again.

          I thought at first that this was just an Avast issue because I get this issue even with version 19 if I've got Avast installed. The workaround for Avast users is to temporarily disable it during the TRIGGERcmd agent install.

          EDIT: I created a new version (v21) that fixed the bug and includes v20's new feature for sending a command's result to the Runs list.

          Sorry for the bug, and thanks again for reporting it.

          Russell VanderMey

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