Startup issue after Migration Data Problem (The current id belongs to another object type)
0
The Mendix project does not startup after migration form version 4 to 5 (Tested to 5.4.1 and 5.9.1) The current id belongs to another object type Creating a new DataBase will not result in this error, is happens to my current db. On a retry of the import and conversion we got a similar error but with different tables. Does anybody seen these error below and could tell me what is going on or how to solve it? Thank you Andries Smit Request action: start Message: Starting Mendix Runtime failed. Cause: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.Language"}', all database changes executed by this action were rolled back Stack trace: com.mendix.m2ee.api.AdminException: Starting Mendix Runtime failed. at com.mendix.core.impl.MxRuntimeImpl.fireZeeMissile(SourceFile:430) Caused by: com.mendix.core.CoreRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.Language"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.ActionManager.executeSync(SourceFile:216) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.Language"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.processErrorState(SourceFile:342) Caused by: java.lang.IllegalArgumentException: The current id belongs to another object type than the given type to set. Type of this MendixObject is 'System.Language', the given id is of type 'AdvEmail.EmailSettings' at com.mendix.core.objectmanagement.MendixObjectImpl.setId(SourceFile:357) at com.mendix.core.objectmanagement.SchemeManagerImpl.getInstance(SourceFile:969) at com.mendix.core.action.user.RetrieveXPathAction.executeAction(SourceFile:58) at com.mendix.core.action.user.RetrieveXPathAction.executeAction(SourceFile:17) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:53) at com.mendix.core.actionmanagement.CoreAction.doCall(SourceFile:291) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:276) at com.mendix.core.actionmanagement.CustomActionMonitorImpl$$anonfun$run$1.apply(SourceFile:17) at com.mendix.core.session.Worker$$anonfun$receive$3$$anonfun$2.apply(SourceFile:148) at scala.util.Try$.apply(Try.scala:161) at com.mendix.core.session.Worker$$anonfun$receive$3.applyOrElse(SourceFile:146) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:498) at akka.actor.ActorCell.invoke(ActorCell.scala:456) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:237) at akka.dispatch.Mailbox.run(Mailbox.scala:219) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:386) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) AND com.mendix.m2ee.api.AdminException: Starting Mendix Runtime failed. at com.mendix.core.impl.MxRuntimeImpl.fireZeeMissile(SourceFile:436) Caused by: com.mendix.core.CoreRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.UserRole"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.ActionManager.executeSync(SourceFile:210) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.UserRole"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.processErrorState(SourceFile:343) Caused by: java.lang.IllegalArgumentException: The current id belongs to another object type than the given type to set. Type of this MendixObject is 'System.UserRole', the given id is of type 'System.TimeZone' at com.mendix.core.objectmanagement.MendixObjectImpl.setId(SourceFile:357) at com.mendix.core.objectmanagement.SchemeManagerImpl.getInstance(SourceFile:968) at com.mendix.core.action.user.RetrieveXPathAction.executeAction(SourceFile:58) at com.mendix.core.action.user.RetrieveXPathAction.executeAction(SourceFile:17) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:53) at com.mendix.core.actionmanagement.CoreAction.doCall(SourceFile:291) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:276) at com.mendix.core.actionmanagement.CustomActionMonitorImpl$$anonfun$run$1.apply(SourceFile:17) at com.mendix.core.session.Worker$$anonfun$receive$3$$anonfun$2$$anon$1.execute(SourceFile:158) at com.mendix.util.classloading.Runner.doRunUsingClassLoaderOf(SourceFile:36) at com.mendix.core.session.Worker$$anonfun$receive$3$$anonfun$2.apply(SourceFile:160) at scala.util.Try$.apply(Try.scala:191) at com.mendix.core.session.Worker$$anonfun$receive$3.applyOrElse(SourceFile:154) at akka.actor.Actor$class.aroundReceive(Actor.scala:465) at com.mendix.core.session.Worker.aroundReceive(SourceFile:147) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) at akka.actor.ActorCell.invoke(ActorCell.scala:487) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238) at akka.dispatch.Mailbox.run(Mailbox.scala:220) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
asked
Andries Smit
1 answers
0
You can try to fix that in the database, however it should not happen. Did you change inheritance and replaced a generic entity with a new entity with the same name as the deleted one?