asked on 4/7/2016

SharePoint Search No Results

Hi Everyone,

New to joining the community. Have an issue with my SharePoint Search. Checking the ULS logs I am not seeing any that really identifies a true cause of what could be my issue with search giving 0 results.

Logs:
Spent 0 ms to bind 1861 byte file stream
Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=11.699776654074
Setting [Display] as the FormContext.FormMode for the current page
SearchBoxEx AfterDeserialize begin
'Search Service Application Proxy', location cache: Refreshing location cache
CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()
at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)
SearchServiceApplicationProxy::GetChannel--Channel Creation time: 0

I have checked the items that have failed within the crawl [Error Breakdown].

Anyone have any ideas what else to look at? Checked IIS/Content Sources/Rebooted Server/Services

Microsoft SharePoint

Last Comment

Josh Gier

4/19/2016

Robin Hall

4/7/2016

The two most common issues for Search relate to permissions and the crawl locations. I had a similar issue where I was getting no results (didn't actually check the ULS logs unfortunately) and it was because I did not have the right URL's defined in the Search content source.

Here is a helpful blog so you can check these two issues: http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=176

Make sure everything is actually started as well. Both the search service application and the proxy.

The other option is to create a new Search Service Application and see if you run into the same issues.

ASKER CERTIFIED SOLUTION

Josh Gier

4/14/2016

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

Josh Gier

4/19/2016

ASKER

Cache was not synced throughout SharePoint farm. Stopped SharePoint Timer Service and cleared cache directory and restarted service.

http://www.sharepointpitstop.com/2013/09/clearing-configuration-cache-for.html