AppInsights logo

How to fix weird “Production Breakpoints” errors in an Azure App Service?

This post was most recently updated on July 16th, 2020.

Reading Time: 2 minutes.

This article describes a curious fix I found to an issue where Application Insights (seemingly) crashes your Azure App Service, leaving behind interesting and non-descriptive errors in the Application Event Logs.


Table of Contents

Does your Application Insights look like this, too? Event logs full of “Production Breakpoints” with weird errors about named pipes?

Azure App Service diagnostic log full of "Production Breakpoints" -error.. What gives?
Azure App Service diagnostic log full of “Production Breakpoints” -error.. What gives?

In my case, the errors were something like these below:

IfFailRet(pNamedPipe->Read((BYTE*)&controlRequest, sizeof(SnapshotHolderControlStruct))) failed in function CSnapshotHolder::HandleNewPipeConnection: -2147024787


CNamedPipe::Read - Read from named pipe failed: 0x8007006D.

These errors would always pop up at the same time the site would crash under fairly meager load of a hundred or so RPS (requests per second). Impossible to tell whether the errors were logged because of the crash, or the app service crashed because of the same thing that caused the errors…

After a quick investigation, Application Insights seemed to be the source (“Production Breakpoints”) for the error. I had never heard of AppInsights crashing an App Service, but we did eas

This didn’t completely remove the issue, but did stabilize the app service. But how to get rid of the errors for good?

There’s a simple fix, though! Or at least there was for me. Maybe it’ll help you as well!


Okay, so the solution for me was kind of weird – but easy.

Earlier, when I had first had Azure DevOps enable “Monitoring”, it would install AppInsights extension to the Azure App Service website.

That’s a horrible mistake. Don’t do that.

The extensions are extremely fragile. I’ve posted about that earlier: You wouldn’t believe these 3 solutions to fix the error “500.32”, and what they look like now!

Anyway – the extensions are kind of wild as they also add random application settings to your app service. And these settings have side effects – like in this case!

I had removed the extension, and we were using AppInsights with the SDK, i.e. without anything extra installed on the Azure App Service. But uninstalling the extension does not remove its Application Settings – which makes sense, because they DO have side effects, so you can’t really remove them, because some other functionality might be using them as well!

Oh, what fun.

Anyway, long story short – remove this property “SnapshotDebugger_EXTENSION_VERSION”:

And with any luck, you’re good!

0 0 vote
Article Rating
Notify of
1 Comment
most voted
newest oldest
Inline Feedbacks
View all comments