Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: nilspc on September 05, 2022, 07:32:17 pm
-
Hi,
We have upgraded to v16.0.1604 64 bits which no longer supports eapx files.
Tried to migrate eapx files to qeax files but the qeax repository becomes more or less corrupt. It is possible to open but takas a long time to open and running to project integrity gives a lot of errors. After correcting the errors the diagrams are missing information.
Anyone have the same problem and solved this?
/Nils
-
How did you migrate? Did you export XMI from eapx then import into qeax?
I download the trial version, set it to ultimate, then do a model database transformation using ultimate (in my case: feap to qea because I wouldn't touch Access with a 10 foot pole). No problems and very fast for me.
-
I used the built-in migration option in v16 because I discovered this after upgrading to v16 and I have eapx I want to continue using
/N
-
Think I found the root cause of the problem.
migrate eapx files to qeax files seems to do en xml export and xlm import.
There appears to be en illegal character (for XML) somewhere in my repository that corrupts the xml and seems to have a lot of side effect. A lot of objects are not imported in the target.
Solved it by doing a xml export from v15 and xml import in v16. In this case the xml export seems to remove the illegal characters so that the xml import works
Needed to install Sparx EA 15 on a separate computer..........
/Nils
-
Send a bug report. Maybe, eventually, perhaps it might be fixed in a future release...
q.
-
upgrade to build 1605
-
Think I found the root cause of the problem.
migrate eapx files to qeax files seems to do en xml export and xlm import.
There appears to be en illegal character (for XML) somewhere in my repository that corrupts the xml and seems to have a lot of side effect. A lot of objects are not imported in the target.
Solved it by doing a xml export from v15 and xml import in v16. In this case the xml export seems to remove the illegal characters so that the xml import works
Needed to install Sparx EA 15 on a separate computer..........
/Nils
Have you tried to open the XMI file with a text editor to delete all characters that are not 'non-extended' ascii?
For example if you have some comments, object names etc. pasted from Windows / Microsoft apps there could be some nonprinting characters and other garbage that throws off the XMI import in EA16.
In the past I have success using Notepad++ to open the XMI file and do a global replace with regex , something like
[^\x09\x0A\x0D\x20-\uD7FF\uE000-\uFFFD\u10000-\u10FFFF]
Or you could paste into MS Excel and run an Excel CLEAN function. May be worth a shot on a backup copy of the XMI file!