Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Mschlecht on March 31, 2006, 01:50:15 pm
-
Unable to bring up project file, getting 'unrecognized database format'.
We were able to save documents earlier in the day. We're not sure why this happened and why we can't open this project file.
Anyone with a solution?
-
Some things to check:
- First, I assume you are using an EAP file.
- If so:
- Have you changed the Jet 4.0 setting in Tools / Options? Is there any chance you have saved a 4.0 file and are trying to open it with this option unchedked in EA? If you change the setting, remember to exit and restart EA before trying to open the file.
- If you have Access 2000 (probably other versions, but I have only tested this with 2000) you can open the EAP file with Access. Before you do so, you will have to use Access' Convert Database utility to convert the EAP file to a format Access can manipulate. Open the converted file, and perform a Compact and Repair operation. When that's done, use the access function to convert the database to a prior version. Choose Access 97 if asked, otherwise just choose Access Database. Rename the converted file extension to .eap, and try to open this with EA.
- If not:
- Have you performed a Data Transfer to your back end repository file in order to initialize the database? If not, you will need to create a new project, with the minimal data you want, in EAP format. Then do a Data Transfer (it is not necessary to open any model first) to the DBMS location. The model should now open.
Good luck, and please let us know how you make out,
David
-
Thanks!!! That worked.
-
You're welcome of course.
But, which one worked?
-
I have the same problem and cant find any solution.
The problem is, when system close the EA process before it can close the project like this
- shutdown or restart comp imidiate
- power switched off
- need to repait initial connection to DB c.c., not content
i tried all of the suggestion expect (repair with access - i wont buy Access to repair AE ;])
-
You can do the "repair" function directly from EA.
Start EA and open your EAP file, let EA complain. If it will open the file at all you should be OK.
From the EA main menu choose Tools | Manage .EAP File | Repair .EAP File. This should do the trick.
If EA won't recognize the file at all, then submit a bug report to Sparx (since you will have EA open, from the main menu choose Help | On-line Resources | Bug Report Page), and please let us know here in the forum.
-
so now i can say >
for any crash, update the version first, any build can correct it ;]
and steps are like this if database crash
- create new empty project or open any
- must have something opened, dont know why ;]
- use repair to specific corrupted file
- and hope to repair it
- it repaires file crashed on power switch off and process kill
hf with EA
-
I have the same problem and cant find any solution.
The problem is, when system close the EA process before it can close the project like this
- shutdown or restart comp immediate
- power switched off
- need to repair initial connection to DB c.c., not content
i tried all of the suggestion expect (repair with access - i wont buy Access to repair EA ;])
In my experience it is extremely rare for even catastrophic failure of EA (such as crashes or forced exits at shutdown or logout - or even power failures) to corrupt the DB. Especially if you are using JET4.0.
Sparx have (in my opinion) done a very good job of isolating/coupling the DB from the Application. You must have just been very unlucky... :(
As to having to have at least one .EAP file open before you can repair another. Yes, that is a minor glitch in EA's UI (Unique Interface) - but it is not a big impost (in my view). Report it as a bug.
As David (Midnight) says... You should be able to repair the DB using EA on its own.
Let us know if you manage it (and any steps required).
Paolo
-
I've had two 'unrecognized database format' errors in the past month, never having experienced them before.
The first time it occurred, I didn't lose much work, so I just restored a backup. (I was able to repair the database using EA's repair feature, but felt it was safer to use the backup, rather than the repaired database.)
Then it occurred yesterday. This time it isn't practicable to restore a backup as 2 people would each lose a day's work.
I've two questions:
- How many others are experiencing database corruption?
- Does anyone know why it happens?
- Has anyone had further problems with a repaired database?
-
I've yet to trash a single file in years of working with EA. I have had one file act strangely, but the repair feature worked and I did not have problems later.
What's your working environment?
BTW, I have always switched the Jet 4.0 option on. The other setting is for those of us who still have the Access 97 drivers, but Sparx staunchly defends the current default. Sigh...