Skip to content
Scientist Z

Scientist Z

Cloud Computing, Blockchain, AI, DevOps, Security, Software/Solution Architecture, Azure, AWS, GSP

  • Home
  • Training
  • About
  • Contact
  •  
  • $0.00 0 items

Tag: Failed to create term set: A default managed metadata service connection hasn’t been specified.

SharePoint 2016

SharePoint 2016: Error loading navigation: TermSet not found

October 5, 2017January 20, 2022 scientistz

Error loading navigation: TermSet not found

This is common scenario to move one application from one SharePoint Farm to another SharePoint Farm, in this process after restoring the database to the new SharePoint Farm following error message came at the top of the site, Error loading navigation: TermSet not found.

TermSet not found
TermSet not found

Solution:

There are couple of reasons, which could cause this issue. Please check below points.

  1. In Central Administration, Manage Service Application and make sure that Managed Metadata Service and Managed Metadata Service Connection are started.
Manage Service Applications
Manage Service Applications
  1. Click on the line of the Managed Metadata Service Connection ( not on name ) and click on Properties
Manage Metadata Service Connection Select
Manage Metadata Service Connection Select

Make sure that “This service application is the default storage location for column specific term sets.”  Is checked. If it is not checked then check it and click OK Button.

This service application is the default storage location for column specific term sets.
This service application is the default storage location for column specific term sets.

Now refresh your main site, to see the issue is fixed. If the issue is still there then proceed to next step

  1. Navigate to Site Settings of your main site (i.e. http://system/_layouts/15/settings.aspx) and Click on Navigation

    Site Settings
    Site Settings
Site Navigation
Site Navigation

Now click on Create Term Set button, if it shows success message “Successfully created Term Set” then refresh the site and issue is resolved.

If you are getting error “Failed to create term set: A default managed metadata service connection hasn’t been specified.” as shown below:

Failed to create term set: A default managed metadata service connection hasn't been specified.
Failed to create term set: A default managed metadata service connection hasn’t been specified.

 

or “A default managed metadata service connection hasn’t been specified.”

Then proceed to next step.

  1. Go to Central Administration, Configure service application associations and then click on default link as shown in pictures below:

 

Configuration service application association
Configuration service application association
Configuration service application association default
Configuration service application association default

Make sure that the Metadata Service Application Connection is checked and click OK.

  1. Configuration service application association default MMS
    Configuration service application association default MMS

    Go back to the navigation settings (~/_layouts/15/AreaNavigationSettings.aspx) and Create Term Set; it will create the System Navigation successfully.

    Successfully created term set
    Successfully created term set

Successfully created term set

  1. Error loading navigation: TermSet not found is resolved. 

    Solved : Error loading navigation: TermSet not found
    Solved : Error loading navigation: TermSet not found
Tagged A default managed metadata service connection hasn’t been specified, Azure Function, Failed to create term set: A default managed metadata service connection hasn't been specified., TermSet not found after database restore1 Comment

Recent Posts

  • How to install Redis on windows WSL
  • Solved: Add-Migration initial -v Build started Build failed or Update-Database Failed
  • Solved: Reason: The response was received at http://somsite/oauth2/callback/saml instead of https://somsite/oauth2/callback/saml in SonarQube
  • How to configure Build Agent to Use Proxy Azure DevOps Server
  • Solved : The folder you specified for the Search index is not empty. Change your configuration setting to specify an empty folder for the index store Elastic Search

Recent Comments

gregtrevellick on Solved: No agent found in pool…
Sampath on How to serve WOFF fonts from A…
Caio on Solved: No agent found in pool…
admin on How to setup your Open API in…
Muhammad Zaheer Nazi… on How to install Application Ins…

Archives

  • August 2022
  • June 2021
  • June 2020
  • May 2020
  • July 2019
  • June 2019
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • October 2017

Categories

  • Azure API Management
  • Azure App Service
  • Azure Blob
  • Azure Cloud
  • Azure Cloud Services
  • Azure Cosmos DB
  • Azure DevOps Server
  • Azure Function
  • Azure SQL Database
  • Azure Storage
  • CICD
  • Cloud Computing
  • Cloud development Patterns
  • Development
  • Dotnet-Core
  • Entity Framework
  • Installation
  • Redis
  • SharePoint 2016
  • SonarQube
  • SonarQube
  • TFS Migration to Azure DevOps Server
  • Uncategorized
  • Visual Studio
  • VSTS
Powered by WordPress.com.

This is an example of a sitewide notice - you can change or remove this text in the Customizer under "Store Notice" Dismiss