FR Tracking Issue: StorageErrorException when uploading
See original GitHub issuehttps://portal.microsofticm.com/imp/v3/incidents/details/328063516/home
{
"errorMessage" : "azure.storage.blob._generated.models._models_py3.StorageErrorException: Operation returned an invalid status"
}
Report
Summary
24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
---|---|---|
0 | 0 | 0 |
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Error writing to local Blob storage using azure ...
StorageErrorException: Operation returned an invalid status 'The value for one of the HTTP headers is not in the correct format.
Read more >Failed to upload blob(s) - Failed to fetch through the Azure ...
I'm receiving an error when just trying to upload a file into a container in Azure, using the portal. It seems the UI...
Read more >Re: Trying to upload tracking no
If yes, and the error persists, it can possibly be a technical glitch which can be fixed by clearing cache and the history...
Read more >Track the upload progress while uploading file to azure blob
I want to track upload progress that how many bytes are uploaded out of total at that moment? Is there any API or...
Read more >didn't upload tracking number, now my seller ratin...
So I have 3 items that I listed and sold but did not use ebay labels. I of these items, the buyer actually...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You added the right labels to make the issue a Critical issue 😄
I don’t think we can use test known issues for this, the error is happens in the Helix client and for test known issues we only scan console logs for test known issues. Analyzing Helix client logs would increase the scope of the search significantly
XStore team removed the service instance that our accounts were on out of rotation because it looked unhealthy, and it looks like that fixed the issue. We’ll keep this issue open until EoD to monitor the issue and see if the fix sticks 😃