Re: SQL 2000 FTS fails with SP 3a

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John Kane (jt-kane_at_comcast.net)
Date: 11/29/04 

Date: Mon, 29 Nov 2004 09:15:17 -0800

Chloe,
First of all, thank you for providing the version (@@select) and eventlog
entries as they are both very helpful info in troubleshooting SQL FTS
issues! Yes, this is a well known issue, but re-register DLLs and while this
should not cause any additional issues, it will not solve this issue. The
primary error is "800700e9 - No process is on the other end of the pipe."
Have you or anyone else changed the MSSQLServer service startup account &/or
password via Win2K's Component Services? If so, please review this 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

Yes, removing or altering the SQL Server login BUILTIN\Administrators can be
the source of this problem for you. If so, then this most likely is the
source of the failure for FT Populations as the MSSearch services needs this
login to log into SQL Server and you can either add back this login with the
original permissions (default master db, sysadmin privileges or see KB
article: 263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server at:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;263712

If you cannot add back the SQL Server login BUILTIN\Administrators login,
you can use the following SQL code as a substitute:

exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin

Regards,
John

"Chloe Crowder" <chloe.crowder@bl.uk> wrote in message
news:f27559a3.0411290431.2cb9b4d3@posting.google.com...
> I know this isn't exactly news, but we've got a development box run
> W2K3 and SQL 2000 (which requires SP3+ to run). Full text indexing
> doesn't work on this machine, and we get the following warnings in the
> event log:-
>
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0000900005> were logged to file
> <e:\sqldata\MSSQL\FTData\SQLServer\GatherLogs\SQL0000900005.1.gthr>.
> If you are interested in these messages, please, look at the file
> using the gatherer log query object (gthrlog.vbs, log viewer web
> page).
>
> The crawl seed <MSSQL75://SQLServer/32e0915f> in project <SQLServer
> SQL0000900005> cannot be accessed. Error: 800700e9 - No process is on
> the other end of the pipe. .
>
> The crawl for project <SQLServer SQL0000900005> could not be started,
> because no crawl seeds could be accessed. Fix the errors and try the
> crawl again.
>
> [Previous pair of message occur 5 times with different crawl seed
> number - presumably once per table]
>
> The end of crawl for project <SQLServer SQL0000900005> has been
> detected. The Gatherer successfully processed 0 documents totaling 0K.
> It failed to filter 1 documents. 0 URLs could not be reached or were
> denied access.
>
> I'm aware this is a known problem, and have tried a couple of things
> to fix it (or rather instructed the server administrator to do so).
>
> i) Re-register DLLs in \Program Files\Common Files\Microsoft
> Shared\MSSearch\Bin and \Program Files\Common
> Files\System\MSSearch\Bin
>
> ii) Checked for the registry keys
> HKLM\Software\Microsoft\Search\1.0\Language\Neutral and
>
HKLM\Software\Microsoft\Contentindexcommon\LanguageResources\Default\Languag
e
> Neutral. Neither existed. Adding registry entries for the second one
> didn't help.
>
> iii) I'm assured that BUILTIN\Administrator isn't the problem
>
> Does anyone have any more ideas on this one. As a library FTS is a bit
> important to us!
>
> Chloe Crowder
> The British Library

Relevant Pages

  • Re: Full text catalog just not populating
    ... exec sp_defaultdb N'NT Authority\System', N'master' ... means either the network guys in my company who don't know SQL but are admins ... > needs this login to log into SQL Server and you can either add back this ... >> fetching U ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot open SQL 2000 default database
    ... 1> EXEC sp_default 'mylogin', ... I have to type EXIT or type ctrl-C to get out of the SQL editor. ... error as I did before the error, as though I didn't type the command prompt ... I assume here that you run OSQL on the SQL Server machine itself, ...
    (microsoft.public.sqlserver.connect)