Our main WSS 3.0 site (not service packed) has a SQL2005 back-end. All appears to be OK, however...it is now necessary to "archive" the contents of a sub-site to media and store it for historical purposes. The export command (stsadm -o export) runs without any problem. To test the validity of the exported data, a test WSS site has been created on a temporary server (running WSS with a SQL Express backend) and attempts have been made to import (stsadm -o import -url http://vsrv09/Operations/GEOC3_Temp -filename %~dp0\GEOC3-WSSSP2Ver\geoc3.dat -updateversions 2 -nofilecompression) the sub-site have failed. The error reported in the import.log is: [7/14/2010 10:57:05 AM]: 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() [7/14/2010 10:57:05 AM]: Progress: Import Completed. [7/14/2010 10:57:05 AM]: Finish Time: 7/14/2010 10:57:05 AM. [7/14/2010 10:57:05 AM]: Completed with 0 warnings. [7/14/2010 10:57:05 AM]: Completed with 1 errors. The WSS sites are configured exactly the same, created using the same exe, the same templates have been installed. The original WSS server was backed up using stsadm -o backup and this was successfully restored on the test WSS site. WSS SP2 was applied to the test site and the sub-site was successfully exported from the test site. An attempt was made to import the sub-site onto a 2nd temporary server running WSS with SP2 failed with the same error. Some sub-sites have successfully exported and imported onto the temporary servers. The only difference I can see is the "size" of the sub-sites. All servers are running Windows Server 2003 Any assistance in overcoming this fatal error would be appreciated!

Hello, Is it possible to take export of the file once again? if so, please take an export with extension as '.cmp' to filename (e.g -filename E:\tempBackup\GEOC3.cmp). Then copy all the GEOC3 exported files (files would be like GEOC3.cmp, GEOC31.cmp, GEOC32.cpm etc.) onto the temperory server in some folder Then make sure that the site/subsite http://vsrv09/Operations/GEOC3_Temp has a template "blank site" or same as the exported site. If you have any queries or if I am not understandable then please let me know.. :-) Hope this help, Regards, Rohan

Hi, Thanks for this, have tried your suggestion and unfortunately the aforementioned error was produced. I have successfully exported and imported other sub-sites using the same syntax without any problem. This error seems to be occurring with the one sub-site, the only difference I have noticed is the size of the sub-sites. I've noticed the subsite concerned has itself got sub-sites. Would this cause any problems? Any other suggestions would be really welcome!! Dave

Hi, No, the subsites for this subsite should not be an issue. Also as you have mentioned that you are able to backup/restore the same site collection, so its definately not an issue with long URLs. Can you please confirm that the features activated on the source and destination top level sites (Site collections) are same. Also please check if there are any customizations on the subsite or its content. btw, what is the collective size of all the export files for this subsite? Regards, Rohan

Hi, Yeah, I've noticed to do this type of work, each WSS server needs to be exactly the same, including templates etc. The config of the two test sites are identical, effectively they were constructed from the installation exe and nothing fancy done (effectively left at the default). A couple of MS templates have been installed (bugdatabase and knowledgebase). A couple of other templates for company use were installed onto the test servers before exporting/importing any data. Otherwise, as far as I'm aware nothing else should have changed. The exports/imports have been done using the same domain admin account. The size of the folder containing the exported files is 2.42GB and contains some 5,208 files. It really has got to head-scratching time so any ideas are gratefully received! Thanks, Dave PS - I've just successfully exported a different sub-site (some 2.1GB) and imported it onto a different server. So, why the fatal error?

Hello Dave, Is it possible to import the subsite in same environment on some other subsite under different site collection? (not on the temperory server). By this, we can actually identify the scope that if this issue is because of Site and its content or because of any server related issues. Do you have any third party tools for the site content migration? (e.g Metalogix etc.) A while ago, we had a kind of similar issue in my previous organization. Later, after lot of trial and errors, we identified that the issue was with the .pptx files. And because of these files, we were unable to import tyhe site content to the new site. So we copied those files locally and then removed from library; then export - imported the site and then uploaded those files again to the new and old site. I am not sure how much this is applicable in your case, but if possible, we can give a try. Make sure you take the full site backup before performing this and necessary client/internal approvals... :-) Regards, Rohan

Hi Rohan, I'll create a new site collection and do as you suggest, it could take a while for me to do this. Nope, no 3rd party tools, I've been using stsadm throughout. I appreciate the suggestion of finding the files etc. One of the beauties of WSS is the ability to retain versions of documentations. Unfortunately, all the versions need to be retained so identifying the file then its version could be a little time consuming though it could be something to be considered. I'll get back to you when I can. Thanks very much!!!!

Hi Rohan, Thanks for your patience. I've done what you have suggested (ie a new site collection on the original server). A fatal error occurred at the same place, with a different error: [7/20/2010 11:17:20 AM]: Progress: Importing ListItem /sites/Test/GEOC3/Configuration?id=876. [7/20/2010 11:17:20 AM]: FatalError: Member 'Versions' was not found. at System.Runtime.Serialization.SerializationInfo.GetElement(String name, Type& foundType) at System.Runtime.Serialization.SerializationInfo.GetValue(String name, Type type) 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() [7/20/2010 11:17:20 AM]: Progress: Import Completed. [7/20/2010 11:17:20 AM]: Finish Time: 7/20/2010 11:17:20 AM. [7/20/2010 11:17:20 AM]: Completed with 0 warnings. [7/20/2010 11:17:20 AM]: Completed with 1 errors. I guess this implies a problem with either the data or possibly the indexing within the DB? All the best, Dave

Hi Rohan, the error seems to indicate that the schema of the export package is not compatible with the patch level of the ..12\template\xml\DeploymentManifest.xsd file on the target machine. Please compare the file from source with target. Is it identical? If not export/import will not work. As a workaround you can copy the file from source to target before importing. Cheers, Stefan

Hi Stefan, With stsadm, I sussed quite early on that the exporting and importing sites need to be exactly the same, particularly any templates etc. If I have understood Rohan correctly, on the original server (so the source & target server are the same), I created a new site collection and imported the "suspect data" on to that, which I did and the fatalerror re-occurred. I'm assuming both the original site and the new site collection will be using the same DeploymentManifest.xsd file? Only problem is, from over 5000 files and 2.4GB of data, - which file is causing the problem? My view at the mo is to backup the site, restore onto a different server then delete all the data from the other sub-sites leaving only the sub-site with the problem. This would be treated as a "one-off" site until the offending file(s) are identified or the site becomes redundant. Regards, Davre

Hi Rock, I'm not sure I agree. I exported the data from the source server. On the same server created a new site collection and imported the data into the new site collection. The same error occurred. There is only one instance of the DeploymentManifest.xsd on the server. Can you explain why the failure occurred? Dave