SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have encountered an error in the web export/import routine. The thing is that the feasibility of import seems to depend on the statу of the web.

I have several subsequent export packages of the same web and say #2 works fine (I can see it extracting the contents of the package and the result is that the web is imported) and #3 fails (I don't see the files being extracted and the import fails almost immediately).

PS C:\Windows\system32> Import-SPWeb -IncludeUserSecurity -Path C:\Install\exportweb2.bak -Identity -Force

Log file generated: C:\Install\exportweb2.bak.import.log

PS C:\Windows\system32> Import-SPWeb -IncludeUserSecurity -Path C:\Install\ -Identity -Force

Log file generated: C:\Install\

Import-SPWeb : Could not find file 'C:\Users\adm_user\AppData\Local\Temp\0cf9aa8f-fc19-401f-a094-0c6cabde6f6b \ExportSettings.xml'. At line:1 char:13 + Import-SPWeb <<<< -IncludeUserSecurity -Path C:\Install\ -Identity sites/ipms -Force + CategoryInfo : InvalidData: (Microsoft.Share...CmdletImportWeb:SPCmdletImportWeb) [Import-SPWeb], FileN
otFoundException + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletImportWeb

The following is logged:

[23.05.2011 10:07:22] Progress: Initializing Import.
[23.05.2011 10:07:22] Warning: Import requirement file C:\Users\adm_user\AppData\Local\Temp\3\9f0699d5-bb0d-4e27-ab44-6d8f534b0271\Requirements.xml was not found no verifications ran.
[23.05.2011 10:07:22] FatalError: Could not find file 'C:\Users\adm_user\AppData\Local\Temp\3\9f0699d5-bb0d-4e27-ab44-6d8f534b0271\ExportSettings.xml'.
[23.05.2011 10:07:22] Debug:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.IO.FileInfo.Open(FileMode mode, FileAccess access, FileShare share)
   at Microsoft.SharePoint.Deployment.SPImport.DeserializeExportSettings()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[23.05.2011 10:07:22] Progress: Import did not complete.

The adm_user account is a local administrator on all the machines in the farm except SQL Server and the SPShellAdmin rights have been granted.

There definitely are the Requirements.xml and ExportSettings.xml inside the package, I checked this with my archiver.

I believe this is rather a common trouble to shoot and any help would be appreciated.

share|improve this question
up vote 8 down vote accepted

Check the size of your export package. There is a default cab size of about 25Mb - this used to be a limit you had to increase with stsadm by setting a parameter. With the PowerShell Export-SPWeb cmdlet it generates multiple files if you hit the limit. You may need to change this limit using the CompressionSize parameter to set the cab size (up to a maximum of 1024Mb).


Export-SPWeb http://mysite -Path c:\backup\ExportFile -CompressionSize 1000
share|improve this answer
And that was a bingo. Thanks for reminding! – Alexey Krasheninnikov May 23 '11 at 10:08

I had a similiar problem. I also exported a web (with subwebs) and got several packages. When I tried to import individual packages, I got the error you describe. If I imported the main package though (e.g. exportweb.bak, exportweb.cmp) - it imported the web (and subwebs) fine.

This may not be the exact problem you're describing though, is it?

share|improve this answer
1. I think this answer should be a comment. – Alexey Krasheninnikov May 23 '11 at 7:13
2. It looks similar to what you describe but the difference is that both packages are generated with the same Export-SPWeb syntax and the difference was in the state of web content and the package file name. Nothing else to my knowledge. – Alexey Krasheninnikov May 23 '11 at 7:15

I have same error but other resolution - I have missed backup files (if backup size is larger than 25 mb by default, sharepoint backup created multiple files).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.