FIX: You may receive the "Server: Msg 7399, Level 16, State 1, Line 1" error message when you run a query against a remote view through a linked server in SQL Server 2000 (890759)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft Data Access Components 2.8
  • Microsoft Data Access Components 2.8 Service Pack 1 (SP1)

SYMPTOMS

In Microsoft SQL Server 2000, you run a query against a local view that is referencing a remote view through a Microsoft OLE DB Provider for SQL Server linked server. When this query returns a text field, an ntext field, or an image field, the query may fail. You may receive an error message that is similar to the following error message:
Server: Msg 7399, Level 16, State 1, Line 1 OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Protocol error in TDS stream]
[OLE/DB provider returned message: Protocol error in TDS stream]
[OLE/DB provider returned message: Protocol error in TDS stream]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetNextRows returned 0x80004005: ].

CAUSE

This problem occurs because the Microsoft OLE DB Provider for SQL Server becomes out of sync when it fetches a non-text-pointer column as a text-pointer-only column. When this behavior occurs, the Microsoft OLE DB Provider for SQL Server displays the following error message:
Protocol error in TDS stream

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Data Access Components service pack that contains this hotfix.

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

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 Microsoft Data Access Components 2.8 installed on your computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.For Microsoft Data Access Components 2.8
   Date         Time   Version         Size     File name
   ---------------------------------------------------------
   10-Dec-2004  19:09  2000.85.1057.0   73,728  Dbnetlib.dll     
   10-Dec-2004  19:10  2000.85.1057.0   28,672  Dbnmpntw.dll     
   10-Dec-2004  19:09  2.80.1057.0     315,392  Msadce.dll       
   10-Dec-2004  19:09  2.80.1057.0     135,168  Msadco.dll       
   10-Dec-2004  19:09  2.80.1057.0      49,152  Msadcs.dll       
   10-Dec-2004  19:09  2.80.1057.0     147,456  Msadds.dll       
   10-Dec-2004  19:09  2.80.1057.0     507,904  Msado15.dll      
   10-Dec-2004  19:10  2.80.1057.0     163,840  Msadomd.dll      
   10-Dec-2004  19:10  2.80.1057.0     184,320  Msadox.dll       
   10-Dec-2004  19:09  2.80.1057.0      53,248  Msadrh15.dll     
   10-Dec-2004  19:10  2.80.1057.0     225,280  Msdaora.dll      
   10-Dec-2004  19:09  2.80.1057.0     192,512  Msdaprst.dll     
   10-Dec-2004  19:09  2.80.1057.0     147,456  Msdart.dll       
   10-Dec-2004  19:09  2.80.1057.0     303,104  Msdasql.dll      
   10-Dec-2004  19:10  2.575.1057.0    139,264  Msorcl32.dll     
   10-Dec-2004  19:09  3.525.1057.0    221,184  Odbc32.dll       
   10-Dec-2004  19:10  2000.85.1057.0   24,576  Odbcbcp.dll      
   10-Dec-2004  19:09  2.80.1057.0     442,368  Oledb32.dll      
   10-Dec-2004  19:09  2000.85.1057.0  503,808  Sqloledb.dll     
   10-Dec-2004  19:09  2000.85.1057.0  401,408  Sqlsrv32.dll     
   10-Dec-2004  18:57  2000.85.1057.0  208,896  Sqlxmlx.dll
For Microsoft Data Access Components 2.8 Service Pack 1
   Date         Time   Version         Size     File name
   ---------------------------------------------------------
   01-Nov-2005  02:34  2000.85.1119.0  520,192  Sqloledb.dll

WORKAROUND

To work around this problem, you can use the Microsoft OLE DB Provider for Open Database Connectivity (ODBC) and the SQL Server ODBC driver instead of using the Microsoft OLE DB Provider for SQL Server.

STATUS

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

MORE INFORMATION

For more information, 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

Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbfix kbbug kbHotfixServer kbQFE KB890759 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.