The storage account for this workspace has been deleted. which I have been using for my Machine Learning Studio. What should I do as when I try to save my experiment it shows that no workspace is found.
See the Image for reference which showing storage account has been deleted
Deepak, this issue maybe related to cache on your browser or a deleted storage account for the workspace.
For scenario one (which you are getting):
After the new Machine Learning workspace is created, you can sign in to Machine Learning Studio by using the Microsoft account you used to create the workspace. If you encounter the error message, “Workspace Not Found” (similar to the following screenshot), please use the following steps to delete your browser cookies. More details can be found here: https://learn.microsoft.com/en-us/azure/machine-learning/studio/troubleshooting-creating-ml-workspace, you can also use in private/incognito mode to confirm.
Scenario 2:
In case if the storage account was deleted, double check in the Storage accounts on the left blade of the azure portal, then select the subscription you created the workspace with, it should list it there, if it is not, then it was indeed deleted. In that case:
"It's not possible to restore a deleted storage account or retrieve any of the content that it contained before deletion. Be sure to back up anything you want to save before you delete the account. This also holds true for any resources in the account—once you delete a blob, table, queue, or file, it is permanently deleted." More details can be found here: https://learn.microsoft.com/en-us/azure/storage/common/storage-create-storage-account
Related
Some one has deleted the file share folder from the storage account in azure . It can be recovered as soft delete is enabled. But how to know that who has deleted the file?
It is possible to view operations within an Azure resource using Resource Logs. This is possible by Monitoring Azure Blob Storage which is a feature of Azure Monitor.
You would first start with creating a Diagnostic Setting- https://learn.microsoft.com/en-us/azure/storage/blobs/monitor-blob-storage?tabs=azure-portal#creating-a-diagnostic-setting
And then view logged activity by using a Log Analytics query or you can go the destination that you are forwarding the logs to as setup in the diagnostics setting and look for the respective API, example- "DeleteBlob" or "DeleteContainer" etc.,
However, if you have not already setup a diagnostic setting already and are forwarding data to a specific destination, it may not be possible to retrieve this information right now. Hope this helps!
I am attempting to debug an application that is comprised of several microservices. Part of the cross service messaging is carried out by storing information in azure blob storage by one service to be read by the other. For local testing we use Azure storage emulator.
Recently my AD logon had to be recreated by our IT team. My username has gone from , to <myname.COMPANYNAME> and since then Azure storage emulator has failed me.
Attempting to view all local blob storage results in an error "Unable to retrieve child resources." though I can can confirm that each container still exists manually. Hunting online suggests the problem is due to the period in my AD logon name (changing this is non trivial due to it needing to be done by another department)
Unable to retrieve child resources.
Details:
{
"name": "RestError",
"message": "The specifed resource name contains invalid
characters.\nRequestId:b305591f-acf0-4e2e-8cc6-e3305fa18fab\nTime:2021-09-
My current thinking is to try and configure the emulator to not store its files in my user account but I have yet to find anywhere that this can be carried out - the config file mentioned in this question doesn't appear to have what I need.
For this a successful answer would be guidance on how to relocate the storage explorer without IT having to create a new logon, or a workaround that will allow storage explorer and the services to retrieve my various blob stores.
Please check this thread > Azure Storage Emulator store data on specific path - Stack Overflow if it can help related to azure storage emulator.
NOTE:
The Azure Storage Emulator is now deprecated. Microsoft recommends
that you use the Azurite emulator for local development with
Azure Storage Refer
Most cases change in Logon names doesn’t have affect on blob, but maybe in few cases due to name connected permissions or SID.
After changing the username, check if any permissions or roles assigned previously are given to that new one and make sure if DN and SID are not modified, to access resources or check all the configurations that have done previously that depend only on DN. The Storage Emulator supports only a single fixed account and a well-known authentication key.
1.Try to restart the emulator and check whenever tried with new port or any newconfiguration.
See this Thread
The invalid characters in the error in most of the cases happens with container name (all lowercase, no special characters) .
Try to check once and refer below threads for resolution possibilities,if it is container issue.
SO ref1
SO Ref 2
Storage Explorer has several options for how and where it can source the information needed to connect to your proxy. To change which option is being used, go to Settings (gear icon on the left vertical toolbar) > Application > Proxy. Network Connections in Azure Storage Explorer | Microsoft Docs
I have a storage account in my Azure sub which I am trying to delete. When I try to do so, it says I have a storage account in my Azure which I cant delete. When I try to delete that it says
Failed to delete storage account <storage acc name>. Error: An operation is currently performing on this storage account that requires exclusive access.
I have tried multiple times, even after waiting, but nothing is working. Any solution?
If you have waited and still facing the issue, you will have to open a support ticket with Azure Support to get it fixed.
Was your storage Account Encrypted?
Was your storage Account used as a VDI Blob storage ?
Thanks and regards,
Abdel
Please try the following:
Login as (or ask your) global admin and attempt to delete the storage account
Unlikely but if the above fails ask Global Administrator add themselves as a Storage Blob Data Owner and then try to delete the Storage Account.
Remove Resource Lock
In my case Microsoft support are attempting to delete the storage account. All other workflows failed. Will post RCA when isolated. Note this is using Professional Direct support contract.
For reference I logged into the Azure portal with an account with no support contract to test your condition. I was able to create a support ticket but with a very limited set of options, under the TECHNICAL heading, only AZURE INFORMATION PROTECTION option was available for example.
My storage account deletion issue has highlighted an error condition exists where a Global Admin user is unable to delete a storage resource containing no data or resource lock. In this case Microsoft are actioning the removal of the problem resource following several weeks of calls , threads and remote sessions.
I suggest you attempt to raise a ticket via any means , highlight your issue and hopefully Microsoft will internally route the issue to the correct department.
Root Cause Analysis
An operation to delete the storage account was never finished Azure side.
Every operation holds a lock on the storage account to prevent conflicts between different operations.
In my case the lock prevented all other operations we performed: deleting, updating, deploying etc.
Microsoft are yet to detect which operation exactly was causing the issue but explained similar issues when another user tried to modify the tag of a storage account with misused escape characters.
In my case its likely that a DevOps pipeline was modifying the storage account, the request to Azure Resource Management(ARM) was somehow incomplete due to, for example, a network fluctuation / transient error.
Resolution
The way to resolve the issue is Microsoft manually reset the status of the lock on the storage account and release the lock form the storage account. Delete operations are then possible. Microsoft are taking steps to improve the process.
I'm aware I can now do this through the portal in the storage blade however the account I need to migrate is a production account. It's just blobs, tables and queues, no VMs.
I can stomach some downtime (say an hour or 2) but am unsure how long it would take to migrate approx 750GB, does anyone have experience with the migration and an idea on the time it takes based on a similar volume size?
I also assume once migrated all my storage keys will change so I will need to update all the references in my app settings.
For anyone else wondering about this what #4c74356b41 said appears to be true.
Thanks to this post and the PowerShell command, couldn't get the ARM template to dpeloy at least not from VS, I was able to create a classic storage account. Didn't think this was still possible!
I then kicked off a 50k files container copy from another storage account in the Azure Storage Explorer container into this new classic resource and then while that was running ran the full migration including commit and the file copy carried on regardless.
Final step was to move the new resource (file copy is still ongoing at this point) from the migrated resource group back into the same resource group as the original classic storage account.
Once the move was complete the file copy was still going smoothly and all the Keys remained unchanged so this does seem to be truly seamless.
I mistakenly created a VM without linking it to an extant storage account. When I realized my mistake I deleted the VM and then sought to delete the storage account. I found the auto created storage account and attempted to remove the container. However even 24 hours later I get told that the container contains resources in use by the (now deleted) VM and so cannot be deleted.
Clearly there is some kind of dependency which is not apparent from the management portal which needs to be removed. I am looking for some advice on a powershell approach to investigating and resolving this issue.
You have to disassociate the disk with the VM image (VHD) before you can delete the blob or container.
You can do so from the Windows Azure management portal. Go to the VMs tab. Choose 'DISKS' from the top menu and remove it. If I remember well, it will also ask you whether you'd also like to delete the blob (VHD) from the storage account.