An Azure service that is used to provision Windows and Linux virtual machines.
Hey, i have the same issue with 4 servers, West Europe.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi, I have a bunch of Windows Server 2019 VMs and they were working fine just yesterday, but this morning none of them can be started. Provisioning state becomes "failed" and the error message is "No version found in the artifact repository that satisfies the requested version '' for VM extension with publisher 'Microsoft.WindowsAzure.GuestAgent' and type 'CRPProd'"
So I called a colleague who also has a bunch of similar Windows Server VMs in a different subscription (created independently, those are not copies of my VMs) and he has the same problem.
Looks like some kind of Azure outage, GuestAgent extension became inaccessible? On the other had, I'm worried about the fact that the requested version is shown as an empty string. If this is what my VM requests for some reason, no wonder it can't find it.
The region is Western Europe, in case it matters.
Tried googling the error message, nothing really useful.
I'll appreciate your help.
An Azure service that is used to provision Windows and Linux virtual machines.
Hey, i have the same issue with 4 servers, West Europe.
Same in North Europe! Disaster Recovery Microsoft by any chance?
Hello, I can't start my VMs in North Europe. I get this error message:
Additional error information is available for this virtual machine:
GENERAL
Provisioning state Provisioning failed.
No version found in the artifact repository that satisfies the requested version '' for VM extension with publisher 'Microsoft.WindowsAzure.GuestAgent' and type 'CRPProd'..
ArtifactVersionNotFound
Provisioning state error code ProvisioningState/failed/ArtifactVersionNotFound
Guest agent Unknown
DISKS
vm6staging-osdisk Provisioning succeeded.
Same issue in West Europe data center
Faced the same error. Morning I was using it fine. I stopped the server and restarted it, then came this error. I thought my server is crashed. Seems like we all have the same issue.