Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Taz on March 14, 2008, 10:10:25 pm
-
This morning after editing a diagram, EA crashed. When I tried to re-open my project I now get the following error:
An Error has Occurred: Unrecognized database format: 'C:\Documents and Settings\...\MyProject.EAP'
How can I fix this so I can open the project again?
-
First, make a copy of your 'broken' file, in case I've got this wrong.
I think the usual procedure is to start EA - strangely, you have to open a project, but it seems you can open any one you want - and then from the main menu choose Tools | Manage EAP File | Repair EAP File.
This brings up a dialog where you can point to (the copy of) your broken file. It runs an MS Access (or Jet) routine to clean up the file in just such a case as you describe.
If that does not work there is advice in the forum, but you'll have to search a while.
Let us know...
David
-
Hi David,
Thanks for your response. I tried what you suggested, but unfortunately it didn't fix it. I guess I have to go to a previous backup of the file and redo the latest changes. However, it is worrying me a bit, that the file wouldn't even open.
Taz
-
That's a Jet thing. When the file is (even a bit) corrupted Jet won't open it at all.
Before you lose your work, search the forum. I have definitely seen this kind of thing mentioned before, and there have been some 'second stage' solutions presented. It comes up infrequently though, so go back quite a while.
David
-
I'm not sure if this will help, but if Jet 4.0 isn't enabled (See Tools | Options) try enabling that, restarting EA and doing the repair again. You'll need to open a model other than the one you're repairing to do this.
Unfortunately I don't have any other suggestions at the moment.
-
I enabled Jet 4.0 as you suggested and tried the repair again. This time instead of just returning doing nothing, it shows the following error message: "Operation is not supported for this type of object".
-
Well, I suppose that's something...
I take it you still cannot open the file.
Perhaps - assuming the contents are not sensitive - you should send it in to Sparx (compressed). You can attach a file to the registered bug report form. This might be something they can tweak, and I'm sure that they would like to know about issues that can trash a model - even if they are consequences of the Jet driver.
David
-
I have the same problem...any word on a fix or help? I tried the repair option following the online help instructions...to no avail.
M
-
OK...I may have figured it out on my own :) I had exactly the same symptoms. The file became corrupted when generated RTF off a custom template...the EAP was about 6.5 MB...and my computer froze (it does this once in awhile...frustrating but I am used to it...so the most I would have lost about 4 hours work...remind me to save out new versions more frequently). I forced a hard reboot and experienced the problem.
I tried the help suggestion of restarting on JET 4.0 and repairing the file...no worky. So I copied the file and renamed it as mdb...opened Access 2003 and did a compact and repair on the "mdb." Opened that...hey I could see tables and data...great. I renamed the file back to EAP and opened it in EA...BACK IN BUSINESS!
Generated an RTF again using custom template...content looks OK.
M