Error : A duplicate content type name was found


I was trying to upgrade a database from SP2013 to SP2016 via database attach method, I received an error & the upgrade failed. when I checked the upgrade logs I found following error

 

11/03/2017 14:41:14.31  powershell (0x19EC)       0x03EC  SharePoint Foundation Upgrade                SPContentDatabaseSequence    a5u5l     ERROR  Please upgrade sites using SharePoint 2010 experience in database WSS_Content_SPIN2013 to SharePoint 2013 before proceeding.                ff47299e-3cac-d0a6-189a-7b63171d484c

 

 11/03/2017 14:41:15.00 powershell (0x19EC)       0x03EC  SharePoint Foundation Upgrade              SPUpgradeSession                an59t    ERROR  Exception: Content database data integrity check has encountered a severe issue that upgrade process must be stopped. See the upgrade log for more information about how to resolve this issue.      ff47299e-3cac-d0a6-189a-7b63171d484c

 

When I checked in my SP2013 farm, I found that the particular site mentioned in the error was not upgraded to SP2013 look & feel. This site was migrated from SP2010 to SP2013. Hence I tried to upgrade the site using the following PowerShell command

 

Upgrade-SPSite <SiteURL> -VersionUpgrade

 

I got following error which says that upgrade failed because duplicate content type ‘holiday’ was found.

 

11/06/2017 07:47:39.57 OWSTIMER (0x4F2C) 0x7068 SharePoint Foundation Upgrade SiteSequence ajywk ERROR Action 15.0.2.0 of Microsoft.Office.Server.Search.Upgrade.SiteSequence failed. 95272a9e-feea-40d6-58a3-6545b6d2ca2a

11/06/2017 07:47:45.15 OWSTIMER (0x4F2C) 0x7068 SharePoint Foundation Upgrade SiteSequence ajywk INFO SPSite Url=http://Server:22811/sites/BusinessTransformat... 95272a9e-feea-40d6-58a3-6545b6d2ca2a

11/06/2017 07:47:45.15 OWSTIMER (0x4F2C) 0x7068 SharePoint Foundation Upgrade SiteSequence ajywk ERROR Exception: A duplicate content type name "Holiday" was found. 95272a9e-feea-40d6-58a3-6545b6d2ca2a

 

so I went to site settings > site content types & found that there are two content types by the name ‘holiday’ & that was the issue

 

I tried to delete one of the content source & received error ‘the content type is in use’

 

I then tried to renamed the content type & I was able to rename it. after that I was able to upgrade the database to SP2016 version without any issues.

hope this helps !

Comments

Post a Comment

Popular posts from this blog

Error ‘Object reference not set to an instance of an object‘ on Review Job Definitions page

Image
error ‘ Object reference not set to an instance of an object ‘ appears while trying to access Review Job Definitions page under Monitoring section from central administration. This could be due to faulty timer job. You can find the bad timer by running the following powershell command: Get-SPTimerJob | ? { $_.DisplayName -eq $null }| select name, Id Run below command to delete bad job $Badjob = Get-SPTimerJob <Guid of the job> $ Badjob.Delete() For me the problem job was Microsoft.Office.Server.Search.Administration.CrawlStoreRebalancerJobDefinition & after I removed it the Review Job Definitions page worked fine.  
Read more

users are able to edit other users' mysites

Issue: we had client complaining that users are able to edit other users' mysites. We checked the user profile service application permissions & found 'Everyone' was granted permission 'Manage profiles' due to which all users could edit other users' mysites. Resolution: Remove the permission 'Manage profiles' for 'Everyone' from Central Administration Central Administration > manage Service applications > highlight User profile service application > click Administrator in the ribbon menu > select Everyone > click Remove.
Read more

"sorry this site is not shared with you". users unable to access sites after migration to sharepoint 2016

after we migrated our SharePoint sites from 2007 to SharePoint 2016, existing users started getting error "sorry this site is not shared with you". newly added users could access the site. this issue occurs because though the new SP2016 web application is using Claims authentication, the database is not claims aware yet. we were able to fix this issue by running following powershell commands which converts the database to claims authentication & migrates the existing users to Claims format. $wa = get-SPWebApplication "WebApplication " Convert-SPWebApplication -Identity $wa -From Legacy -To Claims -RetainPermissions -Force -Verbose $wa.MigrateUsers($true)  
Read more