Hi.
Using Umbraco 8.6.6, we sometimes get the following error:
Cannot insert duplicate key row in object 'dbo.umbracoPropertyData' with unique index 'IX_umbracoPropertyData_VersionId'
in connection with users failing login.
From what I've been able to debug it looks like this happens when the system tries to count the Failed Login property, and save it to the database.
But sometimes the property does not appear in the database, so the system tries to add it to the property collection, which causes the Insert SQL to fail due to duplicate key constraint. (ReplacePropertyValues in ContentRepositoryBase) by having multiple 'values' end up being added to the same Property.
Does anybody else have this, or know how to safeguard against this other than occasionally running a query which assigns the property to all members in case they don't have it?
No - the error is (was) deep within the property handling of Umbraco and it happens 'rarely' enough that it's not causing major issues for me, so I've currently not done more to it.
duplicate key in object 'dbo.umbracoPropertyData', unique index 'IX_umbracoPropertyData_VersionId' with failing login.
Hi. Using Umbraco 8.6.6, we sometimes get the following error:
in connection with users failing login.
From what I've been able to debug it looks like this happens when the system tries to count the Failed Login property, and save it to the database.
But sometimes the property does not appear in the database, so the system tries to add it to the property collection, which causes the Insert SQL to fail due to duplicate key constraint. (
ReplacePropertyValuesinContentRepositoryBase) by having multiple 'values' end up being added to the sameProperty.Does anybody else have this, or know how to safeguard against this other than occasionally running a query which assigns the property to all members in case they don't have it?
We have the same error on Umbraco version 8.6.6, have you managed to resolve it?
No - the error is (was) deep within the property handling of Umbraco and it happens 'rarely' enough that it's not causing major issues for me, so I've currently not done more to it.
is working on a reply...