Telerik.OpenAccess.Exceptions.OptimisticVerificationException: Row not foundCancelThe title field is required!

we upgraded the sitefinity version from 3.7 to 6.2 .when i clicking some page I Encountered this error Some times but not all the times .

Row not found: GenericOID@7e09805f User id=429c01cf-1fa8-6f4a-89ea-ff0000545f3c
UPDATE [sf_users] SET [last_activity_date]=?, [last_modified]=? WHERE [id] = ? AND [last_activity_date]=? AND [last_modified]=?
(set event logging to all to see parameter values)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Anther option is this to be caused by L2 cache. Sitefiniy Steve also recommends this as a solution to the problem, which you can also try.

I hope this helps.

Regards,
Vassil Vassilev
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

Strange, I just came to see if there was an update on this issue, and this thread was the most recent in the forum. I get this roughly 1 in 4 times I rebuild my solution. The only fix I've found is to build again and then wait another 2-3 minutes for the site to warm up.

Here's a more complete stack trace (side note, "directory" is misspelled on line 24):

This error is occurring when users try to Save item as Draft, Send for Approval or Publish. From waht I have read, it appears to be an issue with data caching. For some unknown reason the data that is being cached does not contain the item(s). I checked the DB directly and this row/item does exist in the DB, but it does not exist in the "data cahce".

Based on our experience the "Row not found ..." exception you have received might be related to caching issue. It seems that the rows which are in the description of the error has been already deleted/updated in the database but are still "present" in some cache - thus resulting in this error.

In order to reduce this type of errors I can suggest that you go to Administration -> Settings -> Advanced -> Data and set the Enable data caching property to False. We have positive feedback from our clients experiencing similar issues that disabling the data caching resolves the issue.

The cache is cleared when you recycle the application and the application gets fresh data from the database and this should resolve the issue. So, what I can suggest is to restart the application and then test again. This way we can check if the issue is related to caching.

This issue may also occur if you are in a load balancing environment if the cache is not invalidated and on some nodes you still have some cached data.

What you can try is to set the project on your local machine and test the behavior when you run the project locally? This way we can see if the issue is related to environment settings.

Regards,
Sabrie Nedzhip
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

What effect on performance would we see if we turned data caching off? Also, we are load balanced. Our Pre-Production environment is set up for load balancing as well and we do not see this behavior in that environment. I also have the project set up locally and have not come across the issue there either. Is the only fix to disable data caching?

I have a support ticket open in regards to this issue and just got the following response:

Please note that although disabling the L2 cache manually could fix the problem, it will impact the performance of the whole site. It has been enabled by default since Sitefinity 7.1 for a performance improvement. The first article was written before the version 7.1 was released, when there was no communication for L2 cache messages of OpenAceess. For a better performance this field should be left in blank.

It is a little frustrating to me that within 5 hours I received 2 different responses regarding this issue and both were from a Telerik representative!

Webinars

Tools

Progress, Telerik, Sitefinity and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.