Resolved: Unable to Capture Image: "Endpoint Not found: There was no endpoint listening at..."


  • UPDATE: A fix has now been deployed for this issue.

    An issue has been identified that results in the inability to capture an image. We will update this post when the fix has been implemented.

    To workaround this issue, use the following steps to create an image from an existing VM:

    1. Generalize and shutdown the VM with Sysprep (Windows VMs) or the Windows Azure Linux Agent (Linux VMs).

    2. Under Disks on the VM's Dashboard, make note of the Disk name and VHD URL.

    3. Click Delete at the bottom to delete the VM. This does not delete the VHD.

    4. Go to Virtual Machines | Disks, and find the OS disk from Step 2 and select Delete Disk. This does not delete the VHD, only unregisters it as a disk.

    5. Go to Virtual Machines | Images, and select Create Image, and browse to the VHD from Step 2., select Windows or Linux for the OS, check image has been sysprepped and click the checkmark to create the image.

    6. When the operation completes, the new image will show up under Virtual Machines, Images, and under My Images when creating a VM from New | Virtual Machine | From Gallery | My Images.

    When attempting to capture an image in the Windows Azure management portal you may receive the following error message:
    Endpoint Not found: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

    Using the Save-AzureVMImage PowerShell cmdlet, you may receive error:
    PS C:\> save-azurevmimage -Name myvm -NewImageName myimage -NewImageLabel myimage -ServiceName mycloudservice
     save-azurevmimage : HTTP Status Code: NotFound - HTTP Error Message: does not exist.
     Operation ID: 5d2f45a33ca54ed39886f42b05f2b71c
     At line:1 char:1
     + save-azurevmimage -Name myvm -NewImageName myimage -NewImageLabel ...
         + CategoryInfo          : CloseError: (:) [Save-AzureVMImage], CommunicationException
         + FullyQualifiedErrorId :Microsoft.WindowsAzure.Management.ServiceManagement.IaaS.SaveAzureVMImageCommand

    Using the cross-platform Azure command-line tool you may receive error:
    C:\>azure vm capture myvm myimage --delete
     info:   Executing command vm capture
     verbose: Fetching VMs
     verbose: Capturing VM
     error:  The deployment name 'myvm' does not exist.
     error:  vm capture command failed

    Tuesday, July 3, 2012 8:47 PM


All replies