Publish cloud service fails from Visual Studio 2013 Update 4: Published Asset Entry for Image Microsoft.Azure.Diagnostics_PaaSDiagnostics_europeall_manifest.xml not found.

Question

I have a cloud service project with two roles (service and worker). In Visual Studio 2013 Update 4 when I choose "Publish..." from the "Solution Explorer",  it opens "Microsoft Azure Activity Log" and quickly terminates.
Here the log:
9:43:47 AM - Applying Diagnostics extension.
9:44:09 AM - Published Asset Entry for Image Microsoft.Azure.Diagnostics_PaaSDiagnostics_europeall_manifest.xml not found.
All works fine when uploading the package and updating from https://manage.windowsazure.com/. It only fails from within Visual Studio.
What can I do to get it working?

Answer 1

I have the same problem with our Azure project. Two web roles (service and worker). Just updated from SDK2.2 to SDK2.5 and Visual Studio 2013 Update 2 to Update 4. The main reason behind this was to move from log4net to WAD and in doing so, of course directly
move to the new diagnostics version.
Now, I get the same error message in Visual Studio:
11:45:24 - Checking for Remote Desktop certificate...
11:45:25 - Applying Diagnostics extension.
11:45:45 - Published Asset Entry for Image Microsoft.Azure.Diagnostics_PaaSDiagnostics_europeall_manifest.xml not found.
With my small testing project - also two roles (service and worker) - everything is fine. However, I'm looking for a solution to make by existing production service working.
Also the test project shows no Microsoft.Azure.Diagnostics_PaaSDiagnostics_europeall_manifest.xml,
but this is no problem - so what's the meaning of or solution to this error messages?
What I found so far:
I deployed the Azure project from the same development environment to another Azure test service: Deployment
showed no errors and the service is running fine! So the problem is not with the source, the development environment, library dependencies etc.
Trying Azure cmdlets for PowerShell also work fine for the new service and fails for the production service with almost the same error message:
Following http://blogs.msdn.com/b/kwill/archive/2014/12/02/windows-azure-diagnostics-upgrading-from-azure-sdk-2-4-to-azure-sdk-2-5.aspx
I tried:
PS C:\> Set-AzureServiceDiagnosticsExtension -StorageContext $storageContext -DiagnosticsConfigurationPath $public_config -ServiceName $service_name -Slot 'Staging' -Role $role_name
VERBOSE: Setting PaaSDiagnostics configuration for MyWebRole.
Set-AzureServiceDiagnosticsExtension : BadRequest : Published Asset Entry for Image
Microsoft.Azure.Diagnostics_PaaSDiagnostics_europeall_manifest.xml not found.
At line:1 char:1
+ Set-AzureServiceDiagnosticsExtension -StorageContext $storageContext -Diagnostic ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-AzureServiceDiagnosticsExtension], CloudException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.CloudException,Microsoft.WindowsAzure.Commands.ServiceManagement.
   Extensions.SetAzureServiceDiagnosticsExtensionCommand
The problem seems to be related to those service configuration parts in the cloud which are not replaced
by a new deployment... So what are possible reasons or fixes for this behaviour?
Best regards,
 Andreas