This project has moved and is read-only. For the latest updates, please go here.


Fails at activating Search Topology for SharePoint 2013 Beta


Single server W2K8R2 Datacenter with SQL Server 2012 Express with CU3. Installing all components exept PerformancePoint, Office Web Apps and ForeFront.
Script times ut at "Activating Search Topology".

file attachments

Closed Apr 18, 2013 at 4:33 AM by brianlala
No longer applicable to RTM version of SP2013.


audunms wrote Sep 21, 2012 at 9:49 AM

Seems this was related to problems with Search in 2013 Beta. Was not possible to activate search topology with CA or manual PS either.

Tried again with a fresh server, and then script worked.

(only difference from first time was that first time I had changed the CommonName for spservice in AutoSPInstallerInput, not sure if this was the cause though. Second time I also set PS Executionpolicy tp "bypass".)

wrote Oct 17, 2012 at 9:48 AM

wrote Nov 5, 2012 at 10:46 PM

wrote Nov 7, 2012 at 8:45 AM

MaximilianBerg wrote Nov 7, 2012 at 8:49 AM

Still have the same Problem.

wrote Nov 7, 2012 at 9:22 AM

brianlala wrote Nov 8, 2012 at 3:43 AM

Likewise, I haven't seen this problem with the RTM of SP2013. Which version are you using? What are the resources like (RAM, CPU) on your server? I would imagine you'd need at least a good 16GB. Also I haven't tested with SQL Express, not sure if that could be causing a problem?


audunms wrote Nov 8, 2012 at 7:22 AM

I actually have seen this problem again, both on single server machines (RTM, 16Gb RAM) and server farms.

I however don't think it is related to AutoSPInstaller but to the search provisioninging by SharePoint. I have had this issue when using separate accounts for search for low privileges, especially on single servers when also running domain controller on the same box.

SolidCactus wrote Nov 8, 2012 at 8:57 AM

Hi all

Experiencing the same issues on my end. My setup is:

2 x WFE/APP servers running Windows Server 2012 RTM and SharePoint 2013 RTM.

I'm not installing on a Domain Controller.

I am using the least privilege model of security accounts.

Audumns - what do you change the common name to?

Brian - Happy to help provide whatever I can to help?


audunms wrote Nov 8, 2012 at 9:49 AM

what fixed it for me was this:

Anyway, what fixed it for me was to add the Search Service Account to local admins (=Domain Admins since this is the domain controller also) and to the sysadmin server role (!) in SQL. Then I logged on to the server as the Search Service account and set up search without problems. I had to use a new new for the Search Service Application, even though there was no Search Service Application listed in Central Admin or with Powershell, it seems to be some leftovers after the first try.

I'm quite sure not all of these steps are needed, but I didn't have time to pin it down at the time. Here is my complete post on it:

The first try I had a typo in the xml config file for AutoSPInstaller,you should not change the CommonName like the description also states.

SolidCactus wrote Nov 8, 2012 at 11:17 AM

Thanks for the input. Unfortunately I don't really want to add my the Search Service Account to Local Admins and SQL sysadmin.

Trawling through the ULS I see the following:

Content Plugin can not be initialized - list of CSS addresses is not set.


Failed to extract required parameter FastConnector:ContentDistributor, hr=0x80070002 [pluginconfig.cpp:81] search\native\gather\plugins\contentpi\pluginconfig.cpp

There is a large number of errors in the event log in regards to:

Volume Shadow Copy Service error: The process that hosts the writer with name OSearch15 VSS Writer and ID {0ff1ce15-0201-0000-0000-000000000000} does not run under a user with sufficient access rights.

Faulting application name: hostcontrollerservice.exe, version: 15.0.4420.1017, time stamp: 0x50672c2d
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ab2d
Exception code: 0xe0434352
Fault offset: 0x00000000000189cc
Faulting process id: 0xb28
Faulting application start time: 0x01cdbd9cdb476553
Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\HostController\hostcontrollerservice.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 19dd379c-2990-11e2-93f1-0050569657e8
Faulting package full name:
Faulting package-relative application ID:

This would tie in nicely with the following:

Unfortunately I'm using Server 2012 so this hotfix isn't available.

Not really sure where to go next. I tried manically activating it using PowerShell but it again timed out.

SolidCactus wrote Nov 9, 2012 at 10:09 AM

Here is the stack trace for when it falls over
  • Checking administration component...Creating...Done.
  • Checking content processing component...Creating...Done.
  • Checking analytics processing component...Creating...Done.
  • Checking crawl component...Creating...Done.
  • Checking index component...Creating...Done.
  • Checking query processing component...Creating...Done.
  • Activating Search Topology...--------------------------------------------------------------
  • Script halted!
Exception : System.Management.Automation.MethodInvocationException: Exception calling "Activate" with "0"
                    argument(s): "Timed out waiting for search service 'SPSearchHostController' provisioning timer 
                    job to complete" ---> System.TimeoutException: Timed out waiting for search service 
                    'SPSearchHostController' provisioning timer job to complete
                       at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.WaitForProvisioningComplet
                    e[T](T searchServiceInstance)
                       at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.ActivateSilently()
                       at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.Activate()
                       at CallSite.Target(Closure , CallSite , Object )
                       --- End of inner exception stack trace ---
                       at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext 
                    funcContext, Exception exception)
                       at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame 
                       at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
                       at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
                       at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(Boolean createLocalScope, 
                    ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object 
                    scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
                       at System.Management.Automation.ScriptBlock.<>c__DisplayClass4.<InvokeWithPipe>b__2()
                       at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThre
                    adCheck(Action action)
                       at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope, 
                    ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, Object 
                    scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
                       at System.Management.Automation.ScriptBlock.InvokeUsingCmdlet(Cmdlet contextCmdlet, Boolean 
                    useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input, 
                    Object scriptThis, Object[] args)
                       at Microsoft.PowerShell.Commands.ForEachObjectCommand.ProcessRecord()
                       at System.Management.Automation.CommandProcessor.ProcessRecord()
TargetObject :
CategoryInfo : NotSpecified: (:) [ForEach-Object], MethodInvocationException
FullyQualifiedErrorId : TimeoutException,Microsoft.PowerShell.Commands.ForEachObjectCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, C:\Users\spinstall\Desktop\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
                    line 3576
                    at CreateEnterpriseSearchServiceApp, 
                    C:\Users\spinstall\Desktop\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 3412
                    at Setup-Services, C:\Users\spinstall\Desktop\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 
                    at <ScriptBlock>, C:\Users\spinstall\Desktop\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 
                    at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

wrote Nov 9, 2012 at 10:48 AM

andreasblueher wrote Nov 9, 2012 at 10:57 AM

I ran into the same time out issue using either SPAutoInstaller or doing it manually. So I guess it's a SP problem rather than SPAutoInstaller. Although I'm using Windows Server 2008 R2 SP1 I haven't been able to use the hotfix mentioned in this thread:

I'll keep you updated if I find any solution.

andreasblueher wrote Nov 9, 2012 at 2:28 PM

Not sure which caused the error to go away but after installing the English Language Pack to my german Windows Server 2008 R2 SP1, changing the windows language to english, REBOOTING the system everything went fine.

Not sure if installing the language pack was necessary, maybe the reboot is required. Which threw my off a little was an error message I found while looking for the cause:

"Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist."

If you look closer you'll see that the word ends with "GetMemebers" which obviously should be wrong. Not sure if it's related to this behavior in any way, but eventually we'll find out.

wrote Nov 27, 2012 at 11:30 PM

wrote Dec 17, 2012 at 5:12 PM

wrote Jan 4, 2013 at 4:26 AM

christophd wrote Feb 7, 2013 at 5:04 PM

It works for me if I create a Firewall Inbound Rule for TCP Port 808 on all my SharePoint Servers before starting the Topology activation. Maybe the Firewall settings are causing the problem.
Someone can try to confirm this? I already tried to collect the information here:

wrote Feb 22, 2013 at 1:53 AM

MaxMelcher wrote Apr 5, 2013 at 6:16 PM

I had the same problem - the fix for me was to create a new topology:

Add-PSSnapin Microsoft.SharePoint.Powershell -EA 0
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication
$SearchTopology = $ServiceApplication | New-SPEnterpriseSearchTopology
$SearchInstance = Get-SPEnterpriseSearchServiceInstance
$IndexLocation = "c:\SearchIndex"

New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $SearchTopology -SearSearchInstancechServiceInstance $SearchInstance
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance
New-SPEnterpriseSearchCrawlComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance
New-SPEnterpriseSearchAdminComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance

set-SPEnterpriseSearchAdministrationComponent -SearchApplication $ServiceApplication -SearchServiceInstance $SearchInstance

Remove-Item -Recurse -Force -LiteralPath $IndexLocation -ErrorAction SilentlyContinue
mkdir -Path $IndexLocation -Force

New-SPEnterpriseSearchIndexComponent -SearchTopology $SearchTopology -SearchServiceInstance $SearchInstance -RootDirectory $IndexLocation

Write-Host -ForegroundColor Yellow "Activating new topology"
Write-Host -ForegroundColor Green "Activated new topology"

wrote Apr 18, 2013 at 4:33 AM

hramos wrote May 10, 2013 at 2:51 AM

The above topology script has typos and also doesn't work in a multi-server farm. Try the following article for details on rebuilding the search topology through power shell.

wrote May 16, 2013 at 1:13 PM

kris_m wrote Apr 9, 2014 at 2:04 PM

I had this issue, what eventually solved it was temporarily disabling windows firewall. Turned it back on afterwards without any apparent issues so far.