This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 89%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKT%3C/text%3E%3C/svg%3E)
Hi Everyone,
Getting 500(Could not verify the copy source within the specified time) error for some operations using SyncCopyFromUri. It started happening since yesterday morning. It is happening every around 40min for some of the requests and then its ok for next 40min. It is not an issue with SAS URL since we generate it the same way and for most of the requests it goes ok. The failed one is going also ok after user retry its operation one or few more times. We thought that is its temporary storage issue and it will not last long, but unfortunately it is still there. We checked Yesterday code on our end, and everything looks ok. (our other environments works perfectly fine with the same versions)
We didn’t change anything connected to blob storage in our app last days and it appeared from nowhere. We can see that in most of the cases when there is this exception it is retried by Microsoft SDK DLL (it makes 6 retrials) but when it does not manage to copy file successfully than we get an exception and the user must repeat his actions in the system.
Do You have any idea what may be the issue that it is happening?
Thank you in advance!
Karol
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 81%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Hi Karol Trzaskawka - Thanks for reaching out on Q&A Forum.
I am reviewing this one and shall update the thread shortly.
Hi Karol Trzaskawka - Sorry I just noticed that my answer didn't got submitted.
You appears to be trying to perform Copy Operation which will do a Get from Source and Out on the Destination. The error CannotCopyVerifySource points that the issue happening on performing Get on the source.
Now based on the 500 exception, it points that it could be possible due to some load balancing event, any network side errors, any kind of throttling or any other server side issue.
In general recommendation, there are best practices of retry is suggested to minimize the impact to the application and retry those operation. However it lasts for longer time or re-curring, a deeper investigation might be required. For that, you might need to reach out to the support team via a ticket.
Hope that helps!
Hi Karol Trzaskawka -- This is a gentle follow up to check if there is anything required further for that ask.
If not and the answer helped, request you to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community member.
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 4%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKT%3C/text%3E%3C/svg%3E)
Hi, The issue disappeared after me posting here and it didn't appear again. It looked like some issue on the Azure side that was solved in the meantime. I think we can close this question.
Hi, The issue disappeared after me posting here and it didn't appear again. It looked like some issue on the Azure side that was solved in the meantime. I think we can close this question.
Sorry for above - used my personal account.
Hi Karol Trzaskawka - Thanks for the response.
In that case, as I discussed in my initial response, it could potentially be some kind of transient issue (probably some kind of load balancing event happening at the backend) which should ideally not last for a longer time and having best practices implementation of retry shall help in minimizing the impact to the application.
For more detailed troubleshooting, you can reach out to the support team further in case the issue re-surfaces further.
Lastly, if we are good for now, request you to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community member.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 64%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENR%3C/text%3E%3C/svg%3E)
Hello
Greetings! Welcome to Microsoft Q&A Platform.
I understand that you are encountering a issue with the SyncCopyFromUri operation, it typically occurs when there is a timeout or connectivity issue while trying to access the source file. Please consider checking the below following factors to troubleshoot the issue,
You can refer to this article: Copy a blob with Azure Storage client libraries
The easiest way to move /copy (upload, delete) the data in Azure Storage Account is Azcopy (Fast Data Transfer) and Azure storage explorer tool
Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.
Please "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Hi,
As i mentioned it was not an issue with permissions or access level as the issue appeared by itself and no changes in the functionality were involved on our side. It lasted 2 days for just some of the request which were created the same way as others and now everything looks to be ok. The issue was solved "by itself" or by Microsoft team straight after response from Amrinder Singh and up till now we are having 0 of these errors. I consider it as some Azure issues that were solved by Microsoft Team, am i right?
Best regards
Karol
thanks for the update.