• 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

    Fresh install - problems with m2m2-start.bat

    User help
    2
    14
    6.0k
    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.
    • K
      Koen
      last edited by

      Hi guys,

      I just downloaded tried installing Mango Automation on a new Windows machine. First I installed Java SE Development Kit 6 version 35. Then I downloaded the Mango zip file, and unzipped it to a new folder in the 'program files'.

      When I start 'm2m2-start.bat' in the command window, I get a number of fault messages, and I don't get a page up on http://localhost:8080

      Any help?

      Koen

      Attachment: download link

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

        Hi Koen,

        For now, can you try removing the spaces in your path and try again?

        Best regards,
        Matthew

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

          Actually, that may not be it. Can you check your Java path. Currently it's pointing to "C:\Program Files\Java\jre6...". I believe it should point to something like "C:\Program Files\Java\jdk1.6.0_xx...". You may need to add a JAVA_HOME env var to set this. It should be set to "C:\Program Files\Java\jdk1.6.0_xx" where "xx" is the micro version of Java you have installed.

          Best regards,
          Matthew

          1 Reply Last reply Reply Quote 0
          • K
            Koen
            last edited by

            Thanks for you quick help,

            I entered the JAVA_HOME env var through the Control Panel -> System etc...

            Then I ran the startup script again, it made a difference, but now I have a different problem it seems. See screenshot.

            Attachment: download link

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

              Weird, i just downloaded the core now, ran the bat file and it worked fine. At line 35 in the bat file there is the line "rem echo %M2M2_CP%". Can you remove the "rem" part so that it writes the classpath it is starting with?

              Best regards,
              Matthew

              1 Reply Last reply Reply Quote 0
              • K
                Koen
                last edited by

                Hi Matthew,

                I did as you asked, see attached screenshot.

                Koen

                Attachment: download link

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

                  What version of Windows are you using?

                  Best regards,
                  Matthew

                  1 Reply Last reply Reply Quote 0
                  • K
                    Koen
                    last edited by

                    Windows 7

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

                      Hmm. Can you try the following commands in a command prompt? Check if the results you get are different from mine.

                      
                      C:\Users\Matthew>setlocal
                      
                      C:\Users\Matthew>for
                      The syntax of the command is incorrect.
                      
                      C:\Users\Matthew>
                      

                      Best regards,
                      Matthew

                      1 Reply Last reply Reply Quote 0
                      • K
                        Koen
                        last edited by

                        Hi Matthew,

                        I get the same.

                        Koen

                        Attachment: download link

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

                          Ha! Now it is a problem with spaces in your path. We'll look into a fix for this, but can you try removing the spaces?

                          Best regards,
                          Matthew

                          1 Reply Last reply Reply Quote 0
                          • K
                            Koen
                            last edited by

                            Hi Matthew,

                            I think you nailed it. It started up now.

                            So in short:

                            1. Make sure you set an env var for JAVA_HOME
                            2. Make sure Mango is installed in a directory without spaces in its path.

                            Maybe best to put that in the readme file or so, for future users?

                            Thanks heaps for your help!

                            How come I don't have to install Apache Tomcat for Mango Automation?

                            Koen

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

                              Well, we'll look into fixing the script so that spaces aren't an issue, but it seems like 1. may be necessary, yes.

                              Rather than having MA run within Tomcat, we switched things around so that the web server (Jetty) runs within MA.

                              Best regards,
                              Matthew

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