I am trying to create an instance but I keep getting the error of billing must be enabled. I have enabled billing and I gave it several hours and I am still having the same issue. Project Number: 375741478
Related
I am creating a self hosted integration runtime. There is error in registration after installed the IR on Window.The authentication key is just copied from portal and paste on it. But, the warning says the key is invalid or empty. How can I solve it?
Both Azure Data Factory and on-prem data server are on same time zone so no time delay.
Any suggestion would be great as struggled most of the day.
I have tried by using express route exe and integration runtime msi both but same result no luck :(
It was networking issue as same key working on public endpoint network setting. Now it will fix private endpoint.
I am an IBM employee who created a DB2 on Cloud service. I received a message that I need to reactivate my account, with a link. Clicking the link does not reactivate the account.
When I go to the DB2 on Cloud console there remains a "Reactivate Free Tier" button. Clicking this just brings me the same dashboard the link takes me to and it does not contain (or where I can not find) my DB2 on Cloud service (and it does not reactivate the account)
When trying to log into the DB2 on Cloud database, I continue to receive the error message:
Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000
Benjamin Schubert was able to reactivate my account. I've copied Benjamin's response below:
There is a bug with syndicated instances that we're working to resolve. In the meantime I've reactivated your instance manually. By the time reactivation comes back around (30 days from now) the issue will be fixed.
I tried to create a new logging instance on LogDNA service on IBM cloud , although I chose lite plan
It is always failing with error message
Your account does not allow the use of non-lite plans. You can upgrade by adding a credit card to your account or you can select the lite plan if it's available.
This is a bug, it is being addressed. You could work around this by upgrading your account with a credit card. No charges will be assessed for the free lite plan for the logging with logdna service. Or you can wait for the problem to be addressed.
We currently have one DevOps repository, with a functional CI/CD pipeline. We have another website hosted on a different instance (and different region) on Azure. We are trying to use our existing repo to deploy to the other Azure instance, but it is giving is the following message:
Failed to query service connection API: 'https://management.azure.com/subscriptions/c50b0601-a951-446c-b637-afa8d6bb1a1d?api-version=2016-06-01'. Status Code: 'Forbidden', Response from server: '{"error":{"code":"AuthorizationFailed","message":"The client '2317de35-b2c2-4e32-a922-e0d076a429f5' with object id '2317de35-b2c2-4e32-a922-e0d076a429f5' does not have authorization to perform action 'Microsoft.Resources/subscriptions/read' over scope '/subscriptions/c50b0601-a951-446c-b637-afa8d6bb1a1d'."}}'
I have tried all of the recommended trouble-shooting, making sure that the user is in a Global Administrator role and what-not, but still not luck. The secondary Azure subscription that we are hoping to push our builds to is a trial account. I'm not sure if it being a trial account matters.
I came across the same error. It turns out that, as the error message states, the service principal didn't have Read permission over the subscription. So the solution was to go to Azure Portal, select the subscription, select IAM and assign the role Reader to my service principal. Full explanation on here:
https://clydedz.medium.com/connecting-azure-devops-with-azure-46a908e3048f
I have the same problem. There are one repository and two instances of the application on the Azure portal. For the first instance, the subscription Pay-As-You-Go is used, and there were no problems for it when creating the service connection and CI/CD settings. For the second instance, a free subscription is used and when trying to create a new service connection (Azure Resource Manager) I get the same error.
I tried to do it with the permissions of Owner and Contributor
UPD: I was helped by the re-creation of the application in the azure portal
https://learn.microsoft.com/en-ca/azure/active-directory/develop/howto-create-service-principal-portal
Another option would be to save without verification if the Service Principle will not require permissions at the Subscription level. Like for example providing access to a Keyvault.
Check if the service connection for the second instance is correctly added in project settings:
When trying to send mail with nodemailer library inside Firebase Cloud Function. I'm getting error:
Billing account not configured. External network is not accessible and quotas are severely limited. Configure billing account to remove these restrictions
I'm on Blaze (Pay as you go) plan.
I have same errors recently due to an expirated card, so i replace with fresh new card but errors persist Billing account not configured. External network is not accessible and quotas are severely limited. Configure billing account to remove these restrictions
So i revert to Spark plan and return to Blaze Plan
After that all it's working