Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You may receive an error message when you run a CLR stored procedure or CLR function that uses a context connection in SQL Server 2005

FIX: You may receive an error message when you run a CLR stored procedure or CLR function that uses a context connection in SQL Server 2005

View products that this article applies to.

Bug #: 50000483 (SQL Hotfix)

↑ Back to the top

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

↑ Back to the top

Summary

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether the hotfix package is replaced by any other hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

↑ Back to the top

Symptoms

You execute a common language runtime (CLR) stored procedure or a CLR function in the SQL Server process. In the CLR stored procedure or the CLR function, you use a context connection to open a loop-back connection and execute many Transact-SQL statements. For example, you execute 1 billion Transact-SQL statements. Additionally, these Transact-SQL statements do not return result sets. For example, these Transact-SQL statements are SET statements or cursor operations.

When you run the CLR stored procedure or the CLR function in SQL Server 2005, you may receive one of the following error messages:
Error Message 1
Server: Msg 6535, Level 16, State 49
.NET Framework execution was aborted. Another query caused the AppDomain AppDomain.1 to be unloaded or an unhandled .NET exception happened.
Note AppDomain represents the name of the application domain in which the code runs.
Error Message 2
Server: Msg 6532, Level 16, State 70
.NET Framework execution was aborted by escalation policy because of out of memory.
When this problem occurs, messages that resemble the following are logged in the SQL Server Errorlog:
2007-01-15 14:47:46.76 spid51 AppDomain 3 (CLR_DB.dbo[runtime].2) created.
2007-01-15 14:49:48.06 spid1s AppDomain 3 (CLR_DB.dbo[runtime].2) is marked for unload due to memory pressure.
2007-01-15 14:51:23.47 spid51 Error: 6532, Severity: 16, State: 70.
2007-01-15 14:51:23.47 spid51 .NET Framework execution was aborted by escalation policy because of out of memory.
2007-01-15 14:51:53.31 spid51 AppDomain 3 (CLR_DB.dbo[runtime].2) unloaded.

↑ Back to the top

Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005 32-bit version
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2206.0398,11217-Nov-200603:16x86
Microsoft.analysisservices.adomdclient.dll9.0.2206.0543,52017-Nov-200603:16x86
Microsoft.analysisservices.dll9.0.2206.01,215,26417-Nov-200603:16x86
Microsoft.sqlserver.sqlenum.dll9.0.2206.0908,06417-Nov-200603:16x86
Ms.as.deployengine.dll9.0.2206.0138,01617-Nov-200603:16x86
Ms.ss.mgdsqldumper.dll2005.90.2206.075,55217-Nov-200603:16x86
Msasxpress.dll9.0.2206.022,30417-Nov-200603:16x86
Msgprox.dll2005.90.2206.0197,92017-Nov-200603:16x86
Msmdlocal.dll9.0.2206.015,614,75217-Nov-200603:16x86
Msmdredir.dll9.0.2206.03,990,30417-Nov-200603:16x86
Replprov.dll2005.90.2206.0547,61617-Nov-200603:16x86
Replrec.dll2005.90.2206.0782,11217-Nov-200603:16x86
Sqlaccess.dll2005.90.2206.0347,93617-Nov-200603:16x86
Sqlagent90.exe2005.90.2206.0318,75217-Nov-200603:16x86
Sqlservr.exe2005.90.2206.028,964,69617-Nov-200603:16x86
Xmlsub.dll2005.90.2206.0192,80017-Nov-200603:10x86
Xpstar90.dll2005.90.2206.0292,64017-Nov-200603:10x86
Xpstar90.rll2005.90.2206.0152,86417-Nov-200603:16Not Applicable
SQL Server 2005 x64-based version
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2206.0522,52816-Nov-200618:02x64
Microsoft.analysisservices.adomdclient.dll9.0.2206.0543,52016-Nov-200618:02x86
Microsoft.analysisservices.dll9.0.2206.01,215,26417-Nov-200603:16x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2206.091,42416-Nov-200618:02x64
Microsoft.sqlserver.sqlenum.dll9.0.2206.0875,29616-Nov-200618:02x86
Microsoft.analysisservices.deploymentengine.dll9.0.2206.0138,01617-Nov-200603:16x86
Msasxpress.dll9.0.2206.027,42416-Nov-200618:02x64
Msgprox.dll2005.90.2206.0259,36016-Nov-200618:02x64
Msmdlocal.dll9.0.2206.015,614,75217-Nov-200603:16x86
Msmdredir.dll9.0.2206.03,990,30417-Nov-200603:16x86
Replprov.dll2005.90.2206.0745,24816-Nov-200618:02x64
Replrec.dll2005.90.2206.01,008,41616-Nov-200618:02x64
Sqlaccess.dll2005.90.2206.0355,10416-Nov-200618:02x86
Sqlagent90.exe2005.90.2206.0389,92016-Nov-200618:02x64
Sqlservr.exe2005.90.2206.039,371,04016-Nov-200618:02x64
Xmlsub.dll2005.90.2206.0317,21616-Nov-200618:02x64
Xpstar90.dll2005.90.2206.0540,96016-Nov-200618:02x64
Xpstar90.rll2005.90.2206.0153,37616-Nov-200618:02Not Applicable
SQL Server 2005 Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2206.01,095,45616-Nov-200612:14IA-64
Microsoft.analysisservices.adomdclient.dll9.0.2206.0543,52016-Nov-200612:14x86
Microsoft.analysisservices.deploymentengine.dll9.0.2206.0138,01617-Nov-200603:16x86
Microsoft.analysisservices.dll9.0.2206.01,215,26417-Nov-200603:16x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2206.0163,10416-Nov-200612:14IA-64
Microsoft.sqlserver.sqlenum.dll9.0.2206.0875,29616-Nov-200612:14x86
Msasxpress.dll9.0.2206.055,07216-Nov-200612:14IA-64
Msgprox.dll2005.90.2206.0542,49616-Nov-200612:14IA-64
Msmdlocal.dll9.0.2206.048,610,08016-Nov-200612:14IA-64
Msmdredir.dll9.0.2206.06,244,12816-Nov-200612:14Not Applicable
Replprov.dll2005.90.2206.01,617,18416-Nov-200612:14IA-64
Replrec.dll2005.90.2206.02,141,47216-Nov-200612:14IA-64
Sqlaccess.dll2005.90.2206.0349,47216-Nov-200612:14x86
Sqlagent90.exe2005.90.2206.01,141,02416-Nov-200612:14IA-64
Sqlservr.exe2005.90.2206.072,259,87216-Nov-200612:14IA-64
Xmlsub.dll2005.90.2206.0590,62416-Nov-200612:14IA-64
Xpstar90.dll2005.90.2206.0951,07216-Nov-200612:14IA-64
Xpstar90.rll2005.90.2206.0152,35216-Nov-200612:14Not Applicable

↑ Back to the top

Workaround

To work around this problem, do not use the context connection in your CLR stored procedure or CLR function. Instead, use a regular connection.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the context connection, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms131053.aspx
For more information about restrictions on regular connections and on context connections, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms131101.aspx
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbautohotfix, kberrmsg, kbhotfixserver, kbfix, kbexpertiseadvanced, kbqfe, kbpubtypekc, kb

↑ Back to the top

Article Info
Article ID : 928083
Revision : 5
Created on : 11/20/2019
Published on : 11/20/2019
Exists online : False
Views : 856