Forum Discussion
Solved
URGENT! SharePoint Migration Tool Error: "Package Engine has stopped because Azure queue failed"
Hi, I'm trying to migrate some files from a local drive to OneDrive for Business and I keep getting this error. I have tried it with different folders as well. It's quite urgent as I need to hav...
- Hi Everyone,
Thanks for the responses.
Finally managed to sort it out the other day. Seems to be an issue with the tenant. This worked fine with other tenants.
So, the fix:
1) Create an Azure Storage account in your Azure account. Ensure that the storage is in the same region as your SharePoint tenant. (NOTE: Azure Storage accounts created in this method incurs charges)
2) Get the account name and key for the Azure Storage.
3) In SPMT, once the source and destination for the migration are added. Click on the fly wheel/settings icon.
4) Enable Custom Azure Storage, enable encryption.
5) Enter the Azure account name and key.
6) Apply the settings and start migration.
Once the migration is done, delete the Azure Storage account after ~ a week. Otherwise, you'll keep incurring charges for some encrypted data.
Hope this helps. And I hope the SPMT developers fix this issue.
Hi Everyone,
Thanks for the responses.
Finally managed to sort it out the other day. Seems to be an issue with the tenant. This worked fine with other tenants.
So, the fix:
1) Create an Azure Storage account in your Azure account. Ensure that the storage is in the same region as your SharePoint tenant. (NOTE: Azure Storage accounts created in this method incurs charges)
2) Get the account name and key for the Azure Storage.
3) In SPMT, once the source and destination for the migration are added. Click on the fly wheel/settings icon.
4) Enable Custom Azure Storage, enable encryption.
5) Enter the Azure account name and key.
6) Apply the settings and start migration.
Once the migration is done, delete the Azure Storage account after ~ a week. Otherwise, you'll keep incurring charges for some encrypted data.
Hope this helps. And I hope the SPMT developers fix this issue.
Thanks for the responses.
Finally managed to sort it out the other day. Seems to be an issue with the tenant. This worked fine with other tenants.
So, the fix:
1) Create an Azure Storage account in your Azure account. Ensure that the storage is in the same region as your SharePoint tenant. (NOTE: Azure Storage accounts created in this method incurs charges)
2) Get the account name and key for the Azure Storage.
3) In SPMT, once the source and destination for the migration are added. Click on the fly wheel/settings icon.
4) Enable Custom Azure Storage, enable encryption.
5) Enter the Azure account name and key.
6) Apply the settings and start migration.
Once the migration is done, delete the Azure Storage account after ~ a week. Otherwise, you'll keep incurring charges for some encrypted data.
Hope this helps. And I hope the SPMT developers fix this issue.