Full Text Indexing Error

I see a lot of these in my Event log on the SQL Server for my Windows
Sharepoint Services site.
It would be nice to know what files are not being indexed and why.
Posting in the WSS group got me advice to update to SQL Server SP3 (done at
install) and/or post here.
Event Log Messages:
One or more documents stored in image columns with extension 'xls' did not
get full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
One or more documents stored in image columns with extension '' did not get
full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This normally means your iFilter or related components has/have crashed. Try
to bounce MSSearch to solve this problem.You may need to reboot your server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' did not
> get full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' did not
get
> full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||OK
A little more information...
The server is rebooted weekly
These errors have been cropping up for a while - So far i have had no
reports from users of any problems, but they are not using Sharepoint's
search very extensivly yet.
I hope to change that, but want to have some confidence in the results.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OnhOjEkAFHA.4028@.TK2MSFTNGP15.phx.gbl...
> This normally means your iFilter or related components has/have crashed.
Try
> to bounce MSSearch to solve this problem.You may need to reboot your
server.[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
|||David,
The first event log error indicates that an Excel (*.xls) file did not get
FT Indexed and the 2nd event log error indicates that a file extension of
'' (or NULL) did not get FT Indexed. The former, may occur because of a bad
file, but the latter should not occur, unless you are storing un-known
extensions. You should examine the gather log files (*.gthr) under
\FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
information and post the output of the gthrlog.vbs utility.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' did not
> get full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' did not
get
> full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||John,
Thanks for the quick reply.
I had to switch to my network, security and training hats respectivly but am
now under the Sharepoint hat and have the following result:
1/31/2005 12:55:34 AM Add The gatherer has started
1/31/2005 12:55:36 AM Add The initialization has completed
1/31/2005 8:57:26 AM
MSSQL75://SQLServer/1de57479/CB325AA2334BED409E0F527D35A87A67 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 10:20:06 AM
MSSQL75://SQLServer/1de57479/EBB20D5D67E2EC4F820041532CB288BC Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/76cba758/A86817082BA3E0469D8D07C2D70A8905 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/1de57479/C774194838E91540868BDAF8027CCEC8 Add Error
fetching URL, (80041201 - The object was not found. )
Clear enough, some reference is either expired or corrupt.
In your experience, is this something to be concerned about?
Searches have become much slower than the last time I tried anything, but we
also have 4 or 5 gb more data.
Bt slow, I mean durations of minutes while the SQL Server (dual pentium 4
2.something with 4gb ram) shows 80-95% processor consumed by MSSEARCH.
My users are not making much use of Search in Sharepoint, and at this point
I am holding off on encouraging them
David
btw - Nice pic on your blog - I really need to get out skiing again one of
these years...
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uTVnh0pAFHA.1404@.TK2MSFTNGP11.phx.gbl...
> David,
> The first event log error indicates that an Excel (*.xls) file did not get
> FT Indexed and the 2nd event log error indicates that a file extension of
> '' (or NULL) did not get FT Indexed. The former, may occur because of a
bad[vbcol=seagreen]
> file, but the latter should not occur, unless you are storing un-known
> extensions. You should examine the gather log files (*.gthr) under
> \FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
> information and post the output of the gthrlog.vbs utility.
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>