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.

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." appears with various possible ways. I have tried googling and everybody has given a solution to provide permission to Managed Metadata Service Application. But, this didn't fix my issue.
I have looked at the ULS logs, it gives me access error as below.
Exception occured while connecting to WCF endpoint: System.ServiceModel.Security.SecurityAccessDeniedException: Access is denied.    Server stack trace:  
The below are possible solutions for this issue.
Solution 1:  Check your IIS and check IUSR is added in Anonymous Authentication. Here are the steps.
  • Open the IIS and click on ServerName in left pane. Now Click on Authentication in middle pane as shown in below screenshot.
8206.IIS

Right Click on Anonymous Authentication and select Edit option.

2548.IIS1
  • Click on Specific User radio bution and click on Set Button. The below dialog appears. Type IUSR in user name field and click on OK button.
  • Here is the below screenshot once you set the IUSR user. Click on OK button. Now, you try to navigate managed metadata service from central admin. This will fix your issue.
5775.IIS3

Solution 2: Could be a permission issue on Managed Metadata Service Application. Check the below link for the fix.

1. Go to SharePoint Central Administration Site –> Application Management –> [Service Applications] –> Manage service applications
2. Highlight the Managed Metadata Service that your web application is associated with. (Do not click on the link, just click somewhere else on that row to highlight it)
3. Click on Permissions button in the ribbon area.
4. Add the application pool account used by your web application and give it at least ‘Read Access to Term Store’

5633.image_38698CE7

5. click OK
More Info :
http://blogs.msdn.com/b/allenwang/archive/2011/03/22/the-managed-metadata-or-connection-is-currently-not-available.aspx

Solution 3: Issue could be Managed Metadata Service wouldn't have started. Check the below link for the fix.

Resolution: Make sure the managed metadata service is already started. 

How to check this:-
Central Administration -> manage services on server -> managed metadata service -> start
Once the service is in started mode then check the results again by clicking on the managed metadata service application, it has to open the page without any errors\exceptions.
If you face the same error message as mentioned above then please execute IISRESET once and that’s it. More Info: http://sharepointknowledgebase.blogspot.co.uk/2013/04/the-managed-metadata-service-or.html

Solution 4: Low Disk Space in database Server. Check your disk space in database server.
Solution 5: Check the database permission of the farm account

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read