I'm getting this error on the server of WSS 3.0
The start address <sts3://ebs-sharepoint/contentdbid={d901caff-7863-40aa-8460-c3ef9132cb89}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)
The WSS 3.0 is configured to use Kerberos and both the WSS Search and Timer service is running under a domain account.
Any help. Thanks.
Jason
WSS3 cannot be crawled
murphy.m.j
msaeedf
I haven't specify the host header in IIS and I access the website thr FQDN
and the error log show http://servername ... rather than http://servername.domain.com
Neotech
Hi
I'm having same problem.
Event Type: Warning
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2436
Date: 2/12/2007
Time: 1:50:00 PM
User: N/A
Computer: <computer>
Description:
The start address <sts3://server.domain.dk/contentdbid={7a7f6b78-5fe1-4c0e-a5f2-956a00cc7f04}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The default content access account is DBO on the DB and running NTLM auth
nmharleyrider
KyleNHS
Check for Loopback Checking as per KB Article: http://support.microsoft.com/kb/896861
Worked for me. If it works for you, please mark this thread as answered. Thanks.
Keith Fredericks
Finally i got it working.
The problem is that I cannot broswe to http://servername in the IE of my WSS3 server.
After correct the proxy setting in IE of the server (bypass proxy), I can crawled the content in http://servername now.
However the event log keep showing that it cannot crawled the Central Administration page.
The start address <sts3://ebs-sharepoint:13547/contentdbid={7fa830af-870c-4f83-a04f-b5bf31b3ea58}> cannot be crawled.
It is normal
I can broswe to http://ebs-sharepoing:13547 from the IE of WSS3 server.
bigbob
I fixed the problem on my server
The problem is that we use a FQDN and also running the search service on the frontend server
Have a look on this KB http://support.microsoft.com/kb/896861 - Method 1: Disable the loopback check
It worked for me :)
Francesco De Vittori
All,
Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)
For resolving this error, please make sure that your Content Access Account has enought privileges on the data-sources. If you want to index custom data-sources like documentum, intranet sites, databases, fileshares , internet etc make sure that your content access account has enought privileges on the data-source.
If you just want to index the Sharepoint (WSS) sites only, make sure that Shared Services (Timer, Search etc)
are running properly with privileged User Accounts
ugpj
I resolved a similar type message.
WSS Central Console --> Operations --> Alternate Address Mapping
I reset the default Sharepoint - 80 site back to the servername.
Once this was configured, the crawling warnings went away.
I tried changing these values so the links in outgoing mail (for alerts, workflow etc) would display the external (public) IP address.
Attila Fogel
I had the same crawl error messages in Event Viewer. I have also changed the registry settings according to 896861. It did not work. I think the reason my index crawl failed is because WSS search service is using HTTP urls for indexing whereas all my sites are HTTPS enabled. HTTP urls will not return any results. My question is how am I going to modify WSS indexing engine and get it to scan HTTPS urls instead of HTTP without a lot of work. I wonder if the scan path information is stored in the WSS Search database.
Terry Smith
robinjam