Office Custom Property Is Not Searchable

ID: Q197607

The information in this article applies to:

Microsoft Site Server version 3.0

SYMPTOMS

A Microsoft Office custom property is not searchable by default. Attempting to search the field results in an empty query result.

CAUSE

The schema does not contain proper information to process the custom property.

RESOLUTION

The following steps will allow you to make the custom property called "phrase2" searchable:

1. Open Site Server Dir\Data\Search\Config\DefineColumns.txt. 2. Add the following to DefineColumns.txt:

      # Custom Property for MSOffice document
      # custom_int (DBTYPE_I4) = d5cdd505-2e9c-101b-9397-08002b2cf9ae
      custom_int
      phrase2 (DBTYPE_STR | DBTYPE_BYREF) = d5cdd505-2e9c-101b-9397-
      08002b2cf9ae
      "phrase2"

3. Go to Schema in the MMC. 4. Add custom property. 5. For Other Property Set, enter "d5cdd505-2e9c-101b-9397-08002b2cf9ae"

   (without the quotation marks).

6. For Property ID, enter "9397" (without the quotation marks). 7. Select String. 8. Select Index, and then select Retrievable. 9. Select Submit. 10. Re-crawl the catalog.

MORE INFORMATION

The custom property is part of the property of the Office documents. For example:

1. Open an Office Word document 2. Select File and choose Property. 3. Click the Custom tab.

The query syntax for the custom property called "phrase2" is:

   @phrase2 "the value of the phrase2"

Bug

Version           : WINNT:3.0
Platform          : winnt
Issue type        : kbprb
Solution Type     : kbpending

Last Reviewed: December 17, 1998