Error while updating a custom Windows Azure Diagnostics configuration xml from powershell. "Invalid update to extension reference for role"

Question

I am attempting to upload a manually edited WADConfig xml to my VM. The WAD service is functioning correctly, I needed to add some custom WinEventLogs. The prescribed steps result in an error.
What am I overlooking?
I am following these instructions:
Step 5: Remotely install Diagnostics on your Azure Virtual Machine
azure.microsoft.com/en-in/documentation/articles/cloud-services-dotnet-diagnostics/#virtual-machine
$storage_name = "wadexamplevm"
$key = "<StorageAccountKey>"
$config_path="c:\users\<user>\documents\visual studio 2013\Projects\WadExampleVM\WadExampleVM\WadExample.xml"
$service_name="wadexamplevm"
$vm_name="WadExample"
$storageContext = New-AzureStorageContext
-StorageAccountName $storage_name -StorageAccountKey $key
$VM1 = Get-AzureVM
-ServiceName $service_name -Name $vm_name
$VM2 = Set-AzureVMDiagnosticsExtension
-DiagnosticsConfigurationPath $config_path
-Version "1.*"
-VM $VM1 -StorageContext $storageContext
$VM3 = Update-AzureVM
-ServiceName $service_name -Name $vm_name
-VM $VM2.VM
Unfortunately, I am receiving this error:
Update-AzureVM : BadRequest: Invalid update to extension reference for role: XXXXXX and reference: IaaSDiagnostics.
What's missing from the above script?

Answer 1

Hi,
Since Azure SDK 2.5 uses the extension model the diagnostics extension, the configuration and the connection string to the diagnostic storage are no longer part of the deployment package and cscfg. All the diagnostics configuration is contained within the
wadcfgx. The advantage with this approach is that diagnostics agent and settings are decoupled from the project and can be dynamically enabled and updated even after your application is deployed. 
Due to this change some existing workflows need to be rethought – instead of configuring the diagnostics as part of the application that gets deployed to each environment you can first deploy the application to the environment and then apply the diagnostics
configuration for it.  When you publish the application from Visual Studio this process is done automatically for you. However if you were deploying your application outside of VS using PowerShell then you have to install the extension separately through
PowerShell.
There PowerShell cmdlets for managing the diagnostics extensions on a Cloud Service are -
Set-AzureServiceDiagnosticsExtension
Get-AzureServiceDiagnosticsExtension
Remove-AzureServiceDiagnosticsExtension
You can use the Set-AzureServiceDiagnosticsExtension method to enable diagnostics extension on a cloud service. One of the parameters on this cmdlet is the XML configuration file. This file is slightly different from the diagnostics.wadcfgx file. You can
create this file from scratch by either following the article that you are referring to or  you can modify the wadcfgx file and pass in the modified file as a parameter to the powershell cmdlet.
To modify the wadcfgx file –
Make a copy the .wadcfgx.
Remove the following elements from the Copy:
<DiagnosticsConfiguration xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
   <PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
     <StorageAccount name=" " endpoint="https://core.windows.net/" />
   </PrivateConfig>
   <IsEnabled>false</IsEnabled>
</DiagnosticsConfiguration>
Make sure the top of the file still has xml version and encoding –
   <?xml version="1.0" encoding="utf-8"?>
Effectively you are stripping down the Wadcfgx to only contain the <PublicConfig> section and the <?xml> header. You can then call the PowerShell cmdlet along with the appropriate parameters for the staging slots and roles:
$storage_name = ‘
<storagename>’
$key= ‘<key>’
$service_name = '<servicename>'
$public_config = '<thepublicconfigfrom_diagnostics.wadcfgx>'
$storageContext = New-AzureStorageContext –StorageAccountName $storage_name –StorageAccountKey $key
Set-AzureServiceDiagnosticsExtension -StorageContext $storageContext -DiagnosticsConfigurationPath $public_config –ServiceName $service_name -Slot ‘Staging’ -Role ‘WebRole1’
Hope this helps !
Regards,
Sowmya