Error: Set-SPEnterpriseSearchAdministrationComponent

Nov 7, 2011 at 4:21 PM

I've recieved this error on a couple of different farms now.  I haven't been able to find anything in the input file that might be wrong.  Any idea what might be going on?

 This is from the ouput document...


Set-SPEnterpriseSearchAdministrationComponent : The search service instance on

this server is not online

At C:\AutoInstaller-SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2865 ch

ar:58

+ Set-SPEnterpriseSearchAdministrationComponent <<<< -SearchApplic

ation $searchApp -SearchServiceInstance $searchSvc

+ CategoryInfo : InvalidData: (Microsoft.Offic...rationComponent:

SetSearchAdministrationComponent) [Set-SPEnterpris...rationComponent], Inv

alidOperationException

+ FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchA

dministrationComponent

 

- Waiting for administration component initialization..............


After that it just sits there until I Ctrl+C out of the script.

 Thanks!

Luke

 

 

Coordinator
Nov 9, 2011 at 2:25 AM

Can you send or copy/paste the <EnterpriseSearchService> node of your XML for review?



Thx
Brian

Nov 9, 2011 at 1:18 PM
<EnterpriseSearchService Provision="app01"
                         ContactEmail=""
                         ConnectionTimeout="60"
                         AcknowledgementTimeout="60"
                         ProxyType="Default"
                         IgnoreSSLWarnings="false"
                         InternetIdentity="Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot)"
                         IndexLocation="E:\index"
                         PerformanceLevel="Maximum"
                         Account="DOMAIN\SPSearch"
                         Password="password"
                         ShareName="SearchShare">
     <EnterpriseSearchServiceApplications>
     <EnterpriseSearchServiceApplication Name="Search Service Application"
                                         DatabaseServer="sql01"
                                         DatabaseName="EnterpriseSearch"
                                         FailoverDatabaseServer=""
                                         Partitioned="false"
                                         Partitions="1"
                                         SearchServiceApplicationType="Regular"
                                         ContentAccessAccount="DOMAIN\spcrawl"
                                         ContentAccessAccountPWD="password">
            <ApplicationPool Name="Search_AppPool" Account="DOMAIN\SPSearch" Password="password" />
            <CrawlServers>
                <Server Name="web01 web02 app01" />
            </CrawlServers>
            <QueryServers>
                <Server Name="web01 web02" />
            </QueryServers>
            <SearchQueryAndSiteSettingsServers>
                <Server Name="app01" />
            </SearchQueryAndSiteSettingsServers>
            <AdminComponent>
                <Server Name="app01" />
                <ApplicationPool Name="SearchAdmin_AppPool" Account="DOMAIN\SPSearch" />
            </AdminComponent>
            <Proxy Name="Search Service Application" Partitioned="false">
                <ProxyGroup Name="Default" />
            </Proxy>
        </EnterpriseSearchServiceApplication>
    </EnterpriseSearchServiceApplications>
</EnterpriseSearchService>
I changed some of the names, but that's all.
Nov 24, 2011 at 2:41 PM

Had this Problem too :)

That happens when you use your previous XML files

<EnterpriseSearchServiceApplication .... ContentAccessAccountPWD="xxxxxx">    changed to   ContentAccessAccountPassword

cheers
Tom

Nov 29, 2011 at 12:45 PM

Possibly check this thread too - http://autospinstaller.codeplex.com/discussions/280641

Mar 14, 2012 at 1:51 PM

I also had that problem with offline Search.

I have solved it using this Powershell cmdlet:

$si = get-spenterprisesearchserviceinstance –local

$si.status

If it's disabled then run the following:

Start-SpEnterpriseSearchServiceInstance -identity $SI

After that, i rerun autospinstallerscript and finished successfully.

Anyone an idea, why this happens initially...?

Dec 9, 2012 at 5:46 PM

I've had this same issue on a few installs, but not every one.  (The script sits on "Waiting for administration component initialization..." and never moves forward)

I think what's happening is that the Enterprise Search Admin Component doesn't always start properly, gets hung initializing etc.  However, I've been able to fix this each time without restarting the install. 

Here's the section of powershell script from the AutoSPInstallerFunctions.ps1 that's doing the work:

                If ($installAdminCmpnt) {
                    Write-Host -ForegroundColor White " - Setting administration component..."
                    *****Set-SPEnterpriseSearchAdministrationComponent -SearchApplication $searchApp -SearchServiceInstance $searchSvc
               
                    $adminCmpnt = $searchApp | Get-SPEnterpriseSearchAdministrationComponent
                    If ($adminCmpnt.Initialized -eq $false)
                    {
                        Write-Host -ForegroundColor Blue " - Waiting for administration component initialization..." -NoNewline
                        While ($adminCmpnt.Initialized -ne $true)
                        {
                            Write-Host -ForegroundColor Blue "." -NoNewline
                            Start-Sleep 1
                            $adminCmpnt = $searchApp | Get-SPEnterpriseSearchAdministrationComponent
                        }
                        Write-Host -BackgroundColor Blue -ForegroundColor Black $($adminCmpnt.Initialized -replace "True","Done.")
                    }
                    Else {Write-Host -ForegroundColor White " - Administration component already initialized."}
                }


Here's what I do:

While the "Waiting for administration component initialization..." message is scrolling along, I log into the machine where search admin is installing as the install account. (As an aside, I always run my installs from a machine not in the farm usually one of the SQL Servers.  This gives me more control over what's happening without affecting the installs or "tripping" over anything)

From SP Powershell, run:  " Get-SPEnterpriseSearchServiceInstance -Local " and get the GUID of the service.

Next, run "Set-SPEnterpriseSearchAdministrationComponent -SearchApplication <Name of your search Service App> -SearchServiceInstance <GUID from the previous command>

Go back to your install scripts and within 15-30 seconds it will proceed with the rest of the install.  I'm adding this as an issue as well.  Hope this helps.