May 04 2024 11:09 AM - edited May 04 2024 11:22 AM
Hi everyone,
two different things in one bucket:
1. user reports indidate issues the Arc Deployment using the new wizard might fail
https://learn.microsoft.com/en-my/answers/questions/1660985/azure-arc-configuration-the-given-key-wa...
Error: The given key was not present in the dictonary
2. Download of Arc Connected Machine Agent fails
I have tried to reproduce this today but even failed before the reported step
Error: Could not download AzureConnectedMachineAgent.msi
Has the link or redirector been changed?
according to process monitor it is trying to reach an address that looks like an attestation address, but no public IP.
Feedback hub link and more logs
https://aka.ms/AAq9t0m
May 07 2024 10:21 AM
May 10 2024 04:58 PM - edited May 10 2024 06:01 PM
May 10 2024 04:58 PM - edited May 10 2024 06:01 PM
SolutionHi Karl,
to be clear, the 1st bug (“The given key was not present in the dictionary”) is known and will be fixed soon. As a workaround, for now you can install the agent using PowerShell.
the 2nd bug you're mentioning (“Could not download AzureConnectedMachineAgent.msi”) is not expected and worth checking out, if you're still experiencing this issue. Can you please try again, and if it still fails, tell me more about your environment? Any chance you're running this in a VM on Azure IaaS?
May 10 2024 06:51 PM - edited May 11 2024 01:44 AM
May 10 2024 06:51 PM - edited May 11 2024 01:44 AM
Thank you @Yash_Shekar @Artem Pronichkin, that's good to know. I will try again.
After I have posted I tried to repro already. Failed on Hyper-V Host, but worked in a Hyper-V VM.
Only difference apart that was the VM was WS 2022.
But as said will try again on each.
Appreciate your feedback and time looking into this!
May 11 2024 12:25 AM
May 13 2024 09:25 AM
Hi @Artem Pronichkin
unfortunately no change on the WS 2025 Hyper-V Host b26085
Arc is not / wasn't installed on this one.
Host
Windows Server VM is not affected. Wild, isn't it?
Only that I could think that virtual switches prevent something.
VM
May 10 2024 04:58 PM - edited May 10 2024 06:01 PM
May 10 2024 04:58 PM - edited May 10 2024 06:01 PM
SolutionHi Karl,
to be clear, the 1st bug (“The given key was not present in the dictionary”) is known and will be fixed soon. As a workaround, for now you can install the agent using PowerShell.
the 2nd bug you're mentioning (“Could not download AzureConnectedMachineAgent.msi”) is not expected and worth checking out, if you're still experiencing this issue. Can you please try again, and if it still fails, tell me more about your environment? Any chance you're running this in a VM on Azure IaaS?