FIX: A GCHandle leak occurs when you use the .NET Framework data provider for SQL Server to connect to SQL Azure

Article translations Article translations
Article ID: 2645081 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You use the Microsoft .NET Framework data provider for SQL Server to connect to Microsoft SQL Azure.
  • The logon to SQL Azure fails because the response from SQL Azure is slower than usual.

In this scenario, a System.Runtime.InteropServices.GCHandle leak occurs for each failed connection.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have the Microsoft .NET Framework 4 installed.

Restart requirement

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

File information

The global 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.

For all supported x86-based versions

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Setup.dll10.0.30319.537296,71206-Dec-201106:19x86
Setupengine.dll10.0.30319.537810,25606-Dec-201106:19x86
Setupui.exe10.0.30319.53779,11206-Dec-201106:19x86
System.data.dll4.0.30319.5373,019,53606-Dec-201111:32x86


For all supported x64-based versions

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Setup.dll10.0.30319.537296,71206-Dec-201106:19x86
Setupengine.dll10.0.30319.537810,25606-Dec-201106:19x86
Setupui.exe10.0.30319.53779,11206-Dec-201106:19x86
System.data.dll4.0.30319.5373,019,53606-Dec-201111:32x86
System.data.dll4.0.30319.5373,164,43206-Dec-201112:16x64


For all supported IA64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Setup.dll10.0.30319.537296,71206-Dec-201106:19x86
Setupengine.dll10.0.30319.537810,25606-Dec-201106:19x86
Setupui.exe10.0.30319.53779,11206-Dec-201106:19x86
System.data.dll4.0.30319.5373,019,53606-Dec-201111:32x86
System.data.dll4.0.30319.5373,348,75206-Dec-201113:10IA-64

STATUS

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

Properties

Article ID: 2645081 - Last Review: January 30, 2012 - Revision: 2.0
APPLIES TO
  • Microsoft .NET Framework 4
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2645081

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com