```
if ($xmlinput.Configuration.OfficeWebApps.Install -eq $true)
{
$sp2010OWAUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include wac*.exe -Recurse -ErrorAction SilentlyContinue | Sort-Object -Descending
if($sp2010OWAUpdates)
{
foreach ($sp2010OWAUpdate in $sp2010OWAUpdates)
{
InstallSpecifiedUpdate $sp2010OWAUpdate "Office Web Apps Update"
}
}
}
```
Comments: ** Comment from web user: FlyBock **
I had this issue too, installing SharePoint 2010 Office Web Apps on a new server. However, my Updates folder had the Office Web Apps Service Pack 2 files in it. Still, it failed to install. Changing the lines above in AutoSPInstallerFunctions.ps1 fixed the issue.
My error details were:
--------------------------------------------------------------
- SharePoint 2010 binaries appear to be already installed - skipping installation.
--------------------------------------------------------------
--------------------------------------------------------------
- Office Web Apps binaries appear to be already installed - skipping install.
--------------------------------------------------------------
--------------------------------------------------------------
- No language packs found in C:\Install\AutoSPInstaller\SP\2010\LanguagePacks, skipping.
- Currently installed languages:
- English (United States)
--------------------------------------------------------------
--------------------------------------------------------------
- Looking for SharePoint updates to install...
--------------------------------------------------------------
- Script halted!
Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
at System.Management.Automation.ParameterBinderBase.
ValidateNullOrEmptyArgument(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, Type argumentType, Object parameterValue, Boolean recurse
IntoCollections) at System.Management.Automation.ParameterBinderBase. BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags)
at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags)
at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags)
at System.Management.Automation.CmdletParameterBinderController.BindParameters(UInt32 parameterSets, Collection`1 arguments, CommandMetadata commandMetadata)
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments)
at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)
at System.Management.Automation.CommandProcessor.BindCommandLineParameters(CommandParameterInternal[] parameters)
at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInternal[] parameters)
at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParameterInternal[] parameters) at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
TargetObject :
CategoryInfo : InvalidData: (:) [Split-Path], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.SplitPathCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
PipelineIterationInfo : {}
PSMessageDetails :