Full-text search

  • Hi,

    I have a server in which we are implementing full text search. Some how it is not working. We have removed the BUILTIN\Adminstrators. We have granted rights for a user(Security administrator and Database craetor server roles and dbo database role ).

    KB article says that we need to have BUILTIN\ADMINISTRATORS.

    Any suggesttion how to get that working

    Thanks in advance

     


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • Have you tried just adding "BUILTIN\Administrators" (typing it in) via EM - Security ?! What error messages do you get when you try to do this ?!







    **ASCII stupid question, get a stupid ANSI !!!**

  • Hi Sushila,

    I have added Builtin\administrators via EM. I did not get any errors while adding. It was successful.

    DO I NEED TO RESTART SO THAT IT USES THIS LOGIN AS STARTUP ACCOUNT

    Please clarify.. This is in production


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • As far as I know (haven't come up with this issue myself) - if you just reset the permissions via the "server roles" and "database access" tabs to what it was before you deleted it, it should be ok!

    You should reboot only if this doesn't work! hth!







    **ASCII stupid question, get a stupid ANSI !!!**

  • Check out the KB article on this:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;317746

    Andy

  • As mentioned in the MS article posted above by Andy, you can run full-text search without BUILTIN\Administrators by creating a Windows login for NT Authority\System and adding it to the sysadmin role.  I run all my servers that way, and it works well.  That way, domain admins can't access SQL Server unless you (as the DBA) give them permission.

     

  • Hi

    I have even tried that using the following command and still not able to

    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

    My question is do i need to restart the service..

    What i havent tried is to reregister some dlls and removing keys that have empty values in HKEY_Class_root's file type.

     

     


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • Q. My question is do i need to restart the service..

    A. First of all, are you refering to the restarting the SQL Server (MSSQLServer) service or the Microsoft Search (MSSearch) service? If the latter, then while I don't believe that this is required, you should do it. Note, while the service is stopped and prior to starting, your users will get an error that the MSSearch service is not running. However, it should start quickly and the downtime should be brief. If your refering to the former, then I suspect that you will not have to restart the MSSQLServer service. However, if the restarting of the MSSearch services (try this first) does not allow for SQL Full Text Search queries to succeed, then by all means stop and restart the MSSQLServer service!

    Hope that helps!

    John

    SQL Full Text Search Blog

    http://spaces.msn.com/members/jtkane/


    John T. Kane

  • When you say full-text search is "not working", exactly what do you mean? Can you create catalogs? Can you enable FTS for a database? What errors do you get, if any?

     

  • Hi,

    Please see my error message

    Event Type: Warning

    Event Source: Microsoft Search

    Event Category: Gatherer

    Event ID: 3036

    Date: 6/30/2005

    Time: 2:24:18 PM

    User: N/A

    Computer: TELECOM-EM-DB3

    Description:

    The crawl seed <MSSQL75://SQLServer/3a81b327> in project <SQLServer SQL0003100005> cannot be accessed. Error: 800700e9 - No process is on the other end of the pipe. .

    Event Type: Warning

    Event Source: Microsoft Search

    Event Category: Gatherer

    Event ID: 3024

    Date: 6/30/2005

    Time: 2:24:18 PM

    User: N/A

    Computer: TELECOM-EM-DB3

    Description:

    The crawl for project <SQLServer SQL0003100005> could not be started, because no crawl seeds could be accessed. Fix the errors and try the crawl again.

    Event Type: Information

    Event Source: Microsoft Search

    Event Category: Gatherer

    Event ID: 3018

    Date: 6/30/2005

    Time: 2:24:18 PM

    User: N/A

    Computer: TELECOM-EM-DB3

    Description:

    The end of crawl for project <SQLServer SQL0003100005> 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.

    Event Type: Information

    Event Source: Microsoft Search

    Event Category: Indexer

    Event ID: 7045

    Date: 6/30/2005

    Time: 2:24:18 PM

    User: N/A

    Computer: TELECOM-EM-DB3

    Description:

    The catalog was not propagated, because no new files were detected for the project <SQLServer SQL0003100005>.

    I hope this makes sense

    Thanks

    Helen

     


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • Also please not that I am not able to connect from SQL server to any sharepoint url

    thanks


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • Hi,

    I can also see this in error log

    By checking the N:\MSSQL2000\MSSQL\LOG\ERRORLOG on the SQL we found the following entries:

    2005-07-07 05:51:00.77 spid52 Starting up database 'STS_telecom-em-sps1_1731241258_10451'.

    2005-07-07 05:51:00.84 spid52 Non-clustered index restored for STS_telecom-em-sps1_1731241258_10451.sysobjects.

    2005-07-07 05:51:00.84 spid52 Non-clustered index restored for STS_telecom-em-sps1_1731241258_10451.sysobjects.

    2005-07-07 05:51:00.85 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.syscolumns.

    2005-07-07 05:51:00.85 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.systypes.

    2005-07-07 05:51:00.85 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.sysusers.

    2005-07-07 05:51:00.85 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.sysproperties.

    2005-07-07 05:51:00.87 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.sysfulltextcatalogs.

    2005-07-07 05:51:00.87 spid52 index restored for STS_telecom-em-sps1_1731241258_10451.sysfilegroups.

    2005-07-07 06:05:54.12 spid58 Starting up database 'STS_telecom-em-sps1_1800390479'.

    2005-07-07 06:05:54.18 spid58 Non-clustered index restored for STS_telecom-em-sps1_1800390479.sysobjects.

    2005-07-07 06:05:54.18 spid58 Non-clustered index restored for STS_telecom-em-sps1_1800390479.sysobjects.

    Is this some thing normal

    How do I check that Full-Text is installed correctly on a clustered server

    Any help!!!


    Helen
    --------------------------------
    Are you a born again. He is Jehova Jirah unto me

  • The primary error is "800700e9 - No process is on the other end of the pipe.". This error is often caused by removing or altering the SQL Server login BUILTIN\Administrators and it most likely is the source of this problem for you. This most likely is the source of the failure for FT Populations as the MSSearch service 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. Note, if you have login BUILTIN\Administrators created, you should remove it and then run the following sql code.

    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

    The basic issue is that the external "Microsoft Search" (MSSearch.exe) service requires either the login BUILTIN\Administrators with all default settings OR the above Authority\System settings to access SQL Server and therefore are necessary for SQL Server Full-text Search functionality.

    Regards,

    John

    --

    SQL Full Text Search Blog

    http://spaces.msn.com/members/jtkane/


    John T. Kane

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply