Solved

Sharepoint 2010 search not working

Posted on 2011-02-10
9
2,294 Views
Last Modified: 2012-05-11
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
0
Comment
Question by:stonneway
  • 5
  • 4
9 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 34865366
Have you tried using a regular domain account to crawl (which is best practice)?

The "default" zone must use NTLM for authentication.
0
 
LVL 1

Author Comment

by:stonneway
ID: 34865660
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
 
LVL 38

Expert Comment

by:Justin Smith
ID: 34865675
And you are using Classic / NTLM authentication?
0
 
LVL 38

Accepted Solution

by:
Justin Smith earned 500 total points
ID: 34865686
Also, you may need to disable loopback....

The second solution is easiest....

http://support.microsoft.com/kb/896861
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Author Comment

by:stonneway
ID: 34865692
NTLM. That is, internally we don't need to log on....it just knows....like magic
0
 
LVL 1

Author Comment

by:stonneway
ID: 34868811
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
 
LVL 38

Expert Comment

by:Justin Smith
ID: 34870613
Check your content sources, are they using the correct URL?
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 35177596
Update?
0
 
LVL 1

Author Closing Comment

by:stonneway
ID: 35736284
Havent resolved all errors but that was helpful
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

For SharePoint sites, particularly public-facing ones, there are times when adding JavaScript, Meta Tags, CSS Styles or other content to the page <head> section is more practical than modifying master pages.  For instance, you could add the jQuery l…
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get…
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message. In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now