Commented Unassigned: Enterprise Search Error [20520]

Hi all,

I've been fighting with this problem for a couple of days now and just can't seem to get past it. As a newcomer to SP and this wonderful installer tool, I wonder if more experienced eyes can point me in the right direction please?

My interpretation of the error message is that there is a problem with the Enterprise Search Account, but the parameters all seem to be correct on the XML file and the domain account exists and the password is OK. The consistent error I'm getting is:

--------------------------------------------------------------
- Provisioning Enterprise Search...
- Configuring search service...Done.
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'String' because it is an empty string.
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext
funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
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 : InvalidData: (:) [ForEach-Object], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.ForEachObje
ctCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, C:\Temp\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 4278
at CreateEnterpriseSearchServiceApp, C:\Temp\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 4268
at Setup-Services, C:\Temp\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 209
at <ScriptBlock>, C:\Temp\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 364
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :



-----------------------------------
| Automated SP2013 install script |
| Started on: 13/12/2013 10:50:39 |
| Aborted: 13/12/2013 10:53:42 |


Any help gratefully accepted!

Cheers,

Ikoth.
Comments: ** Comment from web user: StaceMeister **

You should double check your XML, use the AutoSPInstallerGUI, look specifically at your search configuration, line 4255-4278 of the ...functions.ps1 is dealing with search topology

If ($allCrawlServersDone -and $allQueryServersDone -and $queryTopology.State -ne "Active") {
Write-Host -ForegroundColor White " - Setting query topology as active..."
$queryTopology | Set-SPEnterpriseSearchQueryTopology -Active -Confirm:$false -ErrorAction SilentlyContinue -ErrorVariable err
Write-Host -ForegroundColor Blue " - Waiting for Query Components..." -NoNewLine
while ($true)
{
$qt = Get-SPEnterpriseSearchQueryTopology -Identity $queryTopology -SearchApplication $searchApp
$state = $qt.QueryComponents | where {$_.State -ne "Ready"}
If ($qt.State -eq "Active" -and $state -eq $null)
{
break
}
Write-Host -ForegroundColor Blue "." -NoNewLine
Start-Sleep 1
}
Write-Host -BackgroundColor Blue -ForegroundColor Black $($queryTopology.State)

# Need to delete the original query topology that was created by default
$origQueryTopology = $searchApp | Get-SPEnterpriseSearchQueryTopology | where {$_.QueryComponents.Count -eq 0}
If ($origQueryTopology.State -eq "Inactive")
{
Write-Host -ForegroundColor White " - Removing original (default) query topology..."
$origQueryTopology | Remove-SPEnterpriseSearchQueryTopology -Confirm:$false
}

and then since you've already experienced the halted script once, I would disconnect the front end server from the farm, delete all databases, config, content_admin, portal. etc. and start afresh. just open up the SharePoint Management console manually and type psconfigui.exe

or run the SharePoint Product and Technologies wizard,

choose disconnect from farm, etc.

then after disconnected, log into your SQL and delete those db's and start fresh