.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

The Managed Metadata Service or Connection is currently not available.

Posted By:      Posted Date: September 28, 2010    Points: 0   Category :SharePoint
I've been trying to create new Managed Metadata services but get this error when trying to manage them:
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.

I've checked that the application pool that the Metadata service uses is running and that the account it's running under is in the farm administrators group. I've checked that the WCF hotfix is applied on the system by re-downloading KB971831 (I have Windows 2K8 SP2) and trying to run it again but it says it doesn't apply to my system (as I had installed it before installing SharePOint)

I'm not sure what else to do - can anyone give any pointers?


View Complete Post

More Related Resource Links

Sharepoint 2010 - The Managed Metadata Service or Connection is currently not available. The Applica

So I've already installed hot fix http://support.microsoft.com/kb/976394.  Rebooted server and I still get this message.  The account being used is part of local adminstrators group and has full connection permissions for managed metadata service.  Is there anything else I'm missing or needs to be done?

Managed Metadata Service or Connection is currently not available

In service applications this is listed as stopped. Under services on this server it is listed as started. I get the folowing message when I open properties from the service application then click 'ok' Object reference not set to an instance of an object.   Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 10df60d7-a00e-4bb2-9d5c-156a5a15c5f1 Date and Time: 9/13/2010 4:52:25 PM   I have all required KB' hotfixes, the account being used to connect to SQL is working for all other services, the account has local admin rights. THis is a fresh install. I get the error  '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' When I go into Term Store Management   Any help on this?

Service Application Connection: Managed Metadata Service is inaccessible


 Hello all,

I have published the MMSA in one farm so it can be connected to and consumed by another farm. The publishing farm URL is https (SSL) and the consuming farm is http (Non-SSL). The connection to the MMSA shows in Central Admin as succesful, however when I try to open the Managed Metadata in the term store in the consuming farm I get the following error:

"The Managed Metadata Service is inaccessible because the current web application has not been granted permissions to access it."

I followed all the steps in technet, including the certificate exchanges and the publishing farm MMSA has granted the consuming farm full control.


Any clues? Can a farm with SSL publish service applications to non-SSL farms?


Update Managed Metadata Field with using Lists.asmx service

Hello! I am trying to update Managed Metadata Field with using Lists.asmx. I know that I must use this format WSSID;#VALUE|GUID. But I don't Know how I can get WSSID and VALUE Guid! Can I get them with using lists.asmx! Thanks!!

Is it possible to implement your own version of the Managed Metadata Service?

Hi, It would be nice to provision a new instance of the Managed Metadata Service where the service is not implemented by Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication, but a custom provider. Is it possible to expose your own service as a Managed Metadata Service?

Proxy Managed Metadata Service Error

Hi I've deleted my web apps installed a language pack and then I've created new web apps and site collections on them with the new language (not reinstalling all again). On my portal I've made a Content type based on Document Set with a few Custom columns based on some taxonomy created before. My problem is that the new Content type was created like one which was created before deleting my web apps (the custom columns are the same), and now when I publish it the other web app is importing the old content type first (FROM WHERE I DON"T KNOW) and when tries to import the new one (which has a column with the same name) the Proxy Managed Metadata Service gives an error 'Filed internal name conflict.....' If I click on managed Metadata Service url http://portal/_layouts/mngctype.aspx  the old Content type of course that it's not present. Where should I search for it to delete it ? Thank's  Sorin Sandu

Managed Metadata Service - No EMM application proxy can be found



I have Managed Metadata Service configured with the default language German and the target Content Hub it also in German. When I try to publish a content type i got this error "cannot check for changes because no emm application proxy can be found". Any ideea?


Managed Metadata Service



I have some problems configuring the Managed Metadata Service and help would be appreciated.

I managed to add a new group into the Term Store Management Tool, with my own personal structure, not a problem here.
But when I go to a document library or list and I want to make a new colomn of type Managed Metadata, then the problems begin. The notification 
"The required feature is not enabled for this column type." appears in the manage term set search box, but I cán search and find my defined taxonomy. When I try to OK this, following message (under this manage term set box) appears : "The Taxonomy feature (Feature ID "73EF14B1-13A9-416b-A9B5-ECECA2B0604C") has not been activated.".

I'm not able to find this specific feature and have every other feature necessary for the managed metadata options turned on.

Anyone has an idea of what went wrong here?


SharePoint 2010 Search Service - does not escape forbidden signs in Managed Metadata fields



I´m using SharePoint 2010s Search Service to get items from a list. In the list I have managed metadata field for Item. When I search on Item "Item 1 & 2" I get xml that is incorrect. SharePoint does not escape the &. (The mapping is correct so when I search on an item not containg & it returns correct xml.)

But if I in my description field writes "A description & some more text" then & is escaped.

Anyone seen this before? Is there some way to configure the search service to escape forbidden signs to return none broken xml?


Sharepoint 2010 Missing Managed Metadata Service


According to the following MS article, the Tags feature is linked to the Managed Metadata Service, which is required to use Tags. For some reason I cannot find this feature as described in the article where it specified Managed Metadata Service is located in the Application Management section. What should I check to make sure this feature/service can be enabled?



Managed Metadata Service: Cannot check for changes because no EMM application proxy can be found


We have a managed metadata service with two owners. Both of them can't change anything to the term store anymore. The moment they try they get access denied:

The user doesnt have enough permissions. When looking into the log of SharePoint i found the following message:

Cannot check for changes because no EMM application proxy can be found

When I try to add another administrator using the Install_Admin account (who is farm admin) I get the same message that the user doesnt have enough permissions.

Our term store is setup in multiple languages with Dutch being the primary one.

Any help much appreciated.


Publishing the Managed Metadata Service, through a firewall to another AD Forrest - fun and games...


Hi People,

we've got two SP2010 Farms in two separate AD Domains/Forrests, which are connected via a firewall and there is no trust at the AD level.

Both farms consist of an App Server (Central Admin and all Service Applications) and a WFE (Content plus Query/Index role).

The Managed Metadata Service on Farm A is published through to Farm B and so we've had to open up ports through the firewall so the App Server in Farm B can talk to the SharePoint Web Services on Farm A (32843, 32844 and 32845) and that all appears to be working properly, even to the extent that the Content Deployment from Farm A to Farm B is also working and the managed properties in the content are all being mapped/managed correctly.

However I'm now seeing requests by the the WFE in Farm B to access the topology service running on WFE in Farm A! Hold on!
As it was, I already had to allow both the App Server and the WFE in Farm B to be able to access the SharePoint Web Service ports on the App Server in Farm A, and now I have to do the same for the WFE in Farm A?!?!? That can't be right.

Isn't the whole point of having proxy services, Central Admin and an App Server (hosting all the services) that you only have to open up a single server? Why does every machine in one farm have to know about every machine in another farm?

Talk about a firewall mana

Managed Metadata Service Application Problem



I've been trying for a whole day to configure managed metadata services on a windows server 2008 R2 environment but I keep getting this error:

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.

I've tried searching for a resolution and here's what I got:

  1. Change the application pool account / Check that the pool is running.
  2. Download hot fixes KB981002 and KB976462.
  3. IISRESET / Restart the server.
  4. Ensure that Managed Metadata service is running.

The third solution worked for me in my development environment which is Windows 7, but I couldn't get it to work in Windows server 2008 R2 which is the production environment.

Any help would be appreciated :)

SOA Simplified: Service Virtualization With The Managed Services Engine


By using Managed Services Engine service virtualization technology, you can begin participating in the cloud by simply configuring virtual service endpoints and operations that integrate with the .NET Service Bus.

Aaron Skonnard

MSDN Magazine May 2009

Service Station: The Application Connection Designer


In some of my past columns on service orientation and contract-first development, I've mentioned the new suite of designers, formerly codenamed "Whitehorse," that are part of Visual Studio® Team edition for Software Architects Team System.

Aaron Skonnard

MSDN Magazine August 2005

How to maximize use of managed metadata in the document library?

We are creating new Intranet portal based on SharePont 2010 and we have document library with 100-200 documents. Old Intranet is based on previous version of SharePoint. End-users did not like the usability of the document library as it was hierarchical. Users needed to know, which was the folders and its subfolder to find out where is the document. We are currently investigating if we can solve this problem by using managed metadata. We know how to define term set and how to give metadata to the document, but we don't know what is the most usable way to utilizem them in the document library. Let say that end-user would like to see all documents that has managed metadata "User Guide". How to configure document library so that users see only those documents. Not all our users are skilled and we have to provide very intuitive way to search relavant documents to them. Some predefined metadata dropdown would be great.Kenny_I

Setting Managed MetaData default values on site creation

I am working on a project where the requirement is to have specific document content types.  I have therefore create a site columns feature which creates all my columns, I have a Site Contentypes feature which creates all my content type and I have list templates based on my content types.  I also have created a couple of Site definition features which create specific list instance based on my list template As part of my content types I have created a few Managed Metadata fields which I wanted to set defaults for on the creation of my sites.  I have therefore created a feature which is right at the end of the WebFeatures section in my ONET.xml.  This features enumerates through all lists, looking for specific column names(managed metadata columns) and looks to set these to specific values.  The code to set the default value on the field is: TaxonomyField documentCategoryField = (TaxonomyField)library.Fields["Document Category"]; if (documentCategoryTerm != null) { documentCategoryField.DefaultValue = documentLibraryDefault.ToString(); documentCategoryField.Update();                                                     }                         &n
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend