Ir al contenido principal

Metadata Service is unavailable - Event 8088

 

Alert Name:   Metadata Service is unavailable

Event ID:   8088

Summary:   The managed metadata service provides access to one term store and the term sets that it contains, or it provides content types from a content type syndication hub.

Symptoms:   One or more of the following symptoms might appear:

  • The term store management tool displays an error that indicates that the term store is not available.

  • Managed metadata controls and enterprise keyword controls may appear disabled.

  • This event might appear in the event log: Event ID: 8088 Description: The Managed Metadata Service '<Service>' is inaccessible.

Cause:   This can occur if the server is offline or the managed metadata service is not started or has been disabled. The service might not start if the application pool account does not have sufficient permissions to the term store.

Resolution:   Verify the application pool account permissions

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

  2. On the Central Administration Home page, click Application Management.

  3. On the Application Management page, in the Service Applications section, click Manage service applications.

  4. On the Service Applications page, in the Type column, click the managed metadata service application, and then click Properties.

  5. In the Create New Managed Metadata Service dialog box, in the Application Pool section, record the name of the application pool and the application pool account name.

  6. Click Cancel.

  7. Log on as a member of the local Administrators group.

  8. In Central Administration, on the Service Applications page, in the Type column, click the managed metadata service application, and then click Permissions.

  9. Confirm that the account that you recorded in step 5 has one of the following permissions:

    • Read Access to Term Store

    • Read and Restricted Write Access to Term Store

    • Full Access to Term Store

 

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

Comentarios

Entradas populares de este blog

O365 - Forms - Transferir la propiedad de un formulario

Fuente :  https://support.office.com/es-es/article/transferir-la-propiedad-de-un-formulario-921a6361-a4e5-44ea-bce9-c4ed63aa54b4 Si ha creado una encuesta, una prueba o un sondeo, puede moverlos fácilmente a un grupo para que todos los miembros del grupo se conviertan en propietarios de ese formulario. Transferir el formulario a un grupo En el explorador Web, vaya a  Forms.Office.com . En la pestaña  mis formularios  , busque el formulario que desea transferir. Haga clic en  más acciones de formulario    y, a continuación, seleccione  mover . Nota:  Solo puede mover el formulario si es el propietario de ese formulario. No puede transferir la propiedad de un formulario que está compartido con usted. Seleccione el grupo al que desea transferir el formulario y, a continuación, haga clic en  mover . El formulario que ha movido aparecerá en la pestaña  formularios de grupo  . ¿Qué ocurre con el libr...

Event ID 8031 The uri endpoint information may be stale

An exception occurred while updating addresses for connected app {6783ce5e-c88h-4021-8d5b-12614875cbfa_b79f19ab-1d40-4824-9911-3466cf8b070a}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found.    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName, Exception ex, SPServiceLoadBalancerContext context)    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)    at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)    at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId) After de-commissioning some SharePoint servers, you might notice the above error on other WFEs /Application server’s event viewer . It appears that the SharePoint still has a reference...

SP 2013–2010 - An exception occurred in AD claim provider when calling SPClaimProvider.FillResolve(): Thread was being aborted

  Error: An exception occurred in AD claim provider when calling SPClaimProvider.FillResolve(): Thread was being aborted..   Resolution In order to determine the best MaxConcurrentApi value for your servers, several data points must be brought together and calculated by using a formula. The data to be used to estimate MaxConcurrentApi is as follows: Net Logon semaphore acquires Net Logon semaphore time-outs Net Logon average semaphore hold time Duration of the performance logging that is completed, measured in seconds After the data is obtained, the following formula can be used to estimate the correct MaxConcurrentApi value: ( semaphore_acquires + semaphore_time-outs ) * average_semaphore_hold_time / time_collection_length = < New_MaxConcurrentApi_setting After you collect the Net Logon performance data from when the server was under authentication load, you should determine the duration of the data-collecting process by looking at the Line View beginning and en...