Microsoft.Azure.Diagnostics.PaaSDiagnostics 1.4.1.1 has exited with Exit code: -108

After running Azure Diagnostics 2.5 for a period of time, without any problem, it started to fail.

Here is my wadcfgx.

Here is the CommandExecution log from the sole instance of the app.

Here is my DiagnosticsPluginLauncher log.

Here is DiagnosticsPlugin log.

Where is the problem here? DiagnosticsPlugin log ends with :

DiagnosticsPlugin.exe Error: 0 : [6/3/2015 12:02:41 PM] System.Xml.Schema.XmlSchemaValidationException: The element 'CounterSets' has incomplete content. List of possible elements expected: 'CounterSet'.
   at Microsoft.Azure.Plugins.Plugin.BaseMonitoringConfig.Validate(String configFile, String schemaFile)
   at Microsoft.Azure.Plugins.Plugin.WadParser.Translate(String baseMaResourcePath, Int32 actualDiskQuota, String& fullConfigFilePath)
DiagnosticsPlugin.exe Error: 0 : [6/3/2015 12:02:41 PM] Failed to convert WAD1.1 config to Monagent config format
DiagnosticsPlugin.exe Information: 0 : [6/3/2015 12:02:41 PM] DiagnosticPlugin.exe exit with code -108

I have humble suggestion - the performance counters set is making the problem. Am I right?

Solution

The suggestion was right - trifling with performance counters (a.k.a. selecting my own custom list) is punishable. Disabling them mitigated the problem. I suppose there is a default and allowed (a.k.a. possible) list of performance counters.

Here is a good article about diagnostics with exhaustive error list and the very good string :

%SystemDrive%\ WindowsAzure\Logs\Plugins\Microsoft.Azure.Diagnostics.PaaSDiagnostics<DiagnosticsVersion>\CommandExecution.log

which made me discover the all the logs needed.

In order to solve similar problems :

Publish your instances to staging environment with Remote Desktop enabled.
RDP to an instance through the Server Explorer in VS
Use the above mentioned folder and discover the logs.
Open every log and use it to discover the error with the error code and use the article with the error code suggestions.