Hi, We are developing a MOSS 2007 wcms site. It has variations enabled. I used stsadm to export the site(parent site and all the child sites). It went fine without any errors. But when i tried to import it onto a new blank site it ran for almost 5 mins (checked the log file and imported almost everything) andthenthrew me the following error. [12/3/2007 6:59:14 PM]: FatalError: Specified method is not supported. at Microsoft.SharePoint.SPList.set_MajorVersionLimit(Int32 value) at Microsoft.SharePoint.Deployment.ListSerializer.UpdateListData(SPList list, Dictionary`2 listMetaData, SPImportSettings settings) 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() would somebody be able to look through it and tell me what to fix to make it work? thanks for your patience and time. karthik.

try this : Add the parameter "-updateversions 2 "to your stsadm command line. reference : http://technet2.microsoft.com/Office/en-us/library/1178aa35-20b1-45b0-bcb6-4249aa34ea481033.mspx?mfr=true TSC

I tried adding -updateversions 2 and -updateversions 3 and neither made any difference.

I get this new error when I use -versions 1 or -versions 2 also.

Hi everybody,I'm receiving exactly the same error. Anybody knows anything else?!?Thanks in advance.

Part of the import process, before data is imported, updateseach list to make sure it has all the latest settings, columns and so on. This problem seems to only happen when an item is updated which pushed content into version history and then the list has versioning turned off. Unlike the recycle-bin that purges when you turn it off, turning off versioning does not seem to clean out versioned items or version settings. When importing, it updates the target list with "no-versioning" and then it fails when it tries to change the version limit, since a list that does not allow versioning should not be allowed to set a version limit. This is why specifying a -versions settings has no impact, the export/import is still trying to setup the target list. The solution to get past the issue is to just turn versioning back onfor the list giving the errorand then re-export/import. The better solution of course would be to have Microsoft(i) fix it so when you turn off versioning on a list it cleans out all versioned items and clears out the version settings and (ii) not throw an error on import if you set the version, either ignore it or set it in the list (it will be ignored by runtime since list has versioning disabled). This is a also a problem I have run into for sites that use MOSS "content deployment", which uses export and import to push content. I hope this helps....

Hi, i have a big problem. We use the SharePoint Content Deployment. For several weeks it works fine, but since yesterday i get the same error as described above (versioning problem). i tried to search the logfiles, but cant find anything. Can anyone tell me where i can find the logfiles for import-jobs ? i need to find the list or library which causes the problem best regards Thomas

One more thing.. If you've unsuccessfully imported to a site and wish to try again - you need to delete the receiving site (the one you are trying to import into) and make a new one. Otherwise it will continue to fail. Something gets written somewhere when you attempt to import - even if the import fails - and it won't successfully import to that site again. Recreating the site works for me.

Good Point TxAggieJen. If import goes bad for some reason, you must create a new site. Also, after you import the site and receive a File not Found Error, you need to reapply the master page settings from the root site. Dave

Hey Dave, how do you reapply a master page settings from the root on a page that is showing up as File Not Found?Thanks,Jody