When trying to publish a cloud service to Azure i keep getting this error: The extension ID MSVSAZ-ApprovedProducts-WAD11-8 is not found in the hosted service.
Is there a quick resolution to this that doesn't require me to restart visual studio each time this occurs?
As Khoi mentioned it has to do with Windows Azure Diagnostics. You can either disable the Azure Diagnostics from your project
or you need to add the Azure Diagnostics to your Azure subscription.
Here is a link how how to configure.
https://learn.microsoft.com/en-us/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines
To disable you would need to uncheck the Enable Diagnostics and not check it.
Related
I'm using Visual Studio 2019. I can attach the debugger to services running in my own subscription.
When I try to attach to services running in another sub from cloud explorer, I get various errors and the attachment never succeeds. The most common is:
Unable to find a process called w3wp with arguments {app service name}. The process may still be starting, please try again.
When trying to attach under the Debug -> Attach to Process dialog, I get the following error:
Unable to connect to {path}. The connection with remote endpoint was
terminated.
I have owner role on the subscription, on the app service and on the app service plan.
Please validate if you have enable debugging from azure platform side. Screen shot od the same from portal looks like:
Also please confirm if you have deploy application from VS.
Visual Studio remote debugging on azure app services used 4020, 4022, 4024 ports for debugging.
https://learn.microsoft.com/en-us/azure/app-service/networking-features#app-service-ports
I try to add a Azure DevOps Server (on prem) as Symbol Server. Unfortunately I am not able to add the Server with the Connect to Azure DevOps Symbol Server dialog.
After a click on Add I could add my Server Url. But what ever I input, the Dialog is not able to find the Server.
The url pattern is: https://azure-server.de/
What is wrong? Connecting with the Team Explorer instead is no problem.
Meta:
Artifacts: Activated
Version: 17.153.29207.5 (AzureDevOps2019.Update1)
Proxy: Yes
The Symbol Server is not embedded in on-premises installations of Azure DevOps. It is only available in Azure DevOps Services, hence the absence of possibilities to connect to an on-premises server. You can check it in the Features Timeline: search for symbol server and you'll see that the server column indicates N/A.
You can read the same here; and, in this blog, the author says:
We plan to bring Symbol Server support to our on-prem TFS product, as
soon as we can.
But apparently that never happened...
I would advise you to use the File Share option (although not an ideal situation) when publishing & reading Symbols.
I'm trying to follow a tutorial on Azure deployment. I'm stuck on one of the first steps creating the App Service. It seams that the form tries to find all App Service Plans but can't, so all of Visual Studio hangs. I had to kill it with Task Manager. Any clues on how I can fix this? Do I need to create something at the Azure management console?
Had the same issue, turned out I hadn't installed Azure SDK, you'd think there would be some kind of error message, but no. Installing the SDK fixed issue
I did the steps below to resolve the issue.
Login to your Azure account
Manually create an app service (use any dummy app service name). The service plan and resource group will be created while you're creating this app service
Once you see the dummy app service created on your Azure dashboard (it will take around 1-2 minutes), open your visual studio from your pc, create your web project and check api service
--- This time, the service plan and resource group will be brought in.---
Click "Create" to create your "real" web/api project in Azure
Now you can remove the dummy service from Azure
I had the same problem. It started to work after I logged into the Azure Dashboard and manually created an App Services Web App.
Ran into the same issue a few days ago and here is how I got it working.
I had yet to create any App Services in the Azure account I had tied to Visual Studio and when I got to the Create App Service window you posted, Visual Studio would freeze.
I logged into the Azure Portal, created an App Service with a different name than the project. Once it was created, I then deleted the newly created App Service.
After doing this had no problem freezing in Visual Studio. The fix appears to be to create at least one App Service in portal before it works in VS.
I did two things at once, not sure which one got through the lock up.
1) In Visual Studio, went to File -> Account Settings then under the "All Accounts" section of the Account Settings window I reentered my credentials for the Azure account I had linked the project to. This account had a notification raised saying "We need to refresh the credentials for this account."
2) As others have said, I created a new Web App. I'm not sure this was the problem, however - I had previously created a couple other web apps and these resources were still present in my dashboard.
I have to agree with the above comments, too - the error messages provided for this are really, really poor.
Check that there are no characters that it will not accept. For instance an underscore '_'
Azure built a dummy name for me to use including an underscore which it does not accept. It was trial and error for me to find this where a simple warning would have saved lots of time.
Login to Azure Portal and create necessary resources. VS screens do not seem to work properly.
I created Api App on azure portal and my problem solved.
Same problem, however I have 3 Azure subscriptions, but even after making sure all of'em has at least one App Service it still hangs on this step. No other option than to not check the option to host.
Updating Azure SDK on VS2015 fix the problem in my case
I have been using Visual Studio to deploy a Web Service to Azure; downloaded my publish profile to enable that and it was working fine for the past few weeks.
Today I tried to deploy an update and now all my deployments fail with the following:
17:25:03 - Preparing deployment for WindowsAzure1 - 25/03/2013 17:24:53 with Subscription ID 'xxx' using Service Management URL 'https://management.core.windows.net/'...
17:25:03 - Connecting...
17:25:04 - Object reference not set to an instance of an object.
17:25:04 - Deployment failed with a fatal error
I'm not sure what's failing here; is this saying it's unable to connect to the Service Management URL?
Last week I installed an SSL certificate on Azure and now I'm not seeing the option to download my publish settings. I know it used to be there but isn't now. Does having an SSL prevent me from somehow connecting to the management page?
Edit
Before leaving work I removed the certificate but when I then checked for the PublishProfile it was still not showing.
The PublishProfile is not available for any of the other users attached to the subscription - so I don't think it's related to my login.
Edit 2
A bit more drastic; I've now tried deleting my storage and service, to start from scratch. I created a new publishsettings file by removing the subscriptions already imported into Visual Studio and then following the link to "Sign in to download credentials". Next I created a new service and storage in Azure and tried to publish but the deployment still fails when connecting with
Object reference not set to an instance of an object
I have no idea what else I could try or what could be wrong, or where to look to find out.
I got the same error today. Why it wasn't working was because I hadn't uploaded the certificate in the managementportal prior to the publish.
After adding the certificate, everything worked just fine!
You can read more here: http://www.amido.co.uk/mark-omahoney/publishing-in-windows-azure-object-reference-not-set-to-an-instance-of-an-object/
The best way to solve above problem is to download the latest PublishSettings from Azure Management Portal and then use it with Visual Studio. This way your connection to Windows Azure Management Portal from local machine will be verified and validated. Once you have the basic connection working then you can publish your application to specific Windows Azure Service.
Also you can log into your Azure Management Portal and remove all old management certificates which are added in previous publishsettings download attempts.
The problem, in my case, was that my solution Cloud project had the thumbprint of the SSL certificate I'd uploaded in its ServiceDefinition.csdef and ServiceConfiguration.Cloud.cscfg. In my first edit I said that I'd removed the certificate from Azure, but hadn't then removed it from the project files; commenting them out allowed me to publish from Visual Studio again.
I'm not sure why this happened though, I had uploaded the certificate to Azure and was able to connect to my service on https in FireFox so the SSL was "working".
Web Deploy v3.6 BETA3 was released that fixes this issue. To resolve this error, you can download the Web Deploy beta and patch your VS2013 installation. http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/
Test Validate Connection once you installed the above Web Deploy. If it works, then fine else you can modify the proxy settings used by msbuild.exe (msbuild.exe.config) and check you can now publish from behind a proxy with Web Deploy.
Regards,
Logesh Shan
I think the certificate got corrupt. Deleting the solution .suo file and the .ccproj.user file in my Azure project did it for me.
I have gone through the Lab AdvancedWebAndWorkerRoles which you have provided in the latest training kit WAPTK. I followed the steps in Exercise 1:registering sites,Applications and Virtual directories .It is running fine in windows azure emulator(locally),but i cannot find any steps to host in the windows azure management portal.
Can any one suggest(steps) how to host the same application in the windows azure management portal?
We know how to deploy applications in windows azure portal.As i had mentioned in my question about the Exercise 1:registering sites,Applications and Virtual directories in the training kit WAPTK ,we want to create the similar application and host in the azure.The steps to host the Exercise 1 application in management portal is not mentioned in the training kit.We tried to host the application in windows azure portal but it is not working as the ServiceDefinition.csdef include some different configurations.We wanted to know the steps to host that application in management portal.
Under the Introduction to Windows Azure lab, look at Exercise 3: Publishing a Windows Azure Application. This shows how to publish via the portal. The basic steps:
Build your Windows Azure service in Visual Studio, but tell it not to publish. Just generate the package file and configuration file.
Create a new hosted service. This gets a name like myapp.cloudapp.net. You'll need to find a unique DNS prefix.
Select the generated package file and configuration file, from the portal, which results in your service being launched. This takes a few minutes, and you can watch its status via the portal.
You may also publish directly from Visual Studio. See this MSDN article for instructions on setting up Visual Studio correctly (which basically imports your publishing settings from the portal). Visual Studio can perform all of the steps without having you to actually do anything in the portal (aside from exporting your publish settings).