Sharepoint 2010 search not working

Hi all,

I've got a Sharepoint 2010 application where the search isn't working. If you try to search for something it just says that no results were found, despite there clearly being results.

In the Sharepoint Central Admin tool search settings (Central Administration  Search Service Application: Crawl Log - URL ) the log shows the following error;

https://sp.mydomain.com 
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.

However the account being used to search (Network Service) has full read permissions on the application;
(All zones)  Search Crawling Account  NT AUTHORITY\NETWORK SERVICE  Full Read  

The only thing that we have changed from the default setting is the Alternate Access Mappings where we changed the default http://hostname to https://sp.mydomain.com.

I've tried adding http://hostname back as the intranet option but that hasn't worked.

Any ideas ?

Olly
LVL 1
stonnewayAsked:
Who is Participating?
 
Justin SmithConnect With a Mentor Sr. System EngineerCommented:
Also, you may need to disable loopback....

The second solution is easiest....

http://support.microsoft.com/kb/896861
0
 
Justin SmithSr. System EngineerCommented:
Have you tried using a regular domain account to crawl (which is best practice)?

The "default" zone must use NTLM for authentication.
0
 
stonnewayAuthor Commented:
Yeah, just tried that, but it didn't help. Waiting for another crawl shows that the errors remain

The default AAM shows....

 
https://hostname - Default - https://hostname
https://sp.mydomain.com - Internet - https://sp.mydomain.com 
 
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
Justin SmithSr. System EngineerCommented:
And you are using Classic / NTLM authentication?
0
 
stonnewayAuthor Commented:
NTLM. That is, internally we don't need to log on....it just knows....like magic
0
 
stonnewayAuthor Commented:
Well disabling the loopback made a massive difference. Most of the errors have gone and we now have search results. Thanks.

However we still have a few small errors;
************
http://hostname:80/my/person.aspx?accountname=mydomain/myadminaccount 
This item could not be crawled because the crawler could not connect to the repository. Local SharePoint sites 2/11/2011 7:40 AM

sps3://hostname/site$$$people/bucketid=1  
This item could not be crawled because the crawler could not connect to the repository. Local SharePoint sites 2/11/2011 7:40 AM

sps3://hostname/site$$$people  
This item could not be crawled because the crawler could not connect to the repository. Local SharePoint sites 2/11/2011 7:40 AM

sps3://hostname  
This item could not be crawled because the crawler could not connect to the repository.
*************

Certainly the first error about http://hostname is down to the fact that the site doesn't respond to HTTP requests on port 80, it's only HTTPS on port 443. Is there a way to tell the search interface not to search HTTP or to force it to use HTTPS instead?

Any ideas on the other ones?

Olly

0
 
Justin SmithSr. System EngineerCommented:
Check your content sources, are they using the correct URL?
0
 
Justin SmithSr. System EngineerCommented:
Update?
0
 
stonnewayAuthor Commented:
Havent resolved all errors but that was helpful
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.