Publish to Azure succeeds but Visual Studio says that it failed.

Carolyn Schroeder 186

With the publish profiles that I have for my Azure Web Apps, when I publish, the output information is that the publish succeeded but the publish page says that the publish failed. Usually I have fixed this by creating a new publish profile, but I have not been able to sign in to Azure from the Publish dialog in Visual Studio. I can always deploy by importing a publish profile but the publish profile approach does not allow enough for remote debugging.

Carolyn Schroeder 186 Reputation points

2022-09-30T13:10:52.803+00:00

When the Publish page says the publish failed, there is no error in the error logs. This just happens for my web apps deployed to Azure, the Azure functions do not fail.

I keep Visual Studio updated.

I have looked at the basic instructions for deployed a web app but I cannot even get a login from the Publish dialog. I cannot see my subscriptions.
ajkuma 22,401 Reputation points Microsoft Employee

2022-10-01T09:33:09.31+00:00

CarolynSchroeder-2130, Apologies you're still facing this issue. Thanks for the follow-up. To better understand, could you please share a screenshot of the issue after concealing any private details?
I understand you're attempting to provision from VS, in the interim (as a quick step), if you wish you may try to provision Azure WebApp directly from Azure Portal as outlined in this document -

Accepted answer

Jandos 96 Reputation points

2022-10-28T01:01:28.643+00:00

I had the same issue recently. The reason was my azure security token was expired. I just had to open new profile window, and re enter my credentials, and cancel creating new profile. Then everything worked as before.
Please sign in to rate this answer.

4 people found this answer helpful.
Carolyn Schroeder 186 Reputation points

2022-10-28T13:42:15.123+00:00

It is very hard to re enter credentials from the publish dialog. I had to debug remotely recently. I followed all the suggestions given to me in this forum and anything I could online but was unable to debug remotely using the publishsetting file approach. I was finally able to enter my credentials and bring my subscription information up in the publish dialog.

Ben 1 Reputation point

2022-11-27T21:46:07.273+00:00

Also had this problem and this fixed it for me. Thanks.
It's a shame VS couldn't have worked that out and prompted for new credentials when publishing the first time instead of just showing a very unhelpful message.

MCLAUGHLIN, KEN 0 Reputation points

2023-02-28T17:08:38.1366667+00:00

Thanks, this post was helpful. However, I did find a way to enter the credentials directly, without creating a new profile. In the VS Tools Menu, Options -> Azure Service Authentication. Under the Choose an account drop down, there should be a link to click to re-enter credentials (not visible in my screenshot since I just re-entered them).

Carolyn Schroeder 186 Reputation points

2023-02-28T23:46:03.28+00:00

This was not helpful. I am an admin on an account but can only see accounts that have Active Directory.
Sign in to comment

4 additional answers

Carolyn Schroeder 186 Reputation points

2022-10-02T17:38:25.103+00:00

I have attached a screen shot.

There is nothing in the referenced error logs.

I am continuing to deploy from Visual Studio. The publish does succeed in spite of the error message. The newly deployed site does not come up in the browser.
Please sign in to rate this answer.

1 person found this answer helpful.
ajkuma 22,401 Reputation points Microsoft Employee

2022-10-03T11:57:47.84+00:00

Carolyn, Thanks for sharing the requested details.

I understand the webapp is not coming-up automatically after publish is successful (w/error), I see that your WebApp is running fine: https://americanprintmedia.azurewebsites.net/

So, it appears that the issue is isolated to VS and profile, kindly try the suggestions shared by LanHuang-MSFT to further narrow-down the issue.

Just to highlight -

--A publish settings file (*.publishsettings) is different than a publishing profile (*.pubxml) created in Visual Studio. A publish settings file is created by Azure App Service, and then it can be imported into Visual Studio.
--On Azure Portal > App Service > your webApp > 'Get publish profile'

--When publishing to an Azure target, the .pubxml file contains your Azure subscription identifier. With that target type, adding this file to source control is discouraged. When publishing to a non-Azure target, it's safe to check in the .pubxml file.

--ZipDeploy is intended for xcopy or ftp style deployment. It unzips the artifacts and lay them out exactly to d:\home\site\wwwroot.

--One requires VS or MSDeploy tooling to generate MSDeploy zip package. If you are using other tooling such as typical zip tool, the
MSDeploy may not understand the content resulting in unintelligible error such as certain directory not found or create file operation failed.

Just for your info: I'm an SME from azure-webapp tag and LanHuang-MSFT, SME from dotnet | VS tag has shared suggestions.

Carolyn Schroeder 186 Reputation points

2022-10-04T20:13:46.56+00:00

I am unable to get the subscription information into the Visual Studio Publish page when using a Publish Settings file. This is necessary for remote debugging.

ajkuma 22,401 Reputation points Microsoft Employee

2022-10-07T17:10:03.87+00:00

CarolynSchroeder-2130, Thanks for the follow-up. Apologies the issue still persists.

--Remote debugger ports are configurable. Currently, Azure App Service does not use the default ports associated with your version of Visual Studio. Azure App Service uses port 4024 for the remote debugger.
Kindly check this: remote-debugger-ports-on-microsoft-azure-app-service

--If you haven't tried (unless I missed the version you're using), you may try with VS 2017 or VS 2022, there is a known issue with VS 2019 with remote debugging.

--For VS versions VS2022 17.2.0 and later, no changes are required and can use Target Type of Azure App Service.
For Versions less than VS2022 17.2.0 using Debug\Attach in VS you must add port :4024 to the end of the Url.

--(Just to highlight) --Remote debugging: When you scale your app to PremiumV2, you will no longer be able to use remote debugging for your apps. If you scale your App Service plan to a lower tier, you will be able to use remote debug again. See this doc: https://azure.github.io/AppService/2020/03/23/PremiumV2-support-for-older-deployments.html

@Lan Huang-MSFT , feel free to add additional insights.
Sign in to comment
ajkuma 22,401 Reputation points Microsoft Employee

2022-09-30T12:51:36.85+00:00
@Carolyn Schroeder ,

When you say, “but the publish page says that the publish failed“, What is the exact error message you receive?
Does this issue occur only when deploying to Azure App Service WebApp or happens for local deployments?

You may directly login to your Azure subscription via Azure Portal, and find (status) the deployment/resources. https://portal.azure.com/

-You may try these, if you have done it already, you may try these:
• It is recommended that you have the latest version running.
• Install the latest updates in Visual Studio by selecting Help > Check for Updates.
• Add the workload by selecting Tools > Get Tools and Features.

Note:

The dotnet msbuild command is a cross-platform command and can compile ASP.NET Core apps on macOS and Linux. However, MSBuild on macOS and Linux isn't capable of deploying an app to Azure or other MSDeploy endpoints.

Remote debugging does not work in Express editions of Visual Studio.

Publish profiles : When publishing to an Azure target, the .pubxml file contains your Azure subscription identifier. With that target type, adding this file to source control is discouraged.
Please sign in to rate this answer.
ajkuma 22,401 Reputation points Microsoft Employee

2022-09-30T12:54:51.187+00:00

Additional info: If you haven't checked this already:

Checkout the step-step instructions outlined in this doc for deploying Azure WebApp.

Quickstart: Deploy an ASP.NET web app
Publish an ASP.NET Core app to Azure with Visual Studio

View files/deployment on Azure:

To view the files in an Azure App Service web app deployment, use the Kudu service. Append the scm token to the web app name.

http://yoursite.azurewebsites.net/ ( your WebApp)
http://your.scm.azurewebsites.net/ (Kudu site)

Kindly let us know how it goes, I'll follow-up with you shortly.
Sign in to comment
Lan Huang-MSFT 25,556 Reputation points Microsoft Vendor

2022-10-03T06:18:13.94+00:00
Hi @Carolyn Schroeder ,
There are many reasons for this problem, you can try the following methods one by one:

Try open visual studio as admin.

In your solution directory, delete the .vs folder.If your project directory contains a pubxml file, please delete it.After that, restart Visual Studio.

Removed yellow marked files from Visual Studio project solution

Best regards,
Lan Huang
Please sign in to rate this answer.
Carolyn Schroeder 186 Reputation points

2022-10-09T14:51:55.887+00:00

I couldn't make this work. I deleted the pubxml files but could not get logged in through the Publish dialog in Visual Studio (2022) and could not see my resources on Azure.

ajkuma 22,401 Reputation points Microsoft Employee

2022-10-10T20:15:19.657+00:00

CarolynSchroeder-2130, I'll follow-up with you further offline on this for a much deeper investigation.

While I connect, I completely understand you had tried multiple things to fix this, for a one last time, to isolate, please try to publish a new dummy/test project, exactly as mentioned in this Azure document: Deploy an ASP.NET web app via VS method.

Open Visual Studio and then select Create a new project.

In Create a new project, find, and select ASP.NET Core Web App, then select Next.

In Configure your new project, name the application "TestFirstAzureWebApp", and then select Next.

And, then publish to Azure App Service and Enable "Remote Debugging" on the Azure Portal. (screenshot below)

--Test to see if the publish and the remote debugging works fine as expected Or test the same on a different computer running VS 2022.

Carolyn Schroeder 186 Reputation points

2022-10-13T15:35:27.487+00:00

I have done remote debugging as you outline here. I also allow that if I use the publish settings file downloaded from Azure, I do not get the Publish failed message in Visual Studio 2022. My objection is that if I use the publish settings file for a publish profile, I cannot get remote debugging as outlined here: https://stackoverflow.com/questions/69549657/visual-studio-2022-debug-on-remote-azure-server I am not happy that Microsoft has removed functionality from what it seems to make available in the Publish dialog in Visual Studio 2022. I guess I will just have to live with your work arounds.

ajkuma 22,401 Reputation points Microsoft Employee

2022-10-14T19:53:41.943+00:00

Apologies for any frustrating experience with this. I'll relay this feedback internally to our product team.
As soon as I have more updates, I'll share it with you. Thanks for your patience!

Carolyn Schroeder 186 Reputation points

2022-10-15T17:59:34.747+00:00

Thank you.
Sign in to comment
Sjors Miltenburg 6 Reputation points

2022-11-08T11:06:23.33+00:00
I had the same problem.
What helped was

deleting my local publish profile (publish - more actions - delete)

adding it again with the profile.publishssettings file I downloaded from azure
Please sign in to rate this answer.

0 comments No comments
Sign in to comment