 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Full-Text Search / September 2005SqlServer 2000, MSSearch and Fulltext search problems
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  SignatureSQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ > Hello. > I hope someone can help me with this one. [quoted text clipped - 25 lines] > 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 > Tim, > I've worked with SQL FTS since it was first incorporated in SQL 7.0 Beta3 [quoted text clipped - 42 lines] >> 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 SignatureSQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ > 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 [quoted text clipped - 64 lines] >>> Regards >>> Tim |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.