I am having difficulty deploying a basic Azure WebJob from Visual Studio. The deployment will successfully create the web app, app service plan and resource group. However, it fails to deploy the webjob. I receive the error message below:
Following errors occurred during the deploymnent:
Error during deployment for resource 'resourcename' in resource group 'ResourceGroup':
MissingRegistrationForLocation: The subscription is not registered for the resource type 'components' in the location 'Central US'. Please re-register for this provider in order to have access to this location.
I've tried multiple subscriptions, resource groups and app service plans in different regions and continue to receive the same error. Please help.
Deploy the Azure WebJob in the ‘Central US’, it works for me correctly with Visual Studio 2015 Azure .Net SDK 2.9.5.
The errors seems like another SO Thread, it may be caused by old version of Azure SDK. If it is that case, please have a try to use the latest Azure SDK.
And we can follow the document to deploy WebJob with Visual Studio. If we deployed with Azure Resource Manager, some
troubleshoot common Azure deployment errors with Azure Resource Manager please refer to document.
Related
We are getting this error on-and-off since 01/22 on Composer UI, the airflow dags seems to be running fine, the web UI however having the problem. Google cloud status page indicates there is no issue, changing browser or connection through other wifi / mobile hotspot doesn't help either. Not sure what's going on.
An internal server error occurred while authorizing your request. Error code 1
location: us-central1-c
version: composer-1.7.3-airflow-1.10.2
Cloud Composer is a managed workflow automation tool, so I don't think that you can address this issue directly.
For more context on what is happening, Cloud Composer architecture states that the Airflow Web Server is inside of a Tenant project, which is a isolated environment used for deploying managed services, this is for unified Cloud Identity and Access Management (IAM) access control and an additional layer of data security. Given that the error states that something is failing when authorizing, this issue may be related to the Cloud IAM service.
I recommend you to open a new case from the GCP console in the Support section, and ask for further assistance in this issue.
I receive an error message while attempting to deploy anything from the marketplace into a specific GCP project.
You must have a valid default service account in order to create a
deployment, but this account could not be detected. Contact support
for help restoring the account.
Things I've Tried:
Every VM from the marketplace shows the same error message
I can deploy regular VM instance
I can see there is an enabled service account for the project with the name "Compute Engine default service account".
I am able to deploy VM's from the marketplace into other projects under the same organization
I've contacted GCP Billing support and they cannot find anything wrong from a billing perspective
Researching online shows that others that have had this issue have just rebuilt the project. It appears that service account is created by default when the project is spun up.
I'm hoping there is another way around it as this project is a host for a shared VPC deployment. There are already other projects with deployed VM's that are utilizing the host projects networks.
Thank you!
Looks like you deleted a default service account.
As mentioned in one comment some can be recreated by disable/enable the corresponding API
Below are the default service accounts I have in my project, hope it helps you to find the root cause. (these service accounts let me deploy a wordpress solution depending on what you are trying to deploy you might need more service accounts)
PROJECT-NUMBER-compute#developer.gserviceaccount.com Compute Engine
default service account
PROJECT-NUMBER#cloudservices.gserviceaccount.com Google APIs Service
Agent
PROJECT-ID#appspot.gserviceaccount.com App Engine default service
account
service-ORG-ID3#gcp-sa-cloudasset.iam.gserviceaccount.com Cloud Asset
Service Agent
service-PROJECT-NUMBER#cloud-ml.google.com.iam.gserviceaccount.com Google
Cloud ML Engine Service Agent
service-PROJECT-NUMBER#compute-system.iam.gserviceaccount.com Compute
Engine Service Agent
service-PROJECT-NUMBER#container-engine-robot.iam.gserviceaccount.com Kubernetes
Engine Service Agent
service-PROJECT-NUMBER#containerregistry.iam.gserviceaccount.com Google
Container Registry Service Agent
service-PROJECT-NUMBER#dataflow-service-producer-prod.iam.gserviceaccount.com Cloud
Dataflow Service Account
service-PROJECT-NUMBER#service-networking.iam.gserviceaccount.com Service
Networking Service Agent
The service account was intact and had the same permissions as other service accounts for working projects.
We purchased and opened a case with GCP technical support. After a little more than a week of them troubleshooting the issues, they determined there was no way to correct the problem. Their root cause was that something happened during the initial project deployment that caused some backend configuration issues. For what its worth, the project was deployed using Terraform, but its uncertain if that was a factor.
After recreating the host project, we were able to deploy from the marketplace again successfully.
If you run into this problem, save yourself the hassle and time and just recreate the project.
I'm using microsoft TFS and I want to make continuous deployment on AWS using CircleCI.. Is that possible? if not, what should I exactly do?
Afraid not, CircleCI is just a continuous integration tools which TFS could also do the CI and include some useful task easily enable build and release pipelines.
You could use AWS Tools for Microsoft Visual Studio Team Services.
This tool include a new service endpoint type, AWS, to supply AWS credentials to the tasks at runtime.
It will create an AWS Credentials Connection. Select the AWS endpoint type and provide the following parameters:
A name used to refer to the credentials when configuring tasks that
require AWS credentials
AWS Access Key ID
AWS Secret Access Key
After an AWS subscription has be linked to Team Foundation Server, you could use the task deploy to Amazon EC2 with AWS CodeDeploy.
Note: Minimum supported environments
Visual Studio Team Services
Team Foundation Server 2015 Update 3 (or higher)
I'm trying to connect to AWS (Amazon Web Services) using Visual Studio 2017. However, in the AWS Explorer in Visual Studio, it says "Failed to connect to AWS".
I created an account in the AWS IAM Management Console.
I assigned this account AdministratorAccess and created access keys.
I installed the AWS SDK for .NET for Visual Studio 2017.
In the Visual Studio AWS Explorer, I selected and created a New Account Profile.
The AWS Explorer shows "Failed to connect to AWS". (The Region list is still disabled.)
It seems like a rather simple process, but it's not working for me.
As a credential test, I set up the AWS CLI (Command Line Interface). Then I ran aws configure using the same Access key ID and Secret access key. I was able to access AWS--e.g. aws iam list-users and aws lambda list-functions. (I have some test lambda functions in my account already, and they showed up.)
What am I missing? Let me know if you need any more info.
Thanks.
Ok, so now it's suddenly working. I hadn't touched it for a while, and then clicked 'Refresh' in the AWS Explorer. The Regions list is now populated and all of my services are displayed.
Is it possible that AWS takes a while to propagate users and access? Just a thought.
-- Update
I tried again the following day, and now I get the original error again. I have not changed anything. In fact, my dev environment was left open overnight.
What the heck could have possibly changed?
Do you have the Fiddler installed and running? If yes, please close the Fiddler and try again.
I am totally new to Azure, I have stumbled across it as a I wish to farm out a Web Service for updating our database without hosting it internally and potentially involving any security risks.
Therefore I have got myself a free Azure Web Trial to see if its worth it. I have an .ASMX based Web Service (Because this is all I know to build) and I wish to deploy it to Windows Azure.
Is this at all possible?
Cheers,
James
Yes I've done just that myself. Add an AzureCloudService project to your solution (requires the Azure sdk); create as an empty project, do not select any web or worker roles as part of the project creation.
Under the Cloud service select Roles -> Add -> Web Role project in solution...
and select your existing web service project
From the context menu on the Cloud Service project you will be able to package or publish to Azure.
You could do that inside Visual Studio, right click on the name of the project and then click publish, and of course after that you will be asked to log into your azure account and with a click you'll have your web service deployed and ready to be consumed.