Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Thomas Arnbjerg on August 14, 2020, 02:43:38 am
-
We have converted a regular EA 15.1 project to a design master from which each team member creates replicas.
Suddenly 2 out of 3 team members get the error DAO.Database [3049] 'Cannot open database #Temporary QueryDef#'
The one team member still able to open the master transferred it to a new project - and everybody could open it again.
When we converted it to a design master the same two persons got error 3049 again.
Any ideas?
-
Yes.
Don't use Master-Replica!
It's stuff like this an much worse all the way.
Geert
-
As Geert said: trust it as far as you can throw it.
q.
-
Hi Thomas,
My apologies, I didn't catch the significance of this thread earlier.
It appears that a Windows update has broken replication for JET 4 databases. It's still under investigation here to see if there is anything we can do. At this stage the only option for us is to prevent EA from using the updated dll. Aside from bypassing these and any future security updates Microsoft applies to JET the solutions so far are not perfect either.
Personally, I would be uninstalling updates KB4566782 and KB4565351 in order to synchronize anything I can before moving to a DBMS setup.
-
Hi Eve,
are there any other approaches for saving affected files or maybe a functioning workaround?
At my company, we no longer have access to any files since we use master-replica on most of our projects here.
This is a major problem for us at the moment!
And a hint for everyone else involved: DO NOT TRY TO REPAIR your files. After I did, my file came down from 14MB to 800kB - I guess it is shredded now...
-
Unfortunately, there's nothing new to report. I still don't have any kind of workaround other than removing replication, removing patches or replacing the msjet40.dll with an earlier versionh.
-
We have the same problem. Uninstalling update KB4565349 gets it working again.
We have to do it every couple of days because corporate IT policy reinstalls it :-\ and we don’t have much of a voice as a small 6 person team in a large multinational corporation.
Yes, don’t try to repair. We’ve done extensive testing and can confirm it’s related to replication.
-
Do you have enough voice to get yourself a database server for your models? That would be the best way to avoid the problem long term.
-
Maybe Eve, but I expect just a simple Microsoft SQL database is going to provide poor performance when we’re all working from home >:(
-
Rather I'd work with controlled packages (maybe VC) than using that dreaded Mickeysoft replication. Distributed work is tricky in any case. The replication-way is definitely the worst you can choose. Don't ask me why Sparx still promotes its use.
q.
-
I think the options are (in order of my preference)
- Remote Desktop/Citrix installation of EA with a central database
- Version controlled packages
- Pro-Cloud setup
- Central database with VPN setup
Geert
-
Maybe Eve, but I expect just a simple Microsoft SQL database is going to provide poor performance when we’re all working from home >:(
I understand, I wish I had a better solution for you.
I've never used replication except for minor and trivial test cases. All I know is that I've seen lots of users who have run into replication problems over the years. From my perspective Access replication works until it doesn't. I wouldn't trust it with any data of mine, even before this issue.
In terms of performance though, everyone at Sparx Systems is in largely the same situation. Yes, it's not as fast as a local connection, but in my experience it is useable. i even personally connected to our shared database (via PCS) through a satellite connection for a while.
-
I concur on the performance thing.
While EA is notoriously chatty on the network, it doesn't use up much bandwidth. Unless you're doing project transfers and that kind of thing it's all small-packet stuff. EA is much more sensitive to poor connectivity, but even after a loss of connection the client can usually reconnect with no apparent ill effects.
For the past several months I've been working from home, running two or three EA sessions in parallel on the customer's clunky old laptop connecting via a VPN over WiFi. It works just fine.
This is a large company so their server infrastructure is pretty good, but the point is that the remote network thing is not a performance bottleneck for regular modelling. I find the piddly little laptop keyboard and screen to be far more of an issue.
/Uffe
-
I have just updated my personal Windows machine and the problem has been corrected. Because I'm using an Insider Preview build I can't say exactly when this update will be available for general users, or what update to look for.
However, that means that there is a resolution coming. It doesn't appear that the version number for msjet40.dll has been updated with the patch I installed. So my updated advise is that if you are experiencing this issue you should check for Windows updates.
-
Hey,
We had the same issue on Windows 10 2004 and 1909. A Windows Update solved it on my 2004 machine this morning. We still want to switch to a server driven database model. We got EA v15.0 - unfortunately the database scripts are in the download area which is not accessible anymore.
Is it possible to get access to download the scripts?! Our subscription expired but imho a customer should be able to download older files from his subscription period, i.e. get access to the customer section with a subset of downloads. At least that's how it usually works with other companies. Any help is much appreciated!
I can send my credentials via pm if need be.
Kind regards,
Helmut
-
Helmut,
I think you better email [email protected] to get access to the downloads section.
This forum is not an official Sparx communication channel.
It's a forum for communication between users that is sometimes frequented by Sparx employees.
Geert
-
It seems Microsoft has replaced KB4565349 (see https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=115cb91a-8f54-419b-b3d7-25043fa4e135) and neither of the replacement updates have the same bug.
For me, the problem has been solved. ;D