Home‎ > ‎

Initialize-SPResourceSecurity and IISRESET fix inaccessible new Term Store

posted Oct 19, 2016, 12:43 AM by Benny Skogberg
We've all seen this in a new farm, and it's annoying.

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.

And so far I've been unable to solve this, permanently. You check the application pool, services.msc, services on server, database login user mappings, and everything is OK. But today I saw this comment on the post SharePoint Error : The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started

It says: 

Robin Willems
August 19, 2015 at 1:08 am
I was getting "Failed to get term store for proxy ‘Managed Metadata Service Application Proxy’. Exception: System.Security.SecurityException: Requested registry access is not allowed"

It was fixed by Running Sharepoint Management Shell (Powershell) and Type

Initialize-SPResourceSecurity <enter>

After that i did an IISRESET /noforce and it was fixed.

Without having much hope I run:
PS C:\> Initialize-SPResourceSecurity
PS C:\> IISRESET

Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted
PS C:\>

Reload the Term Store - and it just worked. One wonder why this isn't initiated by default after creating a new service application? Anyway - this does the trick when installing using AutoSPInstaller in a SharePoint Server 2016 Farm.

Reference:
Initialize-SPResourceSecurity
Comments