Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: kjourdan on May 26, 2016, 08:55:30 pm
-
For the 2nd time, I am unable to import and enable an MDG technology file. After import, the file is listed it can not be enabled. The last time this happened, I had to completely remove EA (uninstall, remove registry entries, remove roaming, etc...). I would rather not do this because I lose all preferences, etc.
Anyone else have this happen and have an idea on how to fix without completely re-installing? Thanks.
-
this has happened to me before when I had the same MDG both from file as imported in the model.
Geert
-
MDG file is always imported into model (not to user). The MDG file is generated from a separate EA model. Removal of the MDG and reinstall does not work unfortunately. Checking out an older version of the model (which had the MDG imported and functional) results in the MDG being disabled still.
The model can be opened by others and clearly shows that the MDG technology file was imported; I am unable to activate it though. This means this issue follows the user.
-
First thing to do is open the Technology settings dialog. If your technology appears in that dialog more than once, that's not good. Select the technology in the left-hand pane and look in the upper right pane to see the "Location" and that should give you a clue as to where you need to look to get rid of one of them. Click the "Advanced" button and see if you have a path to the folder where you were developing the technology - if so, remove it.
Another idea is rather than delete all your registry settings, just search the registry for MDG_TECHNOLOGY_STATUS. That key lists the enabled/disabled status of every technology. If yours appears in that list twice then that's probably not good either. Just edit or clear the key.
-
Thanks for the help! Finally got to the bottom of it. The ID being used for the MDG was set "1". Using 1 as the MDG ID leads to unusual behavior. When all technologies are enabled, the registry entry is removed and the problem goes away. After disabling technology files I did not use, I found 1=0 in the registry key and my MDG was disabled. Hitting enable would update the key with a 1=1 entry but the technology would still be disabled.
I regenerated the MDG with a string for the ID and removed the bogus entry in the key and now the MDG is working as expected. It can be enabled/disabled without issue. Enabling/disabling other MDG technologies does not disable mine.
Thanks again.
-
Feedback from Sparx:
This behavior occurs when you have a conflict in the MDG Technology ID of any of the MDG Technologies listed in the "Extensions | MDG Technologies" dialog.
EA's does not include any MDG Technologies with the ID "1". In this case it appears the issue is also occurring where your ID matches only part of an existing Technology ID (e.g. "1" conflicts with "BPMN 1.1"). We will fix this, so that where there is a partial match in ID the conflict does not occur (Reference Number: 16053868).
Ideally, EA will also return an error/warning where duplicate MDG Technology ID's are found. We have logged this as a bug to be fixed (Reference Number: 14037317).
Currently, as you already discovered, you should be able to avoid issues by ensuring you use unique MDG Technology ID's.