Getting error - row cannot be located for updating??

Question

We just moved one of our pos lanes to a different computer, we are running version 1.3.1010. After we tender out a transaction and tries to post the transaction, we receive the following Store Operations Business Rules error:

Error #-2147217864 Row cannot be located for updating. Some values may have been changed since it was last read. (Source: Microsoft Cursor Engine) (SQL State: ) (NativeError: 32) No Help file available Error in PostTransactionEntries

Then after that error, we get a run-time error #5, and get kicked out of POS.

If I go to the journal viewer, it does not show the transaction. However if I go into the SQL database and run a SELECT query against the TransactionEntry table, the transaction is there. It seems like it is writing the data to the database, but is not updating the journal.

I cannot find this error documented anywhere here on the discussion group, or in CustomerSource. If someone can help me with this error that would be great.

Thanks Kevin

kskinne · Accepted Answer

Thanks Jeff - it is Windows XP SP3, and I have run Windows update, I think I know what you are referring to, there was a hotfix out there to fix an ADO issue with SP3 - I have downloaded and installed that, but unfortunately still am having issues. In fact I have opened an incident report through customersource and they are troubleshooting with me, but we still haven't figured it out. Do you have any other ideas? When I do get this resolved, I will post back what the problem was.

Thanks Kev> Kevin,

kskinne · Answer

Jeff, the issue turned out to be because this workstation was running XP SP3 and the other registers including the one where the DB resides are running XP SP2 - different versions of MDAC. We rolled the third register back to SP2 and the problem disappeared.

Thanks, Kevin

"Jeff @ Check Po> Kevin,

Configuration Tools, and then click SQL Server Configuration Manager.

Getting error - row cannot be located for updating??

Join the Discussion

Didn't find your answer?