If you don't specify DataDir in the xml this function errors as it tries to remove the trailing '\' from a string that is null.
The line:
$dataDir = $dataDir.TrimEnd("\")
needs to be moved from before the line:
if ([string]::IsNullOrEmpty($dataDir)) {$dataDir = "%PROGRAMFILES%\Microsoft Office Servers\$env:spVer.0\Data"}
to after it.
Comments: Resolved with changeset 114414: Changes in this release:
- Fixed case in AutoSPInstallerInput.xml to match what autospinstaller.com expects
- Enhanced detection of previous XML schema version w/directions for remediation
- Fixed bug in trimming trailing slashes from Data Directory (issue 21911)
- Fixed SP2010 search regression introduced in last changeset (issue 21934)
- In single-server farms (w/ SQL co-installed, e.g. Dev/Demo environments), AutoSPInstaller will now make the Forefront Identity Manager services dependent on SQL so they will start up properly upon server reboots
- Fairly substantial changes to SP2013 search config; you can actually use AutoSPInstaller to reconfigure your search topology! In other words, AutoSPInstaller can now remove search components (in addition to adding components, which it already did) to effectively enable reconfigure a search topology - even on a farm that wasn't originally installed with AutoSPInstaller
The line:
$dataDir = $dataDir.TrimEnd("\")
needs to be moved from before the line:
if ([string]::IsNullOrEmpty($dataDir)) {$dataDir = "%PROGRAMFILES%\Microsoft Office Servers\$env:spVer.0\Data"}
to after it.
Comments: Resolved with changeset 114414: Changes in this release:
- Fixed case in AutoSPInstallerInput.xml to match what autospinstaller.com expects
- Enhanced detection of previous XML schema version w/directions for remediation
- Fixed bug in trimming trailing slashes from Data Directory (issue 21911)
- Fixed SP2010 search regression introduced in last changeset (issue 21934)
- In single-server farms (w/ SQL co-installed, e.g. Dev/Demo environments), AutoSPInstaller will now make the Forefront Identity Manager services dependent on SQL so they will start up properly upon server reboots
- Fairly substantial changes to SP2013 search config; you can actually use AutoSPInstaller to reconfigure your search topology! In other words, AutoSPInstaller can now remove search components (in addition to adding components, which it already did) to effectively enable reconfigure a search topology - even on a farm that wasn't originally installed with AutoSPInstaller