Book a Demo

Author Topic: Microsoft cursor engine error  (Read 5709 times)

Romain_France

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Microsoft cursor engine error
« on: June 06, 2013, 11:52:36 pm »
Hi,

We have frequently the error "Microsoft cursor engine [-2147217864]". This error appears when we create/modify any elements in EA.
So it is very frustrating.

Is there a workaround ?

Regards,
Romain

g.makulik

  • EA User
  • **
  • Posts: 355
  • Karma: +0/-0
    • View Profile
Re: Microsoft cursor engine error
« Reply #1 on: June 07, 2013, 07:42:05 am »
Looks like it's some issue with your EA DBMS repository configuration, or the DB connection setup. Already asked your DB admin about this problem?

Best regards,
Günther
Using EA9.3, UML2.3, C++, linux, my brain, http://makulik.github.com/sttcl/

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: Microsoft cursor engine error
« Reply #3 on: June 07, 2013, 09:23:48 pm »
it was allready asked in this forum  :(
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Microsoft cursor engine error
« Reply #4 on: June 07, 2013, 11:12:27 pm »
Quote
it was allready asked in this forum  :(
I wouldn't really blame anyone not finding threads in this forum as it is a REAL PITA. Now we have THREE search fields. And if you happen to find the right one (that intimidated button) you have default settings that will find nothing with 99.99% probability. So the probability for finding something as less than 0.01%.

q.

Romain_France

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Microsoft cursor engine error
« Reply #5 on: June 18, 2013, 11:46:16 pm »
Hi,

The link on stackoverflow (+ upgrade the mysql driver) solved the problem.

Thanks,