Unable to web deploy to Linux App Service from Visual Studio 2019 - azure

For about 2 weeks now I am unable to web deploy from Visual Studio 2019 16.9.6. I have an ASP.NET Core 3.1 MVC application that I am trying to web deploy to a Linux App Service on Azure. When I try to publish I get the following errors:
Publish has encountered an error.
Build failed. Check the Output window for more details.
A diagnostic log has been written to the following location:
"C:\Users\ken\AppData\Local\Temp\tmpF3BF.tmp"
An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
Prior to two weeks ago I had no issues. The following is a list of items I have tried:
Stopped and started the app service
Stopped the app service and tried deploying while it was stopped
Reset the publish profile and re-imported it into Visual Studio
If I edit the publish profile and click "Validate Connection" it fails and gives the same error message as above:
An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
I am able to publish locally and use an FTPS client to connect to the app service and manually deploy the files.

I deleted the current publish profile and instead of downloading it from the Azure portal I used the new publish profile wizard built into Visual to create the publish profile. Once I did that everything started to deploy with no issues. I looked at what the difference is and it seems the publish profile I downloaded from Azure was missing an XML element called "IsLinux".

Related

.NET Core API failing from Azure DevOps but successful from Visual Studio deployment

I have an issue with an .NET Core API which fails to start after it is deployed from an Azure DevOps deployment pipeline, but manages to startup when published from Visual Studio.
The deployment appears successful on DevOps, but going to the API's Swagger page returns the standard "HTTP Error 500.30 - ANCM In-Process Start Failure" error page.
Here's a screenshot of the pipeline setup:
Screenshot of logs for deployment step:
No App Settings, Configuration Settings or pipeline variables have been defined.
However, publishing from Visual Studio 2019 via imported .publishsettings file deploys successfully and API starts up successfully as well.
I did notice that when deploying with Visual Studio, the usual "Starting up" message from the logs appeared, but it did not log anything when deploying from Azure DevOps.
Any ideas on what could be the issue? Let me know if I need to provide more details.

Deploying ASP.Net Core application to Azure Website using Visual Studio Team Services has an ERROR_DESTINATION_NOT_REACHABLE error.

I'm working on deploying an ASP.NET Core application stored in Git on Visual Studio Team Services. I've been following this process (https://www.visualstudio.com/en-us/docs/build/apps/aspnet/aspnetcore-to-azure); however, I receive the following error on the deployment step, and I'm running into a brick wall. I have verified that I have an SSL cert on xxx.com and www.xxx.com, but it still is failing. Any Ideas?
Error Code: ERROR_DESTINATION_NOT_REACHABLEMore Information: Could not connect to the remote computer ("www.xxx.com"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.Error: The remote server returned an error: (404) Not Found.Error count: 1.
Try adding following script in "PublishAspNet5Website.ps1" to see which is the correct MSDeploy URL:
Write-Output $website.EnabledHostNames[0]
Write-Output $website.EnabledHostNames[1]
Write-Output $website.EnabledHostNames[2]
...
Links for your reference:
Resolve an ASP.NET 5 Deployment Issue to Azure Web App Slot
MSDeploy to Azure Web App: Could not connect to the remote computer using the specified process (“Web Management Service”)

Publishing web application works in Visual Studio, but generated package cmd file fails with insufficient permissions

I'm trying to deploy a web application from the command line. Eventually I'll do this from my build server (running Jenkins), but for now I'm doing it from my desktop.
My web server runs Windows Server 2012. I'm using Visual Studio 2012 on the desktop. Within Visual Studio, publishing directly, using the Web Deploy method, works fine. If instead I use the Web Deploy Package method, then run the generated .cmd file, it fails with
Error: (3/14/2013 7:35:49 PM) An error occurred when the request was processed on the remote computer.
Error: An error occurred when reading the IIS Configuration File 'MACHINE/REDIRECTION'. The identity performing the operation was 'WEB\uoedeploy'.Error: Filename: \\?\C:\Windows\system32\inetsrv\config\redirection.config
Error: Cannot read configuration file due to insufficient permissions
Following instructions from Microsoft and elsewhere, I have created an account on the web server for publishing, and I use the same account credentials for both publishing methods. I added that user to the group MSDepSvcUsers on the web server. I checked the effective permissions for that account on redirection.config, and it shows read permission.
I hate MSDeploy.

TFS PREVIEW: How do I setup a hosted build controller

I have read that Microsoft announce Build Service and hosted build controller as shown in image below. I have have setup TFS preview using this article.
But When I am trying to connect my cloud service it says there no hosted control found.
Can you please tell me how to setup hosted build controller.
Announcing a Build Service for Team Foundation Service
Hosted Build Controller should be available by default. You shouldn't have to do anything to "set it up".
Here's what I see in my TFS Preview account.
Although TFS Preview has been having some issues lately. On Friday, builds that were queued, were stuck in the queued status for a long time before it got picked up for compilation & deployment.
Check the status here - http://tfspreview.com/en-us/support/current-service-status/

ERROR_DESTINATION_INVALID in windows Azure

I have created simple MVC4 website for windows Azure by following this tutorial: https://www.windowsazure.com/en-us/develop/net/tutorials/web-site-with-sql-database/
At step-8, where I am supposed to "Validate Connection", I get an ERROR_DESTINATION_INVALID error.
Editor: Visual Studio 2012 (Winsows Azure tools SP1)
OS: Windows 7
Tried restarting Studio and restarting computer options. Also tried recreating website in manage.windowsazure.com
Logs:
Start Web Deploy Publish the Application/package to https://waws-prod-bay-001.publish.azurewebsites.windows.net/msdeploy.axd?site=trackme ...
2>Starting Web deployment task from source: manifest(C:\.SourceManifest.xml) to Destination: auto().
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4377,5): Error ERROR_DESTINATION_INVALID: Web deployment task failed. ( Could not connect to the remote computer ("waws-prod-bay-001.publish.azurewebsites.windows.net"). Make sure that the remote computer name is correct and that you are able to connect to that computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_INVALID.)
As your publish from VS is not completed due to this error, there are couple of things which could go wrong.
Based on error info it seems the connection to Windows Azure Websites deployment server was unsuccessful. I just pinged the waws-prod-bay-001.publish.azurewebsites.windows.net deployment server and got the IP address so would you please check and verify if you get the same. Also you may need to verify that there are no networking issue which could cause this problem.
Also if you have SQL Database configured with your publish profile then there are two servers needs to be connected during deployment. So if this error occurred when you have had SQL Database configured or before that? Sometime this error is sporadic so you may have to consider as well.
If web deploy fails, publish using FTP. You can download publish settings for you site from Azure portal, under dashboard, click "Download the publish profile". In Visual Studio, when you publish, select Profile, and then Import. Import the settings file. Then unselect the Web Deploy and select the FTP deploy. This worked for me when Web Deploy refused to work (even with the downloaded web deploy settings).

Resources