[SharePoint 2013]问题安全令牌服务不可用 [英] [SharePoint 2013] Issue The Security Token Service is not available

问题描述

您好 

我们已安装SharePoint 2013企业版。以下是环境详细信息。



- 2 SQL Server群集：活动 - 被动



- 3 WebFrontEndServer ，2 App Server（App Server 01主机Farm Central Admin，App Server 02主机搜索拓扑）



- 所有服务器都运行Windows Server 2012 Standard。



- 我们正在使用SharePoint Server 2013 SP1。



我们的环境仍然有效。

7天前，我们在App 02服务器上更新了ApplicationHostConfig（C：\ Windows \ System32 \inetsrv \ config \ applicationHost.config）。因为我们更新了一些错误，IIS无法工作。

我们恢复了ApplicationHostConfig文件。之后，IIS可以正常工作。

 问题：运行状况分析器显示问题安全令牌服务不可用。在发生故障的服务器上：App 02.

我的行动： - 检查APP 02上的安全令牌服务应用程序：仍然有效。我尝试重新启动STS应用程序。

- 检查IIS应用程序池的默认配置设置为32位：假值。

- 检查IIS下的身份验证：允许Windows身份验证和匿名身份验证。

- 从FARM删除App 02，卸载SharePoint，将App02重新加入FARM。

- >仍然无效。



我在ULS上发现问题：
$


SPSecurityContext：安全令牌请求失败exception：System.ServiceModel.FaultException`1 [System.ServiceModel.ExceptionDetail]：由于对象的当前状态，操作无效。 （Fault Detail等于ExceptionDetail，可能是由IncludeExceptionDetailInFaults = true创建的
，其值为：System.InvalidOperationException：由于对象的当前状态，操作无效。  在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请求tInfo，IClaimsIdentity outputIdentity）   在Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity（IClaimsPrincipal principal，RequestSecurityToken请求，范围范围） 
 在Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue（IClaimsPrincipal principal，RequestSecurityToken request）   在Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue（IClaim ...）。 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04/07/2014 12：16：16.67  OWSTIMER.EXE（0x06E4）                    0x04B4 SharePoint Foundation         声明身份验证          8306严重尝试发放安全令牌时发生异常
：由于对象的当前状态，操作无效.. 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04 / 07/2014 12：16：16.67  OWSTIMER.EXE（0x06E4）                    0x04B4 SharePoint Foundation         声明身份验证          fg9z Medium 
SecurityTokenServiceNotAvailable：检查BPA规则时出错：System.ServiceModel.FaultException`1 [System.ServiceModel.ExceptionDetail]：由于对象的当前状态，操作无效。 （Fault Detail等于ExceptionDetail，可能由IncludeExceptionDetailInFaults = true创建
，其值为：System.InvalidOperationException：由于对象的当前状态，操作无效。  在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     声明身份验证      fg9z Medium  ... ForRequest（SPRequestInfo
requestInfo ，IClaimsIdentity outputIdentity）   在Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity（IClaimsPrincipal principal，RequestSecurityToken请求，范围范围）   在Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue（IClaimsPrincipal
principal，RequestSecurityToken request）   在Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue（IClaim ...）.. 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04/07/2014 12：16：16.67  OWSTIMER.EXE （0x06E4）                    0x04B4 SharePoint Foundation         健康                   
    2138警告  SharePoint运行状况分析器检测到需要您注意的情况。  安全令牌服务不可用。  安全令牌服务不会发出令牌。该服务可能出现故障，或者在状态不佳时为
。  管理员应尝试在不发出令牌的框中重新启动安全令牌服务。如果问题仍然存在，KB文章中可能会提供进一步的故障排除。有关此规则的详细信息，请参阅"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         监控                 
  b4ly高   离开受监视的范围（健康规则执行：Microsoft.SharePoint.Administration.Health.SecurityTokenServiceNotAvailable，Microsoft.SharePoint.Health，Version = 15.0.0.0，Culture = neutral，PublicKeyToken = 71e9bce111e9429c）。执行
时间= 17.1748085301344 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04/07/2014 12：16：16.69  OWSTIMER.EXE（0x06E4）                    0x04B4 SharePoint Foundation         监控                 
  b4ly高   离开受监视的范围（EnsureListItemsData）。执行时间= 18.3651832844677 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04/07/2014 12：16：16.73  OWSTIMER.EXE（0x06E4）                    0x04B4 SharePoint Foundation         监控                 
  b4ly中等 离开监控范围（计时器作业microsoft.sharepoint.administration.health.securitytokenservicenotavailable-on-demand-health-analysis-job）。执行时间= 79.9743403142019 37c9849c-41d1-a0b9-f3b6-5a85a60eff21

04/07/2014 12：16：17.65  OWSTIMER.EXE（0x06E4）                    0x00B8 SharePoint Foundation         监控                 
  nasq Medium 输入监控范围（定时器作业作业定时器锁定）。家长否d55b1465-5631-4735-9f42-5a5ef7a99090

04/07/2014 12：16：17.65  OWSTIMER.EXE（0x06E4）                    0x00B8 SharePoint Foundation         记录关联数据      xmnv中等 名称=计时器
作业job-timer-locks 38c9849c-b10f-a0b9-f3b6-5ee1abe1da78

04/07/2014 12：16：17.65  OWSTIMER.EXE（0x06E4）                    0x00B8 SharePoint Foundation         监控                 
  b4ly中等 离开监控范围（定时器作业作业定时器锁定）。执行时间= 9.46544882100937 38c9849c-b10f-a0b9-f3b6-5ee1abe1da78 

 

请帮我解决此问题:(



谢谢你
问候

解决方案

这很奇怪，你说你删除服务器并完全卸载在这个过程中，如果错误仍然存​​在，您是否检查了运行状况分析器？ 

尝试重新分析运行状况规则。

还要检查：  http：// sharepoint .stackexchange.com / questions / 1964 / export-an-agenda-in-a-meeting-workspace

o r可能需要重新配置STS。

http：/ /alstechtips.blogspot.com/2014/02/sharepoint-2010-health-analyzer_18.html

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

解决方案

that's weird, you said you remove the server and completely uninstall the SharePoint and rejoin the server to farm. during this process, did you check health analyzer if error still there? 

try to re analyze the health rule.

also check this: http://sharepoint.stackexchange.com/questions/1964/export-an-agenda-in-a-meeting-workspace

or may be need to re provision the STS.

http://alstechtips.blogspot.com/2014/02/sharepoint-2010-health-analyzer_18.html

这篇关于[SharePoint 2013]问题安全令牌服务不可用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！