Re: Problem creating full text index

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Stacey--

OK, it appears that the machine's registry has information about a Full-Text
Index that does not exist, or is not supposed to. Therefore, what you need
to do is manually delete the Full-Text Index and then you should be good to
go. The steps for doing this can be found here:
http://blogs.technet.com/exchange/archive/2005/02/23/379032.aspx. The name
of the Full-Text Index to delete appears to be "privD7514C6C". Please
realize that you are in a little different problem then what the original
Blog entry talks about, therefore some of the steps may not apply to your
situation. The important thing is to delete the Registry settings and files
for the Full-Text you want deleted.

If you currently have no Full-Text Indexes created for this Exchange Server
and you see other Full-Text Indexes defined in the registry, then you will
probably want to delete those as well.

--Chris

================================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
================================================================================

"5tac3" <5tac3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B40CF9F5-97EC-49C4-B3D6-A26DFA5F5173@xxxxxxxxxxxxxxxx
Good stuff Chris. After I performed what you suggested I restarted the
Microsoft Search and now I don't receive any errors in the Application log
from the Search Service. However, I still get an error from the Gatherer.
Event Type: Error
Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3028
Date: 5/4/2006
Time: 11:02:24 AM
User: N/A
Computer: 1-SZ-02
Description:
The Gatherer object in project <ExchangeServer_1-SZ-02 privD7514C6C>
cannot
be initialized. Error: 0 - The operation completed successfully.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I followed the link but I get the "We're Sorry..." eluding to the fact
there
isn't an answer to this error code yet, I guess.

When I try to create a full-text index I now receive a different error.

A catalog with the name specified already exists. Choose another name to
create a new catalog.
Facility: MSSearch.Admin.1
ID no: 80041901
Exchange System Manager

What's interesting is that I'm not prompted to change the name of the
catalog only the path while in the wizard.

A catalog with the name specified already exists. Choose another name to
create a new catalog.
Facility: MSSearch.Admin.1
ID no: 80041901
Exchange System Manager

I think we're close to resolving this. I appreciate all your help.

Stacey

"Chris Ahlers [MSFT]" wrote:

Stacey--

Are there any events that get logged when the MSSearch service is stopped
and then started? Is that path that you are specifying when creating the
Full-Text Index in ESM a valid path with valid directory names?

By default, here is the directory structure of where the MSSearch data
files
reside when Exchange is installed. Please validate that these default
data
files and directories are in place.
================================================================================
D:\PROGRAM FILES\EXCHSRVR\EXCHANGESERVER_SODAK1
? ExchangeServer_SODAK1.edb
? MSS.chk
? MSS.log
? res1.log
? res2.log
? tmp.edb
?
????Config
? Gathrprm.Txt
? noise.chs
? noise.cht
? noise.dat
? noise.deu
? noise.eng
? noise.enu
? noise.esn
? noise.fra
? noise.ita
? noise.jpn
? noise.kor
? noise.nld
? noise.sve
? Schema.Txt
? tschs.xml
? tscht.xml
? tsdut.xml
? tseng.xml
? tsenu.xml
? tsfra.xml
? tsger.xml
? tsita.xml
? tsjap.xml
? tskor.xml
? tsneu.xml
? tsschema.xml
? tsspa.xml
? tsswe.xml
?
????GatherLogs
????Projects
================================================================================


The MSSearch binaries reside in a different location. The directory
structure of where the MSSearch binaries reside looks like this:
================================================================================
D:\PROGRAM FILES\COMMON FILES\SYSTEM\MSSEARCH
????Bin
? acatctr.h
? acatctr.ini
? catutil.exe
? dmntst.exe
? dsscntrs.h
? dsscntrs.ini
? enablecheckpoints.vbs
? ftsqlpar.dll
? gsrvctr.h
? gsrvctr.ini
? GthrAdmin.exe
? gthrctr.h
? gthrctr.ini
? gthrlog.vbs
? lcdetect.dat
? lcdetect.dll
? mssadmin.dll
? msscntrs.dll
? mssdmn.exe
? mssdmn.exe.local
? mssearch.exe
? mssearch.inf
? msserror.dll
? mssmmcsi.dll
? mssmsg.dll
? mssmulpi.dll
? mssph.dll
? mssrch.dll
? mssrchadm.inf
? msstools.dll
? mssws.dll
? nlhtml.dll
? nlindctr.h
? nlindctr.ini
? objcreat.dll
? offfilt.dll
? propdefs.dll
? pstoreutl.exe
? qt.exe
? query.dll
? SearchStp.exe
? SetTempPath.vbs
? simplepi.dll
? simplepi.pdb
? srchadm.dll
? srchadm.msc
? SrchAdmStp.exe
? srchidx.dll
? srchqt.dll
? sssadmin.vbs
? ST6UNST.LOG
? TControl.exe
? tquery.dll
?
????Common
? mssitlb.dll
?
????Config
????Data
????Applications
????Config
gathrprm.txt
noise.chs
noise.cht
noise.dat
noise.deu
noise.eng
noise.enu
noise.esn
noise.fra
noise.ita
noise.jpn
noise.kor
noise.nld
noise.sve
schema.txt
SearchColumns.txt
tschs.xml
tscht.xml
tsdut.xml
tseng.xml
tsenu.xml
tsfra.xml
tsger.xml
tsita.xml
tsjap.xml
tskor.xml
tsneu.xml
tsschema.xml
tsspa.xml
tsswe.xml
================================================================================

If the binaries and data files are in place, then the next thing you
should
do is validate (verify that they exist) the file paths stored in the
registry for MSSearch. The MSSearch registry settings are all stored
under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0

The interesting thing about the error that you are seeing is that it is
complaining about a Directory Name being invalid, not that the path does
not
exist. So when you are checking the paths, make sure you are checking to
make sure that the directory names appear to be valid as well.

--Chris

================================================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
================================================================================

"5tac3" <5tac3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5B6B630A-6B94-4C92-9C1C-208E28213882@xxxxxxxxxxxxxxxx
Thanks Chris for the reply. When I try to create the full-text index,
I
get
the error. Then I check the Application log and don't find any
MSSearch
events. Any other ideas?
Stacey

"Chris Ahlers [MSFT]" wrote:

Do you see any MSSearch events in the Application Log when you try to
create
the Full-Text Index?

--Chris

================================================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included script samples are subject to the terms specified
at
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
================================================================================

"5tac3" <5tac3@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9828218-24C9-49BE-9454-BC2376E9C629@xxxxxxxxxxxxxxxx
I've followed the following KB: 822932


"5tac3" wrote:

I'm unable to create a full text index of my private store.

When I try to creat the index I get the error:

The directory name is invalid.
Facility: MSSearch.Admin.1
ID no: 80041901
Exchange system Manager

Not sure where to even start.
Stacey


.

Relevant Pages

  • Re: Problem creating full text index
    ... Please do not send e-mail directly to this alias. ... A catalog with the name specified already exists. ... Exchange System Manager ... Are there any events that get logged when the MSSearch service is stopped ...
    (microsoft.public.exchange.admin)
  • Re: Problem creating full text index
    ... A catalog with the name specified already exists. ... Is that path that you are specifying when creating the ... here is the directory structure of where the MSSearch data files ... Please do not send e-mail directly to this alias. ...
    (microsoft.public.exchange.admin)
  • Re: registry cleaner
    ... "Alias" wrote in message ... It booted up quicker and had better performance BEFORE the defrag, right after cleaning up the registry. ... registry entries and defragmenting 4,000 files. ... you can't do it yourself because System Suite 5 is no ...
    (microsoft.public.windowsxp.general)
  • Re: Full text index question
    ... you shut down the MSSearch in Cluster Admin, the registry entries disappear. ... There are only the default index files. ...
    (microsoft.public.exchange.admin)
  • Re: Writing data out before the system dies
    ... note that if a bugcheck occurs after your work, there is no guarantee it is ... Please do not send e-mail directly to this alias. ... registry access) can still occur w/out deadlocks. ... if you are not power pagable ...
    (microsoft.public.development.device.drivers)