We are keep getting The Managed Metadata Service 'Managed Metadata Service' is inaccessible. (EVENT id:8088)

after few minutes The Managed Metadata Service 'Managed Metadata Service' has connected successfully.(event ID:8090).

this causing SharePoint site outage and slowness. how to fix above issue Permanently.

Steps taken so for:

Provide permissions 'Managed Metadata Service' service App Pool identity on 'Managed Metadata Service' service application.

Reenter 'Managed Metadata Service' App Pool Identity Credentials and start service.

checked Disk spaces and it's having enough space.

Followed below blog's and verified everything.

http://blogs.msdn.com/b/guruketepalli/archive/2013/08/09/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-please-contact-your-administrator.aspx

https://technet.microsoft.com/en-us/library/ff383250(v=office.14).aspx

We appreciate your help on this.

Getting  time out exception, is it best practice to increase allotted time 00:00:30

Failed to get term store during cache check for changes.  Proxy 'Managed Metadata Service'. Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:30. 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 'https://de08w3501:32844/14074c94dce44a178baa1060ec738428/MetadataWebService.svc' has exceeded the allotted timeout of 00:00:30. 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.GetResponse()    
 at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)     -
 -- End of inner exception stack trace ---    
 at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)    
 at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(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.Internal.IDataAccessReadOnly.GetChanges(Nullable`1 rawPartitionId, DateTime sinceTime, Nullable`1 groupId, Nullable`1 termSetId, Nullable`1 changedItemType, Nullable`1 changedOperationType)    
 at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyProxyAccess.<>c__DisplayClass22.<GetChanges>b__21(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.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 changedItemType, Nullable`1 changedOperationType)    
 at Microsoft.SharePoint.Taxonomy.Internal.TaxonomyCache.CheckForChanges(Boolean enforceUpdate)

Hi Naveen,

Have you checked if it is related to a network issue since the issue occurs redomly?

Do you have multiple application servers? Have you tried IISRESET on all your SharePoint servers?

If it is not a network issue, you may want to increase the timeout value.

Here are some similar posts for your reference.

https://social.msdn.microsoft.com/Forums/en-US/80f8f428-7eed-4d91-a093-a4c4c6f4ae89/getting-an-error-while-creating-sitecollection-programmatically?forum=sharepointdevelopmentprevious

https://social.technet.microsoft.com/Forums/office/en-US/a687fee8-8ca4-4675-bac1-cd064dd7e11d/the-managed-metadata-service-or-connection-is-currently-not-available?forum=sharepointadminprevious

http://byteloom.blogspot.com/2012/10/sharepoint-taxonomies-commiting-large.html

Thanks

Daniel

HI Daniel,

Thanks for the Response.

we have only 2 APP servers but MMS service is running on 1 App Server. So did Service restart and IIS RESET on MMS Hosted Server.

Ticket is created with Network team and engaged with Network team.

 I want add one point here which i missed in my initial post, MMS is inaccessible randomly and more over it will not work at 9:00 AM server time it will be down for maximum 20 mins, if we do MMS service restart and iisrest then it will start work quickly.

Related to your reference blogs, I will try increase time out value, if not get any clue in Network. My MMS Service App Pool Account password is fine. we did multiple time app pool recycle it's not failing and also provided credentials again to app pool to make sure not an issue with service account.

Thanks,

-Naveen.

Hiya,

When you experience the problems, is it completely down or accessible from Central Administration or only Web Application or neither?

If you enter the service url manually (the .svc), does it then work?

Usually what I try first when I experience issues with the Managed Metadata is:

https://jesperarnecke.wordpress.com/2015/05/22/managed-metadata-unable-to-connect-unable-to-publish-contenttypes/

If it not accessible for more than 1 minute then MMS service application will be down. if it not accessible less than 1 min then it will be accessible.

I have not tried with service url(.svc)

But when every day 9:00 AM server time it will be down for max 20 mins and it will connect successful. if we restartservice and do IISRESET then it will connect quickly.