Help and Support

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

View products that this article applies to.
Article ID:281185
Last Review:March 14, 2006
Revision:4.0
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 '<Providername>' could not set range for table '[<LinkedServerName>]..[<SchemaName>].[<TableName>]' because of column '<ColumnName>'.Could not convert the data value due to reasons other than sign mismatch or overflow.

Back to the top

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.

Back to the top

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 (http://support.microsoft.com/kb/290211/EN-US/) 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 (http://support.microsoft.com/kb/274799/EN-US/) INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

Back to the top

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 (http://support.microsoft.com/kb/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.

Back to the top

APPLIES TO
•Microsoft SQL Server 2000 Standard Edition
•Microsoft SQL Server 7.0 Standard Edition

Back to the top

Keywords: 
kbbug kbfix kbqfe kbsqlserv2000sp1fix KB281185

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Contact Microsoft
    Phone Numbers, Support Options and Pricing, Online Help, and more.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.