locked
Content deployment problem RRS feed

  • Question

  • An incremental content deployment job that has been working for years between two SharePoint 2007 farms has stopped working. There seems to be a problem with one of the sub-sites, but excluding it from the deployment job does not solve the problem and as far as the logs say, some parts of that site are still being exported and imported (unsuccessfully).

    The farms are both post SP3 but not exactly the same version. There also seems to be a slight difference between a specific list in the root sire between the two sites. I am sure the first difference has been around for a long time, the second one I am not sure but I am quite positive the error in the import process does not refer to the list in question.

    This is the relevant log fragment:

    [3/16/2015 8:38:44 PM]: Verbose: Updating field ContentTypeId.
    [3/16/2015 8:38:44 PM]: Verbose: Updating field _HasCopyDestinations.
    [3/16/2015 8:38:44 PM]: Verbose: Updating field _CopySource.
    [3/16/2015 8:38:44 PM]: FatalError: Object reference not set to an instance of an object.
       at Microsoft.SharePoint.Deployment.ContentTypeSerializer.GetContentType(SPContentType sourceContentType, ImportObjectManager importObjectManager, Boolean isParentSystemObject)
       at Microsoft.SharePoint.Deployment.ContentTypeSerializer.ProcessContentType(SPContentType sourceContentType, String contentTypeXml, ImportObjectManager importObjectManager, Boolean IsParentSystemObject)
       at Microsoft.SharePoint.Deployment.ContentTypeSerializer.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()
    [3/16/2015 8:38:44 PM]: Progress: Import Completed.
    [3/16/2015 8:38:44 PM]: Finish Time: 3/16/2015 8:38:44 PM.
    [3/16/2015 8:38:44 PM]: Completed with 0 warnings.
    [3/16/2015 8:38:44 PM]: Completed with 1 errors.

    Changing the site selection or creating a new job with just the root site selected did not solve the problem either.
    We currently cannot run a full deployment job because of disk space limitations.

    Can we do anything besides creating a new content database and starting over?

    Monday, March 16, 2015 6:47 PM

Answers

  • The problem was worked around by removing the offending site from the source. Not a great solution, but it works...
    Thursday, March 26, 2015 12:32 PM

All replies