SharePoint: The INSERT statement conflicted with the FOREIGN KEY SAME TABLE constraint “FK_Objects_Objects”. The conflict occurred in database “SP_Config”, table “dbo.Objects”, column ‘Id’

SharePoint issues… meh

I was provided a standard license for a SharePoint farm in lieu of needing enterprise for Access and Excel services. After the farm build, I attempted to make this right…

I attempted to convert the license, however this option was not available.

sharepoint-the-insert-statement-conflicted-with-the-foreign-key-same-table-constraint-fk_objects_objects-the-conflict-occurred-in-database-sp_config-table-dbo-objects-column-id-a

Attempting to Enable Enterprise Features, the timer job runs which eventually fails to this..

Unknown SQL Exception 547 occurred. Additional error information from SQL Server is included below.

The INSERT statement conflicted with the FOREIGN KEY SAME TABLE constraint “FK_Objects_Objects”. The conflict occurred in database “SP_Config”, table “dbo.Objects”, column ‘Id’.
Table ‘LastUpdate’. Scan count 0, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table ‘Objects’. Scan count 0, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table ‘Classes’. Scan count 0, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table ‘Objects’. Scan count 0, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
The statement has been terminated.

While I found a few posts to fix this, either manipulating the webpage by enabling the disabled functions on the convert license type page or of course the always, not recommended, manual update to the database.

In the end, since this was production, I opted for dropping the attached servers from the farm, deleting the necessary databases (it’s new, so no need to save most), and creating another farm.

After getting central admin online, I now see my farm license is all ok and I can continue on. A more official method would be to uninstall/reinstall the SharePoint bits to properly assign the license, however considering the farm was showing me the correct license and there isn’t any higher to go, I am good with this.

sharepoint-the-insert-statement-conflicted-with-the-foreign-key-same-table-constraint-fk_objects_objects-the-conflict-occurred-in-database-sp_config-table-dbo-objects-column-id-b

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s