Arc Agent installed and connected but failed to initialize
Arc Agent installs and shows connected but fails to initialize and has update status of 'No Update Data'.
Uninstall, delete from AUM, restart, reinstall - process succeeded, but Software Assurance attestation failed and did not fix the 'No updates data' issue.
Error: Assessment failed due to this reason: Extension failed to install. Install of extension failed with error: CreateProcess failed: unknown error
Azure Update Manager
-
Jose Benjamin Solis Nolasco • 3,511 Reputation points
2025-03-18T14:04:41.2633333+00:00 Marina, it sounds like your Azure Arc Agent is connecting but is failing to initialize its update extension—resulting in the “No Update Data” status and the Software Assurance attestation failure errors (specifically, “Extension failed to install. Install of extension failed with error: CreateProcess failed: unknown error”).
Check the Agent Logs
- Log Location: For Windows, check the Arc Agent logs at:
For Linux, logs are typically under%ProgramData%\AzureConnectedMachineAgent\Logs
/var/opt/azcmagent/logs
. - What to Look For: Look for any additional error details around the time the extension fails to install. These logs may provide clues (for example, permission errors or blocked process creation).
Ensure that the account under which the Arc Agent is running (or its service account) has sufficient privileges. A lack of administrative rights can lead to “CreateProcess failed” errors.
- Log Location: For Windows, check the Arc Agent logs at:
-
Naveena Patlolla • 3,775 Reputation points • Microsoft External Staff • Moderator
2025-03-18T15:09:40.4933333+00:00 Hi Marina I
Adding to the Jose Benjamin Solis Nolasco Examine the Azure Arc Agent Logs:
Location: The logs for the Azure Arc agent are typically located in C:\ProgramData\AzureConnectedMachineAgent\Log
Verify Software Assurance Eligibility
Azure Arc-enabled servers require Software Assurance (SA) or Azure Hybrid Benefit to be eligible for certain features and benefits. To check eligibility: Ensure the server is covered under an active Software Assurance agreement with Microsoft.
Verify that the server is licensed under a qualifying Windows Server license with SA
- Temporarily disable antivirus/endpoint protection. Reinstall and check
2.Use curl or Test-NetConnection to verify that your machine can communicate with Azure services:
https://learn.microsoft.com/en-us/azure/azure-arc/servers/network-requirements?tabs=azure-cloud
Windows Run the below commands in PowerShell
Test-NetConnection [login.microsoftonline.com] -Port 443
Test-NetConnection [management.azure.com] -Port 443
Linux Run the below commands in Shell
curl -v https://login.microsoftonline.com
curl -v https://management.azure.com
3.Restart Azure Arc Agent
Windows Run the below commands in PowerShell
Restart-Service AzureConnectedMachineAgent
Linux Run the the Below commands in Shell
sudo systemctl restart azcmagent
- Verify Software Assurance:
The error message mentions "Software Assurance attestation failed." While this might be a separate issue, it could be related to the underlying problems preventing extension installation.
Action: Ensure the server is eligible for Software Assurance benefits as required for Azure Arc. Check your licensing and Azure subscription.
let us know if you have any further queries. I’m happy to assist you further.
Please "Upvote" if comment is helpful
-
Naveena Patlolla • 3,775 Reputation points • Microsoft External Staff • Moderator
2025-03-19T15:28:40+00:00 Hi Marina I,
Did you get a chance to check the above solutions. Please let us know if you have further queries.
-
Marina I • 1 Reputation point
2025-03-20T11:26:28.6533333+00:00 Hi,
Logs - There are no error msgs in the azure agent log.
Warning in himds.log: time="2025-03-20T13:06:55+02:00" level=warning msg="Invalid basic authentication header" session=b41e6335-a3b9-4af1-8e85-f0e162c032a1
time="2025-03-20T13:06:55+02:00" level=info msg="Missing Basic Authorization header" reason=unauthorized_client sessionId=b41e6335-a3b9-4af1-8e85-f0e162c032a1
Verify Software Assurance - verified. And I should add that it works on most of my other machines. I have almost 300 machines and only 7 has this problem.
Temporarily disable antivirus/endpoint protection, reinstall and check - did this twice, didn't help.
Use curl or Test-NetConnection to verify that your machine can communicate with Azure services - Test-NetConnection fails, but it does on machines that do not have a problem too. Opening the URLs in a browser works fine and I can authenticate. I had to authenticate to configure the Arc Agent.
Restart Azure Arc Agent - There is no AzureConnectedMachineAgent service to restart. I checked a couple of working machines and they do not have such a service either. There are only these:
Unless I am missing something....
-
Ashok Gandhi Kotnana • 10,350 Reputation points • Microsoft External Staff • Moderator
2025-03-20T14:02:22.2066667+00:00 Hi Marina I,
Thanks for the response back.
The warning messages in your
himds.log
indicate that there might be an issue with the authentication headers being sent to Azure services. Here are some steps you can take to troubleshoot this issue further:Can you please check
azcmagent show
when you hit above command you need to get the below service running
Agent Service (himds): running
- Wait for 10-15 minutes as extension maybe in transitioning status. If it still doesn't show up, uninstall and install the extension again and repeat the verification to see the extension show up.
- If not, check if you see any errors in extension logs located at
C:\ProgramData\GuestConfig\extension_logs\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent
on your machine - Check for Missing Authorization: The log messages suggest that the Basic Authorization header is missing. Ensure that the machine is correctly configured to authenticate against Azure services. You may need to review the authentication settings and ensure that the service principal or managed identity is correctly set up.
Please refer to the below links that will help you to resolve your issue it has detailed troubleshooting steps: -
https://learn.microsoft.com/en-us/azure/azure-arc/servers/managed-identity-authentication
Hope this helps!
Please let us know how it goes, so that we can work on an alternate solution on this request.
-
Naveena Patlolla • 3,775 Reputation points • Microsoft External Staff • Moderator
2025-03-21T18:00:24.7166667+00:00 Hi Marina I,
Hope the above troubleshooting steps were helpful. Let us know if you have any further queries. I’m happy to assist you further -
Vinod Pittala • 4,175 Reputation points • Microsoft External Staff • Moderator
2025-03-24T05:09:26.82+00:00 Hello Marina I,
We have not received any response from you. It would be great if you could review the above recommendations from Ashok Gandhi Kotnana.
Please let us know if you have any concerns or issues regarding the current matter, as we are here to help you.
Thank you.
-
Marina I • 1 Reputation point
2025-04-02T09:22:10.34+00:00 Appologies for the delay in anwering. I have been on Disaster Recovery Exercises.
Result for azcmagent show:
There does not seem to be any errors for the agent.
-
Madugula Jahnavi • 495 Reputation points • Microsoft External Staff • Moderator
2025-04-03T10:10:50.7033333+00:00 Hi Marina I, I understand that you are still facing the issue. I initiated a private chat asking few details to connect with you for further investigation on the issue. Please respond there.
-
Madugula Jahnavi • 495 Reputation points • Microsoft External Staff • Moderator
2025-04-04T15:33:30.89+00:00 Marina I, We haven't heard any response from you. Can you please provide the required details to connect for further investigation.
-
Marina I • 1 Reputation point
2025-04-08T06:04:24.5333333+00:00 Hi @Madugula Jahnavi . Sorry, but I dont know where the private chat is. Where do I find it? This is my first time on these forums.
-
SadiqhAhmed-MSFT • 49,331 Reputation points • Microsoft Employee • Moderator
2025-04-25T07:09:30.86+00:00 @Marina I You will see private message option on top of thread title. See the snippet below:
You will also be able to see the private message option below your original post.
Hoping to hear back from you on the status of the issue. If this is still an issue, please share the details asked in the private message.
Sign in to comment