Microsoft KB Archive/941184

= FIX: An application that is included in SQL Server 2005 may stop responding when you specify a network protocol that is not valid in the application =

Article ID: 941184

Article Last Modified on 8/30/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition

-



Bug #: 50001598 (SQL Hotfix)



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.



SYMPTOMS
Consider the following scenario. You use an application that is included in Microsoft SQL Server 2005. In the application, you specify a network protocol that is not valid. In this scenario, the application may stop responding.

For example, you may experience this issue when you use the sqlcmd command prompt utility.

Additionally, if you examine the file that is generated by the Dr. Watson for Windows tool, you may find the following information:

SQLNCLI.DLL!XxMpHeapFree

SQLNCLI.DLL!CImpISOSHost_MPMemObj::Free

SQLNCLI.DLL!SNIOpenSyncEx

SQLNCLI.DLL!CTdsParser::SNIOpenConnection

SQLNCLI.DLL!CTdsParser::GetConnection

SQLNCLI.DLL!CTdsParser::DoConnect

SQLNCLI.DLL!CTdsParser::OpenServerConnection

SQLNCLI.DLL!CDBConnection::Connect

SQLNCLI.DLL!CDataSource::ConnectIt

SQLNCLI.DLL!CImpIDBInitialize::Initialize



CAUSE
This issue occurs because a heap corruption occurs when the application connects to SQL Server.

The application uses SQL Native Client (SQLNCLI) to connect to SQL Server. When you specify a network protocol that is not valid in the application, SQL Native Client ignores the error that is returned from the SQL Server networking interface (SNI). Therefore, the heap corruption occurs.



RESOLUTION
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

