This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 95%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E1%3C/text%3E%3C/svg%3E)
PS: VM已加入DCR,并开启System-assigned
[ValidateDataStorePersistence] ErrorCode:0 ERROR: The registry value exists but the key file does not. Cannot launch AMA.[2024-10-25 03:03:39.000] [StartAzureMA] ErrorCode:1120 ERROR: Failed to validate data store persistence C:\WindowsAzure\Resources\AMADataStore.g5pls-au-sRE0
[2024-10-25 03:03:39.000] [AggregateHeartbeat] ErrorCode:1120 WARN: Unable to start or detect MA service running. Will try again in 5 min.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 12%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3E3%3C/text%3E%3C/svg%3E)
If you have still the issue I solved it. by doing the following
What I did was removing the registry key and reboot the machine.
SOFTWARE\Microsoft\AzureMonitorAgent\secret and remove the key "persistenceKeyCreated"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 60%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Thanks for this. I'm not sure what the key does exactly but I guess there's a key that somehow got out of sync. Removing the reg key forces it to generate a new one? At any rate, I was able to fix 2 machines that had this issue for the past couple days out of the blue. Removing and reinstalling the extension did nothing, and the servers still showed that extension as "transitioning" with that same error message "Failed to validate data store persistence".
Once I removed the reg key, on one server I rebooted, but on the other I noticed that shortly after I removed the key, the extension went into "Provisioning succeeded" status without a reboot, so you might check that before restarting.
This was also affecting the MicrosoftDnsAgent we had on the same machines, but once the AMA extension was fixed, the DNS extension could be reinstalled (I'd previously removed it) and it also worked right away. Thanks for posting this fix!