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

SharePoint 2016 RTM Install

While I am generally excited about SharePoint 2016, going through an RTM build of any Microsoft product is not without issues. Going through the install, I will list out any issues that I find to mitigate troubleshooting for the next lost soul or any major differences.

In lieu of the Windows Server, active directory and SQL (Maybe?) install, just focusing on SharePoint for this one. Think single server… maybe because I am lazy, also due to the fact this won’t be anything but a playground for a few months.

//////////////////////////////////////////////////////////////////////////////////

Prerequisite Install
Error: Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850): Installation error

2015-10-06 12:38:36 – Check whether the following prerequisite is installed:
2015-10-06 12:38:36 – Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850)
2015-10-06 12:38:36 – The following file does not exist:
2015-10-06 12:38:36 – C:\Windows\servicing\Packages\Package_41_for_KB2898850~31bf3856ad364e35~amd64~~6.3.1.2.cat

Result: Missing file. Download (Link). Installed manually. Ran the prerequisite installer, completed successfully.

//////////////////////////////////////////////////////////////////////////////////

Default folder is 16.0

C:\Program Files\Microsoft Office Servers\16.0\Data

//////////////////////////////////////////////////////////////////////////////////

Still have the 14, 15 and 16 folder

SP2016_Folders

//////////////////////////////////////////////////////////////////////////////////

Database Access Account.. previously the account executing psconfig.exe was used to access the server and create databases and apply access. Now the account is specified inside the wizard.

And yes, using SQL Alias here, SQL is pointing to the local machine.

SP2016_SQL_New_Farm

//////////////////////////////////////////////////////////////////////////////////

MinRole Options

SP2016_MinRole

I choose custom, mostly because I want to see what I get from it. Without listing what MinRole provides for the other options.

As I suspected, there were no additional options in the PSConfig wizard. Most of you should be selecting custom to get the most out of server infrastructure. However, for you medium to large organizations that may have dedicated Search or DistCache servers, my hats off to you.

//////////////////////////////////////////////////////////////////////////////////

Same old story… Microsoft, please let us name our databases. You let us for some, not all, if inconsistency is what your looking for, you win.¬†DBA Fail.

SP2016_Admin_DB

//////////////////////////////////////////////////////////////////////////////////

After install, admin DB needs an upgrade. Ran PSConfig, no change. Look into this later…

SP2016_Admin_DB_Compatible

Yup, needs upgrade.

SharePoint_AdminContent_9d149a75-48fd-4d01-b14e-78fe5414b515
Microsoft.SharePoint.Administration.SPContentDatabase
5
Needs Upgrade

//////////////////////////////////////////////////////////////////////////////////

Role conversation, back to the initial install, choose wisely.

Central Admin > System Settings > Servers (Section) > Convert Server Role in this Farm

SP2016_Server_Role_Convert

/////////////////////////////////////////////////////////////////////////////////

They added port specification and SSL to outgoing SMTP

SP2016_SMTP

/////////////////////////////////////////////////////////////////////////////////

Servers in compliance. Whew!

SP2016_Compliance

/////////////////////////////////////////////////////////////////////////////////

No default content sources.

SP2016_Search_Sources

/////////////////////////////////////////////////////////////////////////////////

I am not seeing any major changes in the UI. I have more investigation to do on the backend services which will likely be a separate post.