none
This service instance 'Microsoft SharePoint Foundation Usage' cannot be provisioned on server 'APP02' because it is mapped to server 'FE01'. in sharepoint 2010 RRS feed

  • Question

  • Hi

    We are trying to re create the Search Service Application through Central Admin and we receive the error :

    Errors were encountered during the configuration of the Search Service Application.

    Microsoft.SharePoint.SPException:This service instance 'Microsoft SharePoint Foundation Usage' cannot be provisioned on server AP02 because it is mapped to server FE01 . at Microsoft.SharePoint.Administration.SPServiceInstance.Provision()at

    Microsoft.SharePoint.Administration.SPUsageServiceInstance.Provision()at

    Microsoft.SharePoint.Administration.SPUsageService.ProvisionUsageServiceInstances()at

    Microsoft.Sharepoint.Administration.SpUsageService.EnsureApplication()at

    Microsoft.Office.Server.Search.Monitoring.TraceDiagnosticsProvider.Provisionjob(SearchService searchService)at

    Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision()at

    Microsoft.Office.Server.Search.Administration.SearchConfigWizard.b__22()at

    Microsoft.Office.Server.Search.Administration.SearchAdminUtils.UpdateIgnoreSPUpdatedConcurrencyException(String description,SearchAdminUtilsUpdateDelegate updateDelegate, SearchAdminUtilsRefreshObjectDelegate refreshObjectDelegate)at

    Microsoft.Office.Server.Search.Administration.Search.ConfigWizard.CreateSearchApp()at

    Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication()at

    Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()

    Trouble shooting carried out:

    Check all services and service instances via PowerShell - Get-SPSearchServiceInstance, Get-SPEnterpriseSearchServiceInstance, Get-SPUsageApplication, Get-SPUsageService

    Stopped Timer service and reset cache on all server ins the farm

    Check for an remaining redundant search elements in IIS on all servers. Removed if necessary and ran IIS Reset

    Restarted all servers in the Farm

    No matter what we do we always come back to the 'mapped to Fe01' error

    Friday, October 19, 2018 11:16 AM

Answers

  • After a long period of researching and trailing resolutions to this fault it would appear that the only solution to fix it is to rebuild the Farm completely.
    • Marked as answer by PB596 Monday, November 12, 2018 3:28 PM
    Monday, November 12, 2018 3:28 PM

All replies

  • Hi

    The usage service runs on every server in the farm and can not stop. 

    You can see the service instances by using the following cmdlets.

    GEt-SPUsageApplication | Select -ExpandProperty ServiceInstances

    If you find any service instance status is not online, you can try to start the service instance by running the below command via SharePoint management shell

    Start-SPServiceInstance SeviceInstanceId

    SeviceInstanceId: is the Id of your disabled usage service instance.

    Reference: https://technet.microsoft.com/en-us/library/ff607965.aspx

    Friday, October 19, 2018 2:17 PM
  • Hi Tina

    Thanks for your reply. Ive re run your suggested commands and all Usage Application services were already online. There was nothing to start.

    I guess really want to understand how this service became mapped to the FE01 server. How can I 'unmapp' it? If I remove FE01 from the farm will AP02 still think this service is mapped to FE01?

    Monday, October 22, 2018 8:50 AM
  • Hi PB596,

    Please go to Central Administration->Monitoring->Configure usage and health data collection, check if you ticked “Enable usage data collection”.

    Then return to Monitoring page and click “Review job definitions”, make sure “Microsoft SharePoint Foundation Usage Data Import” and “Microsoft SharePoint Foundation Usage Data Processing” timer jobs are running.

    Then run the PowerShell command below as administrator to re-provision the service:

    $instance = Get-SPUsageService
    
    $instance.Provision()
    
    $instance.Update()

    Best regards,

    Grace Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, October 22, 2018 10:25 AM
    Moderator
  • Hi Grace

    Thanks for your reply.

    Enabled usage data collection was ticked and the Microsoft SharePoint Foundation Usage Data Import and Microsoft SharePoint Foundation Usage Data Processing timer jobs are running on a regular basis successfully on each server in the Farm 

    If I run Get-SPUsageService it returns the usual details and the service is online. Get-SPUsageApplication also returns the details for WSS_UsageApplication.

    Try and create a new search service application and still get the same error. Can I remove the WSS_UsageApplication and clear all usage files in the LOGS on every server? Will that help?


    • Edited by PB596 Tuesday, October 23, 2018 1:34 PM
    Tuesday, October 23, 2018 8:34 AM
  • UPDATE: Ive removed AP02 from the Farm and completely removed SharePoint from the server and Rebooted. Then I cleared the config cache and restarted the timer services on the remaining servers in the Farm.

    Attempted to created a search service application - The error is still the same.

    Can anyone tell me where this 'mapped' information is stored? Why does CA still remember a server that is no longer part of the Farm and prevent a Service Instance that simply doesn't exist, from starting and thus prevent a search service application from being created!! Baffled


    • Edited by PB596 Monday, November 5, 2018 1:08 PM
    Monday, November 5, 2018 1:05 PM
  • After a long period of researching and trailing resolutions to this fault it would appear that the only solution to fix it is to rebuild the Farm completely.
    • Marked as answer by PB596 Monday, November 12, 2018 3:28 PM
    Monday, November 12, 2018 3:28 PM