I'm unable to create a cloud object storage plan on my lite account. Everything is fine but it keeps on bringing this error.
[409, Conflict] The account already has an instance created with the
Lite plan.
Transaction ID: 0d6c5ad8f82f401f979876fca94f5254:59967a3beae87f54
what could be the issue.
Related
I am trying to redeploy an Azure Cloud Service (classic) to an "extended support" one since the former is being deprecated. Following this guide and the prerequisites I have created a virtual network and new storage account. I set up a bunch of permissions and the Connectivity Check for my storage account indicates no problems. However when I try to create and deploy a new Cloud Service (Extended Support) using my (updated) .cscfg, .csdef and .cspkg files I get this error:
Error:AuthorizationFailure, message:This request is not authorized to perform this operation. (Code: PackageUriForbidden)
I've tried setting the container and blob access to public for the deploy files, I have added Network Contributor and Storage Blob Data Contributor to both the subscription and the cloud storage resources for my user account. What am I missing?
I tried deploying cloud services extended support via Azure Portal and it got deployed successfully.
Refer below :-
I have uploaded all my cloud services packages in my storage account and used those packages from my storage blobs and created the Cloud service ES instance.
I enabled connection from all networks for my storage account, Thus I did not receive any authorization error :-
It looks like your Storage account has Firewall and V-Net enabled for the selected Networks. Or There’s an IP Address added to restrict storage account.
I created a Create a Service endpoint in my V-Net to allow Microsoft.storage like below :-
Added this V-Net in the selected Networks in Storage account’s Firewall :-
Checked this in order to allow azure services to access storage account like below :-
Now, when I try to deploy another cloud service with the same storage account having firewall and V-Net enabled, I get the same error as yours refer below :-
I allowed my client machine’s IP in the storage account and was able to add the packages without any error while deploying the Cloud Service:-
I'm new to azure service fabric, and tried to setup one using a free trial account in azure. I created a service fabric cluster with a single node. Then I created an app in my local machine with one Stateless Web Service and a Stateful .NET Core Service. In my local machine, I can get everything working, but when I tried deploying it to azure, all stateless services are not working. I say this because, whenever I created an app with only a stateful service in there, it's still not working in azure.
The stateful service app as I monitored it from the Service Fabric Explorer it gives a warning as below image:
and after a warning, it will then turn into an error with the following message:
I tried finding solutions online but I found nothing. I read some articles saying that It could be a disk storage problem, but I don't know how to resolve this because in a Free Trial account, I think you have a limited storage.
Please help. Thanks.
What's the VM SKU of your cluster? Did you setup your cluster?
Go to your cluster via the azure portal, the name of the VMScale set would be the same name as with your cluster's node. Go to the VM Scaleset and check the SIZE in the overview. You might need to change / upscale your VM Scaleset
I am trying to integrate my odoo with azure blob storage, how can I do that?
you should checkout the capabilities of odoo on their documentation page: https://docs.bitnami.com/azure/faq/
There is a section of the supported capabilities in Azure as bellow:
The Bitnami Launchpad for Microsoft Azure creates the following resources in your Microsoft Azure account:
A storage account for each region in which the user launches an instance.
Application images are added to that storage account when the user launches instances.
Machine disks are created in that storage account when the user launches instances.
A resource group with the rest of the resources needed by the instance.
A resource group for the various storage accounts.
Source: https://docs.bitnami.com/azure/faq/
I'm working with Azure Java API in Eclipse.
In my program, I get the Azure credentials from the user. In this way I can use for example the Blob storage service using the Java API for Azure.
But my problem is when I want to manage the data bases deployed in Azure SQL service. My question is if I can list the data bases that the user have created in his Azure account using the Java API and the Azure credentials.
My Web Role is on StorageAccount1 and my Azure Storage Table on StorageAccountB.
My Web Role performs operations (inserts, updates, queries) on the Storage Table.
Both of these Storage Accounts are in the SAME Affinity Group.
Will performance be better if my Web Role and Storage Table are in the same Storage Account?
You are probably confused by the "Publish" window in Visual Studio. The "Publish" window allows you to choose some info on how your application is deployed, like the Cloud Service but also the Storage Account. When you choose a storage account it doesn't mean your application will be stored in that storage account, it only means that the service package (the package which contains your application) will be uploaded there. Once the package is uploaded the Fabric Controller will take it and deploy it to your Cloud Service.
Besides that it's still a good idea to deploy your Cloud Service (Web Role) in the same affinity group as your Storage Account. By choosing the same affinity group Windows Azure will try to physically group your Cloud Services and Storage Accounts to minimize the network overhead.