Has anyone seen this recent KB regarding SQL Full Text indexingconsuming the CPU capacity?http://support.microsoft.com/kb/900390I'm very interested if this could also be part of our problems withSharepoint indexing even though it is not listed as one ofthe 'applies to' products.We are experiencing the same issue on one of our indexing serversand it creates a msssdmn.log file every 2 mins even though it isempty. We cannot seem to complete an incremental crawl on a portalindex with only 2900 docs/6MG. The gather log is full of this error:The address could not be found, (0x80040D7B - Document filteringcannot be completed because the document server did not respondwithin the specified timeout. Try crawling the server later, orincrease the timeout values.Had a case opened with MS who said we had to have Win2003 SP1installed. Changing the resource allocation to dedicated seem toeliminate the problem for a while. But alas.....
yes i have sustained 20% cpu usage divided between sqlsrvr.exe and mssearch.exe - and thats on a default portal build with NOTHING.my variables (that i can see) are that we use MOM2005 and that sql and sharepoint are running on the same box. this is our staging environment.i have found nothing that has answered my question. im running SP4 on all my sql boxes.
SharePoint Portal server doesn’t use SQL Full Text indexing. Probably not the same issue.The error you’ve indicated sort of looks like a backwards compatible document library issue… Do you have one setup?
Right, but does Portal Server indexing use the same Office filtersreferenced in the KB?
Yes, Full Text and SharePoint use the same IFilters. However, the package doesn’t appear to include the Office IFILTER. It looks like it’s only SQL components that were fixed … so I don’t believe it would have any impact.