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,




Interesting Posts on Distributed Cache Services on SharePoint 2013

I was reading about the Distributed Cache Service on SharePoint 2013 and found the following interesting articles about it:

AppFabric Caching and SharePoint: Concepts and Examples (Part 1)

AppFabric Caching (and SharePoint): Configuration and Deployment (Part 2)

Distributed Cache Service in SharePoint 2013


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,


How to Schedule a Powershell Script to Run on Windows 2008

It is a little bit tricky to configure a Powershell  script to run on the task scheduler on Windows 2008.

The separation between the powershell.exe command and the arguments makes a little confusion.

The way I did it was:

  • Create a new task.
  • Define a schedule.
  • Add an action:
    • Program/script: Powershell
    • Add arguments: -command &{E:\scripts\ClearIISLogs.ps1}

Now you just need to run your script and make sure it works as expected.


See you,


How to Check if .NET 4.5 Is Installed on a Server

In order to check if your server has .NET Framewrok 4.5 installed you can go to the Registry and look for the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client

Check the Version value. If it starts with “4.0” you are running on the 4.0 runtime, if it starts with “4.5” you are running on the 4.5 runtime.

See you,

FAST ESP – Links to Offline Install Components

The default FAST ESP installation requires your computer to have an internet connection. In several environments it is not a reality and you then have 2 options: run the first part of the installer on a box with internet connection and stop it after it have downloaded all components or download them manually and copy then to the data sub-folder on the installer path.


Here are the links for the manual download option:


See you,


Turn Static and Dynamic Compression Off on IIS 6.0

We found an issue when downloading dynamic PDFs files on IIS 6.0. Since it uses a regular PDF as a template and binds the data dynamically on the client, IIS compression was modifying the file and it cause the bind to fail. In this case you need to disable IIS’ file compression (both static and dynamic) and the only way to do it on IIS 6.0 is through the IIS Metabase.
You can use metabase editor or edit it manually by the metabase’s XML file. The steps to edit the metabase file manually are the following:


Enable IIS Metabase direct edition

Go to IIS Manager.
Right click on the computer name an select Properties.
Check the Enable Direct Metabase Edit option and click OK.


Backup the metabase file

The metabase file is located at C:\windows\system32\inetsrv\metabase.xml


Edit the metabase file
Add the following attributes to the virtual directory (IIsWebVirtualDir node) or web site (IIsWebServer node):




Save the metabase file


Reset IIS

Run the iisreset.exe command


Disable the IIS Metabase direct edition

Go to IIS Manager.
Right click on the computer name an select Properties.
Uncheck the Enable Direct Metabase Edit option and click OK.


See you,