stsadm -o import results in a error
So we were getting an error where the import command was telling us the parent site didnt exist, and the import fails.
Looking into the Export log, we found:
Error: Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)
at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, Boolean bUnprotected)
at Microsoft.SharePoint.Deployment.FileSerializer.SaveFile(SerializationInfo info, ExportObjectManager objectManager, ExportDataFileManager fileManager, SPExportSettings settings, SPWeb parentWeb, Boolean isGhosted, String setupPath, String setupPathUser, Byte setupPathVersion, String webRelativeFileUrl, Int32 size, Byte level)
The import error was:
Error: The file cannot be imported because its parent web /sites/grizzly/SAISB/grizzly does not exist.
Progress: Importing File Lists/General Discussion/Threaded.aspx.
[8/27/2007 3:20:18 PM]: Error: Current item failed in the export with the error message: Access is denied. (Exception from HRESULT: 0×80070005
The fix was to grant the person doing the export site collection administrator status, then do the export.
Hey, I just came across this post as I’m investigating a failed SharePoint migration that we attempted this weekend. We are trying both imports and exports using stsadm. The exports went just fine, but when we attempted to import, every single site generated the Error: Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED)). What I attempted to do was recreate the site collection and the re-import, but I continued to receive the same ACCESSDENIED error. Are you saying that I need to try both the export and import again? As I said, the exports appeared to go through without error. Thanks for any assistance you can provide.
Comment by Tray Harrison — October 13, 2008 @ 2:56 pm
Hi,
It’s not really doing it again, but rather, granting the person running the imports and exports the correct rights.
I can not definitively off the top of my head tell you exactly the rights you need, but I would start with at least site collection admin for the identity running the stsadm commands for both the source and destination site collections.
If thats not enough, you may need actual DB rights, which could be a problem with your DBAs. In that case, grant them site collection rights, local admin rights, and let them run the command.
A couple hundred stsadm commands later and they may reconsider their policy on DB access for SharePoint admins.
Comment by Folly — October 14, 2008 @ 3:25 pm