I am having a really strange issue with Managed Metadata. I get the classic Error “The Managed Metadata Service or Connection is currently not available” which is usually a permission issue.
However, all the good accounts have permission. In the ULS Logs this is what I found :
Failed to get term store for proxy ‘Managed Metadata Service’. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at Microsoft.SharePoint.Taxonomy.Internal.XmlDataReader.GetDateTime(String name)
at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore.Initialize(IDataReader dataReader, Guid termStoreIdValue, Boolean fromPersistedData)
at Microsoft.SharePoint.Taxonomy.Internal.SharedTermStore..ctor(IDataReader dataReader, Guid termStoreId, Boolean fromPersistedData)
at Microsoft.SharePoint.Taxonomy.Internal.DataAccessManager.GetTermStoreData(MetadataWebServiceApplicationProxy sharedServiceProxy, Boolean& partitionCreated)
I only found 1 blog post on the issue: http://sharepointbabe.blogspot.ca/2013/04/upgrade-managed-metadata-service.html however I was maybe trying to fix before recreating. And for me it’s pure 2013.. no 2010 in there!
So I have a client that has the same issue. This famr may have been a little unique and that helped with tracking down the issue. After reading all the posts and realizing that I am not sure if there is content in the databases right now, I decided to check the service applications and the proxies. What I found was interesting.
I used get-spserviceapplicationproxy to get list of all proxies
Then I used get-spserviceapplicaitonproxy [GUID of Metadata proxy] | fl
This lists all the properties for the proxy. I noticed that the ServiceendpointUri property still points to the old application server name (which no longer exists). I don’t have a resolution to fix it yet, but at least if someone comes looking here, they may have more information to work with.
I had this issue in 2 completely different farms now. And there is no clear indication why this occurs. It worked perfectly for some time and then suddenly, this error occurs. And it still occurs after SP1 !!!
Deleting the Managed Metadata Service application and reusing the database is not an option. You still have the same error… even after rebooting the server.
The only solution to get it running again is to completely create from scratch with a brand new database.
So my advice… make sure you schedule an export of your Managed Metadata on a regular basis. That way, if you have to recreate it from scratch, you can import that data. Saves you from an end-user posse which will be coming for you. 🙂
Doing an export is easy. You can do it using PowerShell.
I got the same error, unfortunately I had to recreate the Service Application from scratch. Using the old database lead me to the same error.
The only thing that I can add to the thread my farm has been recently updated with the October 2013 CU, even if I don’t think this could be the root cause.
Recreate the SA using the same DB! Why is that not an option? you don’t lose the data!