SQL Server Blogs

Voices from the UK SQL Server Community

Rob's SQL Server Blog

... SQL Server thoughts from the field

SQL Server 2000 Full-Text Issues After Failover

I can't take credit for finding the solution to this as that goes to my colleague, but I thought I'd share a problem we experienced after failing over one of our production clusters last night. This is a SQL Server 2000 SP4 Enterprise Edition active/passive cluster running on Windows 2000 Advanced Server SP4. After failover the full-text functionality failed and we were unable to rebuild the catalogs or indexes as SQL Server was returning various errors. The path to the full text catalogs was OK as were all the permissions. The full-text service was reporting as online in the Cluster Administrator and the MS Search service was running on the server. The SQL Agent jobs set up to populate the full-text catalogs were failing with the following errors:

Execution of a full-text operation failed. The Gatherer project has not been initialized. The catalog needs to be remounted. If the project is still not initialized, remove it. [SQLSTATE 42000] (Error 7619).  The step failed.

After some head scratching and googling, which didn't bring up anything conclusive, my colleague found the fix in this article:

The registry keys that contained the location of the word noise files were available on one node of the cluster and not the other, as these keys are only created on the primary node from which the SQL Server setup program was run. The problem was fixed by importing the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\LanguageResources\Override from the other cluster node, setting the Full-Text  Service offline in the cluster Administrator, restarting the MS Search service and then setting the Full-Text service back online.



simonsabin said:

I had to do the hunt as well :). Slightly different behaviour but the same issue.

March 12, 2008 6:21 PM
Powered by Community Server (Commercial Edition), by Telligent Systems