question

EricDavis-0062 avatar image
1 Vote"
EricDavis-0062 asked ·

Why is application deployment failing on waws-prod-blu-167.publish.azurewebsites.windows.net?

Trying to publish a .NET Core 3.1 app via VS 2019 to Azure using the Publish wizard. Publish process kicks off and runs for a while, but eventually fails with the following error:

 C:\Program Files\dotnet\sdk\3.1.200\Sdks\http://Microsoft.NET.Sdk.Publish\targets\PublishTargets\http://Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): Error : Web deployment task failed. (Could not complete the request to remote agent URL 'https://waws-prod-blu-167.publish.azurewebsites.windows.net/msdeploy.axd?site=QAZAuthMvcOidcClient-AS01'.)
    
 Could not complete the request to remote agent URL 'https://waws-prod-blu-167.publish.azurewebsites.windows.net/msdeploy.axd?site=QAZAuthMvcOidcClient-AS01'. The operation has timed out Publish failed to deploy.

I can successfully publish the same application to a different app service instance that is hosted on a different app service plan. That service plan appears to be associated with waws-prod-blu-137.publish.azurewebsites.windows.net, so I assume there is currently some issue with waws-prod-blu-167.publish.azurewebsites.windows.net.

Can someone please take a look???






azure-webapps
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for reaching here! Just to confirm how big is your deployment? As if you have a very large deployment and are getting some issues, consider increasing the http.postBuffer to a larger size, greater than the default size of 1MB. Secondly how are you Deploying if using the shared Publisher Role? If WEBSITE_WEBDEPLOY_USE_SCM app setting is set to False, the shared Web App Publisher Role performs. And it is recommended to use the dedicated process versus the shared one.

You may refer to below article for reference: Troubleshooting Web App deployment issues


0 Votes 0 ·

1 Answer

EricDavis-0062 avatar image
0 Votes"
EricDavis-0062 answered ·

The deployment is really small; < 10MB. WEBSITE_WEBDEPLOY_USE_SCM was set to false. I didn't do this myself. Was set that way be default by the tooling when I stood up the App Service. I changed it to true. I then deleted and recreated the publishing profile and tried again. Now the operation completes successfully.

The weird thing is that I also deployed this exact same application code to a different App Service / App Service Plan that had the WEBSITE_WEBDEPLOY_USE_SCM value set to false and it works just fine. The only difference appears to be the publishing service associated to the target applications; the one that wouldn't work is associated with waws-prod-blu-167.publish.azurewebsites.windows.net and the one that worked without issue is associated with waws-prod-blu-137.publish.azurewebsites.windows.net.

Really strange and a huge pain to troubleshoot. Doesn't make any sense.







· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @EricDavis-0062, can you provide us your app name? Assuming of course you didn't delete the original site that was being deployed to 167. If you don't wish to share publicly, you can email us at AzCommunity[at]microsoft[dot]com ATTN Ryan including your subscription id, the app name, and timestamp in UTC that was failing deployment so we can take a closer look.


0 Votes 0 ·