Wednesday, March 26, 2008

SharePoint MOSS 2007: Troubleshooting content deployment

I've already given a rough overview of how to configure content deployment in MOSS 2007 here

http://bryansgeekspeak.blogspot.com/2008/03/sharepoint-moss-2007-deploying-content.html

and I've also covered the topic of enabling SSL in the central admin here:

http://bryansgeekspeak.blogspot.com/2008/03/sharepoint-moss-2007-deploying-content.html

which gives you the ability to setup content deployment over SSL, so you can securely deploy content from your staging farm to a production farm.

Deployment job hangs on status "Preparing"

In my tests, I've run into situations where I setup a path, then a job, but when I run the job the status hangs at the "Preparing" state and nothing ever happens. I'm not sure exactly what causes this issue, but I've managed to get around it doing a combination of the following:


  1. Cancel all currently running jobs

  2. Login ot the "target" server (produciton) and confirm in the Central Admin that the settings in "Operations->Content Deployment Settings" are correct and save them again.

  3. Check the "Temporary Files" folder set in the "Content Deployment Settings" page. Delete any existing files/folders there. Check the permissions on that folder. It should allow full control to the user described in the source server's central admin application pool (the user account your source server's central admin will use to run the deployment job)

  4. Delete any existing jobs and paths on the source server, then recreate them. This confirms that you can still hit and authenticate to the central admin of the target server.

  5. Setup a new job and run a test job. It should return success or failure within minutes. if it takes longer than 10 minutes, cancel the job and recheck everything.



I'll post more details about this issue when I learn more.



Deployment Failed: The specified name is already in use.

Here is the situation:


  • Site on staging server has data, ready to push to live

  • Staging server has a valid configured path and job (can be set to changed data only or all data, same error for both)

  • Live server has a web application and a default Site Collection configured (no custom data)

  • Live server is peroperly configured to recieve incoming jobs



When I run the job, I get this error:


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.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()

I'm going to try using the backup/restore method described in an earlier article:

http://bryansgeekspeak.blogspot.com/2008/02/managing-moss-2007-backup-and-restore.html

as my "baseline" on production. Then I'll try deploying any future changes via the Central Admin. Hopefully that will work...I think thats an acceptable work around.

No comments: