Caroline, what is the extent of this content type? How many lists is it active 
on and how many pages might be present?

I've hit this before when content types were created at the list level during 
development before being converted to a feature for development. Was content 
migrated by any chance?

Anyway, steps we used to fix follow. Someone may recommend alternatives or 
correct some steps.

Once you've located all the Page libs where the content type is present you'll 
need to:

1.    Publish a major version of all pages.

2.    Disable check-out, versioning and any approval workflows on the library.

3.    Change all pages to use a different content type (and associated layout 
page if a custom one is present).

4.    Delete the problematic content type from the list.

5.    Add it back again from the "Add from existing site content types" link.

6.    Try to create a new page from the content type. If you're successful then 
you can change the content type back on all the pages.

7.    Re-enable check-out and versioning.
There's probably a way to do this programatically or with PowerShell but 
someone else would have to help with that. :)

You may also hit problems with previous Page versions still using the content 
type. Hopefully steps 1

Regards,

Paul

--
Online Developer/Administrator,
ICT Projects Team
CEO Sydney

From: [email protected] [mailto:[email protected]] On Behalf Of 
Specker, Caroline
Sent: Thursday, 20 January 2011 8:31 AM
To: ozMOSS
Subject: RE: A duplicate name "[content type name]" was found - MOSS 2007 
[SEC=UNOFFICIAL]

Ishai,

I forgot to mention that I also did try to deactivate/reactivate the feature 
with the content types and did get the same error.  Which is just what you are 
saying would happen.

Caroline

________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of 
Ishai Sagi
Sent: Wednesday, 19 January 2011 6:52 PM
To: ozMOSS
Subject: Re: A duplicate name "[content type name]" was found - MOSS 
2007[SEC=UNOFFICIAL]
This happens when you have a list level content type (as opposed to a site 
level content type) with a name that is the same as a site level content type. 
When that happens, trying to deploy content types as part of a feature will 
fail with the error you described - even if your feature does not have the 
conflict itself - its enough that there is a conflict in the site.

I need to report this to MS...



Ishai Sagi
Solution Architect and Director
Microsoft SharePoint MVP, MCTS
Extelligent Design
SharePoint Consulting, Training and Products
Mobile: 04-88-789786
Web: www.extelligentdesign.com<http://www.extelligentdesign.com/>
Email: [email protected]<mailto:[email protected]>
Blog: www.sharepoint-tips.com<http://www.sharepoint-tips.com/>
[http://lh6.ggpht.com/_ODZmNiPJO0M/TKvaSmU07VI/AAAAAAAAAtw/ezwzn2I6SXI/s400/Extelligent%20logo%20lrg.jpg]


On Wed, Jan 19, 2011 at 4:18 PM, Specker, Caroline 
<[email protected]<mailto:[email protected]>> 
wrote:
Has anyone encountered this error before:  A duplicate name "[content type 
name]" was found.

It occurs when I try to create a new page that uses a particular page layout.  
I have not had anything to do with developing the site, so I don't know if any 
manual changes to content types have been made.

Can anyone recommend a good place to starting looking to find a resolution to 
this?

The logs are as follows:

A critical error occurred while creating a PublishingPage through 
PublishingPageCollection.Add(string, PageLayout). 
Microsoft.SharePoint.SPException: A duplicate name "content type name" was 
found.     at Microsoft.SharePoint.SPContentTypeCollection.Add(SPContentType 
contentType)     at 
Microsoft.SharePoint.Publishing.PublishingPageCollection.ForceAddContentTypeToList(SPContentType
 contentTypeToAdd)     at 
Microsoft.SharePoint.Publishing.PublishingPageCollection.<>c__DisplayClass5.<Add>b__0()
     at 
Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean 
fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock 
catchBlock, FinallyBlock finallyBlock)
01/05/2011 13:46:42.60  w3wp.exe (0x09FC)                        0x0BFC ULS 
Logging                    Unified Logging Service        8pbf Medium   Not 
reporting 8gym to Watson because the appropriate timespan hasn't passed
01/05/2011 13:46:42.60  w3wp.exe (0x09FC)                        0x0BFC CMS     
                       Publishing                     8gyn Unexpected A 
critical error occurred while creating PublishingPage 'test.aspx' through 
PublishingPageCollection.Add(string, PageLayout). Exception A duplicate name 
"content type name" was found.
01/05/2011 13:46:42.60  w3wp.exe (0x09FC)                        0x0BFC CMS     
                       Publishing                     6ot3 High     CreatePage: 
exception A duplicate name "content type name" was found. at    at 
Microsoft.SharePoint.SPContentTypeCollection.Add(SPContentType contentType)     
at 
Microsoft.SharePoint.Publishing.PublishingPageCollection.ForceAddContentTypeToList(SPContentType
 contentTypeToAdd)     at 
Microsoft.SharePoint.Publishing.PublishingPageCollection.<>c__DisplayClass5.<Add>b__0()
     at 
Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean 
fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock 
catchBlock, FinallyBlock finallyBlock)     at 
Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(ULSTagID 
tagID, ULSCat categoryID, String output, Boolean fRethrowException, TryBlock 
tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Micr...
01/05/2011 13:46:42.60* w3wp.exe (0x09FC)                        0x0BFC CMS     
                       Publishing                     6ot3 High     
...osoft.SharePoint.Publishing.PublishingPageCollection.Add(String name, 
PageLayout layout)     at 
Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.NewPageItemSave(String
 pageName, PageLayout pageLayout)
01/05/2011 13:46:42.60  w3wp.exe (0x09FC)                        0x0BFC Windows 
SharePoint Services    General                        8nca Verbose  Application 
error when access /_layouts/CreatePage.aspx, Error=A duplicate name "content 
type name" was found.   at 
Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.HandleUnexpectedException(PublishingPage
 newPage, Exception exception)     at 
Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.NewPageItemSave(String
 pageName, PageLayout pageLayout)     at 
Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.CreateStandardPage(String
 pageName)     at 
Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.ButtonCreatePage_Click(Object
 sender, EventArgs e)     at System.Web.UI.WebControls.Button.OnClick(EventArgs 
e)     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String 
eventArgument)     at System.Web.UI.WebControls.B...
01/05/2011 13:46:42.60* w3wp.exe (0x09FC)                        0x0BFC Windows 
SharePoint Services    General                        8nca Verbose  
...utton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String 
eventArgument)     at 
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, 
String eventArgument)     at 
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)     at 
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, 
Boolean includeStagesAfterAsyncPoint)

Thanks
Caroline

*************************************************************************
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
*************************************************************************

_______________________________________________
ozmoss mailing list
[email protected]<mailto:[email protected]>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


*************************************************************************
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential.  If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information.  If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.

The Commonwealth does not warrant that any attachments are free
from viruses or any other defects.  You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.

The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
*************************************************************************
_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to