Open francescomagalini opened 6 years ago
We have the same type of problem. We have several nodes in a cluster where the nodes are deployed with the same ARM template and DSC configuration. One of the nodes is causing this problem, the others not. So it is not the configuration that is the problem. The node causing the problem worked previously.
If I uninstall the DSC Extension (2.76) it will not be able to reinstall and it fails with this error. I uninstall and reinstall using the portal. I think somthing must be cleared properly somewhere, but I cannot figure out what. It is not acceptable to have to delete the node. This problem comes back periodically. Some cache somewhere, or something that should be deleted from node to "clear" properly?
I too have the exact same scenario as you inghak, Several nodes, all previously worked, using Azure Automation. 10 days ago I noticed it stopped working, cannot get it to reconnect. Exact same error message. Let me know if you've figured anything out. I have a support ticket with Microsoft and so far their best suggestion is to restart the server.
Same issue here with some brand new Azure Windows Server 2016 VMs. I am however able to add the VMs to Azure Automation DSC configs through the portal - with the exact same configurations I use in the ARM template. Strange.
Any updates on this one. I am facing same issue and I need to do it within ARM template unfortunately.
We're experiencing the same issue, has anyone had any luck fixing this problem consistently?
For me the issue was a bad automation account certificate on the server. I went to the computers certificate store and deleted all of the automation account certs and I was able to deploy the extension then.
Thanks for the tip, I’ll try that and let you know how I get on.
@DanFrei64 Thanks for your suggestion, this didn't work for me but for anyone who does need to remove certificates (I believe by default they only last 12 months) I've written a powershell one liner for this. You will need to have administrator privileges:
Get-ChildItem -Recurse -Path cert: | Where-Object { $_.Subject -like '*AzureDSCExtension*' } | ForEach-Object { $_ | Remove-Item -Force }
We did solve our problem which was actually unrelated to the DSC systems at all. We had created a private load balancer and added the machine to the backend pool, which prevents all outbound connections to the internet. Nodes connecting to an Azure DSC Pull Server require access to a publicly facing web service, in our case "https://uks-agentservice-prod-1.azure-automation.net".
We solved this problem by adding another public load balancer as described in the documentation here
Hi, I'm trying to define a VM with a DSC extension that should register the VM with Azure Automation
Here is the fluent definition:
I get:
[ERROR] Registration of the Dsc Agent with the server https://we-agentservice-prod-1.azure-automation.net/accounts/41fe028f-c44d-475c-8e51-ee93e0251c51 failed. The underlying error is: The attempt to register Dsc Agent with AgentId 58F3E916-47CD-11E8-B04D-000D3A2B8279 with the server https://we-agentservice-prod-1.azure-automation.net/accounts/41fe028f-c44d-475c-8e51-ee93e0251c51/Nodes(AgentId='58F3E916-47CD-11E8-B04D-000D3A2B8279') returned unexpected response code Unauthorized.
full instance view:Parameters are correct. Any guess?