Tuesday, April 17, 2007

The specified name is already in use.

I was working on a content deployment job in MOSS WCM site when I receive the below error messages.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 17/04/2007
Time: 11:54:25 AM
User: N/A
Computer: ComputerName
Description:
The Execute method of job definition Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition (ID 1afc019a-3e27-43a8-8ddd-2555d397e34c) threw an exception. More information is included below.

The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Date: 17/04/2007
Time: 11:54:25 AM
User: N/A
Computer: ComputerName
Description:
Publishing: Content deployment job failed. Error: 'Microsoft.SharePoint.SPException: The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name. ---> System.Runtime.InteropServices.COMException (0x81020012): The specified name is already in use.

A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Use your browser's Back button, and type a new name.
at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.CreateListOnImport(String bstrUrl, Guid& pguidListId, String bstrTitle, String bstrDescription, Int32 lTemplateID, String bstrFeatureId, Guid guidRootFolderId, Int64 llFlags, Int32 iVersion, Int32 iAuthor, String bstrFields, String bstrContentTypes, String bstrImageUrl, String bstrEventSinkAssembly, String bstrEventSinkClass, String bstrEventSinkData, Guid guidDocTemplateId, String bstrViews, String bstrForms, Boolean bCompressedSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.CreateList(SPWeb parentWeb, Dictionary`2 listMetaData, Boolean usingPublicSchema)
at Microsoft.SharePoint.Deployment.ListSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
at Microsoft.SharePoint.Deployment.SPImport.Run()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.DoImport()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.ExecuteJob()
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJob.Run(Boolean runAsynchronously)
at Microsoft.SharePoint.Publishing.Administration.ContentDeploymentJobDefinition.Execute(Guid targetInstanceId)'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


I have a authoring and production environment in same farm environment. I created a path and Job to migrate content from my authoring publishing site to production publishing site. The production site was created using the publishing template.
To fix above problem, I had to delete the production site and recreate it using the blank site template.

Its all working fine now….

12 Comments:

At 4:07 AM, Anonymous Anonymous said...

Use the error log to narrow down to what list it was complaining about. Delete that list from the production server and run a deploy (I did an incremental). This fixed it from me.

 
At 12:53 AM, Anonymous Anonymous said...

Hi Gayan -

Thanks for your post. I was having the same issue and your recommendation did the trick!

 
At 8:05 AM, Blogger Pablo Fung said...

Stupid bug from Microsoft. If on the authoring server you have a file say test.aspx and you delete it, and later add it again, the content deployment will give you this error. So the moral is, don't delete content and recreated it because the developers from Microsoft think this cannot happen.

 
At 8:08 AM, Blogger Pablo Fung said...

Actually the best solution is to do a quick deploy of these items. The error appears if you do an incremental deployment. Quick deploy does not have this bug.

 
At 1:12 AM, Anonymous SPFrank said...

Quick deployment does have this bug. I have tried several times to narrow this down. I'm inteseted in the comment by anonymous on using the error log to narrow down the problem list or library. What error log are you refering too. I have review what I think are all the logs OS Event, SP logs and all refer to the exception but don't document the problem list or library.

 
At 2:26 AM, Anonymous Anonymous said...

Has this been fixed with Service Pack 1?

 
At 1:32 PM, Anonymous Anonymous said...

This has not been properly fixed in SP1.

If you haven't installed it yet, don't. It's not worth the risk unless it's absolutely necessary and it won't fix this deployment bug.

 
At 12:12 PM, Blogger Matt said...

Gayan's fix worked for me as well. It is strange to me being a Newbie that you can't create the site using the template that is was using previously... but not going to complain... Thanks Gayan!

 
At 9:33 AM, Anonymous Anonymous said...

Content Deployment is a joke - if I had to choose between root canal and Content Deployment, I'd choose root canal.

 
At 9:42 AM, Blogger qt said...

Yep, root canal first. However creating a new collection based on blank template worked for me. Then when it was deployed it implemented the template that was needed. Go figure. Thanks a million.

 
At 11:48 PM, Anonymous Anonymous said...

http://vanderbiest.org/blog/2009/10/13/deleting-splist-from-sharepoint-is-not-always-working/

has a possible solution for this problem.

 
At 5:57 PM, Anonymous electronic signature software said...

Excellent! Thanks for this - I've been looking at this feature for ages. Followed your instructions and it works a treat!

 

Post a Comment

<< Home