SharePoint 2016 - Managed Metadata not work (tried many solution)

Question

I have a new SharePoint 2016 (version 16.0.5032.1002) farm install on Windows Server 2019 (version 1809 build 17763.1369)

After install SharePoint -> install CU 2020 -> create SharePoint Farm (custom mode), I can create User Profile Service, Search Service, Web Application but unable to create Manage Metadata Service, the log file when create MMS:

06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://SERVERNAME:1234/_admin/ServiceApplications.aspx) 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwhz Medium SPRequestModule.BeginRequestHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 Web Content Management Publishing aytib Medium ObjectCachePerRequest Global:True, Enabled:False 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh6 Medium SPRequestModule.PostAuthenticateRequestHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Site Cache az4z8 Medium Looking up SPSite by ID 1cac6f79-b853-4476-8709-6dca25b42e42 in memory. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Runtime ajd6k Medium Value for isAnonymousAllowed is : False 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Runtime ajd6l Medium Value for checkAuthenticationCookie is : True 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh7 Medium SPRequestModule.PostAuthenticateRequestHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh8 Medium SPRequestModule.PostAuthorizeRequestHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh0 Medium SPRequestModule.PostResolveRequestCacheHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh1 Medium SPRequestModule.PostResolveRequestCacheHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime aj1kn Medium SPRequestModule.AcquireRequestStateHandler 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh2 Medium SPRequestModule.PostAcquireRequestStateHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh3 Medium SPRequestModule.PostAcquireRequestStateHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwhu Medium SPRequestModule.PreRequestExecuteAppHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a0t92 Medium pre-initializing server 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a08yd Medium Getting content database c5e3321d-25e1-4d62-be94-0426faa64810 from webApp 22a02ce0-8a7e-42de-ae27-a51daeaf31e7 version 92231. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a0t94 Medium pre-initializing server; validating backwards compatibility 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a0t97 Medium pre-initializing server; finding app domain info 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.12 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a0t98 Medium pre-initializing server; calling request.PreInitServer 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.14 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.14 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Site Cache az4z8 Medium Looking up SPSite by ID 1cac6f79-b853-4476-8709-6dca25b42e42 in memory. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.14 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Site Cache az4z8 Medium Looking up SPSite by ID 1cac6f79-b853-4476-8709-6dca25b42e42 in memory. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.14 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwhv Medium SPRequestModule.PreRequestExecuteAppHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.14 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Site Cache az4z8 Medium Looking up SPSite by ID 1cac6f79-b853-4476-8709-6dca25b42e42 in memory. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.15 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation General a4hvw Medium VdbNavStruct::LoadScopeMap - Failed to insert ScopeId:{38A0B544-476B-43A2-A14E-5F30B762713D} into the scope map. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.15 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Database a9g62 Medium Generated nonsnapshot connection string for [MetadataWebServiceDatabase Name=SharePointManagedMetadata][27afa727-58cd-41a8-ac55-833cf3eb15f7] with persisted object version [98862]: Datasource = [DATABASESERVER], FailoverPartner = [] 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.15 w3wp.exe (0x24B0) 0x0918 Document Management Server Reporting a3hwy Medium Taxonomy SqlSession.ExecuteReader Start: My Scenario Start 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.15 w3wp.exe (0x24B0) 0x0918 Document Management Server Reporting a3hwz Medium Taxonomy SqlSession.ExecuteReader Success: My Scenario Success 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.15 w3wp.exe (0x24B0) 0x0918 Document Management Server Reporting aunq1 Medium Metadata backend service request Start: My Scenario Start 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.17 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://SERVERNAME:32843/c2a270dff11341ff873baae2b8518d7c/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IMetadataWebServiceApplication/GetServiceSettings' MessageId: 'urn:uuid:874bd5d1-6d94-4661-ba95-aa127022acee' 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Server Taxonomy ca42 Medium Exception returned from back end service. System.ServiceModel.FaultException1[System.ServiceModel.ExceptionDetail]: The service implementation object was not initialized or is not available. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: The service implementation object was not initialized or is not available. at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)). 208ccd9f-cf67-6006-a09b-0db3032afb7d **06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Server Taxonomy bvo5 Unexpected Failed to create ManageLink for service proxy 'ManagedMetadataService'. Exception: System.ServiceModel.FaultException1[System.ServiceModel.ExceptionDetail]: The service implementation object was not initialized or is not available. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: The service implementation object was not initialized or is not available. at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)). 208ccd9f-cf67-6006-a09b-0db3032afb7d**
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Monitoring nasq Medium Entering Monitored Scope (Render Ribbon.). Parent=SharePointForm Control Render 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (Render Ribbon.) Execution Time=2.63280668353101; CPU Milliseconds=2; SQL Query Count=0; Parent=SharePointForm Control Render 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 Web Content Management Publishing aytib Medium ObjectCachePerRequest Global:False, Enabled:False 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwia Medium SPRequestModule.PostLogRequestHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwib Medium SPRequestModule.PostLogRequestHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwic Medium SPRequestModule.EndRequestHandler Begin 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Site Cache az4z8 Medium Looking up SPSite by ID 1cac6f79-b853-4476-8709-6dca25b42e42 in memory. 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwh5 Medium SPRequestModule.PreSendRequestHeaders End 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 avwhy,0 nasq,0 az4z8,0 avwhz,0 aytib,0 avwh6,1 az4z8,0 agb9s,0 ajd6k,0 ajd6l,0 avwh7,0 avwh8,0 avwh0,0 avwh1,0 aj1kn,0 avwh2,0 avwh3,0 avwhu,0 a0t92,0 a08yd,0 a0t94,0 a0t97,0 a0t98,4 az4z8,0 az4z8,0 avwhv,6 az4z8,15 a9g62,0 a3hwy,1 a3hwz,0 aunq1,12 e5mc,5 ca42,0 aunq3,0 bvo5,3 agxkz,1 nasq,2 b4ly,1 aytib,0 avwia,0 avwib,0 avwic,0 az4z8,0 avwh5 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Runtime aoxsq Medium Sending HTTP response 200 for HTTP request GET to http://SERVERNAME:1234/_admin/ServiceApplications.aspx 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (Request (GET:http://SERVERNAME:1234/_admin/ServiceApplications.aspx)) Execution Time=61.3649919193641; CPU Milliseconds=47; SQL Query Count=6; Parent=None 208ccd9f-cf67-6006-a09b-0db3032afb7d
06/01/2021 03:58:56.18 w3wp.exe (0x24B0) 0x0918 SharePoint Foundation Asp Runtime avwid Medium SPRequestModule.EndRequestHandler End 208ccd9f-cf67-6006-a09b-0db3032afb7d

After MMS created, when open MMS page, the issue below appear

When Open Properties of MMS, message below appear

I did try following solutions but all not work.

• Start Managed Metadata Web Service and associate Proxy http://123it.blogspot.com/2011/02/issues-with-creating-managed-metadata.html
• Change Sendtimeout to 10 minutes https://social.technet.microsoft.com/Forums/en-US/a5213d7c-831f-4a5b-ab52-23526fcfa1fa/the-managed-metadata-service-or-connection-is-currently-not-available-the-application-pool-or?forum=sharepointadminprevious
• Grant permission for WSS_ADMIN_WPG group and execute Initialize-SPResourceSecurity https://www.habaneroconsulting.com/stories/insights/2015/the-managed-metadata-service-or-connection-is-currently-not-available
• Run Initialize-SPResourceSecurity and Install-SPFeature -AllExistingFeatures https://social.technet.microsoft.com/Forums/sharepoint/en-US/edf7946a-a178-46e8-b7f3-82f80ad4a194/have-anyone-set-up-mysite-on-a-frontend-server-and-userporfile-service-application-on-an-appserver?forum=sharepointadmin
• Create new DB and change back to original https://areflyen.no/2014/08/21/the-managed-metadata-service-or-connection-is-currently-not-available-in-sharepoint-2013/

Do you have any suggestion ? Many thanks.

Answer 1

Hello,

Thank you for your suggestion, before see your suggestion, I reinstalled SharePoint without apply any CU and it work normally. Do not have change to try your solution.

Not sure which is the best practice to setup new SharePoint farm:

• Install SharePoint -> Create SharePoint Farm -> apply latest CU Language Independent Files -> apply latest CU Language Dependent Files
• or Install SharePoint -> apply latest CU Language Independent Files -> apply latest CU Language Dependent Files -> Create SharePoint Farm.

Which the second way that I tried I got an issue releated with Manage Metadata Service that can not solve. So this is not the correct way or correct way but that is SharePoint CU issue ?

Answer 2

Hi,@Hung Vo ,
Which method do you use to create Managed Metadata Service Application: UI or PowerShell?

From your ULS log, the error is: Failed to create ManageLink for service proxy 'ManagedMetadataService', the service implementation object was not initialized or is not available, however I couldn’t find any related information to solve the issue.

As a workaround, please try to create a new Managed Metadata Service Application by following PowerShell that worked well according to my test and check if the issue still exists.

Remember to change the relevant parameters for your yourself: $AppPoolAccount, $DatabaseServer, $ContentTypeHub.

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue  
     
#Configuration Parameters  
$ServiceAppName = "Managed Metadata Service Application"  
$ServiceAppProxyName = "Managed Metadata Service Application Proxy"  
$AppPoolAccount = "Crescent\SP16-AppPool"  
$AppPoolName = "Service Application App Pool"  
$DatabaseServer ="SP16-SQL001"  
$DatabaseName = "SP16_Service_MMS"  
$ContentTypeHub="http://intranet.crescent.com/ctypehub"  
    
Try {  
    #Set the Error Action  
    $ErrorActionPreference = "Stop"  
     
    #Check if Managed account is registered already  
    Write-Host -ForegroundColor Yellow "Checking if the Managed Accounts already exists"  
    $AppPoolAccount = Get-SPManagedAccount -Identity $AppPoolAccount -ErrorAction SilentlyContinue  
    if($AppPoolAccount -eq $null)  
    {  
        Write-Host "Please Enter the password for the Service Account..."  
        $AppPoolCredentials = Get-Credential $AppPoolAccount  
        $AppPoolAccount = New-SPManagedAccount -Credential $AppPoolCredentials  
    }  
     
    #Check if the application pool exists already  
    Write-Host -ForegroundColor Yellow "Checking if the Application Pool already exists"  
    $AppPool = Get-SPServiceApplicationPool -Identity $AppPoolName -ErrorAction SilentlyContinue  
    if ($AppPool -eq $null)  
    {  
        Write-Host -ForegroundColor Green "Creating Application Pool..."  
        $AppPool = New-SPServiceApplicationPool -Name $AppPoolName -Account $AppPoolAccount  
    }  
     
    #Check if the Service application exists already  
    Write-Host -ForegroundColor Yellow "Checking if Managed Metadata Service Application exists already"  
    $ServiceApplication = Get-SPServiceApplication -Name $ServiceAppName -ErrorAction SilentlyContinue  
    if ($ServiceApplication -eq $null)  
    {  
        Write-Host -ForegroundColor Green "Creating Managed Metadata Service Application..."  
        $ServiceApplication =  New-SPMetadataServiceApplication -Name $ServiceAppName –ApplicationPool $AppPoolName –DatabaseName $DatabaseName –DatabaseServer $DatabaseServer  
    }  
    #Check if the Service application Proxy exists already  
    $ServiceAppProxy = Get-SPServiceApplicationProxy | where { $_.Name -eq $ServiceAppProxyName}  
    if ($ServiceAppProxy -eq $null)  
    {  
        #Optional Parameters:   
        $ServiceApplicationProxy = New-SPMetadataServiceApplicationProxy -Name $ServiceAppProxyName -ServiceApplication $ServiceApplication -DefaultProxyGroup -ContentTypePushdownEnabled -DefaultKeywordTaxonomy -DefaultSiteCollectionTaxonomy -Uri $ContentTypeHub  
    }  
    #Start service instance   
    $ServiceInstance = Get-SPServiceInstance | Where-Object { $_.TypeName -eq "Managed Metadata Web Service" }  
    
    #Check the Service status  
    if ($ServiceInstance.Status -ne "Online")  
    {  
        Write-Host -ForegroundColor Yellow "Starting the Managed MetadataService Instance..."  
        Start-SPServiceInstance $ServiceInstance  
    }  
     
    Write-Host -ForegroundColor Green "Managed Metadata Service Application created successfully!"  
}  
catch {  
    Write-Host $_.Exception.Message -ForegroundColor Red  
}  

For more information, please refer to:
create-managed-metadata-service-application-using-powershell-in-sharepoint.html

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Thanks,
Yi Lu