Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Publishing Azure Website fails

See original GitHub issue

When trying to deploy an Azure website, i am getting an exception that the site is already created and cannot be created again. This deploy process was working until October 23rd. Did anything change in the deploy script? I think it thinks the site doesn’t exist and tries to create it again.

2015-10-29T03:19:24.6803000Z Get-AzureWebSite -Name WaxonService -ErrorAction SilentlyContinue

2015-10-29T03:19:31.7421204Z New-AzureWebSite -Name WaxonService -Location South Central US

2015-10-29T03:19:34.9330598Z ##[error]Conflict: Website with given name WaxonService already exists.

2015-10-29T03:19:34.9350596Z Publish-AzureWebsiteProject -Name "WaxonService" -Package "C:\a\1\a\Waxon.Service.zip" 

2015-10-29T03:19:51.0621612Z Finishing task: AzureWebPowerShellDeployment

Issue Analytics

State:
Created 8 years ago
Comments:19 (7 by maintainers)

Top GitHub Comments

1reaction

RoopeshNaircommented, Apr 21, 2016

@kpgeek

Based on the update here https://connect.microsoft.com/VisualStudio/feedback/details/2559822/-error-requested-value-dynamic-was-not-found

Removing Azure Functions solves the problem

0reactions

leelepcommented, Mar 6, 2019

I experienced the same issue using the new DevOps web site, and it was due to being logged in to DevOps with the wrong account. The DevOps site doesn’t seem to recognize the difference between work and personal accounts of the same email address. The Get-AzureWebSites PowerShell command does distinguish between the two. If you have multiple accounts and experience the described issue then double check that you are signed in to DevOps with an account that has permissions for the Azure web site.