Re: catalog is empty after populating

From: John Kane (jt-kane_at_comcast.net)
Date: 08/10/04


Date: Mon, 9 Aug 2004 17:53:27 -0700

You're welcome, Andre,
The key error is Error: 800700e9 - No process at the other end of the pipe.

By chance did you or someone else remove the BUILTIN\Administrator login? If
so, you will need to either add it back with the default settings (master db
& sysadmin rights) as the MSSearch service requires that either the
BUILTIN\Administrators login
be present or that [NT Authority\System] localsystem login have the below
rights and this is why you are seeing ("Login failed for NT
AUTHORITY\SYSTEM" ) after removing the BUILTIN\Administrators login:

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

See also KB article Q263712 "INF: How To Prevent Windows NT Administrators
>From Administering a Clustered SQL Server"
at http://support.microsoft.com/default.aspx?scid=kb;EN-US;q263712 for more
info.

Additionally, and depending upon if you're FT Indexing documents imported
into SQL Server, you might also want to review KB article 308771 "PRB: A
Full-Text Search May Not Return Any Hits If It Fails to Index a File" at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;308771&Product=sql2k

Regards,
John

<anonymous@discussions.microsoft.com> wrote in message
news:2c6901c47e2a$8ed69410$a501280a@phx.gbl...
Hi John,
thanks for your advice, now I've found them.
I got five entries (3 informational, 2 errors) in the
application log. Here the 2 errors (I try to translate
them correctly from German):

Source: Microsoft Search
Type/Category: Warning Gatherer
Event Identification: 3036
Description:
Unable to access crawl seed <MSSQL75://SQLServer/6fe99f9f>
in project <SQLServer SQL0002400005>.
Error: 800700e9 - No process at the other end of the pipe.

Source: Microsoft Search
Type/Category: Warning Gatherer
Event Identification: 3024
Description:
Unable to start crawl for project <SQLServer
SQL0002400005> because there is no access to the crawl
seeds. Patch the error and then start again the crawl.

Obviously the second is an aftereffect of the first. So
I'll try to find the reason for the first error. Any idea?

André

>-----Original Message-----
>Andre,
>Hilary's referring to the Window's Application Event log
on the server where
>SQL Server is installed as the "Microsoft Search" service
cannot write it's
>errors to SQL Server's errorlog files as SQL Server has a
lock on these
>files. Specifically, you should click on Start ->
Programs -> Administrator
>Tools -> Event Viewer and review the Application event
log. You can click on
>View and Filter and then select "Microsoft Search" as the
Event Source to
>see only these events. Below is an example error, you may
find or you may
>find a different error.
>
>Microsoft Search
>Warning Gatherer
>3036
>JTKNT0
>Unable to access crawl seed
<MSSQL://LOCALHOST/7.1333579789> in project
><SQLServer SQL0000700006>.
>Error: 8007052e - Logon failure: unknown user name or bad
password. .
>
>Post any related errors in your server's Application
event log.
>Regards,
>John



Relevant Pages

  • Re: Slow Login with Cached Credentials
    ... might relate to my issue of "Slow Login with Cached Credentials" ... Of course when they are on the network and there is a domain controller ... in the event log. ... REM Disconnect existing network mappings - do not prompt the user ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP Service Pack 2 SAS Application Error
    ... There is nothing else unusual in the event log at that time. ... We are having some trouble on Windows XP Service Pack 2. ... process of updating all our computers from Windows XP Service Pack 1 to ... When certain users attempt to login, they receive an error after they ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Connecting to SQL from a Windows Service
    ... There is probably some way to debug this, but that's deeper Windows knowledge than I can dredge up right now. ... I looked into the Event Log and found that when my service ... 1st Login succeeds. ... You can try turning on login auditing in SQL Server and then check the ...
    (microsoft.public.sqlserver.connect)
  • Re: Authentication problem continued
    ... application pool? ... Login failures are logged to the Application event log therefore try to ... SQL Server is configured for Windows Authentication only and not mixed ...
    (microsoft.public.dotnet.framework.aspnet)