Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Cannot Create Azure Cloud Service

    Scheduled Pinned Locked Moved Support
    azureerror
    3 Posts 1 Posters 8 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      I am getting a strange error when trying to create an Azure Cloud Service. I configured the extension with my subscription id, set the path to the Windows Azure 2.0 SDK bin folder, and gave the name of the management certificate. I installed the certificate in the local computer certificate store as well. However, when the task executes I get the following:

      Error creating Hosted Service named billblast-qa-1.0. Error code is: , error description:

      Nothing useful at all. At first I thought it had to do with the certificate name so I played around with that and got an error that it couldn't find the certificate. So I assume with the current configuration it's finding the certificate. I also confirmed that the management certificate has been uploaded to Windows Azure.

      Anyone have an idea?

      Thanks,
      Jason

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        It doesn't look like Azure is returning any useful error messages for this...

        Here's the source code that's throwing the action:
        https://github.com/Inedo/bmx-azure/blob/753632a3b96214ce6df5ac279cca96562665d05f/Compute/CreateHostedServiceAction.cs#L67

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          I figured out the problem was with the cloud service name. I was including the build number in the name and it just so happens that build number includes the {Major}.{Minor} numbers. The period was ultimately throwing it off. If you want to include the build number, then you have to use a url friendly number.

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation