Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have a search service application that won't crawl correctly.

The crawl account has all the right access to the farm and databases. THe AAM are as follows:

- http://machinename - default 

- https://sp.contoso.com - internet

I try crawling "http://machinename" as content source, I get:

Error - The object was not found.

I try crawling "https://sp.contoso.com" as content source, I get:

Deleted(Warning) Item not crawled due to one of the following reasons: Preventive crawl rule; Specified content source hops/depth exceeded; URL has query string parameter; Required protocol handler not found; Preventive robots directive. ( The item was deleted because it was either not found or the crawler was denied access to it. )

Any ideas?

share|improve this question
    
Ah rats. It was my doing. I had a host header in IIS linked to port 80 that was supposed to be entailed in the certificate for SSL. I deleted the host header in the IIS Manager for port 80, and could navigate to the site and the crawl worked successfully. –  Mike Nov 7 '11 at 20:00
    
If anyone wants to post that as the answer, I will mark them as correct. –  Mike Nov 7 '11 at 20:13
    
it acceptable to post your own answer and mark it as such. –  Jesus Shelby Nov 9 '11 at 21:23
add comment

3 Answers

Verify the search account is registered correctly, if you are using claims the search account should have the claims prefix ( 0#.w ) as part of the logon name. If you only see the normal domain or computer prefix without that above, than the search account is only mapped to the windows account, not the claim, so essentially they will be seen as different users with different or non-existent permissions.

Whats the purpose of crawling via the AAM address vs. default zone? In my experience, the default zone over HTTP get's you past a lot of issues. When you access search via the AAM URL all your links will be updated properly, so it's not required to search via the URL you are using.

share|improve this answer
    
I'm not using claims based auth. I crawled using machinename as my content source, and get that error. –  Mike Nov 7 '11 at 19:45
add comment
up vote 1 down vote accepted

Ah rats. It was my doing. I had a host header in IIS linked to port 80 that was supposed to be entailed in the certificate for SSL. I deleted the host header in the IIS Manager for port 80, and could navigate to the site and the crawl worked successfully.

share|improve this answer
add comment

After making changes to the crawl accts and/or content sources I would often get the error Required protocol handler not found. After restarting the Search Service I would find that the crawl woud than perform as required. Worth a shot to see what happens when you restart the search services.

share|improve this answer
    
That didn't work, but thanks for the suggestion. –  Mike Nov 7 '11 at 19:47
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.