Deployment error "The DSC Extension failed to execute"

[FredCumbee]

I'm getting the following error when I deploy the template. The link in the message is returning a 404 error. Can you help me with this?

VM has reported a failure when processing extension 'sessionhost'. Error message: "The DSC Extension failed to execute: Error downloading https://raw.githubusercontent.com/azure/vm-scale-sets/master/hack2017/DSC/Configuration.zipsp=r&st=2018-05-22T18:19:44Z&se=2018-05-23T02:19:44Z&spr=https&sv=2017-07-29&sig=qWjxvNQi2iKrsdDd89GlRxY5YT0CFFQrnP27Odzej1k%3D&sr=b after 2 attempts: 404: Not Found. More information about the failure can be found in the logs located under 'C:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\2.76.0.0' on the VM.".

[gatneil]

What do the logs say?

[FredCumbee]

On 1 of the instances I checked c:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\2.76.0.0\DscExtensionHandler.1.20180522-192458.txt and found the below. I'm trying to find out where that link is being called from. I see that https://raw.githubusercontent.com/azure/vm-scale-sets/master/hack2017/DSC/Configuration.zip does work with out the extra stuff.

"ErrorMessage": "Error downloading
https://raw.githubusercontent.com/azure/vm-scale-sets/master/hack2017/DSC/Confi
guration.zipsp=r\u0026st=2018-05-22T18:19:44Z\u0026se=2018-05-23T02:19:44Z\u002
6spr=https\u0026sv=2017-07-29\u0026sig=qWjxvNQi2iKrsdDd89GlRxY5YT0CFFQrnP27Odze
j1k%3D\u0026sr=b after 2 attempts: 404: Not Found",

[FredCumbee]

I found the URL in c:\Packages\Plugins\Microsoft.Powershell.DSC\2.76.0.0\RuntimeSettings\1.settings and updated it. Any idea how I can kick of the script again?

[gatneil]

You updated it within the actual VM or in the scale set configuration?

[FredCumbee]

I update it in the 2 scale set instances it created and restarted the scale set but it still gives the same error. Is it copied to the image .vhd file l referenced to create the scale set? From: Neil Sant Gat Sent: Tuesday, May 22, 5:13 PM Subject: Re: [Azure/vm-scale-sets] Deployment error "The DSC Extension failed to execute" (#54) To: Azure/vm-scale-sets Cc: FredCumbee, Author You updated it within the actual VM or in the scale set configuration? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#54 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AltBH0gkqxRbgi1Qz2GFYUlfs0FgfXucks5t1H96gaJpZM4UJPUD>.

[gatneil]

You need to update it in the scale set model itself; changing it within the VM won't fix it because (as you point out) there's no way to rerun the extension from within the VM

[FredCumbee]

Ok, I mounted the scale set image file (source .vhd) and the folder doesn't exist. It only contains C:\Packages\Plugins\Microsoft.Compute.BGInfo. Am I looking the wrong place?

[gatneil]

@mgreenegit any thoughts?

Thanks,
Neil

[FredCumbee]

I tried both templates below and found its failing to download the 'sessionhost' extension.

 Deploy scale set with one extension - join domain and sessionhost
 Deploy scale set join domain and sessionhost, and set up CPU based autoscale (scale-out only)

I edited the template and found the sessionhost parameter below. In reviewing the URL in the error code, I found its adding the SAS token to the end. I edited the template and found the sessionhost parameter below. Is the ModulesUrl correct or should the SasToken be separated?

                            "name": "sessionhost",
                            "properties": {
                                   "publisher": "Microsoft.Powershell",
                                   "type": "DSC",
                                   "typeHandlerVersion": "2.11",
                                   "autoUpgradeMinorVersion": true,
                                   "settings": {
                                      **"ModulesUrl": "[concat(parameters('_artifactsLocation'),'/DSC/Configuration.zip', parameters('_artifactsLocationSasToken'))]"**,

[rfcdejong]

Did you ever fix it? I have been trying this for nearly a day now, configurationUrlSasToken and artifactsLocationSasToken within protectedSettings. and then in configuration an url. without the token. I tried several kind of storage accounts, blob, gp V1 and gp V2. It works when I allow public access, but somehow it won't use the protectedSettings.

[Wanderson304]

Our! Helped me a lot. I've been trying for 2 days. I disabled the firewall and went. Thanks ...