Author Topic: Microsoft Cursor Engine [-2147217864] (Read 6614 times)

GPhil · « **on:** February 16, 2012, 08:11:26 pm »

Hi,

during processing some diagrams the following errors appear:

"Microsoft Cursor Engine [-2147217864]
Die zum Aktualisieren angegebene Zeile wurde nicht gefunden. Einige Werte wurden seit dem letzten Lesen ggf. geändert.

ADODB.Recordset [-2146825069]
Operation is not allowed in this context."

I am using a MySql DBMS repository. Do you have an idea, why these errors appear?
It seem like these errors do not have an impact on the consistency of the diagram.

Thanks for the help,

Phil

Geert Bellekens · « **Reply #1 on:** February 16, 2012, 08:25:55 pm »

Phil,

Try to run the Project Integrity Check (Shift-F9).
That might help.

Geert

GPhil · « **Reply #2 on:** February 16, 2012, 08:52:25 pm »

Thanks, it helped.

But when I did the check, i got the following result:

+--------------------------------------------
| Integrity Check Report.
| Generated: Donnerstag, 16 Februar, 2012
| No. Items: 2
+--------------------------------------------
1 - Invalid connector. ITEM: ControlFlow. ACTION: Delete Connector.
2 - 2 Orphaned element stereotypes. ITEM: . ACTION: Delete orphaned stereotypes.

Where was no link to the elements that raised these errors. Do you know how to find out which elements are affected?

Phil

qwerty · « **Reply #3 on:** February 16, 2012, 09:52:41 pm »

No chance. Unless you dive into the wonderful world of EA's database structure. Only a few are enlighted...

q.

Geert Bellekens · « **Reply #4 on:** February 16, 2012, 10:34:45 pm »

Yep, its similar to Alice in Wonderland.

now where did I leave that pocketwatch

Geert

GPhil · « **Reply #5 on:** February 16, 2012, 11:50:58 pm »

Thanks four your help.

I fixed the probles with the integrity check, but still have these error messages :-(

Any other hints?

Thanks,

Phi

Geert Bellekens · « **Reply #6 on:** February 17, 2012, 12:00:33 am »

Report a Bug

Geert

GPhil · « **Reply #7 on:** February 17, 2012, 08:37:43 pm »

The bug report is done, I will post the result (if there is a result :-) )

Thanks again for the help!

Stefan Bolleininger · « **Reply #8 on:** February 17, 2012, 09:27:00 pm »

How did you configure your Database connection?

Have you tried

„Details/Connection/Allow big result sets“ and „Cursor_Results/Return matched row instead of affected row“

in your ODBC Manager Details?

GPhil · « **Reply #9 on:** February 17, 2012, 10:06:40 pm »

Now I tried it, it worked, thanks! :-)

Wolfgang Sprick · « **Reply #10 on:** June 12, 2012, 11:28:17 pm »

I randomly get the same error using an ORACLE database.

Are there recommendations setting ODBC details for Oracle databases? The parameters mentioned do not exist using the Oracle ODBC driver.

Sparx Systems Forum

News: