I am exporting a SharePoint 2007 site and the export is completing without error. When I go to import the site to a different farm I get the error below. It basically stops the import after this error and no more documents are loaded. It looks like it is stopping on a document that is checked out, but it gets by others that are checked out just fine. It is hard to tell exactly where it is having trouble. Has anyone seen this error on an import before: [1/17/2008 12:21:17 PM]: Progress: Importing ListItem /moss2007/Shared Documents?id=372.[1/17/2008 12:21:17 PM]: FatalError: Item does not exist. It may have been deleted by another user. at Microsoft.SharePoint.SPListItem.EnsureItemIsValid() I have tried the export and import multiple times with the same result. If something was deleted I don't know why the error would persist after another export was done.... Thanks, Ryan

An update... There were several folders of documents in the Shared Documents area of the site I was importing. I narrowed the problem down to the folder that was having problems.That folder contained five documents, but none were being imported over. One by one I removed the minor versions for these documents leaving only one major version,and sure enough one by one they started to get imported over without errors until the entire site import completed successfully. It is hard to say why the versions caused problems on these documents. There are several other documents with multiple versions that never had a problem. Has anyone seen this behavior using the import???? Any input is greatly appreciated... Thanks, Ryan

Just want to bump this thread, as I'm having the same problem.Progress: Importing ListItem /_catalogs/users?id=561FatalError: Item does not exist. It may have been deleted by another user. at Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at Microsoft.SharePoint.SPListItem.GetValue(SPField fld, Int32 columnNumber, Boolean bRaw) at Microsoft.SharePoint.SPListItem.GetValue(String strName, Boolean bThrowException) at Microsoft.SharePoint.SPListItem.GetValue(String strName) at Microsoft.SharePoint.Deployment.SPImport.GetTargetUrlAndIdFromSPObject(DeploymentObject deployObject, String& targetUrl, Guid& targetId) at Microsoft.SharePoint.Deployment.SPImport.OnObjectImported(DeploymentObject importedObject) at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() at Microsoft.SharePoint.Deployment.SPImport.Run()

Just wanted to share: We were having other issuewith exporting/importing a site with 200+ docs that had to retain their major and minor versions. We were able to resolve our issues onlyafter we upgraded our SharePoint to SP1. It may be something worth looking into.

Thanks for the info... however we have already installed SP1...

An update: I opened up the huge manifest.xml file inside the exported cab, and was able to find the bad entires that should not be there. I removed them and imported with success. This is not a valid solution of course.

If you want to migrate the complete site collection then try using Back/Restore instead of Export/Import. Try using stsadm -o backup...... stsadm -o restore........

My solution ended up being to open the manifest.xml (in an editor that supports large files!) and find the entries which were generating the error, and remove them. Also, I was able to track them down in the database and remove them.

Thanks for this post. I had a content deployment job that was giving me the same error, however it never gave me a specific object name. I resolved my issue by making sure the minor versions were removed in the publishing farm, delete the identified problem sites and ran the content publishing job. The job finally is working again. This post saved me days of troubleshooting.

*BUMP* Just ran into this problem on a SharePoint 2007 Farm while trying to Import sites that were exported from the same Farm. It definitely seems to be a problem with importing document library versions - and like John Petrutis, I have had to resort to deleting the versioned objects from the source. Not a great solution. The SharePoint installation I am using is a fully updated "Virtual Migration Environment" supplied by Microsoft ( http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=19311 ) Here is a more detailed trace: [7/19/2011 8:39:55 AM]: Progress: Importing ListItem /MySiteCollection/MySite/MyList?id=2. [7/19/2011 8:39:55 AM]: Importing File Version 1.0 [7/19/2011 8:39:55 AM]: Error: Current item failed in the export with the error message: Cannot complete this action. Please try again.. [7/19/2011 8:39:55 AM]: FatalError: Item does not exist. It may have been deleted by another user. at Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, SPWeb web, Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& objAttachmentNames, Object& objAttachmentContents, Int32& parentFolderId) 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, SPList list, 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) . . . Software Consultant - iPMO