1. Key Generation Failed No Agent Running 2017
  2. Key Generation Failed No Agent Running Game
Generation

I am unable to generate a gpg key through the keyring program. Ask Question. Work to give the OS a chance to collect more entropy! (Need 300 more bytes) gpg: no writable public keyring found: eof Key generation failed: eof gpg: note: randomseed file not updated. Is the key acquired from running gpg -export-secret-key encrypted. Thus, they must be managed somewhat analogously to user names and passwords. They should have a proper termination process so that keys are removed when no longer needed. Creating an SSH Key Pair for User Authentication. The simplest way to generate a key pair is to run ssh-keygen without arguments. In this case, it will prompt for the file in.

-->

This article describes some of the most common error codes and messages you may encounter when you create or manage virtual machines (VMs) in Azure.

Note

You can leave comments on this page for feedback or through Azure feedback with #azerrormessage tag.

Error Response Format

Azure VMs use the following JSON format for error response:

Agent

An error response always includes a status code and an error object. Each error object always contains an error code and a message. If the VM is created with a template, the error object also contains a details section that contains an inner level of error codes and message. Normally, the most inner level of error message is the root failure.

Common virtual machine management errors

This section lists the common error messages you may encounter when managing VMs:

Key Generation Failed No Agent Running 2017

Error CodeError Message
AcquireDiskLeaseFailedFailed to acquire lease while creating disk '{0}' using blob with URI {1}. Blob is already in use.
AllocationFailedAllocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.
AllocationFailedThe VM allocation failed due to an internal error. Please retry later or try deploying to a different location.
ArtifactNotFoundThe VM extension with publisher '{0}' and type '{1}' could not be found in location '{2}'.
ArtifactNotFoundExtension with publisher '{0}', type '{1}', and type handler version '{2}' could not be found in the extension repository.
ArtifactVersionNotFoundNo version found in the artifact repository that satisfies the requested version '{0}'.
ArtifactVersionNotFoundNo version found in the artifact repository that satisfies the requested version '{0}' for VM extension with publisher '{1}' and type '{2}'.
AttachDiskWhileBeingDetachedCannot attach data disk '{0}' to VM '{1}' because the disk is currently being detached. Please wait until the disk is completely detached and then try again.
BadRequestAligned' Availability Sets are not yet supported in this region.
BadRequestAddition of a VM with managed disks to non-managed Availability Set or addition of a VM with blob based disks to managed Availability Set is not supported. Please create an Availability Set with 'managed' property set in order to add a VM with managed disks to it.
BadRequestManaged Disks are not supported in this region.
BadRequestMultiple VMExtensions per handler not supported for OS type '{0}'. VMExtension '{1}' with handler '{2}' already added or specified in input.
BadRequestOperation '{0}' is not supported on Resource '{1}' with managed disks.
CertificateImproperlyFormattedThe secret's JSON representation retrieved from {0} has a data field which is not a properly formatted PFX file, or the password provided does not decode the PFX file correctly.
CertificateImproperlyFormattedThe data retrieved from {0} is not deserializable into JSON.
ConflictDisk resizing is allowed only when creating a VM or when the VM is deallocated.
ConflictingUserInputDisk '{0}' cannot be attached as the disk is already owned by VM '{1}'.
ConflictingUserInputSource and destination resource groups are the same.
ConflictingUserInputSource and destination storage accounts for disk {0} are different.
ContainerAlreadyOnLeaseThere is already a lease on the storage container holding the blob with URI {0}.
CrossSubscriptionMoveWithKeyVaultResourcesThe Move resources request contains KeyVault resources which are referenced by one or more {0}s in the request. This is not supported currently in Cross subscription Move. Please check the error details for the KeyVault resource Ids.
DiagnosticsOperationInternalErrorAn internal error occurred while processing diagnostics profile of VM {0}.
DiskBlobAlreadyInUseByAnotherDiskBlob {0} is already in use by another disk belonging to VM '{1}'. You can examine the blob metadata for the disk reference information.
DiskBlobNotFoundUnable to find VHD blob with URI {0} for disk '{1}'.
DiskBlobNotFoundUnable to find VHD blob with URI {0}.
DiskEncryptionKeySecretMissingTags{0} secret doesn't have the {1} tags. Please update the secret version, add the required tags and retry.
DiskEncryptionKeySecretUnwrapFailedUnwrap of secret {0} value using key {1} failed.
DiskImageNotReadyDisk image {0} is in {1} state. Please retry when image is ready.
DiskPreparationErrorOne or more errors occurred while preparing VM disks. See disk instance view for details.
DiskProcessingErrorDisk processing halted as the VM has other disks in failed disks.
ImageBlobNotFoundUnable to find VHD blob with URI {0} for disk '{1}'.
ImageBlobNotFoundUnable to find VHD blob with URI {0}.
IncorrectDiskBlobTypeDisk blobs can only be of type page blob. Blob {0} for disk '{1}' is of type block blob.
IncorrectDiskBlobTypeDisk blobs can only be of type page blob. Blob {0} is of type '{1}'.
IncorrectImageBlobTypeDisk blobs can only be of type page blob. Blob {0} for disk '{1}' is of type block blob.
IncorrectImageBlobTypeDisk blobs can only be of type page blob. Blob {0} is of type '{1}'.
InternalOperationErrorCould not resolve storage account {0}. Please ensure it was created through the Storage Resource Provider in the same location as the compute resource.
InternalOperationError{0} goal seeking tasks failed.
InternalOperationErrorError occurred in validating the network profile of VM '{0}'.
InvalidAccountTypeThe AccountType {0} is invalid.
InvalidParameterThe value of parameter {0} is invalid.
InvalidParameterThe Admin password specified is not allowed.
InvalidParameter'The supplied password must be between {0}-{1} characters long and must satisfy at least {2} of password complexity requirements from the following:
  1. Contains an uppercase character
  2. Contains a lowercase character
  3. Contains a numeric digit
  4. Contains a special character.
InvalidParameterThe Admin Username specified is not allowed.
InvalidParameterCannot attach an existing OS disk if the VM is created from a platform or user image.
InvalidParameterContainer name {0} is invalid. Container names must be 3-63 characters in length and may contain only lower-case alphanumeric characters and hyphen. Hyphen must be preceded and followed by an alphanumeric character.
InvalidParameterContainer name {0} in URL {1} is invalid. Container names must be 3-63 characters in length and may contain only lower-case alphanumeric characters and hyphen. Hyphen must be preceded and followed by an alphanumeric character.
InvalidParameterThe blob name in URL {0} contains a slash. This is presently not supported for disks.
InvalidParameterThe URI {0} does not look to be correct blob URI.
InvalidParameterA disk named '{0}' already uses the same LUN: {1}.
InvalidParameterA disk named '{0}' already exists.
InvalidParameterCannot specify user image overrides for a disk already defined in the specified image reference.
InvalidParameterA disk named '{0}' already uses the same VHD URL {1}.
InvalidParameterThe specified fault domain count {0} must fall in the range {1} to {2}.
InvalidParameterThe license type {0} is invalid. Valid license types are: Windows_Client or Windows_Server, case sensitive.
InvalidParameterLinux host name cannot exceed {0} characters in length or contain the following characters: {1}.
InvalidParameterDestination path for Ssh public keys is currently limited to its default value {0} due to a known issue in Linux provisioning agent.
InvalidParameterA disk at LUN {0} already exists.
InvalidParameterSubscription {0} of the request must match the subscription {1} contained in the managed disk id.
InvalidParameterCustom data in OSProfile must be in Base64 encoding and with a maximum length of {0} characters.
InvalidParameterBlob name in URL {0} must end with '{1}' extension.
InvalidParameter{0}' is not a valid captured VHD blob name prefix. A valid prefix matches regex '{1}'.
InvalidParameterCertificates cannot be added to your VM if the VM agent is not provisioned.
InvalidParameterA disk at LUN {0} already exists.
InvalidParameterUnable to create the VM because the requested size {0} is not available in the cluster where the availability set is currently allocated. The available sizes are: {1}. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
InvalidParameterThe requested VM size {0} is not available in the current region. The sizes available in the current region are: {1}. Find out more on the available VM sizes in each region at https://aka.ms/azure-regions.
InvalidParameterThe requested VM size {0} is not available in the current region. Find out more on the available VM sizes in each region at https://aka.ms/azure-regions.
InvalidParameterWindows admin user name cannot be more than {0} characters long, end with a period(.), or contain the following characters: {1}.
InvalidParameterWindows computer name cannot be more than {0} characters long, be entirely numeric, or contain the following characters: {1}.
MissingMoveDependentResourcesThe move resources request does not contain all the dependent resources. Please check error details for missing resource ids.
MoveResourcesHaveInvalidStateThe Move Resources request contains VMs which are associated with invalid storage accounts. Please check details for these resource ids and referenced storage account names.
MoveResourcesHavePendingOperationsThe move resources request contains resources for which an operation is pending. Please check details for these resource ids. Retry your operation once the pending operations complete.
MoveResourcesNotFoundThe move resources request contains resources that cannot be found. Please check details for these resource ids.
NetworkingInternalOperationErrorUnknown network allocation error.
NetworkingInternalOperationErrorUnknown network allocation error
NetworkingInternalOperationErrorAn internal error occurred in processing network profile of the VM.
NotFoundThe Availability Set {0} cannot be found.
NotFoundSource Virtual Machine '{0}' specified in the request does not exist in this Azure location.
NotFoundTenant with id {0} not found.
NotFoundThe Image {0} cannot be found.
NotSupportedThe license type is {0}, but the image blob {1} is not from on-premises.
OperationNotAllowedAvailability Set {0} cannot be deleted. Before deleting an Availability Set please ensure that it does not contain any VM.
OperationNotAllowedChanging availability set SKU from 'Aligned' to 'Classic' is not allowed.
OperationNotAllowedCannot modify extensions in the VM when the VM is not running.
OperationNotAllowedThe Capture action is only supported on a Virtual Machine with blob based disks. Please use the 'Image' resource APIs to create an Image from a managed Virtual Machine.
OperationNotAllowedThe resource {0} cannot be created from Image {1} until Image has been successfully created.
OperationNotAllowedUpdates to encryptionSettings is not allowed when VM is allocated, Please retry after VM is deallocated
OperationNotAllowedAddition of a managed disk to a VM with blob based disks is not supported.
OperationNotAllowedThe maximum number of data disks allowed to be attached to a VM of this size is {0}.
OperationNotAllowedAddition of a blob based disk to VM with managed disks is not supported.
OperationNotAllowedOperation '{0}' is not allowed on Image '{1}' since the Image is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since the VM is generalized.
OperationNotAllowedOperation '{0}' is not allowed as Restore point collection '{1}' is marked for deletion.
OperationNotAllowedOperation '{0}' is not allowed on VM extension '{1}' since it is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowedOperation '{0}' is not allowed since the Virtual Machines '{1}' are being provisioned using the Image '{2}'.
OperationNotAllowedOperation '{0}' is not allowed since the Virtual Machine ScaleSet '{1}' is currently using the Image '{2}'.
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since the VM is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since the VM is either deallocated or marked to be deallocated.
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since the VM is running. Please power off explicitly in case you shut down the VM from inside the guest operating system.
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since the VM is not deallocated.
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since VM has extension '{2}' in failed state.
OperationNotAllowedOperation '{0}' is not allowed on VM '{1}' since another operation is in progress.
OperationNotAllowedThe operation '{0}' requires the Virtual Machine '{1}' to be Generalized.
OperationNotAllowedThe operation requires the VM to be running (or set to run).
OperationNotAllowedDisk with size {0}GB, which is smaller than the size {1}GB of corresponding disk in Image, is not allowed.
OperationNotAllowedVM Scale Set extensions of handler '{0}' can be added only at the time of VM Scale Set creation.
OperationNotAllowedVM Scale Set extensions of handler '{0}' can be deleted only at the time of VM Scale Set deletion.
OperationNotAllowedVM '{0}' is already using managed disks.
OperationNotAllowedVM '{0}' belongs to 'Classic' availability set '{1}'. Please update the availability set to use 'Aligned' SKU and then retry the Conversion.
OperationNotAllowedVM created from Image cannot have blob based disks. All disks have to be managed disks.
OperationNotAllowedCapture operation cannot be completed because the VM is not generalized.
OperationNotAllowedManagement operations on VM '{0}' are disallowed because VM disks are being converted to managed disks.
OperationNotAllowedAn ongoing operation is changing power state of Virtual Machine {0} to {1}. Please perform operation {2} after some time.
OperationNotAllowedUnable to add or update the VM. The requested VM size {0} may not be available in the existing allocation unit. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OperationNotAllowedUnable to resize the VM because the requested size {0} is not available in the cluster where the availability set is currently allocated. The available sizes are: {1}. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OperationNotAllowedUnable to resize the VM because the requested size {0} is not available in the cluster where the VM is currently allocated. To resize your VM to {1} please deallocate (this is Stop operation in the Azure portal) and try the resize operation again. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OSProvisioningClientErrorOS Provisioning failed for VM '{0}' because the guest OS is currently being provisioned.
OSProvisioningClientErrorOS provisioning for VM '{0}' failed. Error details: {1} Make sure the image has been properly prepared (generalized).
  • Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
OSProvisioningClientErrorSSH host key generation failed. Error details: {0}. To resolve this issue verify if Linux agent is set up properly.
  • You can check the instructions at : https://docs.microsoft.com/azure/virtual-machines/extensions/agent-linux/
OSProvisioningClientErrorUsername specified for the VM is invalid for this Linux distribution. Error details: {0}.
OSProvisioningInternalErrorOS Provisioning failed for VM '{0}' due to an internal error.
OSProvisioningTimedOutOS Provisioning for VM '{0}' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later.
OSProvisioningTimedOutOS Provisioning for VM '{0}' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).
  • Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
  • Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/
OSProvisioningTimedOutOS Provisioning for VM '{0}' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:
  • Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
  • Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/
OverConstrainedAllocationRequestThe required VM size is not currently available in the selected location.
ResourceUpdateBlockedOnPlatformUpdateResource cannot be updated at this time due to ongoing platform update. Please try again later.
StorageAccountLimitationStorage account '{0}' does not support page blobs which are required to create disks.
StorageAccountLimitationStorage account '{0}' has exceeded its allocated quota.
StorageAccountLocationMismatchCould not resolve storage account {0}. Please ensure it was created through the Storage Resource Provider in the same location as the compute resource.
StorageAccountNotFoundStorage account {0} not found. Ensure storage account is not deleted and belongs to the same Azure location as the VM.
StorageAccountNotRecognizedPlease use a storage account managed by Storage Resource Provider. Use of {0} is not supported.
StorageAccountOperationInternalErrorInternal error occurred while accessing storage account {0}.
StorageAccountSubscriptionMismatchStorage account {0} doesn't belong to subscription {1}.
StorageAccountTooBusyStorage account '{0}' is too busy currently. Consider using another account.
StorageAccountTypeNotSupportedDisk {0} uses {1} which is a Blob storage account. Please retry with General purpose storage account.
StorageAccountTypeNotSupportedStorage account {0} is of {1} type. Boot Diagnostics supports {2} storage account types.
  • This error occurs if you use the premium storage account for Boot diagnostics. For more information, see How to use boot diagnostics.
SubscriptionNotAuthorizedForImageThe subscription is not authorized.
TargetDiskBlobAlreadyExistsBlob {0} already exists. Please provide a different blob URI to create a new blank data disk '{1}'.
TargetDiskBlobAlreadyExistsCapture operation cannot continue because target image blob {0} already exists and the flag to overwrite VHD blobs is not set. Either delete the blob or set the flag to overwrite VHD blobs and retry.
TargetDiskBlobAlreadyExistsCapture operation cannot continue because target image blob {0} has an active lease on it.
TargetDiskBlobAlreadyExistsBlob {0} already exists. Please provide a different blob URI as target for disk '{1}'.
TooManyVMRedeploymentRequestsToo many redeployment requests have been received for VM '{0}' or the VMs in the same availabilityset with this VM. Please retry later.
VHDSizeInvalidThe specified disk size value of {0} for disk '{1}' with blob {2} is invalid. Disk size must be between {3} and {4}.
VMAgentStatusCommunicationErrorVM '{0}' has not reported status for VM agent or extensions. Please verify the VM has a running VM agent, and can establish outbound connections to Azure storage.
VMArtifactRepositoryInternalErrorAn error occurred while communicating with the artifact repository to retrieve VM artifact details.
VMArtifactRepositoryInternalErrorAn internal error occurred while retrieving the VM artifact data from the artifact repository.
VMExtensionHandlerNonTransientErrorHandler '{0}' has reported failure for VM Extension '{1}' with terminal error code '{2}' and error message: '{3}'
VMExtensionManagementInternalErrorInternal error occurred while processing VM extension '{0}'.
VMExtensionManagementInternalErrorMultiple errors occurred while preparing the VM extensions. See VM extension instance view for details.
VMExtensionProvisioningErrorVM has reported a failure when processing extension '{0}'. Error message: '{1}'.
VMExtensionProvisioningErrorMultiple VM extensions failed to be provisioned on the VM. Please see the VM extension instance view for details.
VMExtensionProvisioningTimeoutProvisioning of VM extension '{0}' has timed out. Extension installation may be taking too long, or extension status could not be obtained.
VMMarketplaceInvalidInputCreating a virtual machine from a non Marketplace image does not need Plan information, please remove the Plan information in the request. OS disk name is {0}.
VMMarketplaceInvalidInputThe purchase information does not match. Unable to deploy from the Marketplace image. OS disk name is {0}.
VMMarketplaceInvalidInputCreating a virtual machine from Marketplace image requires Plan information in the request. OS disk name is {0}.
VMNotFoundThe VM '{0}' cannot be found.
VMRedeploymentFailedVM '{0}' redeployment failed due to an internal error. Please retry later.
VMRedeploymentTimedOutRedeployment of VM '{0}' didn't finish in the allotted time. It might finish successfully in sometime. Else, you can retry the request.
VMStartTimedOutVM '{0}' did not start in the allotted time. The VM may still start successfully. Please check the power state later.

Key Generation Failed No Agent Running Game

Next steps

If you need more help, you can contact the Azure experts on the MSDN Azure and Stack Overflow forums. Alternatively, you can file an Azure support incident. Go to the Azure support site and select Get Support.

Coments are closed
Scroll to top