Sometimes the Managed Metadata Service can be tricky. Maybe it’s one of the SharePoint services that are more delicate, displaying a lot of error messages like the one this post is about: “There are no addresses available for this application”. This problem just happened when I was going to define my Service Connection through Central Admin.

Opening Properties for the Managed Metadata Service

Opening Properties for the Managed Metadata Service

All of suddenly the error message below appeared and it frustrated me a lot. My first Google results were talking about the User Profile Service Application and they didn’t helped that much.

Sorry, something went wrong...

Sorry, something went wrong…

Contextualizing

First of all, the Managed Metadata Service Application was provisioned by default and its service was Online. As you can see in the next image, the Managed Metadata Web Service was flagged as Auto Provision. Finally, it’s an on-premises deployment running SharePoint 2016.

Services in Farm

Services in Farm

Troubleshooting

Since I was in need of using the service as soon as possible, my first attempt was checking if the Service was created and not corrupt. To accomplish it I’ve executed the script that behaves like that:

  • Initializes all the parameters;
  • Imports the SharePoint snapin for Powershell;
  • Checks if the Managed Service Application exists;
    • If not then creates it;
  • Checks if the Managed Service Application Proxy exists;
    • If not then creates it;

Creating the Managed Metadata Service Application with Powershell

Creating the Managed Metadata Service Application with Powershell

It turned out that the Proxy wasn’t created and I was going to need it. So the script helped me on creating it.

Unfortunatelly, the problem persisted. So I decided to fight in another front and check if the Service was Online by Powershell. Using the script below the service was finally provisioned. The script does the following tasks:

  • Initializes all the parameters;
  • Gets the Managed Metadata Web Service;
  • Checks if it exists, if not then throws an error;
  • If its Disabled, then Starts the Service;
  • If its Online, then Restarts the Service;
  • In both cases it tries to Provision the Service;
  • Awaits until the Service is online.

Provisioning the Managed Metadata Web Service

Provisioning the Managed Metadata Web Service

After applying this script the Managed Metadata settings was functional again!

Managed Metadata Service Connection properties

Managed Metadata Service Connection properties

Final thoughts

Hopefully I could recover this Service Application without needing to recreate everything. It can be useful in cases where the Managed Metadata Service Connection is highly customized and the proccess of recreating it requires attention while keeping the existing Managed Metadata database untouch.

Hope it can help you in your SharePoint adventures. If you have any doubt or opinion about the Powershell snippets, please let me know in the comment section!

See you in a next post!

References:

Script a Metadata Service Application using PowerShell

SharePoint Services Stuck in Provisioning