Typo in error from application An error occured, please contact your system administrator.

0
Has anyone else seen this?  After clicking a button on my application I am presented with a dialog box showing "An error occured, please contact your system administrator."  If I monitor the live log no errors are logged. If I press Ctrl-F5 to reload the page it loads fine.  If I load the application in a guest/incognito window I am not presented with this error.  The error message has the word occurred misspelled.      After clearing browser cache it goes away for a while but eventually comes back.   Thoughts?
asked
5 answers
1

It's usually a Chrome extension that messes up the login flow, see this thread. For me the solution was to disable Lastpass.

answered
2

While disabling extensions could help, the best way to resolve it would be to upgrade to Studio Pro 9.24.4 (or higher) (or Mx10). From the release notes:

  • We fixed an issue where Chrome extensions crashed the client. (Tickets 180229, 180230, 180385, 180405, 180450, 180472, 183144)
answered
0

If you are not seeing anything in the Mendix logs, take a look in your web browser's console. It sounds like it could be a client error, so there should be an error message there.

 

Good luck!

answered
0

Good call.

I see in the browser log the following 2 messages:

 

1. [Client] TypeError: Cannot read properties of null (reading 'insertBefore')    at p.injectUrl (mxui.js?638425169452879949:5:13303)    at He (mxui.js?638425169452879949:5:11631)    at l (mxui.js?638425169452879949:5:466)    at mxui.js?638425169452879949:5:5146    at Fe (mxui.js?638425169452879949:5:9702)    at se (mxui.js?638425169452879949:5:5131)    at ce (mxui.js?638425169452879949:5:5484)    at p (mxui.js?638425169452879949:5:651)    at mxui.js?638425169452879949:5:303937    at mxui.js?638425169452879949:5:303983(anonymous) @ mxui.js?638425169452879949:64(anonymous) @ mxui.js?638425169452879949:64processLog @ mxui.js?638425169452879949:64error @ mxui.js?638425169452879949:64(anonymous) @ mxui.js?638425169452879949:5setTimeout (async)t.showError @ mxui.js?638425169452879949:5o @ mxui.js?638425169452879949:66window.mx.onError @ mxui.js?638425169452879949:5startup @ mxui.js?638425169452879949:5await in startup (async)7337 @ mxui.js?638425169452879949:5I @ mxui.js?638425169452879949:66(anonymous) @ mxui.js?638425169452879949:66(anonymous) @ mxui.js?638425169452879949:66(anonymous) @ mxui.js?638425169452879949:5Ie @ mxui.js?638425169452879949:5(anonymous) @ mxui.js?638425169452879949:5Fe @ mxui.js?638425169452879949:5$e @ mxui.js?638425169452879949:5ce @ mxui.js?638425169452879949:5p @ mxui.js?638425169452879949:5(anonymous) @ mxui.js?638425169452879949:5crsp.santacruzca.gov/:1

2. Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received

 

My initial research points to the browser trying to access an element before the document is fully loaded.  Is this preventable or is there something else that might be going on that caused this recently?

answered
0

This issue has raised it's ugly head again.  It turns out the typo in the message is a result of system texts for client side error.  It turns out the error is due to a depreciated widget.

answered