none
SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

Answers

All replies

  • Hi,

    According to your error message, it says that the Admin Component of your Search service application is not online.

    For your issue, you can run the following command in SharePoint 2013 Management Shell:

    Get-SPEnterpriseSearchServiceInstance -local
    
    Start-SPEnterpriseSearchServiceInstance -Identity <servername>
    
    Get-SPEnterpriseSearchServiceInstance -local
    
    $instance = Get-SPEnterpriseSearchServiceInstance -local
    $searchApp = Get-SPEnterpriSesearchServiceApplication
    Set-SPEnterpriseSearchAdministrationComponent –SearchApplication $searchApp –SearchServiceInstance $instance

    For more information, you can refer to the blog:

    http://mustafaozen.wordpress.com/tag/the-search-service-is-not-able-to-connect-to-the-machine-that-hosts-the-administration-component-verify-that-the-administration-component-guid-in-search-application-search-service-application-is/

    If your issue persists, you can have a look at the thread:

    https://social.technet.microsoft.com/Forums/office/en-US/b04498ec-78d1-4bb9-8077-0481977cef10/the-search-service-is-not-able-to-connect-to-the-machine-that-hosts-the-administration-component?forum=sharepointadminprevious

    https://social.technet.microsoft.com/Forums/en-US/b3ddb00a-71aa-455b-ba5f-52c10d7d0966/the-search-service-is-not-able-to-connect-to-the-machine-that-hosts-the-administration-component?forum=sharepointgeneral

    http://www.thorntontechnical.com/tech/sharepoint/the-search-service-is-not-able-to-connect-to-the-machine-that-hosts-the-administration-component#.VIqj-XkcSM8

    Thanks,

    Eric

    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 tnmff@microsoft.com.


    Eric Tao
    TechNet Community Support

    Friday, December 12, 2014 8:33 AM
  • Hi Eric,

    Since the issue is in SP Foundation 2013, the SPEnterpriseSearch related PowerShell Commands are not working. They all come back with a message saying, "This requires SharePoint Server with Enterprise CAL" :( that is the issue, Any other options?


    Karthick S

    Friday, December 12, 2014 8:49 AM
  • This is the error I get with Foundation 2013Requires a SharePoint Server Client Access License

    Karthick S

    Sunday, December 14, 2014 3:11 AM
  • I am also getting this error when I run this cmd.


    Karthick S

    Sunday, December 14, 2014 5:22 AM
  • I also get this error (SharePoint Server Search - Error Stopping)


    Karthick S

    Sunday, December 14, 2014 5:26 AM
  • Hi Karthick,

    For your issue, could you provide the detail error message of ULS log  to determine the exact cause of the error?

    For SharePoint 2013, by default, ULS log is at      

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

    For troubleshooting your issue,  you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint Foundation:

    [string]$farmAcct = "DOMAIN\service_Account"
    [string]$serviceAppName = "Search Service Application"
    
    Function WriteLine
    {
        Write-Host -ForegroundColor White "--------------------------------------------------------------"
    }
    
    # ---------------------------------------------------------------------
    Function ActivateAndConfigureSearchService
    {
    	Try
    	{
    		# Based on this script : http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
    
    		Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
    		Start-SPEnterpriseSearchServiceInstance $env:computername
    		Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
    		$appPool = Get-SPManagedAccount -Identity $farmAcct
    		
    		New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
    		$saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
    		$svcPool = $saAppPool
    		$adminPool = $saAppPool
    		
    		$searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
    		$searchService = $searchServiceInstance.Service
    		$bindings = @("InvokeMethod", "NonPublic", "Instance")
    		$types = @([string],
    			[Type],
    			[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool],
    			[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool])
    
    		$values = @($serviceAppName,
    			[Microsoft.Office.Server.Search.Administration.SearchServiceApplication],
    			[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$svcPool,
    			[Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$adminPool)
    
    		$methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
    		$searchServiceApp = $methodInfo.Invoke($searchService, $values)
    		$searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
    		$searchServiceApp.Provision()
    		
    	}
    	catch  [system.exception]
    	{
            Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
    		Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
    	}
    	finally
    	{
            WriteLine
    	}
    }
    
    ActivateAndConfigureSearchService
    

    Reference:

    https://sharepointpsscripts.codeplex.com/releases/view/112556

    Thanks,

    Eric

    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 tnmff@microsoft.com.


    Eric Tao
    TechNet Community Support

    Monday, December 15, 2014 6:49 AM
  • Hi Eric,

    I am getting the below errors:

    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.  Context: Application '5c42f5a7-1371-407c-8652-8276c302d6b3'  Details:   (0x80131904)

    ---------------------------------------------

    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (fc487bc8-b305-4463-b693-491e291d037b).  Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by Domain\SPFarm, in the OWSTIMER (7020) process, on machine AppServer1.  View the tracing log for more information about the conflict.  Technical Support Details: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by Domain\SPFarm, in the OWSTIMER (7020) process, on machine AppServer1.  View the tracing log for more information about the conflict.     at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() 
        at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    ----------------------------------------------

    SearchServiceApplication::GetQueryHealthMonitoringSettings--Exception: System.NullReferenceException: Object reference not set to an instance of an object. 
        at Microsoft.Office.Server.Search.Administration.IntegerSearchSetting.GetConfigParameter() 
        at Microsoft.Office.Server.Search.Administration.SearchSetting.GetSetting(String name, List`1 searchSettings) 
        at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.GetQueryHealthMonitoringSettings(String component)
    =--------------------
    Updating SearchDataAccessServiceInstance failed.
    ---------
    Cleanup of Orphan Systems in server APPServer1



    Karthick S

    Tuesday, December 16, 2014 6:47 AM
  • My fundamental question is should the Search Service be STOPPED in the AppServer1 in order for the Search Service and the Search Service Application to work ONLY in App Server2?

    Karthick S

    Tuesday, December 16, 2014 7:14 AM
  • Contribution from:

    Steph van Schalkwyk

     https://www.linkedin.com/profile/view?id=1913064&snapshotID=&authType=name&authToken=rWQi&ref=NUS&trk=NUS-body-member-name

    I've just spoken to MSFT support and it does seem that SP 2013 Foundation Search is not scalable, at least not from the configuration GUI. 
    I looked into it some more and this explains it in more detail: 
    http://www.myfatblog.co.uk/index.php/2012/10/search-in-sharepoint-2013-foundation-versus-full-blown-server/ 
    Not as if MSFT broadcast this "feature".


    Karthick S

    • Marked as answer by S.Karthick Wednesday, December 17, 2014 11:20 AM
    Wednesday, December 17, 2014 11:20 AM