Merging of ETL files has failed

[hiraldesai]

Getting a whole bunch of System.Runtime.InteropServices.COMException at DiagnosticsHub.StandardCollector.Host.Interop.ICollectionSession.Stop errors. Full StackTrace to follow but it looks like it's from Azure extension and not the app itself. Unable to repro locally.

Version Info

SDK Version : 2.3.0
.NET Version : dotnet core 2.1 (SDK 2.1.300)
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : Azure Extension + NuGet in code
OS : Windows
Hosting Info (IIS/Azure WebApps/ etc) : Azure Web App

[hiraldesai]

Custom dimensions value from AI:

{
  "AgentVersion": "2.4.60711.2",
  "AgentSession": "97da0108-b311-4659-aa7e-5a99a8f7e3a5",
  "Description": "StopProfiler failed.",
  "RunningMode": "Antares",
  "MachineName": "removed",
  "Source": "ApplicationInsightsProfiler"
}

Stacktrace from AI:

[
  {
    "parsedStack": [
      {
        "assembly": "ApplicationInsightsProfiler, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "DiagnosticsHub.StandardCollector.Host.Interop.ICollectionSession.Stop",
        "level": 0,
        "line": 0
      },
      {
        "assembly": "ApplicationInsightsProfiler, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "Microsoft.ServiceProfiler.Collectors.StandardCollectorBase.<StopAndCollectAsync>b__10_0",
        "level": 1,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Threading.Tasks.Task`1.InnerInvoke",
        "level": 2,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Threading.Tasks.Task.Execute",
        "level": 3,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw",
        "level": 4,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification",
        "level": 5,
        "line": 0
      },
      {
        "assembly": "ApplicationInsightsProfiler, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "Microsoft.ServiceProfiler.Collectors.DetailedTraceCollector+<StopCollectingAndSaveTrace>d__26.MoveNext",
        "level": 6,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw",
        "level": 7,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification",
        "level": 8,
        "line": 0
      },
      {
        "assembly": "ApplicationInsightsProfiler, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "Microsoft.ServiceProfiler.Collectors.DetailedTraceCollector+<StopCollectingAndUploadTraceAsync>d__24.MoveNext",
        "level": 9,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw",
        "level": 10,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification",
        "level": 11,
        "line": 0
      },
      {
        "assembly": "ApplicationInsightsProfiler, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "Microsoft.ServiceProfiler.Engine+<>c__DisplayClass1_1+<<RunAsync>b__2>d.MoveNext",
        "level": 12,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw",
        "level": 13,
        "line": 0
      },
      {
        "assembly": "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089",
        "method": "System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification",
        "level": 14,
        "line": 0
      },
      {
        "assembly": "Microsoft.ServiceProfiler.Agent.Orchestration, Version=2.4.60711.2, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a",
        "method": "Microsoft.ServiceProfiler.Agent.Orchestration.Orchestrator+<TraceAsyncOperation>d__15.MoveNext",
        "level": 15,
        "line": 0
      }
    ],
    "outerId": "0",
    "message": "Merging of ETL files has failed (0x80070507) (Flags: 0x0000011f).",
    "type": "System.Runtime.InteropServices.COMException",
    "id": "35837433"
  }
]

[erik-forsmyr-stratsys]

We are getting the same or maybe a similar error.

https://stackoverflow.com/questions/51979552/azure-web-apps-throws-error-merging-of-etl-files-has-failed

[pharring]

This is a known issue and the fix is in version 2.6.5 of the Application Insights Site Extension. Please upgrade to the latest Application Insights site extension for your web app.

[hiraldesai]

Upgrading the extension made the ETL error go away. Now it's giving 2 new errors (at ~2 minute interval), one of them says "too many sessions" and the other one says "no active session".

I clicked on the documentation link along with the message and it says 4 active sessions are supported but I only have 2 app service instances connected to my application insights instance and zero staging slots.

There is no active profiling session.
There are too many active profiling sessions on this machine. You can try again after stopping other profiling sessions.For Azure App Service applications, please check if other deployment slots or other App Services using the same App Service Plan have also enabled profiling.See http://aka.ms/ApplicationInsightsProfilerTooManySessions for troubleshooting.

[pharring]

Try scaling up your service plan and scaling it back down again. That has the effect of moving your applications to another VM which should effectively reset any orphaned profiling sessions.

[hiraldesai]

Thanks.