search

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
377 stars 86 forks source link

Retrieval error & failure writing resources #6128

Closed christine1729 closed 2 years ago

christine1729 commented 2 years ago

Preflight Checklist

Storage Explorer Version

1.19.0

Regression From

1.18.0

Architecture

x64

Storage Explorer Build Number

No response

Platform

Windows

OS Version

No response

Bug Description

  1. not able to view child resources -> retrieval error
  2. not able to write resources to the azure blob storage location -> failed ITP job due to failure writing

Steps to Reproduce

  1. launch app
  2. expand to view child resources and got this retrieval error

Actual Experience

  1. not able to view child resources
  2. not able to write resources to the azure blob storage location

Expected Experience

No response

Additional Context

No response

urihsam commented 2 years ago

Similar error when I wanna copy data from blob to cosmos: 2022-10-05 20:56:25Z] [Status: Submitted]: Retriable error happened: Failed to read page blob with id XXX to blob in container bingads, offset 4030726144 [2022-10-05 20:56:25Z] [Status: Submitted]: Execution plan wasn't build and build will be delayed [2022-10-05 20:57:28Z] [Status: Submitted]: Retriable error happened: Failed to list blobs in container bingads with prefix XXX [2022-10-05 20:57:28Z] [Status: Submitted]: Execution plan wasn't build and build will be delayed

MRayermannMSFT commented 2 years ago

@urihsam can you share the exact errors you are seeing in storage explorer?

MRayermannMSFT commented 2 years ago

Closing due to lack of response. If you still need help with this issue, we recommend opening a support ticket via the portal. Alternatively you can open a new issue here.