Re: Help I cannot get the customizing of Full-Text Indexing To work

From: Tom Rizzo [MSFT] (thomriz_at_microsoft.com)
Date: 03/28/04

  • Next message: strout: "Access Denied Error"
    Date: Sun, 28 Mar 2004 08:35:17 -0800
    
    

    You may want to drop the leading 0 in your proptag so 0x0003212 becomes
    x00003212 as an example.

    Also, if you're using contact properties, they are in a different
    propertyset than PS_PUBLIC_STRINGS so you would need to specify the entire
    propertyset and propid, not just the propid.

    Tom

    --
    Looking for a good book on programming Exchange, Outlook, ADSI and
    SharePoint?  Check out http://www.microsoft.com/MSPress/books/5517.asp
    This posting is provided "AS IS" with no warranties, and confers no rights.
    "Forrest Dickinson" <fdickinson@morganhunter.com> wrote in message
    news:70d8fd3d.0403241835.1c9a78e1@posting.google.com...
    > I have posted questions on this on here about a year ago to no avail.
    > I have found several other post where people had the same problem and
    > no one got a resolution.  However, as an optimist, I hope one of the
    > MVPs on here knows how to do this, or at the very least knows whether
    > or not its a bug and even though Microsoft says you can do it, it cant
    > be done.
    >
    > That said, I am running Exchange 2000 SP3 on Windows 2000 SP4 with
    > Outlook XP as
    > the client.  We have a public contacts folder with about 21,000 items
    > in it.  Searches on it by the company or the name fields can take as
    > much as 30 seconds so I figured I would enable full text indexing on
    > the public store.  Doing so had no effect on search times for contact
    > items and after searching Microsoft I found out that Full Text
    > Indexing on Exchange 2000 by default only indexes common fields in
    > mail items like Subject, Body and attachments.  I found a knowledge
    > base article though detailing how to customize what fields are indexed
    > when full text indexing is ran.
    >
    > The following is an excerpt from the article:
    >
    > Customizing Full-Text Indexing
    > You can add properties to participate in full-text indexing and add or
    > remove noise words that are excluded in a search.
    > Adding Properties
    > If you are familiar with adding keys to the Microsoft Windows
    > registry, you can set up other properties to be full-text indexed in
    > addition to the httpmail namespace properties listed in Full-Text
    > Indexing. You create a text file of properties that are referred to in
    > the registry by the following key:
    >
    HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTe
    xtFilePathName
    >
    > To add properties for full-text indexing:
    > Create a text file of a list of properties that you want to be
    > full-text indexed. The full name for each property must on a separate
    > line. As described here, the form of the name to be used depends on
    > the type of property.
    > For properties created by ADO, OLEDB, or WebDAV, use the property
    > name.
    > For MAPI-named properties (such as those created by using Microsoft
    > Outlook forms), use the following format comprised of the property set
    > GUID (such as PS_MAPI, PS_PUBLIC_STRINGS, or a user-defined value),
    > and the property name:
    > http://schemas.microsoft.com/mapi/string/{propset GUID}/property-name
    >
    > For example, for a property named myproperty in the PS_MAPI property
    > set, use:
    >
    http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-0000000000
    46}/myproperty
    >
    > For standard MAPI properties, the format to use is:
    > http://schemas.microsoft.com/mapi/proptag/value
    >
    > For example, for the PR_DISPLAY_NAME property that has a property tag
    > 0x3001001E, use:
    > http://schemas.microsoft.com/mapi/proptag/0x3001001E
    >
    > NOTE: The DAV:href and DAV:displayname properties cannot be full-text
    > indexed.
    > Start Registry Editor by typing regedt32 at a command prompt.
    > Click the HKEY_LOCAL_MACHINE window.
    > Locate the Software\Microsoft\Search\1.0 subkey.
    > If it does not already exist, add a key under 1.0 called
    > ExchangeParameters.
    > Under Exchange Parameters, add a value with the name
    > SchemaTextFilePathName, a data type of REG_SZ, and a string value of
    > the path to the text file of properties, such as
    > "E:\Exchsrvr\Fulltextprops.txt".
    > Quit Registry Editor. The properties will be full-text indexed the
    > next time full-text indexing is run as configured in Exchange System
    > Manager.
    > I did this and created Fulltextprops.txt file with the following
    > contents:
    >
    > http://schemas.microsoft.com/mapi/proptag/0x3A16001E
    > http://schemas.microsoft.com/mapi/proptag/0x3A06001E
    > http://schemas.microsoft.com/mapi/proptag/0x3A44001E
    > http://schemas.microsoft.com/mapi/proptag/0x3A11001E
    >
    > Basically directing Exchange to index the Company and Name fields on
    > contact items.
    >
    > I then deleted the index, recreated it, peformed a full population and
    > made it available for searching in the System Manager.
    >
    > After I did so Advanced Searches on the Company or Full Name fields
    > still took up to 30 seconds to process (like Company contains Acme),
    > but if I do an Advanced Search on the folder using the subject field
    > results are returned instantly (like Subject contains Acme) it seems
    > as though Subject on Contact Items equates to what the item is filed
    > as.  Anyway because searches on the Subject field are so fast the
    > folder must be being indexed, but even though I followed Microsoft's
    > instructions precisely the Company and name fields are apparently
    > still not being indexed.
    >
    > I am at a loss here, what I am doing wrong?
    >
    > Thank you for any assistance you can provide me in advance.
    >
    > Forrest Dickinson
    > System Administrator / Programmer
    > Morgan Hunter Companies
    

  • Next message: strout: "Access Denied Error"