I’ve used the SharePoint Migration Tool successfully on numerous occasions but this week I had a very unusual issue.
In the SharePoint Migration Tool log file from a failed migration we found this error:
Scan File Failure: The parent folder was not migrated 0x0111000F
Failed to Read the file: Could not retrieve file’s metadata 0x01310007
For some reason the files could not be read, it was very random as other files in the same folders being migrated did migrate successfully.
The content being migrated was stored in Azure File Storage with local caching. The Migration Tool was using the local network drive mapping (to the cache) and often the content being accessed needed to be retrieved by the cache from Azure.
The issue is sometimes the file isn’t in the cache and the migration tool doesn’t wait for it to download. The result is the file is zero bytes long and as not file metadata to read.
One solution is to connect directly to Azure File Storage rather than using the cache by mapping a drive.
Hopefully this helps someone else with the same problem!
Hi Steve,
SharePoint noob here.
Whats the relation between the azure storage and share point? Does the Migration tool use an azure cache and by creating storage account there will it be used as well automatically?
I didn’t get this part as well.
“The Migration Tool was using the local network drive mapping (to the cache) and often the content being accessed needed to be retrieved by the cache from Azure.” I didn’t set anything.
I’m getting this error with few files I need to migrate them to SharePoint in Office 365.
Thank you.
Best regards,
Jonny Moura
Hi Jonny, in this case you can use a service call Azure File Store which uses Azure storage and some local caching to provide low cost file storage in the cloud, accessed via network file shares. The issue is because of the caching the Migration Tool sees the file name but can’t access the file quickly and so errors.
Regards,
Steve