locked
Internal Server Error while provisioning VM in portal RRS feed

  • Question

  • I have created a very simple network with 2 subnets.

    <NetworkConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/ServiceHosting/2011/07/NetworkConfiguration">
      <VirtualNetworkConfiguration>
        <Dns />
        <VirtualNetworkSites>
          <VirtualNetworkSite name="brennetwork" AffinityGroup="brensaffinity">
            <AddressSpace>
              <AddressPrefix>10.4.0.0/16</AddressPrefix>
            </AddressSpace>
            <Subnets>
              <Subnet name="FrontEndSubnet">
                <AddressPrefix>10.4.2.0/24</AddressPrefix>
              </Subnet>
              <Subnet name="BackEndSubnet">
                <AddressPrefix>10.4.3.0/24</AddressPrefix>
              </Subnet>
            </Subnets>
          </VirtualNetworkSite>
        </VirtualNetworkSites>
      </VirtualNetworkConfiguration>
    </NetworkConfiguration>

    I have successfully deployed a hosted service with 2 roles to one of the subnets using the cscfg file to specify the details. I can see the service and role instances in the virtual network and all looks good.

    
    I try to add a new vm through the portal and specify the same network and pick the subnet from the drop down list.

    Failed to create virtual machine anothertest.

    I always get the following error "The server encountered an internal error. Please retry the request. The long running operation tracking ID was: cbf4ebdb537148c8a68b471ee64d5364."

    Anyone seen this before ? I can spin up vms fine if i dont pick the vnet and leave them standalone.

    Thanks

    Thursday, November 22, 2012 8:07 PM

Answers

  • Tried this again the very next day and it worked first time. Is there a period of time needed for the VNet to bed in ?
    • Marked as answer by Bren Kehoe Tuesday, November 27, 2012 10:32 PM
    Friday, November 23, 2012 8:30 PM

All replies

  • Tried this again the very next day and it worked first time. Is there a period of time needed for the VNet to bed in ?
    • Marked as answer by Bren Kehoe Tuesday, November 27, 2012 10:32 PM
    Friday, November 23, 2012 8:30 PM
  • Bren,

    Thanks for sharing your experience here. As soon as the portal reports that the VNet is ready, then it can begin receiving VMs. If there is any delay at all, it is at most on the order of minutes, not hours, and certainly not a whole day. Your experience is not typical. Sorry about that.

    Best regards,

    -Steve

    Tuesday, December 4, 2012 9:22 PM