Message says: An error occured, but where?

0
After upgrading a project from Mendix 5.4.1 to version 5.6.2, I get an error every single time after I have logged in. The error is a standard error message in a red dialog box, saying: " Error: An error occured, please contact your system administrator. " Apart from this error, the login process is successful: the homeform for the user is shown and the application can be used without further issues. Unfortunately I don't have a single clue where this error is coming from. The console does not mention any error. Even when I set the log levels to "Trace" for every log node, I still do not see an error appear in the console. Does anyone have a clue where this error might be coming from? It is driving me nuts...
asked
5 answers
1

That's quite odd. Can you use firebug to see if the client actually receives the error from the server or throws it by itself? The latter would indicate it might be a custom widget error. If that doesn't help you, is it easy to reproduce in a stripped-down version of your project? Then you can file a ticket.

answered
1

I've seen this error happen in projects where certain widgets weren't properly compatible with Mendix 5. Are you sure you upgraded all your widgets to the latest versions available in the appstore, and that you checked whether those latest versions are specified to be compatible with Mendix 5?

*Edit for clarity: Yes, I see that you were already using Mx 5, but the previous time I saw this was also after an upgrade to Mx 5.6.

answered
0

Well, I have updated every widget and deleted a bunch of widgets I did not use. Unfortunately the error is still there. :-(

The only piece of extra information that I have is that the error text appears in the JSON data that is returned by the POST to /xas/

This is the node where the error can be found, including the nodes before it and below it. Maybe this will give someone a clue here what might be wrong in my project.

 "reporting":{  
    "widget":{  
      "ReportParameter":{  
        "less_than":"Less than {1}",
        "from_to":"From {1} to {2}",
        "all":"All",
        "greater_than":"Greater than {1}"
      },
      "ReportMatrix":{  
        "excel_btn_caption":"Export to Excel"
      }
    }
  },
  "mobile":{  
    "sys":{  
      "UI":{  
        "connection_error":"A connection error occurred, please try again later.",
        "loading":"Loading...",
        "internal_error":"An error occured, please contact your system administrator."
      }
    },
    "widget":{  
      "ReferenceSelector":{  
        "clean_confirmation":"Are you sure you want to clear this reference?"
      },
      "DataView":{  
        "validation_error":"One or more input fields contain an invalid value."
      },
      "Dialog":{  
        "ok":"Okay"
      },
      "ListView":{  
        "no_items":"No items found",
        "search":"Search",
        "load_more":"Load more..."
      },
      "Progress":{  
        "progress_title":"Progress",
        "hide":"Hide"
      }
    }
answered
0

When I was creating a testproject I finally stumbled upon the widget that caused the problem. I guess I had overlooked this one during my investigation... :-(

The widget that causes the error is the Tooltip Trigger widget from the App Store. I filed a ticket for this widget already a couple of months ago because I experienced issues with this widget earlier when we started converting our Mendix 4 project Mendix 5. I added this issue to the existing ticket instead of creating a brand new one.

The ticket number is #100705.

answered
0

After receiving an update of the Tooltip Trigger widget from Mendix Support, I was still suffering from the red error dialog stating "Error: An error occured, please contact your system administrator".

So again I copied my project to a new folder and started to update and delete widgets one by one from my project to see which one was causing the problem. After a number of hours I finally found the widget that was causing the error: the Mobile Login widget.

Time to fire up the Mendix Support website later today and file a ticket I guess. :)

answered