• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    M2M2 install problem

    Mango Automation general Discussion
    2
    4
    3.6k
    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.
    • J
      jjd124
      last edited by

      I had the latest core and the latest watchlist module running OK then I tried to load the Graphics module and I get the messages below.
      this is on a Mac OS X 10.6.
      can you point me in the right direction to resolve this. Thank You

      Bootstrap: 34 jar files loaded
      Exception in thread "main" java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at com.serotonin.m2m2.bootstrap.Main.main(Main.java:33)
      Caused by: java.lang.RuntimeException: Error loading module properties file
      at com.serotonin.m2m2.Main.getProperties(Main.java:462)
      at com.serotonin.m2m2.Main.getProperties(Main.java:407)
      at com.serotonin.m2m2.Main.openZipFiles(Main.java:112)
      at com.serotonin.m2m2.Main.main(Main.java:69)
      ... 5 more

      [Process completed]

      1 Reply Last reply Reply Quote 0
      • M
        mlohbihler
        last edited by

        You need to ensure that the core version of the module is compatible with the core that you are using. If you are using core 1.x, you need to choose modules listed as "1.x - #.#.#". We will be improving the messaging for this issue in upcoming versions of the core.

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • J
          jjd124
          last edited by

          OK, Thanks, I loaded the compatible module's and all is well, Thank You for your timely reply.

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