Full-text index, no documents

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Eric Phetteplace - 23 Jun 2004 19:01 GMT

Hello,

I have a Sharepoint installation and a SQL Server.

Full text indexing is enabled - in Sharepoint and on the SQL Server.

Using enterprise manager, I see the Full-text index, the tables/columns that
will be indexed.

I've rebuilt my full-text catalog and started a full population.

The index catalog rebuilds.

HOWEVER, no documents are ever added into the catalog. It's always at 0
documents, 0MB.

Any suggestions?

Best Regards,

Eric

Reply to this Message

Hilary Cotter - 23 Jun 2004 19:56 GMT

Are we talking WSS (windows Sharepoint services) or SPS (Sharepoint Portal Server)?

Windows Sharepoint Services does use SQL FTS, whereas SPS does not.

There is a problem with some of the iFilters WSS can use which casuses the iFitler to crash. This is normally solved with a reboot.

before you reboot to clear this problem check the gatherlogs or the event log for error messages from MSSCI or MSSearch.

Signature

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

> Hello,
>
[quoted text clipped - 17 lines]
>
> Eric

Reply to this Message

John Kane - 24 Jun 2004 03:33 GMT

Hilary, it still might be appropriate to confirm some of the basic SQL FTS
setting and the most common problem & solution for "...no documents are ever
added into the catalog. It's always at 0 documents, 0MB."

Eric, please review the following KB articles:

277549 (Q277549) "PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through Control Panel"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q277549 and

317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate
Catalogs"
http://support.microsoft.com/default.aspx?scid=KB;en-us;q317746

Regards,
John

> Are we talking WSS (windows Sharepoint services) or SPS (Sharepoint Portal Server)?
>
[quoted text clipped - 25 lines]
> >
> > Eric

Reply to this Message

Eric Phetteplace - 25 Jun 2004 12:52 GMT

Hi John,

I tried that one. The problem is, on the SQL cluster I can choose service
account - it is disabled.

So, I chose another account, restarted services, re-chose the domain account
and restarted services.

I am still getting errors in the log, and this error is not explicitly
referenced in the KB article:

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7037
Description:
The Property Store <d:\MSSQL\FTDATA\SQL000070000\Build\Indexer\NlFiles\>
failed to initialize. Error: 80070005 - Access is denied.

The annoying thing is I opened up the permissions on the path, and then the
search service removed them, providing full access to the SYSTEM account and
Administrators groups. The SQL service's login account is in the
Administrator's group, so this is obviously a misleading error message.

Any ideas?

Eric

> Hilary, it still might be appropriate to confirm some of the basic SQL FTS
> setting and the most common problem & solution for "...no documents are ever
[quoted text clipped - 46 lines]
> > >
> > > Eric

Reply to this Message

Eric Phetteplace - 25 Jun 2004 17:43 GMT

Let me clarify:

On the SQL cluster I can NOT configure the server to run as a Service
account (choice is disabled). SQL is running as a domain account.

If I MUST choose service and then choose the domain account, how do I
accomplish this?

Eric

> Hi John,
>
[quoted text clipped - 80 lines]
> > > >
> > > > Eric

Reply to this Message

John Kane - 02 Jul 2004 15:42 GMT

Eric,
Sorry for the late reply and perhaps you've resolved this yourself, if so,
let us know the solution!
As I don't have a cluster to "play with" ;-(, I cannot test various
solutions for this, but I do want to ask you: When you refer to
"...configure the server to run as a Service account (choice is disabled)."
are you referring to the MSSQLServer service or the "Microsoft Search"
(MSSearch.exe) service? If the former, you should and must run that account
under a DOMAIN\account and the "Microsoft Search" (MSSearch.exe) service
must be configured to run under the system account (LocalSystem).

Regards,
John

> Let me clarify:
>
[quoted text clipped - 96 lines]
> > > > >
> > > > > Eric

Reply to this Message