• 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

    A server error has occurred

    User help
    2
    3
    2.5k
    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.
    • P
      Pedro
      last edited by

      I often see the message 'A server error has occurred' appear in a pop-up window.A server error has occurred.png Most often it pops up when I click on a link that takes me to another Mango page, but sometimes it occurs on its own, when I have not done anything on the page. Most often I see it on a graphics page, but that's probably because that's the page I have open most often.

      When I check ma.log, I don't see any log entries at all around the times these errors occur. Since I'm on a slow ISP with high latency, I suspect it is a dojo timeout error, or a catch-all javascript error. Could it be caused when the socket closes? Can we please get more clarity as to the possible causes of these errors, or increase the timeout if that is the cause? Ideally, if this is a "no response received" issue, then the message should report "no response" rather than blaming the server.

      I often get on the data_point_edit.shtm page and the events.shtm page, but that is not in a pop-up window, and looks quite different:Server error Timeout.png

      Thanks for your help.

      1 Reply Last reply Reply Quote 0
      • jeremyhJ
        jeremyh
        last edited by

        I get this error a lot when a system has generated a large number of alarms (thousands). Purging the alarms stops the error. You can delete all the events at once by entering:

        delete from events
        

        in the SQL console.

        1 Reply Last reply Reply Quote 0
        • P
          Pedro
          last edited by

          Which error do you get a lot? the Timeout error? Does it make a difference if the alarms are acknowledged, or do they have to be purged?

          Do you ever get the 'A server error has occurred' pop-up dialog?

          Thanks.

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