Import of anything but 'version 1' is problematic

Classic Servoy
1

We are having lots of issues when it comes to importing anything other than the original ‘version 1’ solution.

Example, import of ‘version 2’ of a solution will occassionally fail with some kind of ‘duplicate id’ or ‘item XXX has changed’.
Example, import of ‘version 2’ of a solution works and even runs… but then ultimately fails with the dreaded ‘Internal Error’ screen.

The only solution we have found that works is to burn down the repository and re-install it using the ‘-upgraderepository’ option on the application server, then re-import the solutions — then it works.

Has anyone else run into these types of issues ?? If so, have you found a way to fix it ??

We have run into this trouble ever since version 4.0.x and every beta and release candidate since. We are currently using 4.1.0 rc2

2

The first is as far as i can guess now is really a duplicate uuid export (so the export file is already corrupt somehow, its not the import that goes wrong)
Currently we have those checks in place and you shouldnt be able to export a solution that has those errors.

your second example has nothing to do with importing, that is just a completely different error which can be caused by many things.
And you should check in your logs what those are telling you.

3

The logs don’t mean much to be because they are filled with what look like java error messages and I can’t make any sense of what they are trying to tell me.
I’ve zipped up the logs and forwarded to our Servoy rep.