Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, March 7, 2016 8:39 PM
Hi all,
I attempted to run a script on a target VM in Azure ARM using Custom Script Extension. Custom Script Extension failed by calling out an API error.
I navigated to the portal to see the error messages associated with the extension. However, I see this:
I've obviously checked that the VM is running.
Anyone seen this error before?
All replies (3)
Tuesday, March 8, 2016 4:01 PM | 1 vote
Hello Charlie,
Thank you for contacting us.
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-extensions-customscript/
Could you try uninstalling custom script extensions and check to see if this helps?
Regards,
Dipin Mathew.
Thursday, May 5, 2016 1:39 PM
Hi all,
I would like to reopen this thread. This error with VM extensions is not just limited to Custom Script Extension. All types of different extensions may be listed as unresponsive.
Attempting to uninstall these unresponsive extensions from the portal leads to an error without any meaningful description. Attempting to restart or redeploy the VM also fails, with the error that the installed extensions failed or are unresponsive.
Does anyone have solution to this?
Friday, May 6, 2016 5:43 PM | 1 vote
Hello Charlie.
You could refer the following link for details on Azure Virtual Machines extensions and features for both classic and ARM VMs:
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-extensions-features/
Please try to add an extension on the command line with Azure PowerShell using the Set-AzureRmVmExtension cmdlet (see https://msdn.microsoft.com/en-us/library/mt603745.aspx?f=255&MSPPError=-2147217396), or with Azure CLI using azure vm extension set.
You could start with the command line Octopus example here: http://docs.octopusdeploy.com/display/OD/Azure+Virtual+Machines - though adapt the command to use the new Azure Resource Command above.
Hope this helps.
Regards,
Dipin Mathew