Common issues - uploaded VHDs RRS feed

  • General discussion

  • This posting contains a list of some of the common problems that have been seen in early usage of Windows Azure Virtual Machines. These topics can be used as a guide to resolve some of the most common problems that are likely to occur when first using Windows Azure Virtual Machines

    1.) CSUpload fails with "the subscription is not authorized for this feature"

    CSUpload may fail with an error that the subscription is not authorized for this feature even though the subscription is enabled for IaaS. To resolve this problem: Review which command is being used in CSUpload. The command Add-VMImage is meant to be used only for uploading images for the VM Role (stateless). For Azure Vitual Machines use the command "Add-PersistentVMImage".

    2.) Uploaded VHD image fails to provision with error: Provisioning Timeout

    The two most common cases for this are:

    1. The VHD was uploaded as a image, but was not sysprepped. To resolve this issue: Remove this VHD as an image and instead add it back as a Disk with an Operating System. You can then boot the disk, run "sysprep /generalize" and then capture the VHD as an image.
    2. The second case is if there is an unattend.xml file located on the uploaded VM in one of the directories listed in Implicit Answer File Search Oder in the following article: http://technet.microsoft.com/en-us/library/cc749415.asp. To resolve this issue you can remove the VHD as an image, add it back as a disk without an operating system, and then attach the disk to a running VM to remove the unattend.xml files. Once the files have been removed the VHD can be readded as an image and it should work correctly. This is due to the fact taht when an image is deployed the unattend.xml file must come from the ISO image that is attached to the Virtual Machine by Windows Azure as part of VM provisioning from an image.

    3.) Uploaded VHD image that had the Azure Integration Components installed fails to provision

    Do not install the Azure Integrations Components to VHD to be used for Azure Virtual Machines (persistent). However these integration components must be installed for VHDs uploaded for the VM Role (stateless)

    4.) CSUpload fails to find the management certificate on the client even though it is installed

    To use CSUpload.exe to upload a VHD to Windows Azure you must have the management certificate for the subscription installed on the machine where CSUpload will be ran. However there are situations where the certificate can be installed, but CSUpload may still return the error "Cannot access the certificate specified in the connection string." The solution in this case is typically to move the management certificate to the Personal - Certificates folder on the machine running CSUpload. If the certificate is installed to a different folder it will not be found by CSUpload.exe

    5). CSUpload fails with "The subscription ID was not found."

    The Upload a VHD page contains an incorrect URL for the service management endpoint (correction will be live shortly).

    This command:

    csupload Set-Connection "SubscriptionID=<Subscriptionid>;CertificateThumbprint=<Thumbprint>;ServiceManagementEndpoint=https://management-preview.core.windows-int.net"

    should instead be:

    csupload Set-Connection "SubscriptionID=<Subscriptionid>;CertificateThumbprint=<Thumbprint>;ServiceManagementEndpoint=https://management.core.windows.net"

    Messages posted to this forum are provided "AS IS" with no warranties

    Wednesday, June 6, 2012 9:00 AM