Microsoft KB Archive/187278

= FIX: Large Query Text from Socket Client May Cause Open Data Services Access Violation =

Article ID: 187278

Article Last Modified on 10/7/2005

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q187278



BUG #: 17988 (SQLBUG_65)



SYMPTOMS
Sending large SQL query text from TCP/IP socket network library clients may result in an access violation (AV) with Open Data Services (ODS) Opends60.dll.

Open Data Services is designed to shut down upon encountering an access violation. Therefore, when this problem occurs, the ODS application (such as SQL Server) will also be stopped.

With SQL Server, the ERRORLOG file will contain output that looks similar to the following:

  8/05/02 01:19:03.93 spid180 ******************************************************  8/05/02 01:19:03.96 spid180  * 8/05/02 01:19:03.98 spid180 * STACK DUMP: 8/05/02 01:19:03.98 spid180 * 8/05/02 01:19:04.00 spid180 *   Exception Address = 78787878 8/05/02 01:19:04.01 spid180 *   Exception Code    = c0000005 8/05/02 01:19:04.03 spid180 *   Access Violation occurred reading address 78787878

You may also see other errors within Open Data Services, such as the following:

  98/05/03 13:50:48.26 ods      Error : 17805, Severity: 18, State: 0 98/05/03 13:50:48.26 ods     Invalid buffer received from client.

98/05/03 13:56:44.57 ods     Error : 17824, Severity: 10, State: 0 98/05/03 13:56:44.57 ods     Unable to write to ListenOn connection '1433', loginname 'sa', hostname ''. 98/05/03 13:56:44.57 ods     OS Error : 6, The handle is invalid. 98/05/03 13:56:44.59 ods     Error : 17825, Severity: 17, State: 0 98/05/03 13:56:44.59 ods     Unable to close ListenOn connection. 98/05/03 13:56:44.59 ods     OS Error : 10038,

98/02/02 13:50:31.31 ods     Error : 17803, Severity: 17, State: 0 98/02/02 13:50:31.31 ods     Insufficient memory available.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

  Version    File name      Platform 6.50.422  Opends60.dll   i386 and Alpha 6.50.422  Sqlservr.exe   i386 and Alpha



WORKAROUND
To work around this problem, configure clients to use a different network library than sockets, such as named pipes.



STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5.



MORE INFORMATION
This problem is specific to the use of sockets Net-Library clients. This problem is within the Opends60.dll component, and therefore may be encountered by any Open Data Services application that receives large language event buffers.

Additional query words: dbmssocn ssmsso60 net-lib netlib error log

Keywords: kbbug kbfix kbqfe KB187278

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.