Hi Nick,
Not much out there about this error, but...
Upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to
Release Version
http://blogs.msdn.com/joelo/archive/...tr-to-rtm.aspx
----------------------------------
.... I struggled with this for awhile. In the Event Logs, I found several
"Access Denied" errors with the message "The start address
<sts3://yoururl/contentbid={GUID}> cannot be crawled" and error code 2436.
These messages should appear every 5 minutes, when the SharePoint Search
Service Timer Job fires. 5 minutes is, of course, assuming the value has not
been changed from the default.
Hopefully this will help. I was able to fix the problem with a registry
hack. My issue was Loopback Checking, which IIS uses to protect against
Denial of Service Attacks. Basically, the default value does not allow the
Search Service to crawl the site, because it essentially receives a
dangerous level of Requests coming from the loopback address (default
127.0.1.1), which it denies access to "thinking" it is an attack.
See Knowledge Base Article KB896861 at
http://support.microsoft.com/kb/896861 for the fix.
Short story: Create a DWORD registry key at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Lsa named DisableLoopbackCheck
and set the value to 1, for TRUE, to disable the loopback checking...
----------------------------------
--
Merv Porter [SBS-MVP]
============================
"niewoo" <> wrote in message
news:BE07E929-3600-469D-B5F9-...
> Hello, my event log seems to be filling up with these warnings every few
> minutes:
>
> "The start address
> <sts3s://remote.mydomain.com:987/contentdbid={b480cc4e-a9d8-45f0-aebe-8a56c4cf2067}>
> cannot be crawled."
>
> I assume these are benign given that search is trying to crawl the remote
> site. Is there anyway of turning this off, or is there some other problem?
> Sorry - I have no knowledge of how sharepoint search works, so even a hint
> as
> to where to start looking would be great.
>
> Thanks,
> Nick.
Linear Mode
