none
Start Address cannot be crawled

    Question

  • System: MOSS 2007 (single server) on a Win 2003 R2 Standard Ed. SP2 server

    The start address <sts3://xxxxxx:33236/contentdbid={88b4ab50-66ca-43b6-94fc-7aa99f8eabe3}> cannot be crawled.
    Context: Application 'Search index file on the search server', Catalog 'Search'
    Details:
    The object was not found. (0x80041201)

    These log entries started to appear after applying Windows Updates to the system after which I needed to perform these steps:
    http://support.microsoft.com/default.aspx/kb/896861 (method 2)

    I've allready tried many posts on this subject but none seem to work for me.
    I receive this warning in the application log every time the indexing is scheduled to run. But there's only a warning entry for our 2 SSP content db's in the log. All other content db's can be crawled/indexed and produce search results so the default content access account used must be ok I presume. I've checked the SSP content db's in central administration and they are linked to the right search server.
    Both the SSP web applications only have a default AAM generated automatically on creation so I also don't think that's got something to do with the issue as discussed in:
    http://groups.google.com/group/microsoft.public.sharepoint.windowsservices/browse_thread/thread/bc1ed1af1d87fb7a

    Does someone has another idea why this log warning keeps coming back in the application log?

    Thanks in advance

    Tuesday, September 29, 2009 11:31 AM

Answers

  • Hi,

     

    If you have SP2 applied, it should be caused by a known issue that SharePoint would not index the web application without a root site.

     

    Please create a root site collection on each web application to workaround the issue.

     

    In my opinion, there is no need to crawl SSP administration site, because it suppose to be inaccessible for most of the users and no document should be stored there for collaboration.

    You could safely remove the SSP web application URL from the default content source or ignore the error.

     

    This issue should be fixed in Aug 2009 CU, but it is not available for downloading right now due to a reattach content database issue.

    You could get more information in Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx)

     

    -lambert


    Sincerely,
    Lambert Qin | Microsoft TechNet Managed Forum Support
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, October 02, 2009 8:23 AM

All replies

  • Hi,

     

    If you have SP2 applied, it should be caused by a known issue that SharePoint would not index the web application without a root site.

     

    Please create a root site collection on each web application to workaround the issue.

     

    In my opinion, there is no need to crawl SSP administration site, because it suppose to be inaccessible for most of the users and no document should be stored there for collaboration.

    You could safely remove the SSP web application URL from the default content source or ignore the error.

     

    This issue should be fixed in Aug 2009 CU, but it is not available for downloading right now due to a reattach content database issue.

    You could get more information in Updates Resource Center for SharePoint Products and Technologies (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx)

     

    -lambert


    Sincerely,
    Lambert Qin | Microsoft TechNet Managed Forum Support
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, October 02, 2009 8:23 AM
  • Hi,

    There is indeed no need to crawl the SSP administration site(s). I've re-checked the content sources of both SSP's and neither one of the SSP web application URLs is included. So why does the application log keep mentioning that they cannot be crawled if they in fact aren't even included...

    Best regards,

    Davy

    Wednesday, October 14, 2009 8:19 AM
  • Hi Lambert,
                    I have a WSS v3 server that i applied a SP2 to and since then i have been getting this error:
    The start address <sts3://myserver/contentdbid={6a68a5ab-2b97-419f-9e88-57875d494f39}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:
        The object was not found.   (0x80041201)


    I did a research the errors are quite different regarding the Details info e.g     The object was not found or Access is Denied

    I'm getting the
    The object was not found.
    Any fix for this?
    Yo mentioned removing SSP web app but this is WSSv3...

    Thanks in advance
    Tuesday, October 27, 2009 12:53 AM
  • Hi Patrick,

    Try method 2 from the following link:

    http://support.microsoft.com/default.aspx/kb/896861

    If it does not work try to disable Do not allow Basic Authentication at the Crawl Rules

    Hope it help...
    Tuesday, October 27, 2009 3:05 PM
  • Thanks jstelten but where is this option in the central Admin.
    I'm using a WSS v3 server not MOSS.
    Thanks
    Patrick
    • Proposed as answer by gurpreet145 Friday, October 30, 2009 2:52 PM
    Wednesday, October 28, 2009 12:04 AM
  • Thanks jstelten but where is this option in the central Admin.
    I'm using a WSS v3 server not MOSS.
    Thanks
    Patrick

    hello patrick.

       i had the same problem as you. after searching internet for hours i gave up. i have managed to resolve my issue and here is what i did. 

    I was getting

    The start address <sts3://ServerName:37951/contentdbid={999a818c-ae9a-47fe-82d5-1cebc4edce93}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:

    The object was not found. (0x80041201)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    i opened the sharepoint 3.0 central administration
    clicked on operations tab
    alternate access mappings
    here is a list of url and one which was giving error was also listed here http://ServerName:37951
    i copied and pate the url in a new browser to see what i get. i got nothing. so i decided to delete it from
    application management tab -> delete web application -> select the web application which is causing the problem
    delete content databases and delete IIS web sites. and click on delete button.

    this solved my problem.



    Friday, October 30, 2009 3:10 PM
  • Thanks muchly i did solve my issue too and i blogged it here below

    http://geekswithblogs.net/naijacoder/archive/2009/10/28/135786.aspx

    Hope it helps

    Patrick
    Monday, November 02, 2009 8:57 AM
  • Lambert,

    I have a Search Server 2008 Express install that was working fine until I installed Wss3 Sp2.   My site are typically like: http:\\myserver:portNumber\sites\firsttry\ with no "root" site. My Search crawl, worked before applying SP2.  Now the crawl log just shows:
    "object not found. The item was deleted because it was either not found. or the crawler was denied access to it.



    Then I sawe your Post:

    >>> If you have SP2 applied, it should be caused by a known issue that SharePoint would not index the web application without a root site. 


    Well I didnt know about it.  Is this the hot filx that you were referring to?

    http://support.microsoft.com/kb/974989

    Description of the Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): October 27, 2009

    TIA,

    Barkingdog

    Friday, November 13, 2009 3:00 AM
  • BarkingDog
    Have you had a look at this:

    http://geekswithblogs.net/naijacoder/archive/2009/10/28/135786.aspx 

    Hope it helps
    Patrick
    Friday, November 13, 2009 3:15 AM
  • Hi Barkingdog,

     

    The issue is fixed in Aug 2009 CU (http://support.microsoft.com/kb/973400/).

    As the Oct 2009 CU (http://support.microsoft.com/kb/974989) includes the hotfix after SP2, you could apply in it to resolve the issue.

     

    See October 2009 Cumulative Update Packages for SharePoint Server 2007 and Windows SharePoint Services 3.0 for more information.

     

    -lambert


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, November 13, 2009 4:20 AM
  • I applied the CU for Oct 2009  and it seems to have fixed the problem!

    Thanks to everyerone.


    Barkingdog

    P.S I am still concenred about the reliability of Search Sevrer 2008 Express. For example, on the main search page,, when searching for the string "abc" it, returns nothing. No error messagte, no "string not found", just nothing. But when I hit the advanced button, on the same page, and type "abc" in there, it returns the proper answers.

    Friday, November 13, 2009 4:40 AM