|
|
You're in the
sql server full text search
group:Full Text Indexing Error
sql server full text search:
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 [quoted text, click to view] "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. [quoted text, click to view] "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. > > -- > 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. > > > > > >
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/ [quoted text, click to view] "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... [quoted text, click to view] "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 > 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. > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |