Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 911310 - Last Review: March 16, 2007 - Revision: 1.3
Error message when you run a Transact-SQL query that involves one or more SQL Server CLR Integration (SQLCLR) objects in SQL Server 2005: "Msg 6535"
When you run a Transact-SQL query that involves one or more
Microsoft SQL Server CLR Integration (SQLCLR) objects in Microsoft SQL Server
2005, you may receive an error message that is similar to the
following:
Msg 6535, Severity 16, State {2), In Routine
<RoutineName>, At Line 25, Full Message : .NET
Framework execution was aborted. Another query caused the AppDomain
framework.dbo[runtime].2 to be unloaded or an unhandled .NET exception
happened.
This issue occurs because one of the following conditions is
true:
- The host escalation policy causes the common language
runtime (CLR) to unload the application domain.
SQL Server uses the
host escalation policy to change the CLR error handling behavior. Specifically,
you can configure SQL Server to instruct the CLR to take a different action
when SQL Server will take one action in an error condition. If an error
condition is severe enough, SQL Server can instruct the CLR to unload the
application domain. For example, if a CLR routine causes stack overflow or
still owns a managed lock upon thread exit, the CLR routine unloads the
application domain to help protect the stability of SQL Server. Therefore, this
action affects other users who are running the code in the same application
domain.
The following code example illustrates this condition. public partial class StoredProcedures
{
[Microsoft.SqlServer.Server.SqlProcedure]
public static void usp_Monitor()
{
Object obj = new Object();
Monitor.Enter(obj);
}
[Microsoft.SqlServer.Server.SqlProcedure]
public static void usp_LongRunning()
{
Thread.Sleep(Int32.MaxValue);
}
}Server: Msg 6534, Level 16, State 49, Procedure
usp_Monitor, Line 0 AppDomain CLRTest.dbo[runtime].8 was unloaded by escalation
policy to ensure the consistency of your application. Application failed to
release a managed lock.
- Inappropriate exception handing occurs.
The
following code example causes an out-of-memory error, and then the
out-of-memory error causes a ThreadAbortException exception. However, the following code example tries to catch all
exceptions including the ThreadAbortException exception and tries to access the SqlPipe object in the catch block. [Microsoft.SqlServer.Server.SqlProcedure]
public static void usp_Test()
{
try
{
byte[] b = new byte[2024 * 1024 * 1024];
//Do something here
}
catch
{
SqlContext.Pipe.Send("failed");
}
} - You experience the problem that is documented in Microsoft
Knowledge Base article 910414.
When this condition is true, parallel
threads are inappropriately shut down. This problem is a bug in SQL Server, and
a hotfix is available.
For more information, click the following
article number to view the article in the Microsoft Knowledge Base: 910414Â
(http://kbalertz.com/Feedback.aspx?kbNumber=910414/
)
FIX: You may receive an error message when you try to load data by using CLR functions in a Transact-SQL job in SQL Server 2005
For more information about SQLCLR, visit the following
Microsoft Developer Network (MSDN) Web site:
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Express Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate