locked
VMExtensionProvisioningError RRS feed

  • Question

  • VM Deployment to Resource Group started to fail on 04 Jan 18 at 21:28. The error is "VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'WindowsADC-CustomizeOS'. Error message: \"DSC Configuration 'windowsADC' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xWindowsUpdateAgent failed to execute Test-TargetResource functionality with error message: Exception from HRESULT: 0x8024402F The SendConfigurationApply function did not succeed.

    Could you possibly advice where to look if the code was not changed? 

    Friday, January 5, 2018 5:11 PM

Answers

  • This basically means that your DSC script failed somewhere during it's run. Ufortuantely the errors reported to the portal are not always that helpful.

    To investigate further you are going to need to logon to the VM and take a look at the DSC extension logs which are located in "C:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\<extension version no>".

    This hopefully will give you some more information on what went wrong. You can also check the DSC event log.

    When you come to wanting to run this again, you need to make sure that you either delete the DSC extension from the VM before running, or you are passing at least 1 new parameter value to the DSC extension when you run it, otherwise it will just cache the failed response from last time. The FORCEUPDATETAG parameter can be used to pass arbitrary values that change to avoid this.


    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    • Marked as answer by Dutch DevOps Thursday, February 1, 2018 12:40 PM
    Monday, January 8, 2018 9:50 AM

All replies

  •  Check the Firewall rule(s) on Network to allow access to the extension.

    You refer to the suggestion mentioned in the GitHub link.

    If the issue still persist, un-install and re-install VM agent Extension

    Additional information: refer to this blog.

    -----------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.


    Friday, January 5, 2018 6:25 PM
  • This basically means that your DSC script failed somewhere during it's run. Ufortuantely the errors reported to the portal are not always that helpful.

    To investigate further you are going to need to logon to the VM and take a look at the DSC extension logs which are located in "C:\WindowsAzure\Logs\Plugins\Microsoft.Powershell.DSC\<extension version no>".

    This hopefully will give you some more information on what went wrong. You can also check the DSC event log.

    When you come to wanting to run this again, you need to make sure that you either delete the DSC extension from the VM before running, or you are passing at least 1 new parameter value to the DSC extension when you run it, otherwise it will just cache the failed response from last time. The FORCEUPDATETAG parameter can be used to pass arbitrary values that change to avoid this.


    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    • Marked as answer by Dutch DevOps Thursday, February 1, 2018 12:40 PM
    Monday, January 8, 2018 9:50 AM