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: westerdaled **
Hi
I might be worth giving more details on your setup
* version of AutoSPInstaller - 3.96 has a number of fixes so that this is the one I would use
* sever spec so you using at least dual core and > 8GB of RAM
* version of Windows Server
* target SharePoint version 2010 v 2013 tho this is getting more of a one horse race
* CUs in 2013 the March CU is mandatory
* version of SQLServer and the Service Packs
* if you are referencing "localhost" or the actual server name when the script attempts to create your content or service app dbs. I would recommend you try the server name(s) as I got consistent results when I did this.
* The service accounts a mostly plain old domain accounts ( except sp_farm and sp_profileSync) as the script does the heavy lifting for you - you just need to supply valid account details. By all means reset the pw with the old pw in administrator - AD Computers and Users to just be on the safe side.