Author Topic: Enterprise Architect has experienced a network err (Read 9441 times)

kkilpone · « **on:** May 09, 2006, 12:54:10 pm »

Hello

I have a problem with transfering EAP to DBMS EA will close down with this message "Enterprise Architect has experienced a network error and will close down."

help!!

kkilpone · « **Reply #1 on:** May 09, 2006, 01:01:03 pm »

PS

and when I make some changes to existing data models EA trows this exceptions "

DAO.Recordset[3197]

"The Microsoft Jet database engine stopped the prosess because you and another user are attempting to change the same data at the same time"

What is meanig of this exception.

thomaskilian · « **Reply #2 on:** May 09, 2006, 01:44:26 pm »

Well, I'd take it as it is. You and someone else are working on an EAP file and change data concurrently. Make sure you are working on a local copy of the EAP and noone else can access it that time.

«Midnight» · « **Reply #3 on:** May 09, 2006, 03:38:04 pm »

Which version are you using? EA uses different access rights for the EAP file depending on version. I know that the desktop version locks the file exclusively and the Corporate does not. I think the Professional version works like the corporate, but it could be the other way.

Depending on the version and access rights you might be able to figure this out.

One of the Sparx folks explained this (which version uses what access rights) to me in a recent post, if you want to look.

«Midnight» · « **Reply #4 on:** May 09, 2006, 03:40:44 pm »

BTW, if you are using the automation interface from outside, rather than from an add-in, you might be the "other" user. This can happen if you have the database (the EAP file) open via OLEDB (or whatever) and EA is also using the file.

If this is the case, check the access rights on your 'back' channel. The defaults lock the database in a way that would be antagonistic to EA.

kkilpone · « **Reply #5 on:** May 10, 2006, 11:20:27 am »

Hello

I'am working with a local copy on a local disk and noone is logged on but me. And my version of EA is Corporate.

Midnight! If you have a copy of your explansions, I would be very intrested to read it.

«Midnight» · « **Reply #6 on:** May 10, 2006, 11:34:30 am »

Of course now I can't find it.

In the meantime, take a look at this post:http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1145906931;start=3#3

Here, using the corporate edition, you connect to your EAP file as if it were a repository. At the same time you choose to be the exclusive user. This might convince Access - at least for the current session - that you actually own the file. Conversely, if Access (or Windows) has convinced itself that there is a phantom user sharing the file (unlikely but not unheard of), you will probably get an error message when you try to open exclusively. Either way you have some useful information.

Take a try and tell us if the problem goes away (even temporarily). This is obviously not a real solution but at least it should get you back in the game.

If you are trying to open the model throught the automation interface, try this anyway, and take note of the connecction string. Use the same string when you call Repository.OpenFile().

BTW, please confirm that you are using OpenFile() rather than OpenFile2(). I have no idea whether this would make a difference, but have no experience with OpenFile2().

David

thomaskilian · « **Reply #7 on:** May 11, 2006, 02:20:15 am »

You also should try to open the EAP with MS-tools (like Import External Data from Excel via ODBC or with MSQRY32 etc.) That might help to find out MS-related problems in connecting to Jet databases.

«Midnight» · « **Reply #8 on:** May 11, 2006, 04:06:01 am »

Good point Thomas.

I once had an EAP file that went sour on me. I opened it with Access 2000, after first doing the convert function from Access (which creates a copy from the original, rather than trashing it). I was able to run the compact and repair function, and things seemed OK. Once that was done I think I needed to convert the resulting file to a previous version - in this case Access 97 (but it was some time ago, so I don't remember for sure). After renaming the end result to .EAP I was able to open it in EA.

Now... I immediately exported everything I needed and dropped it into another model. If you try this make absolutely sure things still fit together (i.e. no broken foreign keys) before you do too much work with the file. I think errors would show up pretty quickly.

Please note as well, that I always select the Jet 4.0 option in EA.

David

Eve · « **Reply #9 on:** May 11, 2006, 03:06:59 pm »

Hey Midnight, you can also do those functions from within EA.

'Tools' | 'Manage Eap File' and 'Repair .Eap File' or 'Compact .Eap file'

«Midnight» · « **Reply #10 on:** May 11, 2006, 03:44:46 pm »

Thanks Simon,

They've been there for quite a while too. They are just so familiar with them I hardly notice them...

The one time I had to repair a file, I remember that I had really trashed it. I cannot remember what the problem was, but between my Access tweak and EA, everything came back in one piece.

David

kkilpone · « **Reply #11 on:** May 12, 2006, 09:57:40 am »

By the way

When I try to repair the EA file following message is coming up "Operation Is not supported for this type of object"

«Midnight» · « **Reply #12 on:** May 12, 2006, 10:14:09 am »

Do you get this message when repairing from the EA menu, or with Access (as I described earlier in this thread)?

kkilpone · « **Reply #13 on:** May 12, 2006, 12:01:36 pm »

From EA menu, this problem starts to get to my nervs :-/

kkilpone · « **Reply #14 on:** May 12, 2006, 12:05:23 pm »

When I try to repair the file in Access, Access will prompt that the file has been created in an earlier version, can't repair.

I have acceess 2003

Sparx Systems Forum

News: