every now and again i start to get this error.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_tblWorkContentProperty_tblPropertyDefinition". The conflict occurred in database "EPiServer", table "dbo.tblPropertyDefinition", column 'pkID'.
Once it starts happening, it keeps doing it until i run iisreset.
Does anyone know what is causing this?
I usually have this if the database is shared among multiple developers/environments and something changes in one (new page types, property etc).
Although a iisreset does seem to fix this we have found this can re-occur again - can you give us more details and what is causing this? also will it be fixed in the next release?
as it says above, if you see this, you may have more than one site setup on iis sharing the same database but with different models, properties, pagetypes etc
Old post but a new encounter.
We run a shared delevopment environment in our EPiServer "test"-site and i just raned into this problem. I reseted the IIS and then edited in EPiServer Edit-mode a text on a site which no one else has made any changes in and it appeared again. one of my colleagues has files checked out for editing purposes in Visual Studio which may cause the problem. But what will happen when i deploying the files on the live server? Will the problem persist or is it only bound to the development environment test site?
I deployed the release and the same error occured. However when i reseted the IIS it worked as it should.
I can confirm an IIS reset solved this problem for me as well (on FK_tblContent_tblContentType).
For me, iisreset does not help. Any other suggestions?
it was quite a while ago, but the solution is dont share a database across multiple environments, it just doesnt work and causes a bunch of issues