0

Hi everybody, After a period of no development in Mendix, I'm now asked to help with a migration from Mendix 2.5.3 to version Mendix 4.4.2. I followed the strategy to first convert/upgrade to the highest major 2 version, then to the highest major 3 version and then to Mendix 4.4.2. All went well, until I first started the project in Mendix 4.4.2. I got an exception (pasted below) when I synchronized the database. Surprisingly, the 2nd time I started the runtime, the exception was gone, but I have the feeling that something has to be done with this exception (I didn't verify this yet). So I tried to look on this forum for similar issues/exceptions, but didn't find them... The most relevant part of the stacktrace seems to be this: ExecutionException: n: In the past, the object 'Export.Xml' derives from the object 'System.FileDocument.This is the case for the following id('s): 10977524091715619, 10977524091715620, 10977524091715622, 10977524091715623, 10977524091715626, 10977524091715628, 10977524091715629, 10977524091715632, 10977524091715635, 10977524091715638, 10977524091715639, 10977524091715640To resolve this issue, change manually the data rows with these id's in all the tables which affect this object type. You can delete these rows or change the text in the column 'submetaobjectname' to the name of a higher existing object type in the deriving sequence. My questions are [3]I didn't digg into the database yet, but to be honest, I don't really know where to start: I see a list of id's... but what tables / what fields have to be changed? Any help is greatly appreciated (good references to similar issues as well) Thanks in advance! Request action: start Message: Starting MxRuntime failed. Cause: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"request":"fs (depth = 0, amount = 500): SELECT ID, FileID, DeleteAfterDownload, submetaobjectname FROM System.FileDocument WHERE (ID & 281474976710655) != FileID","type":"RetrieveOQLDataTableAction"}', all database changes executed by this action were rolled back Stack trace: com.mendix.m2ee.api.AdminException: Starting MxRuntime failed. at com.mendix.core.MxRuntime.C(SourceFile:256) Caused by: com.mendix.core.CoreRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"request":"fs (depth = 0, amount = 500): SELECT ID, FileID, DeleteAfterDownload, submetaobjectname FROM System.FileDocument WHERE (ID & 281474976710655) != FileID","type":"RetrieveOQLDataTableAction"}', all database changes executed by this action were rolled back at hC.b(SourceFile:214) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"request":"fs (depth = 0, amount = 500): SELECT ID, FileID, DeleteAfterDownload, submetaobjectname FROM System.FileDocument WHERE (ID & 281474976710655) != FileID","type":"RetrieveOQLDataTableAction"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.c(SourceFile:515) Caused by: l: An exception has occurred for the following request(s): fs (depth = -1, amount = 500): SELECT ID, FileID, DeleteAfterDownload, submetaobjectname FROM System.FileDocument WHERE (ID & 281474976710655) != FileID at x.a(SourceFile:49) Caused by: l: java.util.concurrent.ExecutionException: n: In the past, the object 'Export.Xml' derives from the object 'System.FileDocument.This is the case for the following id('s): 10977524091715619, 10977524091715620, 10977524091715622, 10977524091715623, 10977524091715626, 10977524091715628, 10977524091715629, 10977524091715632, 10977524091715635, 10977524091715638, 10977524091715639, 10977524091715640To resolve this issue, change manually the data rows with these id's in all the tables which affect this object type. You can delete these rows or change the text in the column 'submetaobjectname' to the name of a higher existing object type in the deriving sequence. at dA.a(SourceFile:370) Caused by: java.util.concurrent.ExecutionException: n: In the past, the object 'Export.Xml' derives from the object 'System.FileDocument.This is the case for the following id('s): 10977524091715619, 10977524091715620, 10977524091715622, 10977524091715623, 10977524091715626, 10977524091715628, 10977524091715629, 10977524091715632, 10977524091715635, 10977524091715638, 10977524091715639, 10977524091715640To resolve this issue, change manually the data rows with these id's in all the tables which affect this object type. You can delete these rows or change the text in the column 'submetaobjectname' to the name of a higher existing object type in the deriving sequence. at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at dA.a(SourceFile:367) at dA.a(SourceFile:319) at dA.a(SourceFile:199) at dA.a(SourceFile:150) at dA.a(SourceFile:83) at dE.a(SourceFile:68) at x.a(SourceFile:43) at h.a(SourceFile:269) at hp.a(SourceFile:89) at hp.executeAction(SourceFile:21) at com.mendix.systemwideinterfaces.core.UserAction.execute(SourceFile:57) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:457) at hC.b(SourceFile:203) at com.mendix.core.Core.retrieveOQLDataTable(SourceFile:1497) at hZ.a(SourceFile:66) at ia.a(SourceFile:15) at com.mendix.core.MxRuntime.D(SourceFile:281) at com.mendix.core.MxRuntime.C(SourceFile:246) at com.mendix.core.MxRuntime.a(SourceFile:228) at com.mendix.core.MxRuntime.b(SourceFile:179) at fP.a(SourceFile:50) at fO.execute(SourceFile:26) at com.mendix.m2ee.server.handler.HttpAdminHandler.handle(HttpAdminHandler.java:132) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) at org.eclipse.jetty.server.Server.handle(Server.java:351) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:890) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:944) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:642) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534) at java.lang.Thread.run(Thread.java:662) Caused by: n: In the past, the object 'Export.Xml' derives from the object 'System.FileDocument.This is the case for the following id('s): 10977524091715619, 10977524091715620, 10977524091715622, 10977524091715623, 10977524091715626, 10977524091715628, 10977524091715629, 10977524091715632, 10977524091715635, 10977524091715638, 10977524091715639, 10977524091715640To resolve this issue, change manually the data rows with these id's in all the tables which affect this object type. You can delete these rows or change the text in the column 'submetaobjectname' to the name of a higher existing object type in the deriving sequence. at dA.a(SourceFile:472) Caused by: com.mendix.core.CoreRuntimeException: 'Export.Xml' is not a valid entity at ik.c(SourceFile:1533) at com.mendix.core.Core.getMetaObject(SourceFile:1798) at p.a(SourceFile:52) at r.b(SourceFile:34) at q.c(SourceFile) at dA.a(SourceFile:445) at dB.a(SourceFile:41) at dB.call(SourceFile:14) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

asked 2013-05-14

1 answers