J
John Riddle
Hello Everyone,
I've asked this question twice in the Exchange Admin group with no response
from anyone. I'm really hoping that someone here can help (based on the idea
that you guys use custom properties in Exchange all the time).
I'm REALLY hoping somebody can help me out with this. I've read the KB
Article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;281736 to
the letter (many times). I've tried adding the SchemaTextFilePathName value
with quotes around it and without. I've tried saving it to various locations
and also the default location as outlined in the KB article.
Here's what happens:
If I index a mailbox store with standard configuration (not applying any of
the instructions in the previous KB Article), indexing works fine.
When I apply the instructions as outlined in the KB article and index the
information store (default Public Folders store), it appears to be crawling
the information store (900mb store), however when finished the index size
reverts to 2mb (was up to 4mb at one point in the crawl). After making the
index available for searching by clients and testing a search (any type of
search) no results display. Even results that should display many items
based on standard indexed fields (body of an email or display name of a
contact item). Nothing results. Searching by clients doesn't work at all.
Even standard filters that were previously on various folders now show no
items (such as a filter on a public task folder to only show items that I'm
the owner for) now show nothing in the folder until I remove all filters.
I've tried building a new stand-alone server using Win 2k3
Enterprise/Exchange 2k3 Enterprise and populating a public folder and a
mailbox (mailboxes don't have any custom fields) with sample data from a pst
and still the exact same result. Standard indexes work fine. Once I set a
custom property to be indexed based on the KB Article, searches return no
results at all.
I've tried removing and reinstalling MSSearch as described in KB Article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;295921 and after
this is done, Full-text Indexing is disabled completely and cannot be
enabled at all. This requires that I rebuild the server from scratch,
restore all the data and start over. I've done this several times now in the
last week and cannot figure out how to index custom properties of a Public
Contact Folder. This is very important because we have a custom field called
"resume" (text field, named property, created with Outlook) that holds
resumes of all job applicants. This folder contains more than 10,000 items
and is searched on to find qualified candidates for our organization.
Searches currently take about 10 minutes to complete and I need to get that
down significantly.
Has ANYONE ever gotten a custom property in Exchange 2k3 to index properly?
If so PLEASE tell me how you did it.
Clients use: Outlook 2k3
Server: SBS 2k3 (tried with Win 2k3 Ent/Exchange 2k3 Ent, as well)
Contents of my fulltextprops.txt file as referenced by the above KB article:
http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/resume
Can someone test this on their server with a custom property? I'm really
hoping that this is in fact possible to do.
Thank you very much.
John
I've asked this question twice in the Exchange Admin group with no response
from anyone. I'm really hoping that someone here can help (based on the idea
that you guys use custom properties in Exchange all the time).
I'm REALLY hoping somebody can help me out with this. I've read the KB
Article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;281736 to
the letter (many times). I've tried adding the SchemaTextFilePathName value
with quotes around it and without. I've tried saving it to various locations
and also the default location as outlined in the KB article.
Here's what happens:
If I index a mailbox store with standard configuration (not applying any of
the instructions in the previous KB Article), indexing works fine.
When I apply the instructions as outlined in the KB article and index the
information store (default Public Folders store), it appears to be crawling
the information store (900mb store), however when finished the index size
reverts to 2mb (was up to 4mb at one point in the crawl). After making the
index available for searching by clients and testing a search (any type of
search) no results display. Even results that should display many items
based on standard indexed fields (body of an email or display name of a
contact item). Nothing results. Searching by clients doesn't work at all.
Even standard filters that were previously on various folders now show no
items (such as a filter on a public task folder to only show items that I'm
the owner for) now show nothing in the folder until I remove all filters.
I've tried building a new stand-alone server using Win 2k3
Enterprise/Exchange 2k3 Enterprise and populating a public folder and a
mailbox (mailboxes don't have any custom fields) with sample data from a pst
and still the exact same result. Standard indexes work fine. Once I set a
custom property to be indexed based on the KB Article, searches return no
results at all.
I've tried removing and reinstalling MSSearch as described in KB Article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;295921 and after
this is done, Full-text Indexing is disabled completely and cannot be
enabled at all. This requires that I rebuild the server from scratch,
restore all the data and start over. I've done this several times now in the
last week and cannot figure out how to index custom properties of a Public
Contact Folder. This is very important because we have a custom field called
"resume" (text field, named property, created with Outlook) that holds
resumes of all job applicants. This folder contains more than 10,000 items
and is searched on to find qualified candidates for our organization.
Searches currently take about 10 minutes to complete and I need to get that
down significantly.
Has ANYONE ever gotten a custom property in Exchange 2k3 to index properly?
If so PLEASE tell me how you did it.
Clients use: Outlook 2k3
Server: SBS 2k3 (tried with Win 2k3 Ent/Exchange 2k3 Ent, as well)
Contents of my fulltextprops.txt file as referenced by the above KB article:
http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/resume
Can someone test this on their server with a custom property? I'm really
hoping that this is in fact possible to do.
Thank you very much.
John