Start-SPEnterpriseSearchServiceInstance – SearchServiceInstance is not found on server”

I’ve got this error message when trying to start the Search Service on one of the machines on the farm.

The command I’ve used:

Start-SPEnterpriseSearchServiceInstance servername


The error message was:

Start-SPEnterpriseSearchServiceInstance : SearchServiceInstance is not found on server ‘servername’.


After fighting a while with SharePoint I realized my problem was on my farm data being cached on the SharePoint 2013 Management Shell window I was using. The server I was trying to start the Search Services on was only added to the farm a few minutes before on the same SharePoint 2013 Management Shell window and even though the command Get-SPServer was showing the new server name on it, the cache for the farm on the powershell window was preventing me from accessing the server.

After I closed the SharePoint 2013 Management Shell window and opened a new one, the Start-SPEnterpriseSearchServiceInstance command worked just fine.


See you,




SharePoint 2013 Search Back to Front Course on Pluralsight

In the beginning of August PluralSight released a SharePoint 2013 Search Back to Front  course.

I just took it and really enjoyed it! It demonstrates a complete search setup from the search service provisioning, going through configuration to the usage on the sites and customization of the search results display.

The main modules are:

  • SharePoint 2013 Search Overview
  • SharePoint 2013 Search Configuration
  • SharePoint 2013 Advanced Search Configuration
  • SharePoint Search Results Presentation
  • SharePoint 2013 Search Troubleshooting

The course’s author, Matthew McDermott, is a very good presenter and makes very easy to understand the topics with good and solid examples. The course covers all the main concepts you need to understand to start planning how you going to use search on your organization and projects. Thumbs up!

One of the most interesting things for me was a very cool powershell script available for download to help you configure your search architecture. You should check it out.

See you,


Using Enterprise Search to Build a Product Catalog Site

If you are interested on learning how SharePoint 2013’s Enterprise Search can help you build a product-centric web site check this post series out:

How to set up a product-centric website in SharePoint Server 2013

It uses search out of the box features to build a “Contoso” web site based on a product catalog created and managed on a different site collection.

The series of blog posts by Bella Engen guides you through the sites configuration, data load, site navigation, web parts configuration and refiners placement.

The posts are very interesting and mix information on the features used and steps to configure but it lacks some configuration information and support material.

On Stage 2, the metadata configuration was complicated in my case and the data load into the product catalog site is very confusing. In my case, after I’ve created the Product Catalog site collection I went to the Products list and I couldn’t find the Item Category column on the list.


After I’ve added the Item Category site column to the Products list, I had to go to the Metadata Management  Tool and create a new group to be associated with my site collection.


With the group created, I’ve created the Product Hierarchy term set.



Back to the Product list, I had to associate the Item Category field with my term set:

ProductSite06a ProductSite06b

At the point, I was ready to run the powershell scripts. I’d recommend you to download the script files from this zip file and execute it  instead of the script Bella provided.

Please edit file file InputParameters.ps1 and provide values for the following variables:

  • $productCatalogSiteCollectionURL : Complete URL for your product catalog site collection.
  • $CatalogInpFile : Path to the products.txt file. If you keep the structure from the zip file you don’t need to change this variable.
  • $TaxonomyInpFile : Path to the taxonomy.csv file. If you keep the structure from the zip file you don’t need to change this variable.
  • $termStoreName : Name of your Term Store.
  • $termSetName : Name of your Term Set.

After the configuration is done, execute the powershell script in order:

  • 1CreateSiteColumns.ps1
  • 2ImportListContent.ps1
  • 3ImportTaxonomy.ps1
  • 4LinkListContentWithTaxonomy.ps1

On Stage 6, she doesn’t provide the master page and page layouts templates which doesn’t change the steps you can do but doesn’t make your local experience as cool and fancy as you see on the posts.

Overall, a very good reference if you want to understand the out of the box search capabilities to create dynamic sites based on search.

See you,