Navigation

    • Register
    • Login
    • Search
    • Recent
    • Popular

    Service toec crash

    Support
    2
    14
    1560
    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.
    • C
      Cycy last edited by

      Hi
      I still have this Toec service crash problem
      The problem occurs about a week after the customer's installation.
      The OS is Windows 10 Pro FR 1909, 2004, 2009
      I put a console trace in copy
      Thank you
      Log-Toec_client1.2.0.0.txt

      T 1 Reply Last reply Reply Quote 0
      • T
        theopenem_admin @Cycy last edited by

        I'm thinking this probably has something to do with the language. Can you copy the effective policy for this computer and paste it here?

        1 Reply Last reply Reply Quote 0
        • C
          Cycy last edited by

          The computer is in Workgroup
          By copying the result file
          GPReport.txt

          1 Reply Last reply Reply Quote 0
          • T
            theopenem_admin last edited by

            Sorry, I meant the effective policy in Theopenem. If you search active computer and select view on the computer, in the menu you will see effective policy. But anyway, this is definitely related to the policy that monitors active processes, it is also being caused because of the difference in local. Example: U.S. date 12/14/20 is probably 14/12/20 for you, throwing the exception. I'll get a fix for this soon.

            1 Reply Last reply Reply Quote 0
            • C
              Cycy last edited by

              @theopenem_admin said in Service toec crash:

              Sorry, I meant the effective policy in Theopenem. If you search active computer and select view on the computer, in the menu you will see effective policy. But anyway, this is definitely related to the policy that monitors active processes, it is also being caused because of the difference in local. Example: U.S. date 12/14/20 is probably 14/12/20 for you, throwing the exception. I'll get a fix for this soon.

              Yes sorry I didn't understand
              Yes the date format is 14/12/20 for me.
              I attach the Effective Policy
              Effective Policy.txt

              1 Reply Last reply Reply Quote 0
              • T
                theopenem_admin last edited by

                I believe I have this fixed, but I'll need to run some tests. It may be awhile before it makes it into the next release. In the mean time, you should be able to disable the application monitor on your inventory policy to temporarily work around it.

                1 Reply Last reply Reply Quote 0
                • C
                  Cycy last edited by

                  Ok thank you for finding this solution.
                  I'll set it up and monitor and I'll make a return.

                  1 Reply Last reply Reply Quote 0
                  • C
                    Cycy last edited by

                    Bypass works thanks

                    1 Reply Last reply Reply Quote 0
                    • T
                      theopenem_admin last edited by

                      This should be resolved now in 1.3.0

                      1 Reply Last reply Reply Quote 0
                      • C
                        Cycy last edited by

                        I'll test this quickly
                        If I can help with testing or translation into French or other things, please do not hesitate to contact me.
                        thank you

                        1 Reply Last reply Reply Quote 0