none
SP2010 Upgrade Eror: A duplicate content type name "Resource" was found.

    Question

  • The following error was logged numerous times for different site collections (25 total site collections) during the in-place upgrade from MOSS 2007 to SharePoint 2010.  It is referencing a content type named "Resource".  The only location I could find the "Resource" content type was under the "Group Work Content Types" heading in the Site Content Types page for the site.  I could only find 1 reference, no duplicates as the error suggests.  I did try to rename the content type to "resourceitem" and rerun the upgrade command, but it still errors the same.

    Any ideas?  Thanks in advance.

    [OWSTIMER] [MossSiteSequence] [INFO] [6/12/2010 12:37:52 AM]: SPSite Url=https://domain.com/site

    [OWSTIMER] [MossSiteSequence] [ERROR] [6/12/2010 12:37:52 AM]: Action 13.0.1.0 of Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence failed.

    [OWSTIMER] [MossSiteSequence] [INFO] [6/12/2010 12:37:52 AM]: SPSite Url=https://domain.com/site

    [OWSTIMER] [MossSiteSequence] [ERROR] [6/12/2010 12:37:52 AM]: Exception: A duplicate content type name "Resource" was found.

    [OWSTIMER] [MossSiteSequence] [INFO] [6/12/2010 12:37:52 AM]: SPSite Url=https://domain.com/site

    [OWSTIMER] [MossSiteSequence] [ERROR] [6/12/2010 12:37:52 AM]:    at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionFieldsAndContentTypes(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce)

     

     

     

     

    These errors are causing the content database to prevent complete upgrade.

     

    Content Database

    Database is up to date, but some sites are not completely upgraded.

    Tuesday, June 15, 2010 8:52 PM

Answers

  • Figured out that the Resources field that was giving me this problem was there becuase I had the Application Template Types feature activated on the site in question.  When I deactivated that feature and ran the SQL query again the Resource column went away.  Orginally had this setup becuase we were going to use one of the Server Templates but then decided against it.  Running through the upgrade again and will find out if this solves the problem.

    • Marked as answer by millertime78 Tuesday, July 13, 2010 4:59 PM
    Thursday, July 01, 2010 9:51 PM

All replies

  • Do you happen to use CorasWorks? I have this same error and I believe it is from a custom content type that they use. Unfortunately I have a separate issue where I'm unable to get to any of my sites at all (500 error) except the admin site after the upgrade, so I am very limited in my troubleshooting options at the moment. If I can get to the sites then I can fix the resource issue and let you know the steps.
    Friday, June 18, 2010 1:24 PM
  • We don't.  I am certain the site(s) were setup with Designer 2007 originally. 

    Is there a way to have more details documented in the upgrade process?

    Are there hidden content types?

    Friday, June 18, 2010 4:45 PM
  • You might want to check you recycle bin for left overs. I think that I have seen similar behavior when something is deleted and there is another copy still on the site. The upgrade may not differentiate the recycle bin version. If you forcibly empty the bin you might succeed.


    Steve Hotchkiss
    Friday, June 18, 2010 6:45 PM
  • Excellent idea, but no success.  I deleted the first and second stage recycle bins and tried the upgrade command again

    • psconfig -cmd upgrade -inplace v2v -passphrase ********* -wait

    Error persists.

    Any other ideas out there?

     

    Friday, June 18, 2010 10:28 PM
  • Ok, I'm definitely having the same issue as you. It's a duplicate content type of name "Resource" and it lists EVERY site within my web in the error log, but I don't see the content type anywhere. Here's the full error.

     

    [PSCONFIG] [SPSiteWssSequence2] [ERROR] [6/21/2010 3:47:14 PM]: Feature upgrade incomplete for Feature 'PublishingSite' (Id: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') in Site 'https://domain.com'. Exception: A duplicate content type name "Resource" was found.

    Monday, June 21, 2010 8:02 PM
  • This is all I've found remotely about this issue:

     

    http://technet.microsoft.com/en-us/library/cc288476.aspx

    UI changes

    Changes to the user interface (UI), such as the addition of the Fluent UI (also known as the ribbon) or adherence to XHTML standards, can cause problems in sites. Occasionally, custom elements (such as a content type) may have a name that conflicts with a name in the new version. You may also have pages that must be reverted to the standard site definition, or large lists for which you have to create new views.

    For more information about how to review UI issues in sites, see Verify upgrade and review upgraded sites (SharePoint Foundation 2010).

    In the upgrade log files, you may see errors such as the following:

    • Failed to activate site collection features on site Site Url. Exception: A duplicate content type name "name" was found.

      This error indicates that a 3rd party "Summary Info" content type was added to the specified site in o12 and during upgrade to o14 it name conflicts with our out of the box "Summary Info" content type. Delete or rename the 3rd party content type in the specified site to something other than "Summary Info" and re-run upgrade.
    Monday, June 21, 2010 8:06 PM
  • Do you have content and structure reports running? I noticed that my list has two columns each with the name Resource Id. I know it's not just "Resource" but it seems odd that you would be able to have two columns with the same name within a single list. This list only exists in my top-level site as well, so it's a long shot.
    Monday, June 21, 2010 8:15 PM
  • Do me a favor and run this against your Sql content db and let me know if anything gets returned.

    select

     

    * from dbo.ContentTypes

    where

     

    ResourceDir like '%Resource%'

    This is what I got. I don't know what it means yet, but I'm going to research some more.

    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2001 0 0 16 NULL Resource Reservation 1
    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2002 0 0 16 NULL Resource 1
    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2003 0 0 16 NULL Resource Type 1

    Monday, June 21, 2010 8:23 PM
  • Another thought. Do you have a site column with the name Resource under an RER Columns group on this page?

    https://domain.com/_layouts/mngfield.aspx

     

    Monday, June 21, 2010 8:27 PM
  • Do you have content and structure reports running? I noticed that my list has two columns each with the name Resource Id. I know it's not just "Resource" but it seems odd that you would be able to have two columns with the same name within a single list. This list only exists in my top-level site as well, so it's a long shot.


    I saw the same thing in my setup... I went ahead (before your last post on the query) and renamed one of the content types "ResourceType" and reran the upgrade successfully.  I don't necessarily think this is a solution, but it did get me past the upgrade errors.

    I'll take a look at the SQL Query you provided and postback the results.  Thanks !

    Tuesday, June 22, 2010 1:44 AM
  • This is the only area that had the "Resource" content type... but keep in mind that I renamed it to "Resource Type", so that is what is represented below.  But no duplicate is showing in this view  (the _layouts/mngfield.aspx" page)

    Core Document Columns

       Author Single line of text sitename
       Category Single line of text sitename
       Comments Multiple lines of text sitename
       Contributor Multiple lines of text sitename
       Copyright Single line of text sitename
       Coverage Single line of text sitename
       Date Created Date and Time sitename
       Date Modified Date and Time sitename
       Date Picture Taken Date and Time sitename
       Format Single line of text sitename
       Keywords Multiple lines of text sitename
       Last Printed Date and Time sitename
       Publisher Single line of text sitename
       Relation Multiple lines of text sitename
       Resource Identifier Single line of text sitename
       Resource Type Single line of text sitename
    Tuesday, June 22, 2010 1:52 AM
  • Do me a favor and run this against your Sql content db and let me know if anything gets returned.

    select

     

    * from dbo.ContentTypes

    where

     

    ResourceDir like '%Resource%'

    This is what I got. I don't know what it means yet, but I'm going to research some more.

    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2001 0 0 16 NULL Resource Reservation 1
    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2002 0 0 16 NULL Resource 1
    5596E71B-DD80-4FC7-B3FA-73A818987722 1  0x01005D991708656A4C64AD394B3E31D4CC2003 0 0 16 NULL Resource Type 1


    I know this is a mess... but there does appear to be a duplicate "Resource" reference in the results...  keep in mind, I renamed the content type "Resource Type" from "Resource" which was probably the duplicate value.

    700D1856-747B-4F52-A752-014E587B4B4C 1 clients/ACME 0x01004C9F4486FBF54864A7B0A33D02AD19B1 1 0 1858 <ContentType ID="0x01004C9F4486FBF54864A7B0A33D02AD19B1" Name="ResourceItem" Group="$Resources:core,GroupWork_Content_Types;" Description="$Resources:core,ResourceDescription;" Version="1" FeatureId="{695b6570-a48b-4a8e-8ea5-26ea7fc1d162}"><Folder TargetName="_cts/Resource" /><FieldRefs><FieldRef ID="{c042a256-787d-4a6f-8a8a-cf6ab767f12d}" Name="ContentType" /><FieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" Required="TRUE" /><FieldRef ID="{3f155110-a6a2-4d70-926c-94648101f0e8}" Name="Description" /></FieldRefs><XmlDocuments><XmlDocument NamespaceURI="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms">PEZvcm1UZW1wbGF0ZXMgeG1sbnM9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC92My9jb250ZW50dHlwZS9mb3JtcyI+PERpc3BsYXk+RmFjaWxpdGllc0Zvcm08L0Rpc3BsYXk+PEVkaXQ+RmFjaWxpdGllc0Zvcm08L0VkaXQ+PE5ldz5GYWNpbGl0aWVzRm9ybTwvTmV3PjwvRm9ybVRlbXBsYXRlcz4=</XmlDocument></XmlDocuments></ContentTypeResource 1 NULL

    700D1856-747B-4F52-A752-014E587B4B4C 1 clients/ACME 0x01005D991708656A4C64AD394B3E31D4CC2001 0 0 16 NULL Resource Reservation 1 NULL
    700D1856-747B-4F52-A752-014E587B4B4C 1 clients/ACME 0x01005D991708656A4C64AD394B3E31D4CC2002 0 0 16 NULL Resource 1 NULL
    700D1856-747B-4F52-A752-014E587B4B4C 1 clients/ACME 0x01005D991708656A4C64AD394B3E31D4CC2003 0 0 16 NULL Resource Type 1 NULL
    700D1856-747B-4F52-A752-014E587B4B4C 1 clients/ACME 0x0100CA13F2F8D61541B180952DFB25E3E8E4 0 0 16 NULL Resource Group 1 NULL

    Tuesday, June 22, 2010 1:58 AM
  • Glad you got yours working.  Unfortunately, mine is already called Resource Type under the Core Document Columns group. However, I had another Resource Type column listed under another group and I'm wondering if it didn't like having two column types with the same name and decided to just drop the second word on one of them to try and make them unique during the conversion. I've renamed the ones under the other group and will attempt the upgrade again. I'll keep banging out responses on here until I get mine working too in case someone else has the same issue as me and your solution doesn't work for them as well.

    Tuesday, June 22, 2010 12:09 PM
  • Well, that didn't seem to make any difference.
    Tuesday, June 22, 2010 1:19 PM
  • I have a ticket in with MS support and will post the results after it is resolved.
    Tuesday, June 22, 2010 5:57 PM
  • Have you heard anything about this error?  I'm getting the exact same think.  Looks like it's only happening on one site collection for me.  All other sites upgraded without an error.

    Thursday, July 01, 2010 5:23 PM
  • I used the SQL query to find the duplicates, but one of the listed CT was in the _hidden group.  So, I went into the settings then of another content type (any of the default ones work), then selected Name, description and group, replaced the bolded part of this URL with ID of the hidden type and changed the name to Resource Hidden. 

    http://portal/managedpath/department/_layouts/ctypedit.aspx?ctype=0x00A7470EADF4194E2E9ED1031B61DA088403

    That got me through the upgrade; cleared out the last of my errors and warnings! 

    Thanks for posting the query!

    David

    Thursday, July 01, 2010 7:27 PM
  • Figured out that the Resources field that was giving me this problem was there becuase I had the Application Template Types feature activated on the site in question.  When I deactivated that feature and ran the SQL query again the Resource column went away.  Orginally had this setup becuase we were going to use one of the Server Templates but then decided against it.  Running through the upgrade again and will find out if this solves the problem.

    • Marked as answer by millertime78 Tuesday, July 13, 2010 4:59 PM
    Thursday, July 01, 2010 9:51 PM
  • Figured out that the Resources field that was giving me this problem was there becuase I had the Application Template Types feature activated on the site in question.  When I deactivated that feature and ran the SQL query again the Resource column went away.  Orginally had this setup becuase we were going to use one of the Server Templates but then decided against it.  Running through the upgrade again and will find out if this solves the problem.

    I think you have it nailed.  Reply back with your results please.  Thx.
    Thursday, July 01, 2010 10:11 PM
  • I to have the same problem.  However I have 2 content types named Resource.  One of them, I cannot access using the guid (eg. http://portal/managedpath/department/_layouts/ctypedit.aspx?ctype=0x00A7470EADF4194E2E9ED1031B61DA088403 ) The other I can which turns out to be the _hidden one, which Ive renamed and when I run the SQL query again,  It still shows up as being Resource.

    So its possible the first one is corrupt or something

    One possibility is I may get one of our DB admins to remove it via SQL

    Ive got a feeling it's one of the features we have activiated, Ill deactivate some and see how I go.  Howd you guys go with the ticket through to MS?

     


    Monday, July 05, 2010 5:41 AM
  • *Update*

    Ok So I went into SQL,  and I ran the query,

    select

    * from dbo.ContentTypes

    where

    ResourceDir like '%resource%'

    Which returned 2 content types which had the name Resource so then I checked in the content type gallery which didnt show any content types of the name Resource, so I accessed this by clicking on another content type, and in the URL I replaced the guid with the guid of both Resource content types which came up in the SQL query.  One showed up as _hidden and the other came up as file not found.

    I used the guid from the Resource content type which came up with file not found. and ran this query

    DELETE FROM ContentTypes

    WHERE     (ContentTypeId = 0x01004C9F4486FBF54864A7B0A33D02AD19B1)

    I Re-ran the upgrade, Open SharePoint Powershell Management console, type in Upgrade-SPContentDatabase Identity: <WSS_Content_Database> and A for Yes to All,  and it worked 100%

    I hope this helps a few of you out.  This was done in my development environment, which I suggest to do with yours as well ;)

    • Proposed as answer by Troy_xlr8 Monday, July 05, 2010 7:09 AM
    Monday, July 05, 2010 6:17 AM
  • *Double Update*

    Once successfully updated,  my site actions would not enable me to use the new User Interface look and feel.  I had to go to Central Admin and Enable Enterprise Features on my site.

    Also if that doesnt work,  run Get-SPSite http://sitename | Foreach{$_.UIVersionConfigurationEnabled=1;}

     

    I hope this helps everyone!   Also feel free to recommend me for a MVP status!  haha ;)

    Monday, July 05, 2010 7:14 AM
  • Disabling the Applications Template Types worked for me.
    Tuesday, July 06, 2010 2:45 PM
  • I renamed the Resource content type to Group Work Resource as referenced on this site, reran the upgrade and it cleared out all my errors as well.

     

    http://office.microsoft.com/en-us/sharepoint-foundation-help/use-content-types-to-manage-content-on-a-sharepoint-site-HA010375560.aspx

     

    Tuesday, July 20, 2010 6:28 PM
  • deactivate feature applicationtemplatecore.wsp  and run upgrade again it work!!!
    Nok
    Friday, October 29, 2010 5:10 AM
  • I had the exact same problem and resolved it only with the help of an MSDN support call.

    Long story short is you will get this it's because you most likely have the Publishing Infrastructure activated as well as on any sites you have the Publishing Feature activated.

    Don't disable any features or retract any solutions as some may suggest - it will resolve those errors but cause others.  I tried disabling Publishing and also the applicationtemplatecore.wsp and it just caused more headaches.

    What you have to do is to rename all content type columns from "Resource"  to something else.  The catch is that there are some "Resource" columns that exist before the conversion in MOSS2007 that you need to fix - then during the upgrade other "Resource" colums are created so after the conversion fails, you need to go in and delete them as well, then rerun the upgrade.

    Took too many hours with MSFT to resolve this one, but I'm glad it's behind me.

     

    • Proposed as answer by sema12 Tuesday, March 01, 2011 12:04 AM
    Tuesday, January 11, 2011 11:47 PM
  • xlr8,

     

    that was the exact solution - all the way to the GUID itself.  Well done.

     

    I love you.

    Friday, January 21, 2011 10:57 PM
  • Hey Tewwor, how you rename all content type columns from "Resource"  to something else? you do it from database or from a site content types?

     

    thanks

    Tuesday, March 01, 2011 12:06 AM
  • You do not have to rename any column. Just go to the sitecollection features area for all the sites that are listed in the log file with the "Resources" error and deactivate 'Fields and Content Types for the Windows SharePoint Services Application Templates' feature. Now run the upgrade-spcontentdatabase and it should succeed.


    Dheepa
    Tuesday, March 29, 2011 7:41 PM
  • I can't believe this wasn't marked as helpful. I couldn't find anything about this error anywhere. Good to know Microsoft didn't catch this conflict with one of their own customizations. Sharepoint is just dying on the vine, isn't it? I don't even know why we are upgrading. They only thing they want is to make it look better. A week of my time when they could have had someone do a nice master page.

    Friday, June 15, 2012 12:31 AM
  • the issue is resolved

    I am very thirsty for knowledge, specifically its about technology. I go into the printer at this time

    Friday, June 15, 2012 4:13 AM