AzureStorageExplorer icon indicating copy to clipboard operation
AzureStorageExplorer copied to clipboard

Azure Storage Explorer copy paste failed between different tenants

Open agungputra123 opened this issue 3 years ago • 1 comments

Trying to copy a disk from one RG to another RG, its works in a same tenant. But when trying to copy disk from tenant A to another tenant B, it fails when nearing completion (its taking a couple hours). is there any advice where i could go wrong?

Bug Description: AzCopy failed to complete the transfer: %s Disk 'data_node1' in 'POC-RG' was likely created. You may need to delete this disk before retrying this operation.

AzCopy error message: failed to perform copy command due to error: -> github.com/Azure/azure-pipeline-go/pipeline.NewError, /home/vsts/go/pkg/mod/github.com/!azure/[email protected]/pipeline/error.go:157 HTTP request failed

Head "https://md-impexp-zmnqnqmtbb44.z31.blob.storage.azure.net/rlbnq00pkrm5/abcd?si=017de38b-6ee4-4f42-bde3-7815ba5c5981&sig=-REDACTED-&sr=b&sv=2018-03-28&timeout=901": authenticationrequired

AzCopy log file can be found at undefined

Storage Explorer was unable to revoke access to a disk. The disks involved in this operation may still be in an 'Active SAS' or 'Active Upload' state. You may need to return the disks to an 'Unattached' state before retrying this operation, or before performing new operations on the disks.

agungputra123 avatar Aug 10 '22 09:08 agungputra123

Sorry about this bit:

AzCopy log file can be found at undefined

That's definitely an unrelated bug.

In the meantime, can you go to <home/user directory>/.azcopy, and then either:

  1. Find the log file from your disk copy that failed. It should have the URL you pasted (https://md-impexp-zmnqnqmtbb44.z31.blob.storage.azure.net/rlbnq00pkrm5/abcd)
  2. Try the transfer again, and when it fails, the newest log file will be the right one

Either way, once you have a log file, can you drag and drop it to this issue on GitHub?

MRayermannMSFT avatar Aug 12 '22 00:08 MRayermannMSFT

Closing due to lack of response. If you are still encountering this problem, we recommend opening a support ticket via the Azure portal alternatively you can open a new issue here.

MRayermannMSFT avatar Sep 07 '22 17:09 MRayermannMSFT