Can not open some EA repositories with EA 13 after Users tried out EA14

[SBB]

Our company (500 ea users) are working with ea 13 1309. Because of changing to ea 14, we gave 10 users the ea 14 build 1419 Version to make their daily work with this new version. We do the upgrading process always in this sequence - testers are working with the new version for about 2 month - if all is fine, we upgrade to the new version at the very end. We started that with Version 9.
Yesterday, the 10 users started to work with ea 14. Today, i got lot's of messages that users with ea 13 are not able to login to the repositories where these 10 users worked with ea14. It seems that ea14 is doing some changes on the database which causes these problems after for the ea13 version.
We are working on Windows7 and Windows10 64bit, the Repositories are on a mysql Server 5.7.
The error ea13 users get is:

Access to this model requires the following technologies which are not available:
SysML1.1
Togaf
BRM
.....  a list of 25 technics

On another repository,the error is only
Access to this model requires the following technologies which are not available:
Checklists
SysML1.4

....only 2 technics

We are having a big problem now as we can not change all these peoples to version ea14 on the fly.
Opening the repositories with ea14 is no problem at all

Can you help me somehow??
I already made a Sparx support call for registered users.
And i am badly waiting for a reply

Mario Widmer
Schweizerische Bundesbahnen SBB
Bern Switzerland

[Geert Bellekens]

Someone has been messing with the required MDG technology settings it seems.

Check Configure|Model|Options|MDG Technologies and uncheck everything in the "Required" column.

Geert

[SBB]

Thanks a log Geert. You are my hero. That's exactly what happened. After disabling the required checkboxes of these mdt technologies, all is running fine now. I have to find out why these setting has been changed. Obviously that has not happen before because, as i said, we are doing updates in this way since years and i never had such an experience earlier.
Thanks again and all the best for you

Mario Widmer

[qwerty]

Maybe you removed the MDGs in your previous distribution and the new install brought them back. People always click to where the should not.

q.

[steen.jensen]

Yepp, this happend to my work also, when I installed the BABOK MDG, it changed the Required MDG to BABOK in the SQL-based repository for about 25 users with no access. Saved by Geert 

This setting should have its own settings i Security list, but its related to other settings that several users need, bad config by Sparx

[Eve]

This setting should have its own settings i Security list, but its related to other settings that several users need, bad config by Sparx

The permission used is 'Configure Project Prerequisites'. It only allows configuration of the minimum EA version and the required MDG technologies.

[SBB]

That's good to know. In our environment, 'Configure Project Prerequisites'  was enabled for everyone.  I've turned that off now.
Is there somewhere a set of rights that a professional developer or business analyst needs to work trouble-free?
This should including coding, reverse engineering, import/export data etc. But there should be no way to change global settings!
We have a lot of projects divided into 28 repositories. A repository can contain up to 40 projects. The projects are mostly independent and have nothing to do with each other.

We prevent accidental mixing or deletion of data by defining groups and assigning each project to a group. A user get's write access to a project only,  if he is a member of the corresponding group.
For this reason, we do not want a user to globally rename or delete for example stereotypes, therefore we do not give out the permission 'configure stereotypes' to any user.
All settings have been made due to company regulations and must not be changed.

regards
Mario

[charlyprg]

I can't open the project because are not available the technologie BRM. I installed a version 13. Please I need help because the work on my company it's stopped because this issue.

[Paolo F Cantoni]

I can't open the project because are not available the technologie BRM. I installed version 13. Please, I need help because the work at my company it's stopped because of this issue.

Open EA without the project and enable BRM technology.  Then you should be able to make the BRM not active and finally disable it.

If that fails, the problem can be fixed by directly editing the EA DB, but you need to be capable.

Paolo

[qwerty]

FWIW: Running a script to perform

Code: [Select]

repository.execute("DELETE FROM t_genopt WHERE AppliesTo = 'MDGRequire'")will silence that annoying message. I just had that without an idea how it was turned on (there shouldn't be anyone with V14).

q.

P.S. I forgot to mention when that nasty message popped up. I wanted to use a MDG imported in the model. So I did that and removed the path where I created the MDG(s) for testing. As soon as the path was gone, I got that message (however this "required" had been turned on) upon re-opening the model. Restored the path, ran the DELETE from inside EA (else I'd had needed an external client) and removed the path. Now say what: the model opened since those MDGs were actually present. Namely inside the model. Smells like a bug. Not reported (since it's futile).