The Search Dictionaries term store group does not exist

Today's SharePoint 2013 configuration quagmire is this: you provision the Search service application, you click on Search Dictionaries - for example, to manage company name extraction or query spelling correction - and you see a largely empty term store.

In other words, you click this:



























You expect to see this:



























But instead you see this:















As is often the case with these issues, you'll probably that everything works fine if you use the Farm Configuration Wizard to provision your services. However, if you do things properly and create your service applications by hand, you come across this kind of issue.

The Solution


The Search Dictionaries term set group is not created when you provision the Search service application, it's created when you provision the Managed Metadata service application. When you create a Managed Metadata service application, it should create the Search Dictionaries and the People term set groups in addition to the System group. However, this will only happen if you have provisioned the State service application before you provision the Managed Metadata service application.

You can find details on how to configure the State service here (SharePoint 2010 article, but the steps are the same). For convenience, for a basic deployment, you can provision a State service application by running the following PowerShell cmdlets:

$state = New-SPStateServiceApplication -Name "Contoso State Service"
New-SPStateServiceDatabase -Name "ContosoStateDB" -ServiceApplication $state
New-SPStateServiceApplicationProxy -Name "Contoso State Service" -ServiceApplication $state -DefaultProxyGroup

So, in summary, configure your service applications in the following order:
  1. Provision a State service application.
  2. Provision a Managed Metadata service application.
  3. Configure usage and health data collection.
  4. Ensure the usage and health data collection proxy is started.
  5. Provision the Search service.
Everything should then work fine.

Note: steps 3 and 4 aren't necessary to create the Search Dictionaries group, but the Search service will report errors if the usage and health data collection service app isn't set up. When you configure usage and health data collection manually, rather than using the Farm Configuration Wizard, you'll typically find that the service application proxy is in the Stopped state. For a good explanation on how to start it, see http://tristanwatkins.com/fixing-the-usage-and-health-data-collection-sa/.

Comments

  1. What about an existing farm with MMS already created ?
    Shoul I recreate again ?

    ReplyDelete
    Replies

    1. Hi Sorin

      If the existing MMS is in use, maybe you could create a second MMS after you've configured the State service? You can have as many MMS instances as you like - then whenever you get directed to a term store page, you'll have the option to select the term store you want. It's not something I've tested but it might be worth trying.

      Incidentally, I've seen some instances where the Search Dictionaries group gets created when you provision the MMS even if the State service isn't configured first. However, configuring the State service first seems to make it work consistently.

      Delete

Post a Comment

Popular posts from this blog

Server-side activities have been updated

Image
If you use SharePoint Designer 2013 to build workflows, there's a fair chance you'll have come across the following error message:
Server-side activities have been updated. You need to restart SharePoint Designer to use the updated version of activities.  Needless to say, restarting SharePoint Designer rarely makes the error go away. The usual advice is:

Approach 1: Clear the cache folders
See for example How to Clear Your SharePoint Designer 2010/2013 Cache. If you've just deployed some custom workflow activities to your site, this will probably solve your problem (and you should clear the cache folders every time you deploy custom activities). If the error occurs spontaneously, this approach often won't help.

Approach 2: Reinstall SharePoint Designer
This might work if you've got a preview version of SharePoint Designer installed. If not, it's unlikely to help. It didn't work for me, and it didn't work for countless others on the forums.

Approach 3: Insta…
Read more

The target principal name is incorrect. Cannot generate SSPI context.

Image
Today's problem occured after I restarted a Hyper-V based SharePoint 2013 farm (Windows Server 2012, one SharePoint 2013 machine, one SQL Server 2012 machine, one DC). I fired up Central Administration and was hit with the following error:

Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

The target principal name is incorrect. Cannot generate SSPI context.

After checking the obvious things - testing connectivity to the DB server, checking the SQL service was running, verifying permissions, etc - I initially figured this was an issue with my Hyper-V snapshots being out of sync, so I ran the SharePoint Products Configuration Wizard. This hit me with the following error:

Failed to detect if this server is joined to a server farm. Possible reasons for this failure could be that you no longer have appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessib…
Read more

Getting or Setting Multi-Value Metadata Fields with the REST API

Image
A couple of years ago, I published a series of posts on getting and setting taxonomy field values in SharePoint workflows by using the REST API in custom workflow activities. These custom activities have served me well, but they've always been unable to work with multi-value taxonomy fields. It's time to fix that.

Background As you probably already know, when you add a taxonomy field to a SharePoint list, SharePoint adds a corresponding hidden note field. For example, if you add a taxonomy field named Colours, you actually get:

A taxonomy field named Colours. Depending on whether the column allows the user to select multiple terms, the field accepts values of type SP.Taxonomy.TaxonomyFieldValue or Collection(SP.Taxonomy.TaxonomyFieldValue).A hidden note field, probably named Colours_0.  The hidden note field stores the contents of the field in a term string format. In a single-value taxonomy field, the format looks like this:
Red|87999a76-e3cb-433c-96ad-c6fe354db476
And in a mult…
Read more