Thursday, December 13, 2012

Search Service INOP in SharePoint 2013 Foundation

Now that I have SharePoint Foundation 2013 installed a member server I thought that I start looking at how well search works and in anything needs to be done to index third party documents like PDFs. What I found so far hasn’t been good news I am afraid to report.

 

Let me set the scene. I installed SharePoint Foundation 2013 on a member server and used the Complete installation method with the data residing on SQL Server 2012 Express. I used the SharePoint Configuration Wizard to set up the site using the defaults.

 

With SharePoint Foundation 2012 it turns out that search is now more like the old Search Server Express 2010. Thus, think of SharePoint Foundation 2013 as SharePoint Foundation merged with Search Server Express. You would think that is good wouldn’t you?

 

The first thing I found was that even using the SharePoint Configuration Wizard to set up farm indexing wasn’t enabled. When you go into the Search Application administration you see the following:

 

image

 

Local SharePoint Servers are a content source but there is no crawl enabled on these sites by default. Easy enough to enable some crawl rules. However, with that done I found that the indexing commences but remain stuck in the Starting state as shown.

 

image

 

And here it stayed no matter what I tried or how long I waited. When I attempt to do a search I get this every time.

 

image

 

My expectation is that out of the box, using a default installation that search would be enabled and would operate. I certainly not found that to be the case in my experience.

 

As I said, I have tried reinstalling and reconfiguring in a number of different ways and have still had no luck. I’m continuing to try and get to the bottom of why search on Foundation 2010 does seem to work. More updates soon.