I've just built a 3 tier farm using AutpSPInstaller (Release 3.98)
All of the servers were provisioned successfully apart from the second web server where I received the following error during the 'Checking for portal site collection phase':
```
Get-SPSite : The server was unable to process the request due to an internal error. For more information about the
error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the client, or turn on
tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2696 char:36
+ $getSPSiteCollection = Get-SPSite -Limit ALL | Where-Object {$_.Url ...
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletGetSite:SPCmdletGetSite) [Get-SPSite], FaultExce
ption
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetSite
- Creating Site Collection "http://portal-dev"...
--------------------------------------------------------------
- Script halted!
Exception : System.ServiceModel.FaultException: The server was unable to process the request due to an
internal error. For more information about the error, either turn on
IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the
<serviceDebug> configuration behavior) on the server in order to send the exception
information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK
documentation and inspect the server trace logs.
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst,
RequestSecurityTokenResponse& rstr)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean
bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo,
SPRequestSecurityTokenProperties properties)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(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.Administration.SPSiteCollection.get_Item(String strSiteName)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.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.SPConfigurationDatabase.CreateSite(SPWebApplication
application, SPContentDatabase database, String path, Boolean useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPSiteCollection.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.CreateDataObject()
at Microsoft.SharePoint.PowerShell.SPNewCmdletBase`1.InternalProcessRecord()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewSite:SPCmdletNewSite) [New-SPSite], FaultException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2715
at CreateWebApplications, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2506
at Setup-Farm, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 209
at <ScriptBlock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 408
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```
I also see the above error in the Application Event Log categorized as a 'Claims Authentication' issue.
I've also seen Event log errors about the Security Token Service.
The STS App Pool is running as the correct account (and has been restarted).
Browsing to the STS web service gave me a message about enabling Metadata publishing for this service which I did by editing the web.config and setting both httpGetEnabled and httpsGetEnabled as 'true.'
Once I did this it just states that the service has been created.
When trying to load the portal site I just receive an internal server error with a correlation ID although it doesn't appear that the trace logging is working on this particular server as the logs are 0 KB, presumably the root cause it causing logging to fail as well.
I've tried uninstalling SP and trying to reinstall although I receive the same error.
I'd appreciate any help as I would very much prefer not to have this server rebuilt.
Kind regards,
David
Comments: ** Comment from web user: djkemp **
I should have posted I actually sorted this issue.
FIPS was enabled via Group Policy and SharePoint isn't FIPS compliant so it causes havoc with the install.
After I got that disabled it was smooth sailing.
Cheers,
David