Article ID: 910414 - Last Review: July 26, 2006 - Revision: 2.7 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
Bug #: 412358 (SQLBUDT) Bug #: 406946 (SQLBUDT) On This PageSUMMARYThis article
describes the following about this hotfix release:
SYMPTOMSConsider the following scenario. In Microsoft SQL Server 2005, you try to use common language runtime (CLR) functions to load data. You do this by running a Transact-SQL job. This Transact-SQL job is started by SQL Server Agent. In this scenario, the job fails, and you receive the following error message: Error 563. ETL
Load: Error Number 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. 54 DateTime spid1s
AppDomain 2 (framework.dbo[runtime].1) doomed due to memory pressure.
DateTime spid1s AppDomain 2 (framework.dbo[runtime].1) unloaded. DateTime Logon Error: 17830, Severity: 20, State: 2. DateTime Logon A network error occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 26 ms, enqueued 1 ms, network writes 1 ms, network reads 25 ms, establishing SSL 25 ms, negotiating SSPI 0 ms, validating login 0 ms. [CLIENT: 10.218.40.134] DateTime spid83 AppDomain 3 (framework.dbo[runtime].2) created. CAUSEThis problem
occurs because CLR parallel threads are incorrectly shut down when you run
parallel queries. Typically, this problem occurs when the following conditions
are true:
RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
Hotfix informationA 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
(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.PrerequisitesYou must have SQL Server 2005 installed to apply this hotfix.Restart informationYou do not have to restart the computer after you apply this hotfix.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain 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 tool in Control Panel. SQL Server 2005, 32-bit versionsCollapse this table
SQL Server 2005, 64-bit versionCollapse this table
SQL Server 2005, IA 64-bit versionCollapse this table
STATUSMicrosoft has confirmed that this is a
bug in the Microsoft products that are listed in the "Applies to"
section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1. MORE INFORMATION
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
(http://support.microsoft.com/kb/822499/
)
New
naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when Microsoft corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
