.NET Framework execution was aborted by escalation policy because of out of memory

I am posting this in the .NET Framework inside SQL Server forum as I assume the issue is related to CLR / SQL Server.  Please let me know if this is the incorrect forum.

I am receiving the following error in the event log:

AppDomain [DB_NAME].dbo[runtime].5253 was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource. 
System.Threading.ThreadAbortException: Exception of type 'System.Threading.ThreadAbortException' was thrown.
System.Threading.ThreadAbortException: 

The system that this is occurring on is a Windows Server 2003 R2 SP2 (32 bit), SQL Server 2005 SP2 with 8 GB of RAM:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

9.00.3042.00	SP2	Standard Edition

The CLR assembly is relatively simple and is referenced by both store procedures as well as by a table trigger (update).  Essentially the CLR assembly instantiates an object (in a referenced webservice on a separate&

Good evening all,

I developed a C# class libray code. Under which i called a third party .asmx web service. I used "CREATE ASSEMBLY" command to register all my custom assembly and needed .net core assemblies. I did register all needed .net dll's. for Ex:-

C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Web.dll

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Core.dll

I created a procedure and called my class libray methods from SQL analyzer. See Ex:- code below. But when i executed the code method i see the error ".NET Framework execution was aborted. The UDP/UDF/UDT did not end thread affinity.". For testing purpose i logged the flow of my code and the flow of code is good and it even fetched the miles i wanted, except the error. What possibley could be going wrong? Could somebody help me?

CREATE PROCEDURE usp_GetCalcMilesTest
@strXML nvarchar(3000),
@blnSkipMilesCalcByZip bit,
@bLogProcessFlow bit,
@calledFrom nvarchar(3),
@distance nvarchar(15)OUTPUT
AS EXTERNAL NAME CalculateMilesPCM.[CalculateMilesPCM.clsMiles].CalcMilesGetcitystate
GO

DECLARE @distance nvarchar(15)
declare @testval nvarchar(15)
begin
 EXEC usp_GetCalcMilesTest '<int_Loads BtLoadid="508952996" SHID="2480" Routetype="HB" SkipMil

This article describes the WSE policy framework, which allows you to describe constraints and requirements a Web service must enforce. Discussions include security scenarios in WSE 3.0 and extending the framework with custom constraints and requirements.

Tomasz Janczuk

MSDN Magazine February 2006

The first part of this two-part article explained how the garbage collection algorithm works, how resources can clean up properly when the garbage collector decides to free a resource's memory, and how to force an object to clean up when it is freed. The conclusion of this series explains strong and weak object references that help to manage memory for large objects, as well as object generations and how they improve performance. In addition, the use of methods and properties for controlling garbage collection, resources for monitoring collection performance, and garbage collection for multithreaded applications are covered.

Jeffrey Richter

MSDN Magazine December 2000

Garbage collection in the Microsoft .NET common language runtime environment completely absolves the developer from tracking memory usage and knowing when to free memory. However, you'll want to understand how it works. Part 1 of this two-part article on .NET garbage collection explains how resources are allocated and managed, then gives a detailed step-by-step description of how the garbage collection algorithm works. Also discussed are the way resources can clean up properly when the garbage collector decides to free a resource's memory and how to force an object to clean up when it is freed.

Jeffrey Richter

MSDN Magazine November 2000

Since Upgrading to SSAS 2008, cannot explore Data or Browse cubes from Vista Untimate machine.