stsadm import is failing due to unknown reasons
I am facing a problem while importing site using stsadm, it get failed with the following error: FatalError: Value cannot be null.Parameter name: gat System.Guid..ctor(String g)at Microsoft.SharePoint.Deployment.FieldTemplateSerializer.FixLookupFieldSchema(XmlNode fieldNode, Guid parentWebId, Guid fieldId)at Microsoft.SharePoint.Deployment.FieldTemplateSerializer.UpdateField(SPWeb web, SPField field, SerializationInfoHelper infoHelper)at Microsoft.SharePoint.Deployment.FieldTemplateSerializer.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() I have done some googling on this issue and I have found that this is a known issue with stsadm export-import (Reference : http://scottprice.me/2009/05/02/stsadm-import-error/ ). Typically this issue comes with the custom columns in content types. I have tried some of the solutions mentioned on different articles but nothing is working for me. Any suggestions/ideas?
March 10th, 2010 12:24pm

hellothe most common problem with SPExport/SPImport API (which is used in stsadm internally when you use export/import commands) is RetainObjectIdentity problem. Briefly when you export your site the most reliable way is to use RetainObjectIdentity = true in order to keep the same guids as original objects have. If you have RetainObjectIdentity = false - you need to do additional steps, e.g. retarget content by query web part (see http://stsadm.blogspot.com/2007/10/retarget-content-query-web-part.html). Also lookup fields may not work after import if they use guids for lookup listsBut it is not so simple to make export/import with RetainObjectIdentity = true. It works only for first level child objects of a site collection. Anyway I suggest you to use gl-import2 command for stsadm. Please see the following link for details http://stsadm.blogspot.com/2007/10/better-import.html. It also describes issues with RetainObjectIdentity. gl-import2 doesn't avoid limitation on first level child objects of a site collectionhttp://sadomovalex.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 1:54pm

Hi, Sorry for replying late but I am not in sync due to some problmes. Actually we have set the RetainObjectIdentity = true, even than this error is coming up. I am not sure what is going wrong. Any other ideas? Thanks, Vijay
May 6th, 2010 8:45pm

Hi, Update on the issue: I have tried deleting the list that is causing the issue ( in the logs) but it did not solve my problem. After deleting that list, the same error is coming up for another list. This keeps going on. At one of the forum, it is written that this could be because of the Custom Site Columns so I have deleted all the Custom Site Columns and try to do export-import again but that too doesn't work. :( I am stuck at this position. Any ideas or help is highly appreciated. Thanks, Vijay
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2010 11:21pm

i have the same problem with the import my list has custom content but i get the same error when i remove any list of custom content, is their a solution for this ?thanks
February 11th, 2011 4:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics