We're using Search Server 2010 Express to crawl our own sites that do not use SharePoint. There are several other content sources that are crawled without issue, but this one is giving me the following error.
The start address ****** cannot be crawled.
Context: Application 'Search_Service_Application', Catalog 'Portal_Content'
Details: Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.
Here's what I have tried so far.
- Following the this for the LoopbackCheck fix http://support.microsoft.com/kb/896861
- Safe method using BackConnectionHostNames didn't work
- DisableLoopbackCheck set to 1 also didn't work
- Server has been rebooted after BackConnectionHostNames key added
- Added crawl rule that specified a different content access account
- Re-added the same content access account with "Do not allow Basic Authentication" checked and unchecked
- Used different domain admin account with same result
- Updated the Default Content Access account
- Re-added the same account and also tried with a different domain admin account
- Came across mentions of UserProfile Service Application, but I don't see this on my service applications list
- This is the only content source that's giving me this issue
- I don't think it's an issue with access privileges with the account being used
- This shouldn't be an issue with connecting to SQL Server since the other content sources work fine
- Can access the site from the server while logged in as the content access account in IE
I've gone through most of the comments in the below two links along with much time spent reading Google search results. Most seem to point the the LoopbackCheck fix as the solutoin to this error, but this has not worked for me.
I would appreciate any help in this since it's been driving me nuts for two days now.
EDIT: The account used for this is not a domain account. It's just a local account on the server that's in the admin group. But like I said, the other content sources crawl without issue using this setup.