"Hilary Cotter" <hilaryk@att.net> wrote in message
news:684C16E0-CB17-4DC0-A96B-655033C247C0@microsoft.com...
> 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.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
>
>
> "Eric Phetteplace" wrote:
>
> > 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
> >
> >
> >

"John Kane" <jt-kane@comcast.net> wrote in message
news:%23jrDaOZWEHA.3944@tk2msftngp13.phx.gbl...
> 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
>
>
>
>
> "Hilary Cotter" <hilaryk@att.net> wrote in message
> news:684C16E0-CB17-4DC0-A96B-655033C247C0@microsoft.com...
> > 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.
> > --
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> >
> >
> >
> > "Eric Phetteplace" wrote:
> >
> > > 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
> > >
> > >
> > >
>
>

"Eric Phetteplace" <eric.phetteplace@mhd.state.ma.us> wrote in message
news:%23LB6prqWEHA.2520@TK2MSFTNGP12.phx.gbl...
> 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
>
>
> "John Kane" <jt-kane@comcast.net> wrote in message
> news:%23jrDaOZWEHA.3944@tk2msftngp13.phx.gbl...
> > 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
> >
> >
> >
> >
> > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > news:684C16E0-CB17-4DC0-A96B-655033C247C0@microsoft.com...
> > > 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.
> > > --
> > > Looking for a SQL Server replication book?
> > > http://www.nwsu.com/0974973602.html
> > >
> > >
> > >
> > >
> > > "Eric Phetteplace" wrote:
> > >
> > > > 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
> > > >
> > > >
> > > >
> >
> >
>
>

"Eric Phetteplace" <eric.phetteplace@mhd.state.ma.us> wrote in message
news:eFTFEOtWEHA.2520@TK2MSFTNGP12.phx.gbl...
> 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
>
> "Eric Phetteplace" <eric.phetteplace@mhd.state.ma.us> wrote in message
> news:%23LB6prqWEHA.2520@TK2MSFTNGP12.phx.gbl...
> > 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
> >
> >
> > "John Kane" <jt-kane@comcast.net> wrote in message
> > news:%23jrDaOZWEHA.3944@tk2msftngp13.phx.gbl...
> > > 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
> > >
> > >
> > >
> > >
> > > "Hilary Cotter" <hilaryk@att.net> wrote in message
> > > news:684C16E0-CB17-4DC0-A96B-655033C247C0@microsoft.com...
> > > > 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.
> > > > --
> > > > Looking for a SQL Server replication book?
> > > > http://www.nwsu.com/0974973602.html
> > > >
> > > >
> > > >
> > > >
> > > > "Eric Phetteplace" wrote:
> > > >
> > > > > 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
> > > > >
> > > > >
> > > > >
> > >
> > >
> >
> >
>
>