Managed MetaData Service

Is there any way around the limit of 20,000 items for the managed terms?
Managed terms (does not include enterprise keywords)
20,000 (20 per term set)
I need some input on this before I can proceed with migration from 2007 to 2013.

Where are you seeing that limit? The official boundaries and limits doc says 30,000 items in a term set and 1,000,000 terms total.
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#termstore
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

SP 2010 in win 8.1 - Managed Metadata service issue

I recently installed SP 2010 in my WIN 8.1. Installation was successful and I am able to create and modify sites etc. I am able to deploy solutions via VS2010 as well. all are working fine.
issue 1:
BUT in Central Admin - when I go to Managed Metadata service - I get"The server Method 'Check Permission' failed".
in the ULS log I see
Request for security token failed with exception: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of
the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
http//www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd> <html xmlns=http://www.w3.org/1999/xhtml> <head> <title>IIS 8.5 Detailed Error - 500.0 - Internal Server Error</title> <style type="text/css">
<!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code...
Exception occured while connecting to WCF endpoint: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of
the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd> <html xmlns=http://www.w3.org/1999/xhtml> <head> <title>IIS 8.5 Detailed Error - 500.0 - Internal Server Error</title> <style type="text/css">
<!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source co...
issue 2:
I then clicked "managed meta data service connection" and at that point I get
"The remote server returned an error:
(500) Internal Server Error" with correlation ID - logs below
An exception occurred when trying to issue security token: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1).
If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd>
<html xmlns=http://www.w3.org/1999/xhtml> <head> <title>IIS 8.5 Detailed Error - 500.0 - Internal Server Error</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;}
code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;...
WHAT I DID: I included all file extentions like "aspx", "json", "svc" etc. but no luck.

Hi,
Please browse the below URL
Issue 1
http://blogs.technet.com/b/sykhad-msft/archive/2012/02/25/sharepoint-2010-nailing-the-error-quot-the-security-token-service-is-unavailable-quot.aspx
Issue 2
.Net trust level for Security token service application in IIS may be not set to Full
Thanks and Regards Rahul Dagar

The Managed Metadata Service or Connection is currently not available.

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?
Thanks

I've got the default one working again now, the new one "TM Metadata" has been added but shows the same error on the management page.
I have some info from the logs:
Failed to get term store during cache check for changes. Proxy 'TM Metadata'. Exception: System.ServiceModel.ServerTooBusyException: The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.     at System.Net.HttpWebRequest.GetResponse()     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)     --- End of inner exception stack trace ---    Server stack trace:      at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)     at System.ServiceModel.Channels.HttpChannel...
01/06/2010 15:38:18.98*    w3wp.exe (0x123C)                           0x079C    Office Server                     Taxonomy                          ch90    Monitorable    ...Factory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)     at Syst...
01/06/2010 15:38:18.98*    w3wp.exe (0x123C)                           0x079C    Office Server                     Taxonomy                          ch90    Monitorable    ...em.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)     at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustClient.Issue(Message message)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustClient.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustClient.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)     at Microsoft.SharePoint.SPChannelFactoryOperations.InternalCreat...
01/06/2010 15:38:18.98*    w3wp.exe (0x123C)                           0x079C    Office Server                     Taxonomy                          ch90    Monitorable    ...eChannelActingAsLoggedOnUser[TChannel](ChannelFactory`1 factory, EndpointAddress address, Uri via)     at Microsoft.SharePoint.SPChannelFactoryOperations.CreateChannelActingAsLoggedOnUser[TChannel](ChannelFactory`1 factory, EndpointAddress address)     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.GetChannel(Uri address, Boolean& cachedChannel)     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2c.<RunOnChannel>b__2b()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePo...
01/06/2010 15:38:18.98*    w3wp.exe (0x123C)                           0x079C    Office Server                     Taxonomy                          ch90    Monitorable    ...int.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2c.<RunOnChannel>b__2a()     at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)     at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.RunOnChannel(CodeToRun codeToRun)     at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyProxyAccess.GetChanges(Nullable`1 rawPartitionId, DateTime sinceTime, Nullable`1 groupId, Nullable`1 termSetId, Nullable`1 changedItemType, Nullable`1 changedOperationType)     at Microsoft.SharePoint.Taxonomy.Internal.DataAccessManager.GetChanges(Boolean forAllPartitions, DateTime sinceTime, Nullable`1 groupId, Nullable`1 termSetId, Nullable`1 changedIte...
01/06/2010 15:38:18.98*    w3wp.exe (0x123C)                           0x079C    Office Server                     Taxonomy                          ch90    Monitorable    ...mType, Nullable`1 changedOperationType)     at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyCache.CheckForChanges()
UPDATE : I've just gone back to IIS to check the pools and it looks like adding the 2nd metadata store has knocked out the app pool that the SecurityTokenService runs in.

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.

Hi,
I'm not able to access the term store. I get an below mentioned 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. "
Since this is happening on my local machine (Dev environment). I have full control on the term store and the all the site collections.
Hence, this is not a permission issue.
I have checked, the Metadata service is active on the machine. All the application pools in IIS is running.
After reading one of the recommendation on internet, I created a new Managed Metadata Service.
After which I was able access both (old and new) MMS from Central Admin only (highlight the MMS from manage service applications and click Manage ) and not from the site collection (term store management).
Now again its not working after I did an IISRESET.
The managed metadata service (Managed Metadata Service Connection) is grayed out.
ULS Error says:
Failed to create ManageLink for service proxy 'Managed Metadata Service'. Exception: System.TimeoutException: The request channel timed out attempting to send after 00:00:09.9999999. Increase the timeout value passed to the call to Request or increase the SendTimeout
value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://mitkar4:32843/7a91ec90b46843e995c144be48d804f0/MetadataWebService.svc' has exceeded the allotted
timeout of 00:00:09.9990000. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
Please let me know if you need more information.

Hi Victoria,
Thanks for your reply
I tried making all the changes you had recommended and which are mentioned in the link you have provided.
I tried making all possible combination of changes to the web.config and client.config files but it does not make any difference to the environment.
One thing is that, my error in ULS logs has changed.
Error 1:
Exception returned from back end service. System.TimeoutException: The request channel timed out attempting to send after 00:00:09.9999999. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted
to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://mitkar4:32843/b1640facdf8b49b0886fea1bd37b8eb3/MetadataWebService.svc' has exceeded the allotted timeout of 00:00:09.9990000. The time
allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() --- End of inner exception stack trace ---
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace:
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication.GetServiceSettings(Guid rawPartitionId)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2f.<ReadApplicationSettings>b__2e(IMetadataWebServiceApplication serviceApplication)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2c.<RunOnChannel>b__2b()
Error 2:
Error encountered in background cache check System.TimeoutException: The request channel timed out attempting to send after 00:00:09.9999999. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time
allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://mitkar4:32843/b1640facdf8b49b0886fea1bd37b8eb3/MetadataWebService.svc' has exceeded the allotted timeout of 00:00:09.9990000.
The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() --- End of inner exception stack trace ---
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace:
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication.GetServiceSettings(Guid rawPartitionId)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2f.<ReadApplicationSettings>b__2e(IMetadataWebServiceApplication serviceApplication)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2c.<RunOnChannel>b__2b()
at Microsoft.Office.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.<>c__DisplayClass2c.<RunOnChannel>b__2a()
at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.RunOnChannel(CodeToRun codeToRun, Double operationTimeoutFactor)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.ReadApplicationSettings(Guid rawPartitionId)
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.get_ServiceApplicationSettings()
at Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy.TimeToCheckForUpdates()
at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyCache.CheckForChanges()
at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyCache.<LoopForChanges>b__0().

Managed Metadata Service and Content Type Hubs - Service Connection necessary?

I created a site collection and activated the content type hub feature at the site collection level. We have an existing managed metadata service but I am unable to edit its settings, so I created a new MMS in a new database, however; there is no "service
connection" row below the MMS row for the new MMS Application, but there is one for the old MMS Application. Will this still work with my content type hub? If not, how can I get the service connection setting/row? I have to do this via PowerShell since
the menus in the ribbon are not usable due to our JavaScript settings...

Are you using Custom claim provider??
If you are then try this:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/120ab535-63d2-4205-a51f-1987e9c0cf79/sharepoint-fba-the-content-type-texthtml-charsetutf8-of-the-response-message-does-not-match-the
http://www.chapmanconsulting.ca/post/2010/04/23/The-Case-of-the-Failing-SharePoint-2010-FBA-Configuration.aspx
#RoHsTr

User Profile Application and Managed Metadata services are missing

Running SharePoint 2013 servers on a set of 2012 R2 Servers. One of our farm administrators deleted the Secure Store service account. They recreated the Secure Store account, but after doing so, the Managed Metadata Service and User Profile Service
are now unavailable.
When going to the User Profile Page, there is an error that says "Sorry, something went wrong."
When going to the Metadata page, there is an error that says "The Managed Metadata Service or Connection is currently not available."
There is an additional error that says "The Security Token Service is not available."
How can all three services be brought back online?

That specific event log error is as follows:
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/12547953
Exception: System.ServiceModel.ServiceActivationException: The service '/SecurityTokenServiceApplication/securitytoken.svc' cannot be activated due to an exception during compilation. The exception message is: Exception has been thrown by the target
of an invocation.. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: certificate
   at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate, String id, Boolean clone, Boolean disposable)
   at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate)
   at Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceManager.ConfigureTokenHandlerCollection(SPSecurityTokenServiceManager manager, SecurityTokenHandlerCollectionManager collectionManager, String key, SecurityTokenHandlerCollection&
tokenHandlerCollection)
   at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceConfiguration.ConfigureTokenHandlerCollectionForLocalIssuer(SPSecurityTokenServiceManager manager, SecurityTokenHandlerCollectionManager collectionManager, String key)
   at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceConfiguration..ctor()
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceHostFactory.CreateSecurityTokenServiceConfiguration(String constructorString)
   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
   at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
Process Name: w3wp
Process ID: 5504

The tagging service is unavailable - Managed Metadata Service issues

After SP1 I am unable to use the tagging service in my test farm of SharePoint 2013. Users see the error message popup "The tagging service is unavailable. Please try again later."
I've ensured that the Managed Metadata service is up and running and is the location for keywords. I've tried deleting and re-creating the service to no avail.
Any ideas on what might be happening? The service looks fine, the database looks fine but no tagging....

Hi,
According to your post, my understanding is that you were unable to use the tagging service.
Per my knowleadge, even if the Managed Metadata Service is associated with the web application and term store is accessible from within the site collection, it still needs to be set as the default for the web application.
To set the service as the default you need to click on the proxy service, and then select the top two check boxes.
For more information, please refer to:
The tagging service is currently unavailable
Tagging Service is not available when using hashtags in Microblog entry
Thanks,
Jason Guo
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support
Jason - thanks for the input. Unfortunately the service was already set to the default for the web app (both top checkboxes are already checked.) The service looks identical to my Prod and DR farms, but simply doesn't work. I've blown it
away and recreated it without success.

When to use Managed Metadata service in Sharepoint 2013 and 2010

Hi Folks,
I have been working on sharepoint from quiet some time now. I have been using managed metadata service also.
What I have not been able to find out so far is when should I be using MMS.
What are the real advantages that I can draw out of it.
I have one application that has Managed Metadata installed and has various terms stores and terms.
The Managed metadata service created is utilized in search,
What I do not know is what is why are we using it at all.
What is benefit of it.
Managed metadata service could also be used in navigation is what i know.
But what confused me is when is the best scenario to use it for navigation.
Why can we not use the navigation provider in the managed metadata service.
There might be other uses also, but that is not clear to me.
Can any one tell me why and in which scenario to really use it.
I know how to configure the mms and how it works though the jargons around the managed metadata.
Regards

Managed Metadata has some specific advantages that make it useful for certain situations.
A managed metadata column has the following advantages over a lookup or choice column:
A managed metadata term set can be shared across the entire SharePoint farm, so you can use it in different site collections.
You can set up "synonyms" so that multiple similar terms resolve to the same underlying piece of information
Terms can be hierarchical (terms can be nested under other terms), and the SharePoint interface allows hierarchical filtering. For example, if I have a term set for Location, and one of my terms is North America, with terms below that for United States,
Mexico, and Canada, I could choose to filter my list to show me all records with any North America location (inclusive of US, Mexico, and Canada), or to filter on a specific term (such as Mexico).
You can allow people to enter new terms, which will then appear in the term set.
You can specify information owners/stakeholders who maintain the term sets without them needing elevated access to sites; normally only site owners can mess with site columns and content types. Managed metadata lets you separate information management
(what terms/synonyms should be used) from site management (granting access, creating groups and lists, etc).
There are some disadvantages too. For example, with a lookup column, the lookup list can store additional columns of information. A managed metadata term set (on the other hand) only really stores terms (and descriptions/synonyms), but not related
info. You might be tempted to do something like create a term set for part numbers, representing every part that your company produces; the term set would handle the part numbers just fine, but wouldn't let you add extra columns of information for
description, weight, price, etc. In such a case, a lookup list is the better option.
Microsoft has some suggested guidelines for when to use managed metadata/term store:
SharePoint 2013:
http://technet.microsoft.com/en-us/library/ee519604(v=office.15).aspx
SharePoint 2010:
http://technet.microsoft.com/en-us/library/ee519604(v=office.14).aspx
A brief summary...
Managed metadata is a good option when the potential metadata meets the following criteria:
Is something for which a user will select a valid value
Represents information that is likely to be used multiple times
Has valid values that can be organized hierarchically
Includes synonyms or abbreviations that should be aggregated
Can be applied in one language, but might be viewed in other languages
Managed metadata is not a good option if the potential metadata meets any of the following criteria:
Is represented by a built-in column (such as “last modified date”)
Has an infinite number of valid values
Has different valid values in each location that it is used (such as different values for the “version” attribute depending on which product team’s site the item appears in)*
Has only “yes” and “no” as valid values
*This type of metadata could still be captured in site collection-specific term stores

How to find ContentDb Name for any of the service application (e.g. User profile , Managed metadata , etc) programmatically in a farm ?

Hi,
I have a application where i need to display Name for all the service application. Specifically i need to get the size of user profile service application and Managed metadata service application name.
Please guide me. :)
Thanks and Regards:
Sanjay

You can use
http://blogs.technet.com/b/tothesharepoint/archive/2011/12/19/find-active-databases-used-by-sharepoint-server-2010.aspx
Get-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name”
http://webcache.googleusercontent.com/search?q=cache:kMHQXNGmjcwJ:sharepointstruggle.blogspot.com/2011/08/programmatically-enumerating-databases.html+&cd=1&hl=en&ct=clnk&gl=in
using(SPSitesite
= newSPSite(url))
using(SPWebweb
= site.OpenWeb())
SPFarmf
= site.WebApplication.Farm;
foreach(SPDatabaseServices
inf.Services.OfType<SPDatabaseService>())
Console.WriteLine(string.Format("Found
Database service {0} of type {1}",
s.Name, s.GetType().Name));
foreach(SPDatabaseServiceInstancespdsi
ins.Instances)
Console.WriteLine(string.Format("|-Found
Database Service Instance {0} ({1})",
spdsi.DisplayName, spdsi.Name));
foreach(SPDatabasespdb
inspdsi.Databases)
Console.WriteLine(
string.Format(" |-DB: {0}\r\n |-TYPE: {1}\r\n
|-HOST: {2} ",
spdb.Name.Length
> 70? spdb.Name.Substring(0,
65)
+ "...": spdb.Name,
spdb.GetType().Name, spdb.Server.Name)
http://social.msdn.microsoft.com/Forums/en-US/61e4e56e-e373-4167-ba97-e0f411feefe9/how-can-we-programmatically-find-the-names-of-sharepoint-databases

Users with read access to the site unable to view Managed Metadata Navigation

Hi everyone,
I created a Managed Metadata service and created group, term-set and terms
I gave read access to users
I set up navigation to use Managed Navigation
I am logged in as farm admin and able to view the navigation when i browse site. But user are not seeing navigation.
One thing i noticed is when i give users full access or designer access to site they will be able to see the navigation. but i don't want to give users full access or designer access to the site.
How can users with read only access to site can view Managed Metadata Navigation...Please help?

Hi Sunil,
Have you given your users permissions to actually read the MMS data from the service application?
http://technet.microsoft.com/en-us/library/ff625176.aspx covers permissions on the MMS.
Regards
Paul.
<<edit>> On reflection you might be hitting the issue in this Stackexchange post..
http://sharepoint.stackexchange.com/questions/75636/permissions-and-managed-metadata-in-navigation Is yours behaving the same way?
Please ensure that you mark a question as Answered once you receive a satisfactory response. This helps people in future when searching and helps prevent the same questions being asked multiple times.

How to create a managed metadata column in sharepoint document library programmatically

Hi,
I want to create a column of type "Managed metadata" in a document library.
I am new to managed metadata and its basics. So i need to know what it requires to create it. i got this
1. Create a term set Group.
2. Create term set.
3. Create a term.
I am using sharepoint foundation where "Term Store Management" service is not available.
I am writing this code for OFFICE 365. So can write a code with prediction, assuming i have basic info required to run my code?
var termStore = session.TermStores["Managed Metadata"];
var group = termStore.Groups.GetByName("KB Submission Policy");
var termSet = group.TermSets["KB"];
Can write this code with respect to screen shot as follows in my term store
Please reply...

Hi,
Please check this
http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2011/08/03/sharepoint-2010-cookbook-programmatically-create-term-sets-amp-metadata-columns-in-managed-metadata-service.aspx
Please remember to click 'Mark as Answer' on the answer if it helps you

Updating a managed metadata column from choice column value

I am trying loop through
all lists in a web, and for each list,
1. create a managed metadata column->Working
2.
Pull value from choice column->Working
3. Move
choice column value to managed metadata column->Not Working
Point number 3 is not working. Please advise
Here is the code:
static void Main(string[] args)
//Pulling the rootweb of the Site
const string SPLocationListColumn = "CHECK6";
SPSite site = new SPSite("http://sp2010:8080");
SPWeb rootweb = site.RootWeb;
//Setting up the taxonomy terstore, termset and term
Microsoft.SharePoint.Taxonomy.TaxonomySession taxonomySession = new Microsoft.SharePoint.Taxonomy.TaxonomySession(site);
TermStore termStore = taxonomySession.TermStores["Managed Metadata Service"];
Console.WriteLine(termStore.Name);
Group group = termStore.Groups["KM Metatags"];
Console.WriteLine(group.Name);
TermSet termSet = group.TermSets["Document Classification"];
Guid termsetid = termSet.Id;
Console.WriteLine(termSet.Name);
Term term = termSet.Terms["Document subclassification"];
TermCollection terms = termSet.Terms;
Console.WriteLine(term.Name);//Looping through all webs of the input website
SPWebCollection collWebsite = site.AllWebs;
for (int i = 0; i < collWebsite.Count; i++)
using (SPWeb oWebsite = collWebsite[i])
//Looping through all lists in web
SPListCollection collList = oWebsite.GetListsOfType(SPBaseType.DocumentLibrary); ;
for (int j = 0; j < collList.Count; j++)
SPList list = collList[j];//if the list name is Documents, create a new field of MMS type
if (list.Title == "Documents")
Console.WriteLine(list.Title);
TaxonomyField field = list.Fields.CreateNewField("TaxonomyFieldType", SPLocationListColumn) as TaxonomyField;
field.SspId = termSet.TermStore.Id;
Console.WriteLine(termSet.TermStore.Id);
field.TermSetId = termSet.Id;
Console.WriteLine(termSet.Id);
field.AnchorId = Guid.Empty;
try
{//Add the newly added MMS field to default view
Console.WriteLine("Entering");
Console.WriteLine("Entering");
list.Fields.Add(field);
Console.WriteLine("Entering");
Console.WriteLine("Entering1");
SPView view = list.DefaultView;
Console.WriteLine("Entering2");
list.Update();
SPViewFieldCollection collViewFields = view.ViewFields;
collViewFields.Add("CHECK6");
Console.WriteLine("Entering3");
view.Update();
Console.WriteLine("Entering4");
catch (Exception e1)
Console.WriteLine(e1.Message);
}//Capture a choice field by name subclass and move it to the newly added MMS field
for (int f = 1; f < list.ItemCount; f++)
if (list.Title == "Documents")
Console.WriteLine(list.Title);
SPListItem item = list.Items[f];
if (item.Fields.ContainsField("subclass"))
SPField field9 = item.Fields["subclass"];
String subclassvalue = field9.GetFieldValueAsText(item["subclass"]);
Console.WriteLine(subclassvalue);
TaxonomyField taxonomyField = item.Fields["CHECK6"] as TaxonomyField;
TaxonomyFieldValue taxonomyFieldValue = new TaxonomyFieldValue(taxonomyField);
taxonomyFieldValue.TermGuid = term.Id.ToString();
taxonomyFieldValue.Label = subclassvalue;
taxonomyField.Update();
item.Update();
list.Update();

From here:
http://www.c-sharpcorner.com/uploadfile/anavijai/programmatically-set-value-to-the-taxonomy-field-in-sharepoint-2010/
taxonomyFieldValue.TermGuid = term.Id.ToString();
taxonomyFieldValue.Label = term.Name;
SPListItem item = list.Items.Add();
# item["Title"] ="Sample";
item["TaxonomyField"] = taxonomyFieldValue;
item.Update();
list.Update();
it appears you're missing the point where you assign that taxonomyFieldValue to the item's taxonomy field in question.

Managed Metadata appearing in wrong columns after Restoring a site to a new Site Collection

I've restored a site with some libraries that have Managed Metadata (MM) columns from one site collection into another site collection inside the same web app so it should all subscribe to the same Managed Metadata
Service Application.
There are two MM columns in one library, one holds a single value which is what type of document it is, the other is a general tag field that allows the user to add multiple MM values to it if they want.
What we've found is that data has randomly disappeared on some MM fields, on others it appears in the wrong column, and in other cases it appears fine.
I used native out of the box GUI backup and restored with the command line,
I've done it twice with the same result, so it’s not a one off corruption during backup. It's the same story in a different doc library based on different term sets as well.
Of all the things to not work properly, MM was probably last on my list to expect, it's knocked my confidence in it a bit, as well as worried me about future upgrades.
If anyone has any ideas over what may be the cause of this, it would be appreciated, I've read lots of blogs, but nothing quite like this has cropped up.
Thanks,
Jon

Most of the ISV offerings will allow you to 'Migrate' content from one SP location to another. I'm pretty sure AvePoint and a few others have tools specifically developed for shifting bits and pieces around SharePoint farms.
It is a limitation but the ISV tools tend to do a good job and maintain nearly full consistency.
There's scripts around that can do much/most of the migration and you could always extend them to do the same things as the ISV migration tools however the cost to do so can quickly get to the same ballpark as buying an already made tool.
Paul is also in the London office, we often work together when projects requiring his brains and my beauty crop up.

Managed Metadata Navigation not showing to users

I created a Managed Metadata service and created group, term-set and terms
I gave full access to application pool service account. read access to all the users via AD Security Group.
I set up navigation to use Managed Navigation (Managed Metadata Service).
I am logged-in as farm admin and able to view the navigation when i browse site. But user are not seeing navigation.
i went to the hidden taxonomy list and gave read access to all users. but this didn't help.
One thing i noticed is when i give users full access or designer access to site they will be able to see the navigation. but i don't want to give all users full access or designer access to the site.
Am i missing anything here? Please help!!!!

Hi prakasnh,
According to your description, you have created a Managed Metadata service and created group, term-set and terms, but the users who have read access, were not seeing the navigation.
How did you grant the read access to the users? By a group or directly?
For resolving your issue, please add the users to the site Visitor group, and compare the result.
Here is a similar post for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/d2aa85e1-93e0-4e12-8389-28e13b11e877/managed-metadata-navigation-permissions-issue?forum=sharepointadminprevious
I hope this helps.
Thanks,
Wendy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Sharepoint 2013 Publish ContentHub Error Metadata web service application proxy Metadata Service Application Proxy.

I'm trying to republish the content hub but getting mms errors. I checked the coorlation id but make no sense of it. Any help would be appreciated.

Hi,
According to your post, my understanding is that you failed to republish the content hub.
I recommend to execute the following PowerShell command to add all permissions needed:
Initialize-SPResourceSecurity
In addition, you can create a new managed metadata service application and also a new application pool account to check whether it works.
More information:
Troubleshooting “The Managed Metadata Service or Connection is currently not available in SharePoint
2013”
Upgrade Managed Metadata Service App
Migrate Managed Metadata Service to SharePoint 2013 error
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Managed MetaData Service

Similar Messages

Maybe you are looking for