| Author |
Message |
Massimo
Guest
|
 Posted:
Thu Jan 20, 2005 7:47 pm Post subject:
Public Folders Contacts. |
|
|
Microsoft Exchange 2003 Server Standard Edition
We use our public folders as a costumer base and we have about 15,000
contact.
We noticed that when doing searches by using the conventianal "Find" button
located in the outlook 2003 toolbar, the search would be painfully slow and
the CPU usage on the server would sky rocket for about 2 minutes. After many
months of waiting, we received a solution from Microsoft located below. Now
the conventional way of doing serches works like a charm, conversely we now
encounter an additional problem. The advanced find feature (Which we use for
reporting and mailings) no longer works. If we planned to do an advanced
search by category for example, no contacts are found unless I disable the "
This index is currently available for searching by clients" feature located
in the Exchange Server 2003 System Manager. Please help!
This is the Solution Provided by Microsoft.
1) Save the MSSearch_Extended_Indexed_Properties.txt file to your Exchange
server
2) Add the Registry STRING
"HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTextFilePathName".
3) Modify the value of the Registry STRING created in Step #2 to contain the
full path to the text file created in Step #1. (i.e. C:\
MSSearch_Extended_Indexed_Properties.txt)
4) Stop and restart the MSSearch service
5) A Full Population will now need to take place so that MSSearch reindexes
all existing messages with these additional properties.
6) Make sure that the properties on the MDB object allow MAPI clients to use
the full-text index.
|
|
| Back to top |
|
 |
Mike Lagase
Guest
|
| Posted:
Thu Jan 20, 2005 8:27 pm Post subject:
Re: Public Folders Contacts. |
|
|
What is the contents of the MSSearch_Extended_Indexed_Properties.txt file?
"Massimo" <Massimo@discussions.microsoft.com> wrote in message
news:F75D35A0-DFEC-4C33-B63C-2936DC4D538F@microsoft.com...
| Quote: | Microsoft Exchange 2003 Server Standard Edition
We use our public folders as a costumer base and we have about 15,000
contact.
We noticed that when doing searches by using the conventianal "Find"
button
located in the outlook 2003 toolbar, the search would be painfully slow
and
the CPU usage on the server would sky rocket for about 2 minutes. After
many
months of waiting, we received a solution from Microsoft located below.
Now
the conventional way of doing serches works like a charm, conversely we
now
encounter an additional problem. The advanced find feature (Which we use
for
reporting and mailings) no longer works. If we planned to do an advanced
search by category for example, no contacts are found unless I disable the
"
This index is currently available for searching by clients" feature
located
in the Exchange Server 2003 System Manager. Please help!
This is the Solution Provided by Microsoft.
1) Save the MSSearch_Extended_Indexed_Properties.txt file to your Exchange
server
2) Add the Registry STRING
"HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTextFilePathName".
3) Modify the value of the Registry STRING created in Step #2 to contain
the
full path to the text file created in Step #1. (i.e. C:\
MSSearch_Extended_Indexed_Properties.txt)
4) Stop and restart the MSSearch service
5) A Full Population will now need to take place so that MSSearch
reindexes
all existing messages with these additional properties.
6) Make sure that the properties on the MDB object allow MAPI clients to
use
the full-text index.
|
|
|
| Back to top |
|
|
Massimo
Guest
|
| Posted:
Thu Jan 20, 2005 8:59 pm Post subject:
Re: Public Folders Contacts. |
|
|
Hello Mike and thanks for your interest.
Listed below is the content of that file.
urn:schemas:contacts:account
urn:schemas:contacts:bday
urn:schemas:contacts:billinginformation
urn:schemas:contacts:businesshomepage
urn:schemas:contacts:callbackphone
urn:schemas:contacts:childrensnames
urn:schemas:contacts:cn
urn:schemas:contacts:computernetworkname
urn:schemas:contacts:co
urn:schemas:contacts:customerid
urn:schemas:contacts:c
urn:schemas:contacts:department
urn:schemas:contacts:dn
urn:schemas:contacts:email1
urn:schemas:contacts:email2
urn:schemas:contacts:email3
urn:schemas:contacts:employeenumber
urn:schemas:contacts:facsimiletelephonenumber
urn:schemas:contacts:fileasid
urn:schemas:contacts:fileas
urn:schemas:contacts:ftpsite
urn:schemas:contacts:gender
urn:schemas:contacts:givenName
urn:schemas:contacts:governmentid
urn:schemas:contacts:hobbies
urn:schemas:contacts:homeCity
urn:schemas:contacts:homeCountry
urn:schemas:contacts:homefax
urn:schemas:contacts:homelatitude
urn:schemas:contacts:homelongitude
urn:schemas:contacts:homephone2
urn:schemas:contacts:homePhone
urn:schemas:contacts:homepostaladdress
urn:schemas:contacts:homePostalCode
urn:schemas:contacts:homepostofficebox
urn:schemas:contacts:homeState
urn:schemas:contacts:homeStreet
urn:schemas:contacts:hometimezone
urn:schemas:contacts:initials
urn:schemas:contacts:internationalisdnnumber
urn:schemas:contacts:language
urn:schemas:contacts:location
urn:schemas:contacts:l
urn:schemas:contacts:mailingaddressid
urn:schemas:contacts:mailingcity
urn:schemas:contacts:mailingcountry
urn:schemas:contacts:mailingpostaladdress
urn:schemas:contacts:mailingpostalcode
urn:schemas:contacts:mailingpostofficebox
urn:schemas:contacts:mailingstate
urn:schemas:contacts:mailingstreet
urn:schemas:contacts:manager
urn:schemas:contacts:mapurl
urn:schemas:contacts:middlename
urn:schemas:contacts:mobile
urn:schemas:contacts:namesuffix
urn:schemas:contacts:nickname
urn:schemas:contacts:office2telephonenumber
urn:schemas:contacts:officetelephonenumber
urn:schemas:contacts:organizationmainphone
urn:schemas:contacts:othercity
urn:schemas:contacts:othercountrycode
urn:schemas:contacts:othercountry
urn:schemas:contacts:otherfax
urn:schemas:contacts:othermobile
urn:schemas:contacts:otherpager
urn:schemas:contacts:otherpostaladdress
urn:schemas:contacts:otherpostalcode
urn:schemas:contacts:otherpostofficebox
urn:schemas:contacts:otherstate
urn:schemas:contacts:otherstreet
urn:schemas:contacts:otherTelephone
urn:schemas:contacts:othertimezone
urn:schemas:contacts:o
urn:schemas:contacts:pager
urn:schemas:contacts:personalHomePage
urn:schemas:contacts:personaltitle
urn:schemas:contacts:postalcode
urn:schemas:contacts:postofficebox
urn:schemas:contacts:profession
urn:schemas:contacts:proxyaddresses
urn:schemas:contacts:referredby
urn:schemas:contacts:roomnumber
urn:schemas:contacts:secretarycn
urn:schemas:contacts:secretaryphone
urn:schemas:contacts:secretaryurl
urn:schemas:contacts:sn
urn:schemas:contacts:sourceurl
urn:schemas:contacts:spousecn
urn:schemas:contacts:street
urn:schemas:contacts:st
urn:schemas:contacts:telephonenumber2
urn:schemas:contacts:telephoneNumber
urn:schemas:contacts:telexnumber
urn:schemas:contacts:title
urn:schemas:contacts:ttytddphone
urn:schemas:contacts:weddinganniversary
urn:schemas:contacts:workaddress
http://schemas.microsoft.com/mapi/email1emailaddress
http://schemas.microsoft.com/mapi/email2emailaddress
http://schemas.microsoft.com/mapi/email3emailaddress
http://schemas.microsoft.com/mapi/fileunder
http://schemas.microsoft.com/exchange/keywords
"Mike Lagase" wrote:
| Quote: | What is the contents of the MSSearch_Extended_Indexed_Properties.txt file?
"Massimo" <Massimo@discussions.microsoft.com> wrote in message
news:F75D35A0-DFEC-4C33-B63C-2936DC4D538F@microsoft.com...
Microsoft Exchange 2003 Server Standard Edition
We use our public folders as a costumer base and we have about 15,000
contact.
We noticed that when doing searches by using the conventianal "Find"
button
located in the outlook 2003 toolbar, the search would be painfully slow
and
the CPU usage on the server would sky rocket for about 2 minutes. After
many
months of waiting, we received a solution from Microsoft located below.
Now
the conventional way of doing serches works like a charm, conversely we
now
encounter an additional problem. The advanced find feature (Which we use
for
reporting and mailings) no longer works. If we planned to do an advanced
search by category for example, no contacts are found unless I disable the
"
This index is currently available for searching by clients" feature
located
in the Exchange Server 2003 System Manager. Please help!
This is the Solution Provided by Microsoft.
1) Save the MSSearch_Extended_Indexed_Properties.txt file to your Exchange
server
2) Add the Registry STRING
"HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTextFilePathName".
3) Modify the value of the Registry STRING created in Step #2 to contain
the
full path to the text file created in Step #1. (i.e. C:\
MSSearch_Extended_Indexed_Properties.txt)
4) Stop and restart the MSSearch service
5) A Full Population will now need to take place so that MSSearch
reindexes
all existing messages with these additional properties.
6) Make sure that the properties on the MDB object allow MAPI clients to
use
the full-text index.
|
|
|
| Back to top |
|
|
Mike Lagase
Guest
|
| Posted:
Thu Jan 20, 2005 10:09 pm Post subject:
Re: Public Folders Contacts. |
|
|
It appears that you do not have sub namespaces for your referenced
namespaces. There are 3 sub namespaces that you can use. proptag, id, and
string.
See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_cdo_schema_mapi.asp
for more info and examples on this.
Mike
"Massimo" <Massimo@discussions.microsoft.com> wrote in message
news:4485C3E5-5F6A-4F89-B3B9-0230663DC8D2@microsoft.com...
| Quote: | Hello Mike and thanks for your interest.
Listed below is the content of that file.
urn:schemas:contacts:account
urn:schemas:contacts:bday
urn:schemas:contacts:billinginformation
urn:schemas:contacts:businesshomepage
urn:schemas:contacts:callbackphone
urn:schemas:contacts:childrensnames
urn:schemas:contacts:cn
urn:schemas:contacts:computernetworkname
urn:schemas:contacts:co
urn:schemas:contacts:customerid
urn:schemas:contacts:c
urn:schemas:contacts:department
urn:schemas:contacts:dn
urn:schemas:contacts:email1
urn:schemas:contacts:email2
urn:schemas:contacts:email3
urn:schemas:contacts:employeenumber
urn:schemas:contacts:facsimiletelephonenumber
urn:schemas:contacts:fileasid
urn:schemas:contacts:fileas
urn:schemas:contacts:ftpsite
urn:schemas:contacts:gender
urn:schemas:contacts:givenName
urn:schemas:contacts:governmentid
urn:schemas:contacts:hobbies
urn:schemas:contacts:homeCity
urn:schemas:contacts:homeCountry
urn:schemas:contacts:homefax
urn:schemas:contacts:homelatitude
urn:schemas:contacts:homelongitude
urn:schemas:contacts:homephone2
urn:schemas:contacts:homePhone
urn:schemas:contacts:homepostaladdress
urn:schemas:contacts:homePostalCode
urn:schemas:contacts:homepostofficebox
urn:schemas:contacts:homeState
urn:schemas:contacts:homeStreet
urn:schemas:contacts:hometimezone
urn:schemas:contacts:initials
urn:schemas:contacts:internationalisdnnumber
urn:schemas:contacts:language
urn:schemas:contacts:location
urn:schemas:contacts:l
urn:schemas:contacts:mailingaddressid
urn:schemas:contacts:mailingcity
urn:schemas:contacts:mailingcountry
urn:schemas:contacts:mailingpostaladdress
urn:schemas:contacts:mailingpostalcode
urn:schemas:contacts:mailingpostofficebox
urn:schemas:contacts:mailingstate
urn:schemas:contacts:mailingstreet
urn:schemas:contacts:manager
urn:schemas:contacts:mapurl
urn:schemas:contacts:middlename
urn:schemas:contacts:mobile
urn:schemas:contacts:namesuffix
urn:schemas:contacts:nickname
urn:schemas:contacts:office2telephonenumber
urn:schemas:contacts:officetelephonenumber
urn:schemas:contacts:organizationmainphone
urn:schemas:contacts:othercity
urn:schemas:contacts:othercountrycode
urn:schemas:contacts:othercountry
urn:schemas:contacts:otherfax
urn:schemas:contacts:othermobile
urn:schemas:contacts:otherpager
urn:schemas:contacts:otherpostaladdress
urn:schemas:contacts:otherpostalcode
urn:schemas:contacts:otherpostofficebox
urn:schemas:contacts:otherstate
urn:schemas:contacts:otherstreet
urn:schemas:contacts:otherTelephone
urn:schemas:contacts:othertimezone
urn:schemas:contacts:o
urn:schemas:contacts:pager
urn:schemas:contacts:personalHomePage
urn:schemas:contacts:personaltitle
urn:schemas:contacts:postalcode
urn:schemas:contacts:postofficebox
urn:schemas:contacts:profession
urn:schemas:contacts:proxyaddresses
urn:schemas:contacts:referredby
urn:schemas:contacts:roomnumber
urn:schemas:contacts:secretarycn
urn:schemas:contacts:secretaryphone
urn:schemas:contacts:secretaryurl
urn:schemas:contacts:sn
urn:schemas:contacts:sourceurl
urn:schemas:contacts:spousecn
urn:schemas:contacts:street
urn:schemas:contacts:st
urn:schemas:contacts:telephonenumber2
urn:schemas:contacts:telephoneNumber
urn:schemas:contacts:telexnumber
urn:schemas:contacts:title
urn:schemas:contacts:ttytddphone
urn:schemas:contacts:weddinganniversary
urn:schemas:contacts:workaddress
http://schemas.microsoft.com/mapi/email1emailaddress
http://schemas.microsoft.com/mapi/email2emailaddress
http://schemas.microsoft.com/mapi/email3emailaddress
http://schemas.microsoft.com/mapi/fileunder
http://schemas.microsoft.com/exchange/keywords
"Mike Lagase" wrote:
What is the contents of the MSSearch_Extended_Indexed_Properties.txt
file?
"Massimo" <Massimo@discussions.microsoft.com> wrote in message
news:F75D35A0-DFEC-4C33-B63C-2936DC4D538F@microsoft.com...
Microsoft Exchange 2003 Server Standard Edition
We use our public folders as a costumer base and we have about 15,000
contact.
We noticed that when doing searches by using the conventianal "Find"
button
located in the outlook 2003 toolbar, the search would be painfully slow
and
the CPU usage on the server would sky rocket for about 2 minutes.
After
many
months of waiting, we received a solution from Microsoft located below.
Now
the conventional way of doing serches works like a charm, conversely we
now
encounter an additional problem. The advanced find feature (Which we
use
for
reporting and mailings) no longer works. If we planned to do an
advanced
search by category for example, no contacts are found unless I disable
the
"
This index is currently available for searching by clients" feature
located
in the Exchange Server 2003 System Manager. Please help!
This is the Solution Provided by Microsoft.
1) Save the MSSearch_Extended_Indexed_Properties.txt file to your
Exchange
server
2) Add the Registry STRING
"HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTextFilePathName".
3) Modify the value of the Registry STRING created in Step #2 to
contain
the
full path to the text file created in Step #1. (i.e. C:\
MSSearch_Extended_Indexed_Properties.txt)
4) Stop and restart the MSSearch service
5) A Full Population will now need to take place so that MSSearch
reindexes
all existing messages with these additional properties.
6) Make sure that the properties on the MDB object allow MAPI clients
to
use
the full-text index.
|
|
|
| Back to top |
|
|
Massimo
Guest
|
| Posted:
Thu Jan 20, 2005 11:07 pm Post subject:
Re: Public Folders Contacts. |
|
|
Thanks for all of your help Mike.
Though I must admit that being new to Exchange and windows servers, this
does not make much sense to me. I am still tring to figure out how to obtain
the propset GUID string.
Best regards,
Massimo
"Mike Lagase" wrote:
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in