Author Topic: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL  (Read 464 times)

satrman

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Hi everybody,
I have gone through all possible topics concerning Microsoft Cursor Engine [-2147217864] error, but have never found an answer for MS SQL DB - all solutions were for ODBC setting for MySQL and PostgreSQL.

We have pretty big repository (about 1 mio objects, 1 mio connectors, 100 000 diagrams) running on Microsoft SQL Server 2017 (we had to turn compatibility mode to previous version, though, as we had terrible performance on opening some sequence diagrams). We have 50+ concurent users.

We are using encrypted Data Link created via Connection wizard using standard Microsoft OLE DB Provider for SQL Server.
I've been looking for some Data Link parameter corresonding those of MySQL that solved their issue but nothing like

"Return matched rows instead of affected rows"
nor
"Allow big result sets"

could be found.

Also equivalent of Postgre MaxVarchar that needs to be set to 1024 and the Max LongVarChar needs to be set to 1000000 couldn't be found.

So we still have the issue and have no clue, what to do about it. Repository is still very fast, but this is a real pain.

Can anybody help?

Thanks

Miloš Lang (Satrman)

qwerty

  • EA Guru
  • *****
  • Posts: 11390
  • Karma: +295/-263
  • I'm no guru at all
    • View Profile
Re: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL
« Reply #1 on: July 13, 2020, 10:51:47 pm »
At that size you probably have priority support so you should contact them via mail. If V14 is buggy you won't see a fix for it. Any fixes (if done) go to the current version which will be 15.x

q.

satrman

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL
« Reply #2 on: July 14, 2020, 06:27:00 pm »
Thanks for the answer.
Well, yes, that's the way we are about to go, but there are three special circumstances, that make it hard to tell whether it is on the App or the DB side:
1. EA 14.1 worked without this issue on previous MS SQL version
2. This issue is hard to reproduce - there are no 100 % steps that lead to bug reproduction (thus we cannot use debugging on DB side)
3. And finally the worst thing - there is not a word about this problem (MS SQL & Microsoft Cursor Engine Error) on any discussion/web page I went through so far...

Thats why I am asking this community directly;-)

M.

qwerty

  • EA Guru
  • *****
  • Posts: 11390
  • Karma: +295/-263
  • I'm no guru at all
    • View Profile
Re: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL
« Reply #3 on: July 14, 2020, 06:44:27 pm »
You state that you are using 14 with the issue. Now you say it works with 14?

q.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 7290
  • Karma: +84/-12
    • View Profile
Re: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL
« Reply #4 on: July 15, 2020, 08:13:32 am »
You state that you are using 14 with the issue. Now you say it works with 14?
What I see is that the same version of EA fails after updating SQL Server.

I'm currently connected to a SQL Server 2016 repository, from what I've seen there are no documented compatibility issues going from there to 2017.
« Last Edit: July 15, 2020, 08:31:14 am by Eve »
Eve

support@sparxsystems.com

satrman

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: [EA 14.1.1427] Microsoft Cursor Engine [-2147217864] on MS SQL
« Reply #5 on: July 15, 2020, 10:31:16 pm »
Well, there are 2 more clues:
- we have audit log turned on with cca 7 month history (set to max. info excluding XMI export/import log)
- we are using VBScripts for certain user tasks (e.g. creating structures and elements according to naming conventions) - in this case, there is no SQL injection and everything happens via API

We have experienced higher number of the error occurence, when we ran the same script sumultaneously on cca 20 stations (However I tried to simulate it on 2 concurent PCs and it happened only 1 out of 15 tests).
However, the error appears mostly when creating new object by drag&drop on diagram (but in such environment we have, I cannot trully say whether someone else does or doesn't run the script)

We expereince the issue on PROD and TEST environment as well (but both on the same MS SQL version)