Hi All,
Has anyone come across this error below, my script keeps getting stuck at the following point when provisioning my first App server and not sure why??
Could it be that my Crawl and Query components are specified to be provisioned on other servers in the farm??
- Setting up crawl addresses for default content source...Done.
- Requesting searchfarmdashboard.aspx (resolves Health Analyzer error)...------
--------------------------------------------------------
- Script halted!
Exception : System.Net.WebException: The operation has timed out.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.
GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.
ProcessRecord()
TargetObject : System.Net.HttpWebRequest
CategoryInfo : InvalidOperation:
(System.Net.HttpWebRequest:HttpWebRequest)
[Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Comm
ands.InvokeWebRequestCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateEnterpriseSearchServiceApp, \\agsql1\share\SP\
2013\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 4040
at Setup-Services, \\agsql1\share\SP\2013\AutoSPInstall
er\AutoSPInstallerMain.ps1: line 207
at <ScriptBlock>, \\agsql1\share\SP\2013\AutoSPInstalle
r\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
-----------------------------------
| Automated SP2013 install script |
| Started on: 4/28/2013 9:42:39 AM |
| Aborted: 4/28/2013 9:53:32 AM |
-----------------------------------
PS C:\Windows>
Comments: Resolved with changeset 100404: Changes in this release:
AutoSPInstallerFunctions.ps1:
- InstallCumulativeUpdates function now parses opatchinstall*.log for result code to determine if the patch application worked, was not needed, etc.
- InstallCumulativeUpdates also no longer requires the SP2013 March 2013 PU patch to be present in \Updates (e.g. in case it was already applied or slipstreamed)
- Added try & catch to the section of CreateEnterpriseSearchServiceApp that issues a request to searchfarmdashboard.aspx so script doesn't blow up if it fails or times out
- Consistently used the MatchComputerName function throughout script to better support FQDNs
Has anyone come across this error below, my script keeps getting stuck at the following point when provisioning my first App server and not sure why??
Could it be that my Crawl and Query components are specified to be provisioned on other servers in the farm??
- Setting up crawl addresses for default content source...Done.
- Requesting searchfarmdashboard.aspx (resolves Health Analyzer error)...------
--------------------------------------------------------
- Script halted!
Exception : System.Net.WebException: The operation has timed out.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.
GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.
ProcessRecord()
TargetObject : System.Net.HttpWebRequest
CategoryInfo : InvalidOperation:
(System.Net.HttpWebRequest:HttpWebRequest)
[Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Comm
ands.InvokeWebRequestCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateEnterpriseSearchServiceApp, \\agsql1\share\SP\
2013\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 4040
at Setup-Services, \\agsql1\share\SP\2013\AutoSPInstall
er\AutoSPInstallerMain.ps1: line 207
at <ScriptBlock>, \\agsql1\share\SP\2013\AutoSPInstalle
r\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
-----------------------------------
| Automated SP2013 install script |
| Started on: 4/28/2013 9:42:39 AM |
| Aborted: 4/28/2013 9:53:32 AM |
-----------------------------------
PS C:\Windows>
Comments: Resolved with changeset 100404: Changes in this release:
AutoSPInstallerFunctions.ps1:
- InstallCumulativeUpdates function now parses opatchinstall*.log for result code to determine if the patch application worked, was not needed, etc.
- InstallCumulativeUpdates also no longer requires the SP2013 March 2013 PU patch to be present in \Updates (e.g. in case it was already applied or slipstreamed)
- Added try & catch to the section of CreateEnterpriseSearchServiceApp that issues a request to searchfarmdashboard.aspx so script doesn't blow up if it fails or times out
- Consistently used the MatchComputerName function throughout script to better support FQDNs