EA16.1 Frequent DB Errors ADODB.Recordset [0x800a0e78]

[satrman]

Hi all,

in our company we always wait for the last build of EA version to get as stable app as possible.
We decided to upgrade from 1559 to 1628 (64 bit). Prior rollout I did go through complete changelog and through all forum posts between those two releases (a lot of reading...). However it did not get me ready for unexpected frequent DB Errors.
On EA 15.2 we got  used to "Microsoft Cursor Engine Error" - it was anoying, but didn't have effect on underlying data.
On EA 16.1 we are getting amount of new DB error messages - the most frequent is:

Code: [Select]

Enterprise Architect (Build: 1628 - 64 bit)

ADODB.Recordset [0x800a0e78]

Operation is not allowed when the object is closed.
We get this message during various operations related to XMI export (XMI export, Copy full structure... which is XMI exp/impo on background anyways, clone element as a new version, baselining)

I also experienced slight variation of our popular error:

Code: [Select]

Enterprise Architect (Build: 1628 - 64 bit)

Microsoft Cursor Engine [0x80004005]

The data provider or other service returned an E_FAIL status.
We are in pilot run at these days and many users refuse to work with EA16.1 and want their EA15.2 back.
We do integrity check regullarly, we maintain our MS SQL DB regullarly, we discuss issue with DB admins, but cannot get to any solution - still in EA15.2 we are pretty fine, in EA16.1 we cannot work.

Here is our setup:

EA16.1.1628
directly connected to DB via OLEDB:
DBType=1;Connect=Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=XXXX;Data Source=XXXX.YYYY.ZZZ,PPPP;LazyLoad=1;

Microsoft SQL Server 2017 - 14.0.3465.1 (X64)
Enterprise Edition (64-bit) on Windows Server 2016 Standard 10.0 (Build 14393)

DB size:
t_object 1 500 000
t_diagram 170 000
t_connector 1 150 000
t_snapshot 1 015 000 (we maintain 5 month audit history)

cca 30-50 concurent users (several hundred in total)
 
Does ANYONE have clue, what can be done in this situation?

Thanks in advance

PS My guess is that it may have something to do with OLE DB and switch to 64 bit, but I am not an expert in this area

[Geert Bellekens]

There are a few things to look at or experiment with

- try to connect using the new native sql connection (server connection)
- Install PCS on the server and connect to PCS instead of directly to the database

And then my all-time favorite:

- Install the EA client on a server close to the database, and use  a remote desktop/AVD/Citrix solution to use the client application.

This should instantly resolve all database and performance issues, and has the added benefit of having a much simpler installation/upgrade process.

Geert

[satrman]

Thanks Geert,

we have successfully run this repo for about 11 years and we have'had pretty good performance for its size so far.
Except MS  Cursor engine error and sometimes Locked transactions we had no other DB issues so far.
We got our end user stations (virtual and physical) as close to DB as possible by our security standards.
However the trick with Native connection might work - we'll definitelly give it a try a let you all know.

Thanks again



 

[skiwi]

Yes, we see this a lot (we use SQL Server). (as I referred to in may post about instability).
It basically makes direct DB access unusable, because you have to click through so many messages each time you change something (although to its credit EA does keep working)


I wonder if it is related to a DB connection being dropped and then reinstated.