Storage Exception on Blob.UploadTextAsync - InvalidBlockList

Error returned :

{ "ErrorCode": "InvalidBlockList", "ErrorMessage": "The specified block list is invalid.\nRequestId:f31c101a-0001-0031-075e-d0c218000000\nTime:2017-05-19T05:15:53.0372722Z", "AdditionalDetails": {} }

StackTrace: [0] at Microsoft.WindowsAzure.Storage.Core.Util.StorageAsyncResult1.End() in c:\Program Files (x86)\Jenkins\workspace\release_dotnet_master\Lib\ClassLibraryCommon\Core\Util\StorageAsyncResult.cs:line 77 at Microsoft.WindowsAzure.Storage.Blob.CloudBlockBlob.EndUploadFromStream(IAsyncResult asyncResult) in c:\Program Files (x86)\Jenkins\workspace\release_dotnet_master\Lib\ClassLibraryCommon\Blob\CloudBlockBlob.cs:line 776 at Microsoft.WindowsAzure.Storage.Core.Util.AsyncExtensions.<>c__DisplayClass4.<CreateCallbackVoid>b__3(IAsyncResult ar) in c:\Program Files (x86)\Jenkins\workspace\release_dotnet_master\Lib\ClassLibraryCommon\Core\Util\AsyncExtensions.cs:line 115 — End of stack trace from previous location where exception was thrown — at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at … `

My Code await blob.UploadTextAsync(content, null, null, bro, null);

[mirobers]

This can happen when a concurrent upload commits after you have started to upload but before you commit. In that case, your upload fails. You can retry this error or attempt some other recovery action based on your scenario.

[leroibeukes]

Ok - So turns out we were receiving concurrent requests and assumed optimistic concurrency would work for us … it didn’t. We’ve deployed a new version using leases (pessimistic concurrency) and this has helped us resolve the issue. Thanks for the help in pin-pointing the problem.