Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2003

    Unhappy Unanswered: Full-Text population problems


    I'm getting the following error when I attempt to populate our Full Text Index on SQL
    2000: The crawl seed in project SQL0000500005> cannot be accessed. Error: 800705b4 - This operation returned because
    the timeout period expired. .

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

    I have seen in other threads and on the MS site how this is caused by the MSSQLService and the MS Search services not being syncronized and it can be fixed by changing the MSSQLService account to use the system account and back again.

    The BUILTIN\Administrators group is present in SQL and has OWNER permissions. I even tried giving the SYSTEM group full access to the FTDATA folder.

    This did NOT work for me. I am still getting the messages. One thing that is probably unique to my instalation is that it resides on the only server on this network so it is also the primary domain controler. Could this be why I cannot get the FT population to work?

    I have another machine on a seperate network that is not a PDC and FT-Indexing works great on it but that doesn't help me for the network I need it to work on.

    Does anyone have any other ideas I could try? I have been working on this for close to a week now.

    The "Mav"

  2. #2
    Join Date
    Aug 2002
    How about the SQL Services account privileges and which accout is used?

    Check what is the current state of process for indexing.

    Refer to this
    KBA to resovle the issue.
    --Satya SKJ
    Microsoft SQL Server MVP

  3. #3
    Join Date
    Jun 2003

    RE: Full-Text population problems

    I looked through that document and I have tried all that still no dice. The MS Search service is using the Local System account and the MSSQLServer service is using the local server administrator account. I tried changing this to the Local System acount using SQL Server Enterprise Manager(SSEM) this did not work so I changed it back to the local administrator account, once again using the SSEM.

    Any other suggestions?

    The Mav

  4. #4
    Join Date
    Jun 2003

    No one?

    No one has any ideas? =(

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts