Microsoft KB Archive/281185

= FIX: Linked Index Server Query Through OLE DB Provider with OR Clause Reports Error 7349 =

Article ID: 281185

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q281185



BUG #: 57805 (SHILOH)



SYMPTOMS
If these conditions are true:
 * You have a linked server that uses a provider, which supports the IRowsetIndex interface.
 * A query is run using the four part naming convention.
 * The query contains an OR in the WHERE clause.

This error message occurs:

Server: Msg 7349, Level 16, State 2, Line 1

OLE DB provider '' could not set range for table '[]..[].[]' because of column ''.Could not convert the data value due to reasons other than sign mismatch or overflow.



CAUSE
SQL Server opens two IRowsets on the provider and mistakenly passes the second condition in the WHERE clause to the first condition's IAccessor.



RESOLUTION
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

To resolve this problem, obtain the latest service pack for SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider. Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

Additional query words: 7349

Keywords: kbbug kbfix kbqfe kbsqlserv2000sp1fix KB281185

-

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

© Microsoft Corporation. All rights reserved.