Re: Full Text Search
- From: "Todd Klindt [MVP]" <usenet@xxxxxxxxxx>
- Date: Mon, 30 Oct 2006 11:45:34 -0600
First thing, the PDF iFilter isn't written as well as it could be, and it
does cause problems from time to time.
Second the FTS might be rebuilding catalogs. If you let it run for a while,
does it calm down? Are there documents cycling through the FTS temp
directory? Have you checked the status of the FTS catalogs for your
ContentDBs, are they getting updated?
tk
"Jack" <anonymous@xxxxxxxxxxxxx> wrote in message
news:%234m2KkE$GHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
I had a client call the other day that their search stopped working in WSS
(2.0, SQL Server 2k). I checked and I think the Microsoft Search service
was stopped. I started it, and their search started working again.
Now there is a mssdmn.exe process that stays at about 25% cpu usage. I
can restart services and it comes back. They are not activley adding new
documents now.
All of their documents are in pdf format, and I do have the pdf iFilter
installed.
Any suggestions?
.
- Follow-Ups:
- Re: Full Text Search
- From: Jack
- Re: Full Text Search
- References:
- Full Text Search
- From: Jack
- Full Text Search
- Prev by Date: Re: Server rejects large file from one user, accepts from another...
- Next by Date: Data View Web Part
- Previous by thread: Full Text Search
- Next by thread: Re: Full Text Search
- Index(es):
Relevant Pages
|