XADM: "Full-Text Indexing Must Be Enabled to Use the CONTAINS() Clause in a Query" Error Message When You Search the Information Store (823854)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

SYMPTOMS

When you use a complex Web Distributed Authoring and Versioning (WebDAV) query to search the Microsoft Exchange 2000 Server information store, you may receive the following error message:
Error: 80550050: Full-Text Indexing must be enabled to use the CONTAINS() clause in a query.

CAUSE

This problem may occur if the following conditions are true:
  • The hotfix that is documented in the following article in the Microsoft Knowledge Base is installed on your computer:

    815296 XADM: Size of the Information Store Unexpectedly Increases When You Perform a Deep Traversal Query of a Non-MAPI Public Folder

  • The query is too complex to be processed by the Query Optimizer of the ExOleDb.

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 Exchange 2000 Server 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: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.
Component: Exchange OLE DB provider

The English version of this hotfix has the file attributes (or later) 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.

Date         Time   Version            Size    File name
--------------------------------------------------------
25-Jul-2003  00:26  6.0.6490.0    3,915,776    Cdoex.dll        
25-Jul-2003  00:20  6.0.6490.0      851,968    Davex.dll        
25-Jul-2003  00:20  6.0.6490.0     53,248    Davexpc.dll      
25-Jul-2003  00:18  6.0.6490.0  577,536     Dsaccess.dll     
24-Jul-2003  23:36  6.0.6490.0     184,320    Dscmsg.dll       
24-Jul-2003  23:35  6.0.6490.0   958,464    Emsmdb32.dll     
25-Jul-2003  00:26  6.0.6490.0    3,575,808    Excdo.dll        
25-Jul-2003  00:18  6.0.6490.0     258,048    Exmime.dll       
25-Jul-2003  00:20  6.0.6490.0   143,360    Exodbesh.dll     
25-Jul-2003  00:20  6.0.6490.0     57,344    Exodbpc.dll      
25-Jul-2003  00:20  6.0.6490.0   200,704    Exodbprx.dll     
25-Jul-2003  00:20  6.0.6490.0  2,174,976    Exoledb.dll      
25-Jul-2003  00:15  6.0.6490.0      81,920    Exosal.dll       
25-Jul-2003  00:20  6.0.6490.0     307,200    Exprox.dll       
24-Jul-2003  23:37  6.0.6490.0   143,360    Exschema.exe     
24-Jul-2003  23:39  6.0.6490.0    675,840    Exwform.dll      
24-Jul-2003  23:28  6.0.6490.0    49,152    Mdbevent.dll     
24-Jul-2003  23:33  6.0.6490.0   2,285,568    Mdbmsg.dll       
24-Jul-2003  23:29  6.0.6490.0     32,768    Mdbrole.dll      
25-Jul-2003  00:18  6.0.6490.0     24,576    Mdbtask.dll      
25-Jul-2003  00:17  6.0.6490.0    4,657,152    Store.exe    

Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/3/2005
Keywords:kbHotfixServer kbQFE kbQFE kbfix kbExchange2000preSP4fix kbbug KB823854 kbAudITPRO