• 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

    [SOLVED] Daily Report didn't run today and has this error

    User help
    3
    26
    13.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.
    • JoelHaggarJ
      JoelHaggar
      last edited by

      It looks like something is wrong in the database. When you deleted the module did you use the Mark for Deletion button on the modules page and then restarted Mango? This should remove the old table. You can then put the latest reports module back in the modules folder and restart again. After the first restart you can use the SQL console to check and make sure the reports table is removed.

      1 Reply Last reply Reply Quote 0
      • danD
        dan
        last edited by

        Gidday.. yeh I used the mark for deletion button and it greyed out the whole reports module in red. Then I hit restart this instance button..

        1 Reply Last reply Reply Quote 0
        • JoelHaggarJ
          JoelHaggar
          last edited by

          Hi Dan,

          I'm not sure what to say at this point. Probably best to get on a remote support session. Contact me tomorrow as early as you can if possible.

          Joel.

          1 Reply Last reply Reply Quote 0
          • danD
            dan
            last edited by

            Attached the output of the show tables command..

            I can't see a reports table in there now that I've deleted the reports module.

            If I was to delete the whole instance of Mango, if I backed up the config script, does that take all the scripts and data points with that?
            Then how do I back the Graphical Overview up? Or would I have to set that one up manually again?

            Cheers
            Dan

            Attachment: download link

            1 Reply Last reply Reply Quote 0
            • JoelHaggarJ
              JoelHaggar
              last edited by

              I don't see any of the reports tables. Is this with the module installed? If not then I think it needs to be installed again. I'm sure you know but just to clarify, to install a module you place the zip file in the modules folder and DON'T unzip it. When mango starts up it will install it the module and create it's needed database tables.

              1 Reply Last reply Reply Quote 0
              • danD
                dan
                last edited by

                yeh sorry mate, this was after I removed it to check that it dropped the table. I'll reinstall now..

                1 Reply Last reply Reply Quote 0
                • danD
                  dan
                  last edited by

                  Yep I got the report tables back:

                  REPORTINSTANCEDATA
                  REPORTINSTANCEDATAANNOTATIONS
                  REPORTINSTANCEEVENTS
                  REPORTINSTANCEPOINTS
                  REPORTINSTANCES
                  REPORTINSTANCEUSERCOMMENTS
                  REPORTS

                  1 Reply Last reply Reply Quote 0
                  • danD
                    dan
                    last edited by

                    still same error :(

                    1 Reply Last reply Reply Quote 0
                    • JoelHaggarJ
                      JoelHaggar
                      last edited by

                      This seems to have been resolved by converting the Derby database to H2. For others interested to know the conversion settings are in the env.properties file and it's really easy to do. H2 is a much better database than derby so we recommend everyone either converts away from Derby to either H2 or MySQL.

                      Thanks,

                      Joel.

                      1 Reply Last reply Reply Quote 0
                      • danD
                        dan
                        last edited by

                        Thanks for your time on this Joel, it's great to get a resolution and have the reports running again.

                        Cheers
                        Dan

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