Windows Sharepoint Services 3 Event ID: 2436: cannot be crawled, Access is denied

hello

netbios site with stsadm

stsadm.exe -o createsite -url http://servername -ownerlogin DOMAIN\username
-owneremail email@mail.com

Once a crawl was completed  could return search results from the new site but the
sites that had been created previously would only show search results if you added
new content to the sites. The previously incremental crawled content had been
flagged or security trimmed so it could not be returned in search.

There is no way to start a full crawl for WSS search, it is always incremental so
we had to stop the search service in the SharePoint Admin page and start it
again.

http://servername:PORT/_admin/Server.aspx

Once this had been done we could return search results from all of the clients WSS
sites.
----------------------------------------------------
Make sure that if you go to the Central Admin - Operations - Alternate access URLs
- Edit URL and then select the web application you're working on has the 'Default'
URL that can be browsed on the server locally.
===================================================




Regards
Sunil

Try to sign into one of the sites with network service account, if you get an access is denied, go to central admin, application management, policy management, and be sure your the following account are present, if they are not, add them to all zones in all web applications:

NT AUTHORITY\LOCAL SERVICE  NT AUTHORITY\LOCAL SERVICE - Full Read  
Search Crawling Account - Network Service  - Full Read  

Thanks for the replies guys;

jtarabay: The permissions on my site is as you describe above and as a test I added a domain account to this list and set the WSS Search service to run under this domain account but get the same result; the domain account does have access to the site and is also db_owner on all databases..

Sunil: I checked the kb article but sadly this was not the answer for me (.txt files are not being blocked). Also, am I right in saying stsadm.exe -o createsite -url http://servername will create a new site? I hope its not necessary to go to these length's to sort this out since from the event log I can tell that its just a permissions problem somewhere I'm not looking; other than this issue the site works great..

Any other idea's? Also the event log mentions the possibility of adding a crawl rule, is this a possibility?

one more thing i would like to add is if site is using the SSL or if you are using the site with the host header  then creating the crawl rule will definately help to resolve the issue you are facing.
there aresome knwn issues when crawling site with SSL ,basic authentication or if sites are using the hostheader.
pesonally i have came across multiple instance in above mentioned situations unable to crawl the content
workaround would be extening and mapping the existing web application with new web application and using the new web app URL as the default URL and should be able to crawl the site without any error message.

creaing the rule also helps when using  SSL on the web app or if using the complex URLs which sharepoint crawleris not able to SEE . is there any error message in crawl log which will help us to understand what is happening in the background.

sunil
 

Check your hosts file on the index server.  It is located at:

C:\windows\system32\drivers\etc\

Copy and paste it here, change anything you need to keep your server anonymous, but leave be sure to leave all instances of the entries so we can see if its okay.