sql server full text search: Alex,
While SQL Server 2000 is fully supported in a clustered environment,
SharePoint Portal Server 2001 is not cluster-aware. See, KB article
"Programs that cannot coexist with SharePoint Portal Server 2001" at
http://support.microsoft.com/default.aspx?scid=kb;en-us;295012&sd=tech
"Note You cannot install Microsoft SharePoint Portal Server 2001 in a
clustered environment." However, SharePoint Portal Server 2003 is supported
in a clustered environment. What version of Sharepoint are you using?

Secondly, have you or anyone else modified the MSSQLServer startup account
&/or password via Win2K's Component services and not via the Enterprise
Manager? See KB article 277549 (Q277549) PRB: Unable to Build Full-Text
Catalog After You Modify MSSQLServer Logon Account Through [NT4.0) Control
Panel [or Win2K Component Services] at
http://support.microsoft.com/default.aspx?scid=KB;EN-US;277549 for details.

Yes, the MSSearch service MUST always be started and running under the
LocalSystem account and it is cluster-aware, as the fail over happens at the
FT Catalog or application level and not at the service level.

I'd recommend that you review your servers Application event log for
specific errors and review the following KB articles:

Q304282 PRB: Full Text Resource Fails to Come Online on a Cluster with
"Event ID 1069 : SQL Cluster Resource 'Full Text' failed" Error Message
http://support.microsoft.com/default.aspx?scid=kb;en-us;304282&sd=tech

812666 How to recover a failed full-text search resource on a clustered
instance of SQL Server 2000
http://support.microsoft.com/default.aspx?kbid=812666

Hope that helps!
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/




[quoted text, click to view]

In Windows Sharepoint, I can't get the catalogs to build either manually or
by using the Sharepoint Central admin console. They have between 1-8 items,
and are never larger than 1 mb, even though the content is > 3 GB!

This is on a SQL 2000 Ent. running on a 2-node A-A cluster; could that be
the problem? Also, the account the MSSEARCH is running as is Local System
which is not that of the MSSQL service? Does that matter?

I take it you mean Windows Sharepoint Services, or Windows Sharepoint Team
Services.

Can you connect to your SQL Server using EM, and then right click on your
SQL Server, select properties, security, and change the start up account for
SQL Server to local system, and then change it back to your local admin
account. This will involve a restart of SQL Server.

Then expand your team services database, expand Full-Text catalogs, and
right click on the catalog which appears there and start a full population.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

[quoted text, click to view]