"OptimisticVerificationException: Row not found" e - Sitefinity - Bugs & Issues

All Replies

Posted by Community Admin on 25-Sep-2013 00:00

Hi,

Our website is using Sitefinity standard edition, today we encountered this issue when doing authentication with SecurityManager from Sitefinity:

Telerik.OpenAccess.Exceptions.OptimisticVerificationException: Row not found: GenericOID@73ca9289 User id=ae44eb21-19f8-6eb6-bbbb-ff000095e6a4 UPDATE [sf_users] SET [fld_psswrd_ttempt_window_start]=?, [is_logged_in]=?, [last_login_date]=?, [last_modified]=? WHERE [id] = ? AND [is_logged_in]=? (set event logging to all to see parameter values)
at Telerik.Sitefinity.Data.TransactionManager.CommitTransaction(String transactionName)
at Telerik.Sitefinity.Security.SecurityManager.AuthenticateUser(String membershipProviderName, String userName, String password, Boolean persistent, User& user)
at Telerik.Sitefinity.Security.SecurityManager.AuthenticateUser(String membershipProviderName, String userName, String password, Boolean persistent)

At that time, there are a few users doing signin to our website, but among 40+ users, only 1 user has this exception. And he manages to replicate the same exception the 2nd time, although so far we are not successful in replicating the issue

I did a search and found this thread which seems to have the same problem: www.telerik.com/.../row-not-found-genericoid-1e.aspx

But what I wonder is if it's indeed because of concurrent access/update to database then why only one user got this exception? And he even manages to generate exception twice

The method that causes exception is SecurityManager.AuthenticateUser()

Thank you very much

Posted by Community Admin on 28-Mar-2014 00:00

We are having the same issue, in a load test scenario. The dbContext.Refresh example we found in the Docs, doesn't seem to apply here, or I can't find a way to get the user manager to refresh the user and try again..

Posted by Community Admin on 31-Mar-2014 00:00

Hi all,

The behavior you are noticing is a bug in our system. It has been logged and you can follow its progress in our Portal. We will do our best to eliminate this in our future releases.

Please accept our apology for any inconvenience caused.

Regards,
Ivan D. Dimitrov
Telerik

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items

Posted by Community Admin on 02-Aug-2016 00:00

Ivan -- based on the link you posted this issue still exists with version 9.1. This bug in the system is coming up on at least 3 years old and over 2 years since your last post dated March 31, 2014. Any idea as to when this will be fixed?

This thread is closed