|
|
You're in the
sql server full text search
group:SqlServer 2000, MSSearch and Fulltext search problems
sql server full text search:
Hello.
I hope someone can help me with this one. We have an SqlServer2000 database SP3, running on Win2003 server. On of the tables in one of the databases we use the fulltext search, and we have set up schedules jobs, one doing a incremental population on the catalog every hour from 07.00 to 19.00, and one doing a full text indexing on the table once a week. The dbserver is also rebooted once a week. What happens from time to time is that when we use the ASP.NET application and searching the table using a "CONTAINS", then we get an error message saying that indexing is not setup on the server, or some other error message. When we try to do an incremental population or rebuild the catalog from SQLServer Enterprise Manager, we get an error message saying that the operation can't be executed. When we try to restart the MSSearch service, the server goes into BlueScreen(!). The eventlog states sometimes that the catalog index is corrupt. What can be done here? I have tried to search msdn but I have found no help there. If you can help, or have suggestions what to do, it would be great. Regards Tim
Tim,
I've worked with SQL FTS since it was first incorporated in SQL 7.0 Beta3 in 1998 and I've never heard of the MSSearch service blue-screening NT4, Win2K or Win2003... Something, seriously wrong here... Can you ensure that all past changes to the MSSQLServer startup account & password have been done via the Enterprise Manager and not the Component Applet? Additionally, can you confirm that the MSSearch services is started and running under the System Account (LocalSystem)? If not, reset the MSSearch service to the System Account (LocalSystem) and then stop & restart that service. Finally, review your server's Application event log for any "Microsoft Search" or MssCi source event warnings or errors, especially check all MssCi source events (including informational) as there may be possible FT Catalog corruption that may be the cause of this issue. Thanks, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Tim Skau" <noreply@nowhere.com> wrote in message news:%23SGxYRtvFHA.460@TK2MSFTNGP15.phx.gbl... > Hello. > I hope someone can help me with this one. > > We have an SqlServer2000 database SP3, running on Win2003 server. > On of the tables in one of the databases we use the fulltext search, and > we have set up schedules jobs, one doing a incremental population on the > catalog every hour from 07.00 to 19.00, and one doing a full text indexing > on the table once a week. > > The dbserver is also rebooted once a week. > > What happens from time to time is that when we use the ASP.NET application > and searching the table using a "CONTAINS", then we get an error message > saying that indexing is not setup on the server, or some other error > message. > > When we try to do an incremental population or rebuild the catalog from > SQLServer Enterprise Manager, we get an error message saying that the > operation can't be executed. When we try to restart the MSSearch service, > the server goes into BlueScreen(!). > > The eventlog states sometimes that the catalog index is corrupt. > > What can be done here? I have tried to search msdn but I have found no > help there. > If you can help, or have suggestions what to do, it would be great. > > Regards > Tim > >
Thank you for your reply, and yes I know something is seriously wrong. :-)
I have worked with SqlServer 2000 for 3 years now, and I have nexer experienced this. I forgot to mention that we run Win2003 under a VMWare server, but I can't see that it should the cause of the problem. (?) One possibility, as you mention, could be that catalog corruption is the cause of this issue. Any suggestions how we can avoid that or repair the corrupted catalog? As I mentioned, whenever we try to restart the mssearch, either from the Services panel or from the SqlServer Services Manager, the server goes into blue screen - approx 80% of the times we do it. As far as I know, all changes has been done via the Ent. Man, and the MSSearch service is running under "Local System Account", which is, as far as I know, the default setting after the installation. This has not been changed. Regards Tim "John Kane" <jt-kane@comcast.net> skrev i melding news:u6vw6CyvFHA.3588@tk2msftngp13.phx.gbl... [quoted text, click to view] > Tim, > I've worked with SQL FTS since it was first incorporated in SQL 7.0 Beta3 > in 1998 and I've never heard of the MSSearch service blue-screening NT4, > Win2K or Win2003... Something, seriously wrong here... Can you ensure that > all past changes to the MSSQLServer startup account & password have been > done via the Enterprise Manager and not the Component Applet? > > Additionally, can you confirm that the MSSearch services is started and > running under the System Account (LocalSystem)? If not, reset the MSSearch > service to the System Account (LocalSystem) and then stop & restart that > service. Finally, review your server's Application event log for any > "Microsoft Search" or MssCi source event warnings or errors, especially > check all MssCi source events (including informational) as there may be > possible FT Catalog corruption that may be the cause of this issue. > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > "Tim Skau" <noreply@nowhere.com> wrote in message > news:%23SGxYRtvFHA.460@TK2MSFTNGP15.phx.gbl... >> Hello. >> I hope someone can help me with this one. >> >> We have an SqlServer2000 database SP3, running on Win2003 server. >> On of the tables in one of the databases we use the fulltext search, and >> we have set up schedules jobs, one doing a incremental population on the >> catalog every hour from 07.00 to 19.00, and one doing a full text >> indexing on the table once a week. >> >> The dbserver is also rebooted once a week. >> >> What happens from time to time is that when we use the ASP.NET >> application and searching the table using a "CONTAINS", then we get an >> error message saying that indexing is not setup on the server, or some >> other error message. >> >> When we try to do an incremental population or rebuild the catalog from >> SQLServer Enterprise Manager, we get an error message saying that the >> operation can't be executed. When we try to restart the MSSearch service, >> the server goes into BlueScreen(!). >> >> The eventlog states sometimes that the catalog index is corrupt. >> >> What can be done here? I have tried to search msdn but I have found no >> help there. >> If you can help, or have suggestions what to do, it would be great. >> >> Regards >> Tim >> >> > >
You're welcome, Tim,
Yea, VMWare might be an issue here... While I believe SQL Server can run successfully under this software, I'm not as sure about the "Microsoft Search" service. The MSSearch service is a windows-specific utility and due to the fact that the FT Catalogs files are stored and maintained outside of SQL Server, there may disk-level I/O issues. Note, I know that SQL Server is fully supported by Microsoft under Virtual Server 2005, I suspect that this configuration may only be supported by VMWare. You might want to open a support issue with VMWare to confirm this. Did you see specific corruption errors in your server's application event log? If so, (and its a big if) the FT Catalog corruption can be workaround via dropping and re-creating the FT Catalog and run a Full Population, but this may not prevent the problem from re-occurring... Hope that helps! John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Tim Skau" <noreply@nowhere.com> wrote in message news:O2bwgA0vFHA.904@tk2msftngp13.phx.gbl... > Thank you for your reply, and yes I know something is seriously wrong. :-) > I have worked with SqlServer 2000 for 3 years now, and I have nexer > experienced this. > I forgot to mention that we run Win2003 under a VMWare server, but I can't > see that it should the cause of the problem. (?) > > One possibility, as you mention, could be that catalog corruption is the > cause of this issue. > Any suggestions how we can avoid that or repair the corrupted catalog? As > I mentioned, whenever we try to restart the mssearch, either from the > Services panel or from the SqlServer Services Manager, the server goes > into blue screen - approx 80% of the times we do it. > > As far as I know, all changes has been done via the Ent. Man, and the > MSSearch service is running under "Local System Account", which is, as far > as I know, the default setting after the installation. This has not been > changed. > > Regards > Tim > > "John Kane" <jt-kane@comcast.net> skrev i melding > news:u6vw6CyvFHA.3588@tk2msftngp13.phx.gbl... >> Tim, >> I've worked with SQL FTS since it was first incorporated in SQL 7.0 Beta3 >> in 1998 and I've never heard of the MSSearch service blue-screening NT4, >> Win2K or Win2003... Something, seriously wrong here... Can you ensure >> that all past changes to the MSSQLServer startup account & password have >> been done via the Enterprise Manager and not the Component Applet? >> >> Additionally, can you confirm that the MSSearch services is started and >> running under the System Account (LocalSystem)? If not, reset the >> MSSearch service to the System Account (LocalSystem) and then stop & >> restart that service. Finally, review your server's Application event log >> for any "Microsoft Search" or MssCi source event warnings or errors, >> especially check all MssCi source events (including informational) as >> there may be possible FT Catalog corruption that may be the cause of this >> issue. >> >> Thanks, >> John >> -- >> SQL Full Text Search Blog >> http://spaces.msn.com/members/jtkane/ >> >> >> "Tim Skau" <noreply@nowhere.com> wrote in message >> news:%23SGxYRtvFHA.460@TK2MSFTNGP15.phx.gbl... >>> Hello. >>> I hope someone can help me with this one. >>> >>> We have an SqlServer2000 database SP3, running on Win2003 server. >>> On of the tables in one of the databases we use the fulltext search, and >>> we have set up schedules jobs, one doing a incremental population on the >>> catalog every hour from 07.00 to 19.00, and one doing a full text >>> indexing on the table once a week. >>> >>> The dbserver is also rebooted once a week. >>> >>> What happens from time to time is that when we use the ASP.NET >>> application and searching the table using a "CONTAINS", then we get an >>> error message saying that indexing is not setup on the server, or some >>> other error message. >>> >>> When we try to do an incremental population or rebuild the catalog from >>> SQLServer Enterprise Manager, we get an error message saying that the >>> operation can't be executed. When we try to restart the MSSearch >>> service, the server goes into BlueScreen(!). >>> >>> The eventlog states sometimes that the catalog index is corrupt. >>> >>> What can be done here? I have tried to search msdn but I have found no >>> help there. >>> If you can help, or have suggestions what to do, it would be great. >>> >>> Regards >>> Tim >>> >>> >> >> > >
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 |