Login fails, Http-response 560, logmessage Ids should not be null

0
Every now and then, it is no longer possible to log in to my Mendix app with correct uid+pwd. Even with MxAdmin and a freshly changed password. Result is always: In the web-browser, this log message is shown in the console:   In the log these message are shown: 10:29:55 AMappERRORConnector: An error has occurred while handling the request. 10:29:55 AMappcom.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"type":"LoginAction","user":"myUsername"}', all database changes executed by this action were rolled back 10:29:55 AMappat com.mendix.basis.actionmanagement.ActionManager.executeSync(ActionManager.scala:117) 10:29:55 AMappCaused by: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"type":"LoginAction","user":"myUsername"}', all database changes executed by this action were rolled back 10:29:55 AMappat com.mendix.util.classloading.Runner$.withContextClassLoader(Runner.scala:23) 10:29:55 AMappCaused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"type":"LoginAction","user":"myUsername"}', all database changes executed by this action were rolled back 10:29:55 AMappat com.mendix.basis.actionmanagement.CoreActionHandlerImpl.processErrorState(CoreActionHandlerImpl.scala:153) 10:29:55 AMappCaused by: java.lang.IllegalArgumentException: requirement failed: Ids should not be null The text "Ids should not be null" is nowhere in the Mendix source-code.   Restarting the application does not help, but I (luckily) can resolve the incident by doing a redeploy of a different package. Login is possible again for a while. A couple of days or weeks later, the login-issue is back again.   Got my app currently in Mx 10.15.0, but this has been going on for a while, since 10.6.0. At one point I thought I got it solved by removing the SAML module, but it is still happening.   Any ideas on how to solve this? Or even just how to get more information on this error?
asked
1 answers
0

Hi Tim,

 

I have another error that I could also solve only by redeployment. 

 

Try logging on using an Incognito Window. If that works, clear the cache in the browser <Ctrl> + <F5>

 

Go Make It

answered