We have been using Google Cloud Transfer to move files from Azure Storage to Google Cloud Storage on production. The transfer stopped working recently (with error message permission denied) and no new transfer from this source is working. We noticed that Google again displays the tag "beta" next to the Microsoft Azure Storage Container option (despite the fact that according to their logs it went to General Acess in July 2020).
Does anybody else experience the same issue?
I was not able to find any official or unofficial information about this issue.
Related
Have attempted the following using ARM Templates, through the Azure portal and via the latest Azure Powershell scripts.
Create new Azure Maps account
Delete Azure Maps account
Create new Azure Maps account with same name from step 1
Expected: Azure Maps account is created and able to be used
Actual: Azure Maps is 'created' but attempting to retrieve or interact with the resource results in a 404 Not Found error. All blades in Azure just show
Is anyone aware if this is an existing limitation of Azure Maps or if there is a known workaround without having to create the maps account on a different name?
Thanks for reporting. There is an issue with this process which started occurring late last night. The team is working on resolving this.
Update (3/8/2019): This issue has now been fixed in production.
How to fix this bug?
Open Cloud Explorer (logged in)
Open "Files" folder for some Azure Web App (former Azure Website)
Result:
Cloud Explorer has encountered an unexpected error: Unable to retrieve
child resources.
Details: 'Newtonsoft.Json.Linq.JObject' does not contain a definition
for 'requestNamespace'
I'm using:
Microsoft Visual Studio Community 2015 Version 14.0.25431.01 Update 3
Azure App Service Tools v2.9.6 14.0.21111.0
Common Azure Tools 1.8
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.9.41104.6
I had this problem and it was a permissions issue, mine was with a Cosmos Document DB database node.
I had my DevOps guy add me as a contributor to the IAM Azure role and it started working for me. So check all the permissions, and it is the cloud so sometimes you have to give it time to propagate the changes too.
I had this issue when both Azure Storage Emulator and Azure Storage Explorer trying to run at the same time. Try uninstall one or run only one at a time to solve the issue.
Have a look at troubleshooting guide might also help.
I am developing with Azure storage locally using VS2015. I created and accessed my development storage blob container fine. I upload three images and have code to calculate the size of the images.
For some unknown reason, I cannot expand the Blob Containers node in Cloud Explorer any more. I.e. Cloud explorer > Storage Accounts > (Development) > Blob Containers. Doing so results in the following error message:
Cloud Explorer has encountered an unexpected error: Unable to retrieve
child resources.
It has been working fine in the past, so not sure what's changed. I know there are containers inside and I can seemly create one but then it doesn't show up in the list.
It works for live Azure storage accounts but not development.
Though I can still write code against this Development container - so it's there and functional but Cloud Explorer just not listing the containers i.e. no access to view files / upload file through VS UI.
Here are my steps to resolve
Uninstall Cloud Explorer via Extensions and Updates
Restart VS
Update the Cloud Explorer in Extensions and Updates (that apparently wasn't uninstalled)
Experience the catastrophic behaviour (very slow)
Restart VS
Fixed (seemingly)
Look into Extensions and Updates to see Cloud Explorer is disabled
Everything is fixed.
Update (29/07/2018)
If you are having trouble launching Microsoft Azure Storage Explorer (Development) e.g. blob storage and get the error message "Unable to retrieve child resources" followed by details of "A network error occurred...ECONNREFUSED 127.0.0.1:10002" then simply (install and) run the Azure Storage Emulator.
The aforementioned solution didn't work for me.
The error went away after upgrading to Azure SDK 3.0 (using web platform installer). After that I am able to expand the child resources in App Services, and attach the debugger.
Another option that worked was using the Server Explorer to expand files/attach the debugger, but that option seems to have been turned off in 3.0.
The name of the Storage Account Name is case sensitive to teh azure service. The client however is not.
Because of this you can connect, but when the Storage Explorer tries to enumerate the child object it will fail if the Storage Account is not entered with the proper case.
I got this error when my system-clock was accidentally set a couple of hours back in time. Just saying.
I am deploying Umbraco 6.05 to Windows Azure. I am currently using "Azure Web Sites" to do this, but from what I can glean, it appears that this may cause future problems with the storage of media being on the local file system (both due to space limitations and also due to scaling considerations). The site was created and uploaded using WebMatrix.
I have found various articles about using Blob Storage for this, but they all refer to "Cloud Services" and "Web Roles" - none of which seem to match with the current terminology used on Azure, and to be totally honest I am not that familiar with Azure yet anyway. I have also found various "accelerators" for previous versions but nothing for this version.
Can anybody provide any links to a definitive guide to the installation of this version of Umbraco as an Azure Web Site, utilising Azure Blob Storage where appropriate? If this is not feasible, perhaps further advice can be provided as to the recommended way of hosting Umbraco in Azure.
There are no different in term of how they store the file whether you use Web Sites or Cloud Services as long as you didn't modify the Umbraco.
Both Web Sites and Cloud Services keep the file, in this case, the Media folder in their local storage unless you modify Umbraco to save into Blob Storage to have a better scaling.
You can write and modify your own custom Media location or try to look at this URL http://our.umbraco.org/projects/backoffice-extensions/universal-media-picker
I'm trying to use the Azure Preview. When I try to configure my storage account I receive the following error:
Monitoring Failure: The server encountered an error while retrieving the metric selection. Retry the operation.
This has been occurring since yesterday. I see the error on both ie10 and Chrome.
I tried to create a new storage account and see the same error.
When I run the app the application fails to connect to the storage account with the following error (from node.js):
Config: C:\DWASFiles\Sites\mychild\VirtualDirectory0\site\wwwroot
Creating Blob Service profile
Creating Blob ...
Fail.{"code":"EACCES","errno":"EACCES","syscall":"connect"}
As you're not the only one seeing this problem (myself included), I don't think this is anything to do with what you've done. I suspect that this is a general problem that Microsoft are having. I'd recommend logging a support call with the Azure support team if you need this problem resolved.