New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy to Azure "Failed Deployment" #244

Closed
DevlinSchoonraad opened this Issue Sep 11, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@DevlinSchoonraad

DevlinSchoonraad commented Sep 11, 2017

When using the Deploy to Azure button from GitHub the process runs to the step "Updating Website Config" before it errors out.

The error message is simply: "Failed Deployment"...

image

I am unable to get past this on the one subscription, but all works fine on my MSDN sub.

@patrickebates

This comment has been minimized.

Show comment
Hide comment
@patrickebates

patrickebates Sep 11, 2017

Member

Is there anything unique about the one subscription? Also, is the MSDN sub the default sub for your account? I seem to recall a known issue with the Azure Deploy system with subscriptions other than the default.

Member

patrickebates commented Sep 11, 2017

Is there anything unique about the one subscription? Also, is the MSDN sub the default sub for your account? I seem to recall a known issue with the Azure Deploy system with subscriptions other than the default.

@DevlinSchoonraad

This comment has been minimized.

Show comment
Hide comment
@DevlinSchoonraad

DevlinSchoonraad Sep 11, 2017

Thanks for the pointer @patrickebates.

The subscription that it's failing on is on the company EA and as mentioned was not the default subscription. I used Azure Powershell to set it as the rm context, but still bet the same failure. Is there another means of setting a subscription to be the default?

DevlinSchoonraad commented Sep 11, 2017

Thanks for the pointer @patrickebates.

The subscription that it's failing on is on the company EA and as mentioned was not the default subscription. I used Azure Powershell to set it as the rm context, but still bet the same failure. Is there another means of setting a subscription to be the default?

@patrickebates

This comment has been minimized.

Show comment
Hide comment
@patrickebates

patrickebates Sep 11, 2017

Member

You'll probably need to do a "manual" deployment. You will need to create the SQL Database and Web App in the Azure portal. But you can link the Web App to this repository by using the notes below the video on this page....
http://projectnami.org/video-updating-project-nami/

Member

patrickebates commented Sep 11, 2017

You'll probably need to do a "manual" deployment. You will need to create the SQL Database and Web App in the Azure portal. But you can link the Web App to this repository by using the notes below the video on this page....
http://projectnami.org/video-updating-project-nami/

@jordanmills

This comment has been minimized.

Show comment
Hide comment
@jordanmills

jordanmills Mar 13, 2018

I'm getting the same issue. Using a non-default sub that is MSDN. Let me know if another data point will help.

jordanmills commented Mar 13, 2018

I'm getting the same issue. Using a non-default sub that is MSDN. Let me know if another data point will help.

@patrickebates

This comment has been minimized.

Show comment
Hide comment
@patrickebates

patrickebates Mar 13, 2018

Member

The issue of the non-default sub is with the underlying Slingshot website by Microsoft which processes the request. Unfortunately, you'll need to use the manual deployment method.

Member

patrickebates commented Mar 13, 2018

The issue of the non-default sub is with the underlying Slingshot website by Microsoft which processes the request. Unfortunately, you'll need to use the manual deployment method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment