Sparx EA 14 Crashes when opening a file from a shared drive

[Space_Fan]

Hi everyone.

I've got a question that, hopefully, has an easy answer.

I've recently moved an EAP file onto a locally shared networked drive. When I go to open the EAP on that drive, the file opens and I can view the file structure in the Project Browser, but when I go to view one of the architectural viewpoints, EA acts like it's going to open the file, but then eventually Windows throws an error to either close the program or to let it keep working on opening it.

We have plenty of other EAP files on this same share drive and they operate as expected.

Also, the file opens and functions just fine when it's stored locally on that same machine.

Something that might be confounding factors:
The file was created in EA v. 13 and I'm moving it to a system that uses EA v. 14


Any suggestions on this would be greatly appreciated.

[Aaron B]

Just as a test - What happens if the model file is copied to your local machine first and opened from there? Are you able to browse the entire model from there without issues?

My general advice would be to avoid accessing EAP files over a network drive where possible. Depending on various factors such as the speed and reliability of the network connection, and the size/complexity of the file, there is a risk of corrupting the model file.

If you have a shared model which multiple users need to access and work on then you are better to configure a server based repository, or use Pro Cloud Server.
https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_repository/settingupdatabasemodelfile.html
https://sparxsystems.com/enterprise_architect_user_guide/15.2/model_repository/connect_to_the_cloud.html

[Space_Fan]

Thank you for your help!

Just as a test - What happens if the model file is copied to your local machine first and opened from there? Are you able to browse the entire model from there without issues?

I'm able to open, navigate, and edit the file when it's sitting on my desktop without any problems.

My general advice would be to avoid accessing EAP files over a network drive where possible. Depending on various factors such as the speed and reliability of the network connection, and the size/complexity of the file, there is a risk of corrupting the model file.

This might be the issue. The network is sometimes questionable, and the file I'm working with is bigger than any of the other architecture files we've got. We may not be able to set up a server, but I'll start bringing the idea up in meetings to see if I can get any buy in.

In the meantime, I'll just keep working off of a local version, and just move the required parts into the other files as needed.

[qwerty]

EAP == MSAccess. MSAccess is not meant to work over a network (just google for it). Consider using a real DB like SQL Server, MySQL or the like. Avoid Oracle for EA, though.

q.