Azure App Service "Production Breakpoints" errors

Performance freak
Search for a command to run...

Performance freak
No comments yet. Be the first to comment.
When you use Response.Redirect with its second parameter set to true, it triggers a call to Response.End() Response.Redirect("Login.aspx"); // default is true Response.Redirect("Login.aspx", true); // same as above This causes AS...

Using ThreadPool.QueueUserWorkItem: Helps bypass limitations when trying to run async code inside IHttpModule. Does not interfere with the ASP.NET pipeline. Email sending does not block the main thread. Calling SendMailAsync().Wait() is safe here...

Introduction In SQL Server, the bit data type is used to store boolean values (0 for false, 1 for true). However, when working with SQL Server in a .NET application using Entity Framework or LINQ to SQL, the bit field is automatically converted to a ...

System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() To avoid the ThreadAbortException error when using Response.Redirect, setting the second parameter to false is generally sufficient. However,...

In Visual Studio; Solution Explorer-Project-Properties-Application. Check "Auto-Generate binding redirects" When this is selected, versions are specified in the web.config file after the Nuget package updates. When is binding necessary? If there is...

This article describes a curious fix I found to an issue where Application Insights (seemingly) crashes your Azure App Service, leaving behind interesting, yet non-descriptive errors in the Application Event Logs.
Does your Azure App Service’s event log look like this? Full of “Production Breakpoints” with weird errors about named pipes?
In my case, the errors were something like these below:
These errors would always pop up at the same time the site would crash under fairly meager load. In one case, any user would crash the site.
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.
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!
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. You might’ve also enabled these extensions by clicking the tempting buttons in Azure Portal. That might be a mistake as well.
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.
Remove the unnecessary application settings that somehow mess up the app service
Click App Service, then Navigate to Configuration (under the Settings)
Remove the property called SnapshotDebugger_EXTENSION_VERSION
Hit Save
Optional : Navigate App Service-Extentions. and if you have Application Insights extension installed, remove it.


Thank you Antti K. Koskela for this article :
https://www.koskila.net/how-to-fix-weird-production-breakpoints-errors-in-an-azure-app-service/