FIX: Error message when you run a SQL Server 2005 application that contains user-defined data types: "AppDomain 3 (<db_name>.dbo[runtime].2) is marked for unload due to memory pressure" (917271)

SUMMARY

This article describes the following about this hotfix release:

The issues that are fixed by the hotfix package
The prerequisites for installing the hotfix package
Whether you must restart the computer after you install the hotfix package
Whether the hotfix package is replaced by any other hotfix package
Whether you must make any registry changes
The files that are contained in the hotfix package

SYMPTOMS

When you run a Microsoft SQL Server 2005 application that contains user-defined data types, the following symptoms may occur:

A memory leak occurs.
An error message that resembles the following is logged in the SQL Server error log:
AppDomain 3 (<db_name>.dbo[runtime].2) is marked for unload due to memory pressure.
Error: 6533, Severity: 16, State: 49.
AppDomain <db_name>.dbo[runtime].4 was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource.

Error: 6532, Severity: 16, State: 74.
.NET Framework execution was aborted by escalation policy because of out of memory.
System.Threading.ThreadAbortException: Thread was being aborted.
System.Threading.ThreadAbortException:
at System.RuntimeType.RuntimeTypeCache.MemberInfoCache`1.AddMethod(RuntimeTypeHandle declaringType, RuntimeMethodHandle method, CacheType cacheType)
at System.RuntimeType.RuntimeTypeCache.GetMethod(RuntimeTypeHandle declaringType, RuntimeMethodHandle method)
at System.RuntimeType.GetMethodBase(RuntimeTypeHandle reflectedTypeHandle, RuntimeMethodHandle methodHandle) at System.RuntimeType.GetMethodBase(RuntimeMethodHandle methodHandle)
at System.Reflection.Emit.DynamicScope.GetTokenFor(RuntimeMethodHandle method)
at System.Reflection.Emit.DynamicILInfo.GetTokenFor(RuntimeMethodHandle method)
The number of garbage collection handles for the SQL Server process gradually increases until the application domain is unloaded.

CAUSE

This problem occurs when you repeatedly run an SQL stored procedure that takes a user-defined data type as a parameter. The SQL stored procedure may be the sp_executesql system stored procedure or a stored procedure that you create.

Note These symptoms may be caused by the problem that is described in this article. These symptoms may also be caused by user code that does not release common language runtime (CLR) memory or garbage collection handles.

RESOLUTION

To resolve this problem, apply the cumulative hotfix package (build 2153) for SQL Server 2005 that is discussed in Microsoft Knowledge Base article 918222. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

918222 Cumulative hotfix package (build 2153) for SQL Server 2005 is available