SharePoint Foundation search issues giving object not found error


  • Hello,

    Has anyone else run into this issue w/ SharePoint Foundation, where the crawler generates this warning in the app event log under Event ID 14?

    The start address sts4://servername/contentdbid={9fdc6f6b-0034-4beb-bf98-701117a3b385} cannot be crawled.

    Context: Application 'Search_index_file_on_the_search_server', Catalog 'Search'


    The object was not found. (0x80041201)

    I have found a few posts in the forums referencing KB 896861, which I thought would resolve the issue given that I am using host headers on my site, but stil no luck.

    I also see where this was an issue in WSS 3.0 - so whatever the issue it's been around for a while.

    Any ideas?

    • Moved by Wayne Fan Friday, December 09, 2011 1:48 AM It's SharePoint 2010 issue, thanks. (From:SharePoint - Search (pre-SharePoint 2010))
    Thursday, December 08, 2011 6:47 AM

All replies

  • Hi Gaylen,


    Thanks for your post.

    1.       Please check whether the content database Is existed on the server at first. It can be achieved using the powershell command below:


    2.       Try to reset the index, and rebuild again.

    Wayne Fan

    TechNet Community Support

    Friday, December 09, 2011 3:12 AM
  • Hi Wayne,


    Same result after rebuilding the index.  Same exact issue that I--I had in the other post and I did the exact same things, disabling the loopback check in the registry.  How can I get more information on this error?  I wonder if this is related to alternate access mappings somehow.  It looks like it's trying to crawl http://servername but if it is in fact going to that site, it will not find my SharePoint Foundation site.  My SharePoint foundation site resides at on my server.  Of course I can browse my SharePoint site by the FQDN from the server and from any other device. 

    I just thing the crawler is not going to the correct site on this server.

    Thanks ahead of time for any help!




    Friday, December 09, 2011 5:57 AM
  • Hello all -


    My issue was in fact related to alternate access mappings for my site.  The crawler is using http://servername which is a completely seperate site running in IIS.  I changed the bindings for that site in IIS.  Violoa, the crawler completed and I now have search results displaying in the SharePoint site itself.

    This is probably not the correct way to resolve the issue.  I should confront this issue head on and figure out how to either have the crawler service use the URL of my choosing OR configure AAM correctly for the site in accordance to the Search Crawler.

    After all, what if I was not able to change the bindings on this other site that the crawler was using at http://servername/ ???

    Anyway - hopefully this helps someone else and maybe someone can reply w/ the correct methods of handling this dilema.




    Thursday, December 15, 2011 4:10 AM