Quantcast
Channel: AutoSPInstaller
Viewing all 2279 articles
Browse latest View live

Commented Unassigned: Error sp2016 null-valued [22222]

$
0
0
- Granting DOMAIN\SPADMIN rights to "Portal Home"...--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.RuntimeException: You cannot call a method on a null-valued
expression.
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)
TargetObject :
CategoryInfo : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : InvokeMethodOnNull
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2810
at CreateWebApplications, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 2670
at Setup-Farm, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
at <ScriptBlock>, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
Comments: ** Comment from web user: franky113 **

We have the same problem. We try to install SP2016 on Server 2012R2 with a separate SQL 2016 Server.
The fix works fine, but is there any update or idea how to solve the problem without deleting the wep app and launch the script again?


Created Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe

New Post: How to perform a repair on a Sharepint install that used autospinstaller

$
0
0
Hi
Is there a specific set of steps required to perform a repair on a Sharepoint 2010 Installation that had been performed using the autospinstaller? For example if I have SP1 slipstreamed into the Autospinstaller Updates folder and choose to do a repair from the control panel it seems to only install the basic RTM binaries. I have tried installing some of these binaries directly from the updates folder but there are too many. Should I be able to simply rerun the batch file and reinstall the server? The rest of the farm is fine so I dont want to run the risk of the installer making changes just because I want to update a single server with SP1. Any insights would be great thanks, Ian

Commented Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe
Comments: ** Comment from web user: owarya **

+1 this.

sts2016-kb3115181-fullfile-x64-glb.exe (June 2016) was also ignored. Installed it manually during the pause after SharePoint binary installation.

New Post: How to perform a repair on a Sharepint install that used autospinstaller

$
0
0
There is nothing special about AutoSPInstaller which would lead to a different course of action. If I understand your situation correctly, one of your servers maybe missing the correct binaries and still part of the farm i.e., shows on Get-SPServer.

If this is the case, I would suggest that you run configuration wizard on that server, disconnect it from the farm first (more care needed if server is part of Search Topology).

How to fix after this point should not affect the farm as it will only join the farm when binaries match. I would not manually install anything from the updates folder and No, you cannot simply rerun the batch file and reinstall the server. You would have to disconnect, uninstall all the binaries, then re-install. At this point, you may be better off starting with a fresh server.

As of AutoSPInstaller making changes, it actually may do that. It depends whether your farm configurations have changed since you have first installed SharePoint. You may want to use AutoSPInstaller to install the binaries, Join the farm, install standard services and features, then stop. That will likely leave a lot to be done, but it will likely not change the configuration of your farm.

It is not a very good position to be and the constraints you have given does not make this task any simpler.

New Post: How to perform a repair on a Sharepint install that used autospinstaller

New Post: Add a new wfe to an existing farm

$
0
0
Hi all,

I want to add a new wfe to an existing farm but I'm not sure about the steps that I should follow. Should I leave the rest of the servers in the XML? AutoSPInstaller expects a web application to create but if it's just add a new wfe why I need a web application? Can anyone help me please?

Thanks!
Victor

New Post: Autospinstaller bypassing managed metadata service application

$
0
0
Sorry for reviving this old post

I have the same issue as well. I need to create a new MMS for use for a different app. Currently AutoSPInstaller will not allow more than 1 MMS created as the function CreateMetadataServiceApp check on the SPServiceInstance type rather than the display name as such
$metadataServiceInstances = Get-SPServiceInstance | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceInstance"}

$metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy"}
Changing it to the following will solve your pain.
$metadataServiceInstances = Get-SPServiceInstance | ? {$_.DisplayName -eq $metadataServiceName}

$metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.DisplayName -eq $metadataServiceProxyName }

Created Unassigned: Possibility of Creating multiple Managed Metadata Service Application [22300]

$
0
0
I need to create a new MMS for use with RecordPoint however current AutoSPInstaller will not allow more than 1 MMS created as the function CreateMetadataServiceApp checks on the SPServiceInstance type rather than the display name as such

> $metadataServiceInstances = Get-SPServiceInstance | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceInstance"}

> $metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy"}

Changing it to the following solved my pain.

> $metadataServiceInstances = Get-SPServiceInstance | ? {$_.DisplayName -eq $metadataServiceName}

> $metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.DisplayName -eq $metadataServiceProxyName }

I was wondering can this flexibility be incorporated in AutoSPInstaller for the benefit of others who have similar requirement as mine?

Created Unassigned: Stop-DefaultWebsite stops wrong IIS website [22333]

$
0
0
Function Stop-DefaultWebsite

Specifically
```
$defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}

```
Stops wrong site. In my case it stopped SPWeb services
```

Name ID State Physical Path Bindings
---- -- ----- ------------- --------
SharePoint Web 1 Started C:\Program Files\Common http *:32843:
Services Files\Microsoft Shared\Web https *:32844:
Server sslFlags=0
Extensions\16\WebServices\Root net.tcp 32845:*
net.pipe *

```
please remove this from where statement
```
$_.ID -eq 1
```

Commented Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe
Comments: ** Comment from web user: KoenZomers **

Same issue here. It comes down to the line in AutoSPInstallerFunctions.ps1 where it states:

```
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe,sharepointsp2013*.exe,coreserver201*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
```

It should be:

```
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe,sharepointsp2013*.exe,coreserver201*.exe,sts2016-kb*.exe,wssloc2016-kb*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
```

Created Unassigned: Error: Custom file location is not accessible while offline prerequisite installer [22339]

$
0
0
I am having an issue when autoinstaller is trying to configure the SharePoint 2013 Standalone offline mode.

My system configurations: OS: Windows Server 2012 R2
SharePoint : 2013 Enterprise Trail

please see below error. I copied prerequisites in proper location.

--------------------------------------------------------------

- Installing Prerequisite Software:

- .Net Framework 3.5.1 from "C:\SP\2013\SharePoint\PrerequisiteInstallerFiles\sxs"...Already installed.

- Running Prerequisite Installer (offline mode)....Done.

- Prerequisite Installer completed in 00:00:05.

WARNING: 2016-08-24 21:43:44 - Error: Custom file location is not accessible

--------------------------------------------------------------

- Script halted!

Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to

parameter 'Message' because it is null.

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)

TargetObject :

CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningComman

d

ErrorDetails :

InvocationInfo : System.Management.Automation.InvocationInfo

ScriptStackTrace : at InstallPrerequisites, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 882

at Run-Install, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184

at <scriptblock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 381

at <scriptblock>, <no file="">: line 1

PipelineIterationInfo : {}

PSMessageDetails :

-----------------------------------

| Automated SP2013 install script |

| Started on: 8/24/2016 9:43:38 PM |

| Aborted: 8/24/2016 9:43:50 PM |

-----------------------------------

PS C:\SP\AutoSPInstaller>

Commented Unassigned: Error: Custom file location is not accessible while offline prerequisite installer [22339]

$
0
0
I am having an issue when autoinstaller is trying to configure the SharePoint 2013 Standalone offline mode.

My system configurations: OS: Windows Server 2012 R2
SharePoint : 2013 Enterprise Trail

please see below error. I copied prerequisites in proper location.

--------------------------------------------------------------

- Installing Prerequisite Software:

- .Net Framework 3.5.1 from "C:\SP\2013\SharePoint\PrerequisiteInstallerFiles\sxs"...Already installed.

- Running Prerequisite Installer (offline mode)....Done.

- Prerequisite Installer completed in 00:00:05.

WARNING: 2016-08-24 21:43:44 - Error: Custom file location is not accessible

--------------------------------------------------------------

- Script halted!

Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to

parameter 'Message' because it is null.

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)

TargetObject :

CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException

FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningComman

d

ErrorDetails :

InvocationInfo : System.Management.Automation.InvocationInfo

ScriptStackTrace : at InstallPrerequisites, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 882

at Run-Install, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184

at <scriptblock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 381

at <scriptblock>, <no file="">: line 1

PipelineIterationInfo : {}

PSMessageDetails :

-----------------------------------

| Automated SP2013 install script |

| Started on: 8/24/2016 9:43:38 PM |

| Aborted: 8/24/2016 9:43:50 PM |

-----------------------------------

PS C:\SP\AutoSPInstaller>
Comments: ** Comment from web user: venukasa **

Please help I struck here

New Post: Add beta support to use "SharePointDsc" with autospinstaller.com

$
0
0
I think that can be a great idea to use "SharePointDsc" (https://github.com/PowerShell/SharePointDsc) as engine for future autospinstaller development.
For example from autospinstaller.com generate a configuration file that using SharePointDsc.
Both are powershell code/function to install SharePoint automatically.
Autospinstaller is more simple, easy debugging, solid, robust and consolidate than SharePointDsc so can be a great idea transfer the knowledge and experience to it.

New Post: Add beta support to use "SharePointDsc" with autospinstaller.com

$
0
0
Actually as I see it, SharePointDSC will eventually replace AutoSPInstaller. In fact I'm already working with the SharePointDSC folks to bring it to feature parity with AutoSPInstaller.

Thanks,
Brian

Created Unassigned: WebAdministration Error 2012 R2 [22344]

$
0
0
I have set the XML file up correctly and have all the pre-req's installed. About midway through the script when it starts creating webapplications it errors out saying the PowerShell module "WebAdministration" is not loaded. Attempting to do Import-Module does not work.

Commented Unassigned: WebAdministration Error 2012 R2 [22344]

$
0
0
I have set the XML file up correctly and have all the pre-req's installed. About midway through the script when it starts creating webapplications it errors out saying the PowerShell module "WebAdministration" is not loaded. Attempting to do Import-Module does not work.
Comments: ** Comment from web user: brianlala **

What OS are you using? Anyhow it appears the PowerShell module for IIS wasn't installed in your case. Can you run:

Get-Module -ListAvailable | ? {$_.Name -eq "WebAdministration"}

And see if anything is returned? If not, then possibly the module wasn't installed for some reason during the IIS portion of the prerequisiteinstaller.

Brian

Commented Unassigned: WebAdministration Error 2012 R2 [22344]

$
0
0
I have set the XML file up correctly and have all the pre-req's installed. About midway through the script when it starts creating webapplications it errors out saying the PowerShell module "WebAdministration" is not loaded. Attempting to do Import-Module does not work.
Comments: ** Comment from web user: Ghost5525 **

So i ran that and got this back:

PS C:\Windows\system32> Get-Module -ListAvailable | ? {$_.Name -eq "WebAdministration"}

Directory: C:\Windows\System32\WindowsPowerShell\v1.0\Modules


ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Manifest 1.0.0.0 WebAdministration {Start-WebCommitDelay, Stop-WebCommitDelay, Get-WebConfigu...


The OS i'm using is Windows Server 2012 R2, with SQL Server 2016, and wanting to install SP 2016 using this script which i find is awesome and very organized. Anything else i can provide let me know.

Commented Unassigned: WebAdministration Error 2012 R2 [22344]

$
0
0
I have set the XML file up correctly and have all the pre-req's installed. About midway through the script when it starts creating webapplications it errors out saying the PowerShell module "WebAdministration" is not loaded. Attempting to do Import-Module does not work.
Comments: ** Comment from web user: brianlala **

OK so the module is definitely there - we need to figure out why Import-Module WebAdministration doesn't work - what error message do you get?

Brian

New Post: Script Halted - No endpoint listening

$
0
0
Receiving the below error:
  • Script halted!
Exception : System.ServiceModel.EndpointNotFoundException: There
                    was no endpoint listening at http://localhost:32843/Sec
                    urityTokenServiceApplication/securitytoken.svc that 
                    could accept the message. This is often caused by an 
                    incorrect address or SOAP action. See InnerException, 
                    if present, for more details. ---> 
                    System.Net.WebException: Unable to connect to the 
                    remote server ---> System.Net.Sockets.SocketException: 
                    No connection could be made because the target machine 
                    actively refused it 127.0.0.1:32843
                       at System.Net.Sockets.Socket.DoConnect(EndPoint 
                    endPointSnapshot, SocketAddress socketAddress)
                       at 
                    System.Net.ServicePoint.ConnectSocketInternal(Boolean 
                    connectFailure, Socket s4, Socket s6, Socket& socket, 
                    IPAddress& address, ConnectSocketState state, 
                    IAsyncResult asyncResult, Exception& exception)
                       --- End of inner exception stack trace ---
                       at System.Net.HttpWebRequest.GetRequestStream(Transp
                    ortContext& context)
                       at System.Net.HttpWebRequest.GetRequestStream()
                       at System.ServiceModel.Channels.HttpOutput.WebReques
                    tHttpOutput.GetOutputStream()
                       --- End of inner exception stack trace ---

                    Server stack trace: 
                       at System.ServiceModel.Channels.HttpOutput.WebReques
                    tHttpOutput.GetOutputStream()
                       at 
                    System.ServiceModel.Channels.HttpOutput.Send(TimeSpan 
                    timeout)
                       at System.ServiceModel.Channels.HttpChannelFactory`1
                    .HttpRequestChannel.HttpChannelRequest.SendRequest(Mess
                    age message, TimeSpan timeout)
                       at System.ServiceModel.Channels.RequestChannel.Reque
                    st(Message message, TimeSpan timeout)
                       at System.ServiceModel.Channels.ServiceChannel.Call(
                    String action, Boolean oneway, ProxyOperationRuntime 
                    operation, Object[] ins, Object[] outs, TimeSpan 
                    timeout)
                       at System.ServiceModel.Channels.ServiceChannelProxy.
                    InvokeService(IMethodCallMessage methodCall, 
                    ProxyOperationRuntime operation)
                       at System.ServiceModel.Channels.ServiceChannelProxy.
                    Invoke(IMessage message)

                    Exception rethrown at [0]: 
                       at System.Runtime.Remoting.Proxies.RealProxy.HandleR
                    eturnMessage(IMessage reqMsg, IMessage retMsg)
                       at System.Runtime.Remoting.Proxies.RealProxy.Private
                    Invoke(MessageData& msgData, Int32 type)
                       at Microsoft.IdentityModel.Protocols.WSTrust.IWSTrus
                    tContract.Issue(Message message)
                       at Microsoft.IdentityModel.Protocols.WSTrust.WSTrust
                    Channel.Issue(RequestSecurityToken rst, 
                    RequestSecurityTokenResponse& rstr)
                       at Microsoft.IdentityModel.Protocols.WSTrust.WSTrust
                    Channel.Issue(RequestSecurityToken rst)
                       at Microsoft.SharePoint.SPSecurityContext.SecurityTo
                    kenForContext(Uri context, Boolean bearerToken, 
                    SecurityToken onBehalfOf, SecurityToken actAs, 
                    SecurityToken delegateTo, 
                    SPRequestSecurityTokenProperties properties)
                       at Microsoft.SharePoint.SPSecurityContext.SecurityTo
                    kenForLegacyLoginContext(Uri context)
                       at 
                    Microsoft.SharePoint.SPSite.InitUserToken(SPRequest 
                    request)
                       at 
                    Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm 
                    farm, Guid applicationId, Guid contentDatabaseId, Guid 
                    siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri 
                    requestUri, String serverRelativeUrl, Boolean 
                    hostHeaderIsSiteName, SPUserToken userToken, Boolean 
                    appWebRequest, String appHostHeaderRedirectDomain, 
                    String appSiteDomainPrefix, String subscriptionName, 
                    String appSiteDomainId, Uri primaryUri)
                       at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, 
                    Uri requestUri, Boolean contextSite, Boolean 
                    swapSchemeForPathBasedSites, SPUserToken userToken)
                       at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, 
                    Uri requestUri, Boolean contextSite)
                       at Microsoft.SharePoint.Administration.SPSiteCollect
                    ion.get_Item(String strSiteName)
                       at Microsoft.SharePoint.Administration.SPConfigurati
                    onDatabase.CreateSite(SPWebApplication application, 
                    SPContentDatabase database, String originalPath, Guid 
                    id, Guid siteSubscriptionId, Boolean 
                    useHostHeaderAsSiteName, Boolean bDeleted, DateTime 
                    deletionTime, String subscriptionName, String 
                    appSiteDomainId, List`1 siteUrls, Boolean bResyncMode)
                       at Microsoft.SharePoint.Administration.SPConfigurati
                    onDatabase.CreateSite(SPWebApplication application, 
                    SPContentDatabase database, String path, Boolean 
                    useHostHeaderAsSiteName)
                       at Microsoft.SharePoint.Administration.SPSiteCollect
                    ion.Add(SPContentDatabase database, SPSiteSubscription 
                    siteSubscription, String siteUrl, String title, String 
                    description, UInt32 nLCID, Int32 compatibilityLevel, 
                    String webTemplate, String ownerLogin, String 
                    ownerName, String ownerEmail, String 
                    secondaryContactLogin, String secondaryContactName, 
                    String secondaryContactEmail, String quotaTemplate, 
                    String sscRootWebUrl, Boolean useHostHeaderAsSiteName, 
                    Boolean overrideCompatibilityRestriction)
                       at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.C
                    reateDataObject()
                       at Microsoft.SharePoint.PowerShell.SPNewCmdletBase`1
                    .InternalProcessRecord()
                       at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessR
                    ecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData:
                    (Microsoft.Share...SPCmdletNewSite:SPCmdletNewSite) 
                    [New-SPSite], EndpointNotFoundException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, C:\Temp\SP\AutoSPInstaller\AutoSPInsta
                    llerFunctions.ps1: line 2889
                    at CreateWebApplications, C:\Temp\SP\AutoSPInstaller\Au
                    toSPInstallerFunctions.ps1: line 2670
                    at Setup-Farm, 
                    C:\Temp\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: 
                    line 211
                    at <ScriptBlock>, 
                    C:\Temp\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: 
                    line 410
                    at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :


All app pools are running and I can browse to the link:
http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc

As soon as script tries to run above link becomes unavailable
Viewing all 2279 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>