Book a Demo

Author Topic: Row cannot be located for updating. Some values...  (Read 8342 times)

Ryan Kelly

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Row cannot be located for updating. Some values...
« on: June 16, 2011, 08:40:49 pm »
I'm seeing errors reported updating certain elements within our model.  The update seems to work but I'm concerned by the error. The following is the error reported.

Microsoft Cursor Engine [-2147217864]
Row cannot be located for updating. Some values may have been changed since it was last read.



We are using the shared database (MySQL) backed by VC (Subversion) team sharing setup.

Other members of the team are not experiencing the problem. I have tried re-installing EA and using a fresh Subversion working copy of the model but this has not rectified the problem.

Does EA store some data locally, outside of any VC working copy? I'm thinking that it does since this error seems to suggest that this data is out-of-sync with that in the shared database.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Row cannot be located for updating. Some value
« Reply #1 on: June 17, 2011, 08:20:42 am »
That error usually indicates that you haven't checked the 'Return matched rows instead of affected rows' checkbox when setting up your MySQL ODBC connection.

Otávio Ventura

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Row cannot be located for updating. Some value
« Reply #2 on: June 21, 2011, 12:27:55 am »
Same here when trying to create/edit Documentation Templates. It doesn't get to insert the register in the database successfully.

Using PostgreSQL 9.0 as the project repository.

Any sugestions?

Tks in advance!

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Row cannot be located for updating. Some value
« Reply #3 on: June 27, 2011, 08:04:05 am »
I've noticed this or something similar when EA has generated duplicate GUIDs.

Tools | Data Management | Run Data Integrity check

(note your model may change!)
« Last Edit: June 27, 2011, 08:04:51 am by skiwi »
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.