Azure Arc connection Error: Invalid namespace

Johnny Nguyen 0

Hello All,

I have a vendor who is applying Windows Server 2012 1-Year ESU's to some devices that I have, however, my vendor uses Azure Arc for these ESU's.

The servers themselves are not on Azure. The vendor runs a powershell script to establish an Azure Arc connection, then they are able to apply the ESU.

There is on server in particular that is having trouble establishing this connection, and I'm not able to understand/identify what the issue is.

FYI, there is another server on the same network that connects without any issues. I have also tried running this script with the firewall unrestricted, no luck.

The output from running the script returns this invalid namespace error:

Screenshot (2)

I desperately need to get this connection established, otherwise the client will have a much harder time planning and budgeting for an upgrade. Any ideas are greatly appreciated.

Thank you,

AnuragSingh-MSFT 20,431 Reputation points

2024-03-13T11:19:31.3633333+00:00
Johnny Nguyen, Based on the error in the screenshot, it was line 21 of "AzureArc ACE.ps1" script where the error occurred. I would suggest reviewing line 21 of this script to understand more about the error.

You could also run the cmd below to check if the Azure Arc agent was successfully installed (launch a new instance of powershell/cmd before running the cmd below)

azcmagent show

If Azure Arc Agent was installed, it should give an output containing various properties. The important ones are highlighted below:

. . . Resource Namespace : Microsoft.HybridCompute . . Cloud : AzureCloud Agent Version : 1.36.02501.1366 Agent Logfile : C:\ProgramData\AzureConnectedMachineAgent\Log\himds.log Agent Status : Connected Agent Last Heartbeat : 2024-03-13T10:59:09Z Agent Error Code : Agent Error Details : Agent Error Timestamp : Using HTTPS Proxy : Proxy Bypass List : Cloud Provider : N/A Cloud Metadata Manufacturer : Microsoft Corporation Model : Virtual Machine MSSQL Server Detected : false Dependent Service Status GC Service (gcarcservice) : running Extension Service (extensionservice) : running Agent Service (himds) : running

In case, the cmd azcmagent show does not give any output or gives something as below, then the agent itself was not installed and there are chances that the failure happened when installing the agent.

azcmagent: The term 'azcmagent' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

If you get the error above (not recognized as a name of a cmdlet...), then I would suggest running the powershell script line by line. This would give you the exact location where the failure happens. You could also share the script being used here (after removing sensitive information like subscriptionId, correlationId, resource group, location etc.) to help us get an understanding of the cause.

Hope this helps. Please let me know if you have any questions.
Johnny Nguyen 0 Reputation points

2024-03-13T17:26:04.5166667+00:00

Hi AnuragSingh-MSFT,

Thank you so much for your help and information.

This is the script that I'm trying to run (thank you for the warning to remove sensitive information portions):

try {

$env:SUBSCRIPTION_ID =

$env**:RESOURCE_GROUP =**

$env**:TENANT_ID =**

$env**:LOCATION =**

$env**:AUTH_TYPE =**

$env**:CORRELATION_ID =**

$env**:CLOUD =**

[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor 3072;

# Download the installation package

Invoke-WebRequest -UseBasicParsing -Uri "https://aka.ms/azcmagent-windows" -TimeoutSec 30 -OutFile "$env:TEMP\install_windows_azcmagent.ps1";

# Install the hybrid agent

& "$env:TEMP\install_windows_azcmagent.ps1";

if ($LASTEXITCODE -ne 0) { exit 1; }

# Run connect command

& "$env:ProgramW6432\AzureConnectedMachineAgent\azcmagent.exe" connect --resource-group "$env:RESOURCE_GROUP" --tenant-id "$env:TENANT_ID" --location "$env:LOCATION" --subscription-id "$env:SUBSCRIPTION_ID" --cloud "$env:CLOUD" --correlation-id "$env:CORRELATION_ID";

}

catch {

$logBody = @{subscriptionId="$env:SUBSCRIPTION_ID";resourceGroup="$env:RESOURCE_GROUP";tenantId="$env:TENANT_ID";location="$env:LOCATION";correlationId="$env:CORRELATION_ID";authType="$env:AUTH_TYPE";operation="onboarding";messageType=$.FullyQualifiedErrorId;message="$";};

Invoke-WebRequest -UseBasicParsing -Uri "https://gbl.his.arc.azure.com/log" -Method "PUT" -Body ($logBody | ConvertTo-Json) | out-null;

Write-Host -ForegroundColor red $_.Exception;

}

So the issue seems to be an error with getting the Azure Connected Machine Agent to install.

AzureConnectMachineAgent.msi is downloaded in the #Download the installation package portion of the script.

It is then ran as part of the install_windows_azcmagent.ps1 script in the #Install the hybrid agent portion of the script. However, there is an fatal error that occurs here. So I tried manually locating the installer file and running it.

When I run the installer, it nearly completes the installation before abruptly "backing out" (installer progress bar retracts then closes-- no error message or notification).
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 answer

AnuragSingh-MSFT 20,431 Reputation points

2024-03-14T08:20:46.0133333+00:00
Johnny Nguyen, thank you for the detailed information and narrowing it down to the installation issue.

The script shared earlier, downloads the installation script - install_windows_azcmagent.ps1 which contains code for downloaded the AzureConnectedMachineAgent.msi and installing it.

If this file (install_windows_azcmagent.ps1) was already downloaded to $env:TEMP folder (you can run $env:TEMP in powershell to get the exact location), please run it from an elevated (admin) powershell using the cmd below:

& "$env:TEMP\install_windows_azcmagent.ps1";

Note the output in the PowerShell window.

Also, note that the detailed msi log files for the Arc agent installation are being generated in $env:Temp\installationlog.txt

In case the installation fails again, even after trying it from admin powershell window check, please check the following:

Application logs in the Eventviewer of the machine

$env:Temp\installationlog.txt file for details on error

Output in powershell window, if any

Please let me know if you have any questions.
Please sign in to rate this answer.
Johnny Nguyen 0 Reputation points

2024-03-15T19:19:34.7066667+00:00

Hi AnuragSingh-MSFT,

Thank you again for your help and suggestions.

My previous comment got deleted due to code of conduct violations, so I'm not exactly sure how to share the evidence I gathered, but to recap:

I ran & "$env:TEMP\install_windows_azcmagent.ps1"; in powershell as an admin and it failed again.

The application logs from the event viewer showed a failed installation and provided the error code: 1603. After looking into this code, I verified that the application was not already installed and that the SYSTEM account has Full Control permissions. The drive settings should be fine as well, but I will need to look further into it before confirming.

$env:Temp\installationlog.txt - I admittedly am not knowledgeable enough to say that I went through the complete log thoroughly. I did, however, notice the end of the log had the only relevant information that I could associate with the issue. I've attached that portion in a .txt file, but essentially it mentioned the error code 1603 as well. installationlogexcerpt.txt

The powershell output (mentions code 1603 again, also line 1;char 1)

AnuragSingh-MSFT 20,431 Reputation points

2024-03-19T07:27:22.08+00:00

Johnny Nguyen, thank you for the detailed response.

Error code 1603 indicates installation failure for MSI package. Thus, we have narrowed down the issue to actual arc agent msi installation.

Looking the output in PowerShell screenshot, the error happens in the following section:

After a bit of further investigation, this looks like an issue with misconfigured/corrupt WMI namespace on this particular server. You may perform some of the basic tests for WMI as mentioned in the following article - Basic WMI Testing

Since it is a critical component of the server, trying to rebuild/troubleshoot it with incorrect steps might land you in unsupported scenarios and may cause issues with other applications as well.

Due to the nature of this issue, it will not be feasible to troubleshoot it via the online community forum. It will be best investigated/troubleshot 1:1 by one of our Support Engineers. Therefore, I would suggest reaching out to Azure Support so that detailed traces, testing and troubleshooting can be done for this server.

Hope this helps.

Johnny Nguyen 0 Reputation points

2024-03-20T17:47:31.61+00:00

AnuragSingh-MSFT,

Thank you so much for all of your help with understanding and resolving this issue. I greatly appreciate the information and your time.

I will proceed to contact Azure Support for further assistance.

Kind Regards,
Sign in to comment

Share via

Azure Arc connection Error: Invalid namespace

1 answer