All geek questions in one place

Diagnostic configuration for Azure Deployment fails

I am trying to get diagnostics to work with my Azure Web Worker role. I start with a solution for the Web Worker Role role by selecting "New Project / Azure Cloud Service". If I deselect Enable Diagnostics in the Worker Role properties, I can successfully deploy the website role. It is not so much, but it is being deployed and seems to be starting. If I select "Enable Diagnostics", the deployment will fail:

9:27:34 PM - Applying Diagnostics extension. 9:27:37 PM - Value cannot be null. Parameter name: s

I tried various combinations for "Configure ..." but got the same error. Now it appears on two machines, so the likelihood that this is some kind of corruption is subtle.

Does anyone know what is happening or has a simple, working example of emitting and reading diagnostic messages?

+5
source share
2 answers

I received another response from MS support: "Our product team has canceled the change."

I am testing it, and now I can publish with the included diagnostics without problems.

+2
source

I received a response from support: this is an identified issue with the backend, and the technical team is working on it with the highest priority.

As a workaround, disable the diagnostics:

enter image description here

+1
source

Source: https://habr.com/ru/post/1263900/

More articles:


All Articles