[2/3/2011 10:50:11 AM] Verbose: Performing final fixups. [2/3/2011 10:50:11 AM] FatalError: Cannot complete this action.
Please try again. [2/3/2011 10:50:11 AM] Debug: at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.ImportNavigationXml(String bstrUrlWeb, String bstrNavXml, Boolean fClearNavigation) at Microsoft.SharePoint.Deployment.ImportObjectManager.ImportWebStructure() at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() at Microsoft.SharePoint.Deployment.SPImport.Run() [2/3/2011 10:50:11 AM] Progress: Import did not complete.
What are you trying to export and import? Did you try the PowerShell Export-SpWeb ?
The reason I'm trying the STSADM is because the powershell commands have there own issues. For instance http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/330ee5ee-ddfe-4b44-9e4f-c566e6c04f7b
Riture, did you ever find a solution?
Greetings everyone,
I am facing the same problem, I have no other errors in my import log.
Just the one that riture describes.
We have Sharepoint Server 2010 Enterprise edition SP1 and February 2012 patch (14.0.6117.5002)
I have also tried PowerShell Export-SpWeb and Import-SpWeb commands but the result is the same.
We are trying to divide our sites from one site collection to four, because the size of the content database is 120GB.
I have successfully moved two sites to two other site collections but the last site's import always fails.
For example I want to move the site https://computername/site1 to https://computername/sites/site1 using
stsadm -o export -url https://computername/site1 -filename g:\site1 -includeusersecurity -nofilecompression
stsadm o import url https://computername/sites/site1 -filename g:\site1 -includeusersecurity updateversions 2 nofilecompression
Because the import log has no errors, I don't know what to do, can anyone help?
HI,
I am facing the same issue.
Did you find any solution to this ?
No Ahmed, I didn't find a solution and I left the database as it is.
Good luck!
The issue is with moving site collections or sites?
What is the error you are getting while working with Powershell?
check the below tool