Thank you very much for this invaluable tool!
Using AutoSPInstaller - 103809
The script halted during creation of "Portal" web application with the following exception (img1 captures the full error message):
Exception: Microsoft.SharePoint.PowerShell.SPCmdletException: ApplicationPoolAccount is not found. at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecorderrorRecord).
The issue is resulting from an incorrect common name "Portal" in the function CreateWebApp (see img2), line 2253 of AutoSPInstallerFunctions.ps1. This common name is in conflict with the common names established in AutoSPInstallerInput.xml line 135 (see img3).
At the point of script halting, the managed accounts had been created. So, I changed the common name in the function to match the common name of the managed accounts (portalapppool) in the input.xml file. This resolved the issue and the web application was created upon subsequent execution of AutoSPInstaller.
After viewing the source code, I must have changed the common name and thus created my own issue!
Comments: ** Comment from web user: jwolcott **
Using AutoSPInstaller - 103809
The script halted during creation of "Portal" web application with the following exception (img1 captures the full error message):
Exception: Microsoft.SharePoint.PowerShell.SPCmdletException: ApplicationPoolAccount is not found. at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecorderrorRecord).
The issue is resulting from an incorrect common name "Portal" in the function CreateWebApp (see img2), line 2253 of AutoSPInstallerFunctions.ps1. This common name is in conflict with the common names established in AutoSPInstallerInput.xml line 135 (see img3).
At the point of script halting, the managed accounts had been created. So, I changed the common name in the function to match the common name of the managed accounts (portalapppool) in the input.xml file. This resolved the issue and the web application was created upon subsequent execution of AutoSPInstaller.
After viewing the source code, I must have changed the common name and thus created my own issue!
Comments: ** Comment from web user: jwolcott **
Hi Brian,
Yes, at the time of posting I was using the latest version 103809. I apologize for the confusion. I created and solved my own issue (see the last line posted).
Jeanne