Hi
We have installed SharePoint 2013 Enterprise edition. Below are the environment details.
- 2 SQL Server Clustering: Active - Passive
- 3 WebFrontEndServer, 2 App Server ( App Server 01 host Farm Central Admin, App Server 02 host Search Topology)
- All server are running Windows Server 2012 Standard.
- We are using SharePoint Server 2013 SP1.
Our environment still work.
7 days ago, we have updated ApplicationHostConfig ( C:\Windows\System32\inetsrv\config\applicationHost.config) on App 02 server. Because we updated with some error, IIS couldn't work.
We restored ApplicationHostConfig file. After that, IIS can work.
Problem: The Health analyzer shows issue with The Security Token Service is not available. On failing server: App 02.
My action: - Check Security Token Service Application on APP 02: still work. I tried restart STS application.
- Check default configuration of the IIS Application Pools were set to 32-bit : False value.
- Check Authentication under IIS: Allow Windows Authentication and Anonymous Authentication.
- Remove App 02 from FARM, uninstall SharePoint, re-join App02 to FARM.
-> Still not work.
I found issue on ULS:
SPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Operation is not valid due to the current state of the object. (Fault Detail is equal to An ExceptionDetail, likely
created by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo
requestInfo, IClaimsIdentity identity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutp...
37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67* OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Claims Authentication fsq7 High
...utIdentityForRequest(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope) at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaim...). 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Claims Authentication 8306 Critical An exception
occurred when trying to issue security token: Operation is not valid due to the current state of the object.. 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Claims Authentication fg9z Medium
SecurityTokenServiceNotAvailable: Error checking BPA rule: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Operation is not valid due to the current state of the object. (Fault Detail is equal to An ExceptionDetail, likely created
by IncludeExceptionDetailInFaults=true, whose value is: System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo
requestInfo, IClaimsIdentity identity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentity...
37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67* OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Claims Authentication fg9z Medium ...ForRequest(SPRequestInfo
requestInfo, IClaimsIdentity outputIdentity) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope) at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal
principal, RequestSecurityToken request) at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaim...).. 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Health 2138 Warning The SharePoint Health Analyzer detected a condition requiring your attention. The Security Token Service is not available. The Security Token Service is not issuing tokens. The service could be malfunctioning or
in a bad state. Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531". 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.67 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (Health Rule Execution: Microsoft.SharePoint.Administration.Health.SecurityTokenServiceNotAvailable, Microsoft.SharePoint.Health, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c). Execution
Time=17.1748085301344 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.69 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (EnsureListItemsData). Execution Time=18.3651832844677 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:16.73 OWSTIMER.EXE (0x06E4) 0x04B4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job microsoft.sharepoint.administration.health.securitytokenservicenotavailable-on-demand-health-analysis-job). Execution Time=79.9743403142019 37c9849c-41d1-a0b9-f3b6-5a85a60eff21
04/07/2014 12:16:17.65 OWSTIMER.EXE (0x06E4) 0x00B8 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-timer-locks). Parent No d55b1465-5631-4735-9f42-5a5ef7a99090
04/07/2014 12:16:17.65 OWSTIMER.EXE (0x06E4) 0x00B8 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Timer
Job job-timer-locks 38c9849c-b10f-a0b9-f3b6-5ee1abe1da78
04/07/2014 12:16:17.65 OWSTIMER.EXE (0x06E4) 0x00B8 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job job-timer-locks). Execution Time=9.46544882100937 38c9849c-b10f-a0b9-f3b6-5ee1abe1da78
Please help me to resolve this issue :(
Thank you
Regards