locked
stsadm Import error : FatalError: Member 'FileValue' was not found RRS feed

  • Question

  • Hi all,

    I'm trying to move a site from one sharepoint 2007 installation to another.

    I've used stsadm export to create a backup file, and am attempting to use stsadm to restore the site to a new application and site collection.

    The import works partially (I have half a site when it's finished) but fails part of the way through with the below fatal error:

    [9/14/2013 11:39:51 PM]: Importing File Version 0.1
    [9/14/2013 11:39:51 PM]: FatalError: Member 'FileValue' was not found.
       at System.Runtime.Serialization.SerializationInfo.GetElement(String name, Type& foundType)
       at System.Runtime.Serialization.SerializationInfo.GetString(String name)
       at Microsoft.SharePoint.Deployment.FileSerializer.UploadFileData(Object fileOrListItem, SPWeb web, Guid id, String fileUrl, Boolean fileExistsInDb, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, MetaInfoHandler metaInfo, SPImportSettings settings, StreamingContext context, ImportObjectManager objectManager)
       at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFile(Object fileOrListItem, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, Boolean isFirstVersion, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context, ImportObjectManager importObjectManager)
       at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileVersion(Object fileOrListItem, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, String version, Boolean isFirstVersion, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context, ImportObjectManager importObjectManager)
       at Microsoft.SharePoint.Deployment.ListItemSerializer.AddOrUpdateDoclibItemVersion(SerializationInfoHelper infoHelper, SPListItem& listItem, SPWeb web, Guid newId, String& listItemServerRelativeUrl, Boolean bIsPublish, Boolean exists, String version, Boolean isFirstVersion, Boolean isLastVersion, StreamingContext context, ISurrogateSelector selector, ImportObjectManager objectManager)
       at Microsoft.SharePoint.Deployment.ListItemVersionSerializer.AddListItemVersion(SPWeb web, SPListItem listItem, Guid newId, Boolean editHistory, Boolean existsInDb, Boolean isFirst, Boolean isLast, Boolean isDocLib, StreamingContext context, XmlElement listItemData, SPImportSettings settings, ImportObjectManager objectManager, SerializationInfoHelper listItemInfoHelper, String& listItemServerRelativeUrl, ISurrogateSelector selector)
       at Microsoft.SharePoint.Deployment.ListItemSerializer.UpdateListItemVersionData(SerializationInfoHelper infoHelper, SPWeb web, SPListItem& listItem, Guid newId, Boolean existsInDb, Boolean isDocLib, String& listItemServerRelativeUrl, StreamingContext context, SPImportSettings settings, ISurrogateSelector selector)
       at Microsoft.SharePoint.Deployment.ListItemSerializer.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()

    Can anyone shed any light on what this means? It's a little cryptic.

    Thanks in advance for any help, much appreciated.


    Sunday, September 15, 2013 12:53 AM

Answers

  • We actually managed to fix this.

    In case anyone else has a similar issue, here's what we did:

    During the import, it would always fail at the same point. We managed to figure out which exact file it was failing on each time. Using the manifest.xml that's produced with the stsadm -o export, we mapped the .dat filename to the actual filename in our live Sharepoint environment.

    The offending files were 0 byte .txt files - we found around 7 of these and removed them. After this we re-ran the import and everything worked Ok.

    • Marked as answer by AcousticStories Wednesday, September 18, 2013 10:08 AM
    Wednesday, September 18, 2013 10:08 AM