Author Topic: Cannot Open Old Model After Windows Update - DAO.Database [0x00000be9] (Read 7854 times)

drjmansell · « **on:** August 19, 2020, 12:42:25 am »

After the most recent Windows 10 update, which did affect SQL database files I believe, I am now unable to open my model with the error:
"DAO.Database [0x00000be9] Cannot open database '#Temporary QueueDef#'. It may not be a database that your application recognizes, or the file may be corrupt." We were able to open it without problem on a computer that had not been updated. Can you advise on how to proceed?

Geert Bellekens · « **Reply #1 on:** August 19, 2020, 12:56:41 am »

You can try the .eap repair option
Configure | Model | Integrity | Manage .EAPX/EAP File | Repair .EAPX/EAP File

Geert

drjmansell · « **Reply #2 on:** August 19, 2020, 04:06:24 am »

I get "Unrecognized database format" error, followed by "To enable Jet 4, go to Start | Preference | Use JET 4.0, restart EA."

Again, this opens on a computer before the recent Windows 10 update, so its not a file format issue, but something more fundamental to the program. I think we're going to need a patch.

Eve · « **Reply #3 on:** August 19, 2020, 08:05:35 am »

What is the exact build/version of Windows 10?

We have had one report of this to our support email, unfortunately I can't reproduce this on my home computer with either the latest regular build or the latest insider developer build.

Other than that, I'd recommend directly emailing our support team so they can give it their full attention.

drjmansell · « **Reply #4 on:** August 19, 2020, 08:40:33 am »

Windows 10 - Version 2004 (OS Build 19041.450)

There is some evidence that it might be associated with pictures inside the model, but I have yet to confirm this on my system. Could it be the t_image database?

drjmansell · « **Reply #5 on:** August 19, 2020, 08:45:51 am »

I forgot to include that it is Windows 10 Pro for Workstations.

drjmansell · « **Reply #6 on:** August 19, 2020, 08:55:56 am »

Also, I did send several e-mails to the support team 4 days ago and have not received any response back. It seems like the forum site is much more responsive than the support e-mail.

Eve · « **Reply #7 on:** August 19, 2020, 09:24:24 am »

From what I can see your emails have been responded to. Perhaps check your spam filter.

The forum can be quicker, you get direct access to me and a few other Sparx Systems developers, but they are acting in a less official capacity and there's less that we can directly do.

Looks like the model I connected to did have contents in the t_image table. Still not sure what's going on.

Eve · « **Reply #8 on:** August 20, 2020, 08:27:51 am »

Hey, is your deployment using replicated eap files?

We now have another user (or set of users) that are having the same problem. They were able to continue work by using a Windows machine that did not exhibit the problem to remove replication and then they could open the non-replicated files.

Unfortunately, my test of making the EA Example model into a design master, creating a replica, making a small change and then synchronizing it back all worked and I could still open the models afterwards. Would you mind running a similar test on your system?

DavidC · « **Reply #9 on:** August 20, 2020, 02:14:09 pm »

We have a very similar problem after recent updates were applied to MS Windows 10. I have tried to create a basic model and create a master which seems to work okay. When i try to create a replica I get a message suggesting the database is wrong type or corrupt i.e. "Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt."

If I now try and open the master project I get the DAO.Database error i.e. "DAO.Database [3049] Cannot open database '#Temporary QueryDef#'. It may not be a database that your application recognizes, or the file may be corrupt."

I have tried a repair but to no avail other than the message changes i.e. "All Enterprise Architect tables in the selected repository are missing, please confirm it is an Enterprise Architect repository and the configured user has the required permissions."

RichHead1821 · « **Reply #10 on:** August 20, 2020, 04:53:03 pm »

Quote from: DavidC on August 20, 2020, 02:14:09 pm

If I now try and open the master project I get the DAO.Database error i.e. "DAO.Database [3049] Cannot open database '#Temporary QueryDef#'. It may not be a database that your application recognizes, or the file may be corrupt."

I have tried a repair but to no avail other than the message changes i.e. "All Enterprise Architect tables in the selected repository are missing, please confirm it is an Enterprise Architect repository and the configured user has the required permissions."

EXACTLY the same here

qwerty · « **Reply #11 on:** August 20, 2020, 05:26:56 pm »

Guys, replication? You never had word that this is the worst thing you can do? Get rid of it as soon as possible!

q.

Uffe · « **Reply #12 on:** August 20, 2020, 06:06:42 pm »

Hello all,

Error 0x0be9 or 3049 means the Microsoft Access database, which is what an .EAP file contains, has been corrupted.
Access, especially in its earlier versions, is notoriously unreliable and will often corrupt the database when faced with large amounts of data, large numbers of transactions (especially over a network file system), and/or interruptions during write operations.

Probably what has happened to some users is that an update has been rolled out in the background, installing a new version of some DLL or other, while the user is working in the project. This has interrupted a write operation, causing the corruption.

It may be possible to restore the database, or it may not be.
In order to try, you'll need to use Access administration tools. Back up the file first.

If you are successful, the next step is to transfer the data to either a Firebird (.FEAP) or a JET 4 (.EAPX) database (assuming that the corrupted project was in a JET 3 .EAP file). To clarify, JET is the DB engine in MS Access; 4 is a better version than 3 (but still pretty terrible).
If you can afford it, stop using file-based projects and go to a proper DBMS such as Microsoft SQL Server.

Finally, Sparx: please remove the option of creating new JET 3 projects. Making JET 4 the default is not enough.
Nobody needs JET 3 for new projects, and since you hide the fact that that is what an .EAP file is problems like this will keep cropping up.
Whenever a user opens a JET 3 repository, you should also pester them to transfer it to a JET 4 or Firebird one.

/Uffe

Eve · « **Reply #13 on:** August 21, 2020, 08:24:01 am »

The best I can offer you right now is the content of the following link.

https://answers.microsoft.com/en-us/msoffice/forum/all/august-2020-office-2010-updates-break-access-jet/b1b89aa4-05fd-4c2c-859f-6557f41a619e

This is a Microsoft bug that impacts multiple applications. The only workaround so far is uninstalling updates KB4566782 and KB4565351. I'll keep looking, but it's highly likely that this can't be fixed on our side.

Sparx Systems Forum

News: