Export (0) Print
Expand All
Expand Minimize

The Security Token Service is not available (SharePoint 2013)

Published: July 16, 2012

Summary: Learn how to resolve the SharePoint Health Analyzer rule "The Security Token Service is not available."

Applies to:  SharePoint Foundation 2013 | SharePoint Server 2013 

Rule Name:  The Security Token Service is not available.

Summary: The Security Token Service is not issuing tokens.

Cause: The service could be malfunctioning or in a bad state, or some assemblies are missing when you deploy the custom claims provider.

Resolution: Restart the Security Token Service application pool.

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

  2. Identify the server on which this event occurs. On the Central Administration Home site, in the Monitoring section, click Review problems and solutions, and then find the name of the server in the Failing Servers column. If there are multiple failing servers in a server farm, you must repeat the following steps on each failing server.

  3. Verify that the user account that is performing the following steps is a member of the Administrators group on the local computer that you identified in the previous step.

  4. Log on to the server on which this event occurs.

  5. Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

  6. In the Internet Information Services management console, in the Connections pane, expand the tree view, and then click Application Pools.

  7. In the Application Pools list, right-click SecurityTokenServiceApplicationPool, and then click Start. If the application pool is started already, click Stop and then, in the Action pane, click Start to restart it.

For more information, see Configure the security token service (SharePoint Server 2010) and Set-SPSecurityTokenServiceConfig.

Resolution: Install the missing assemblies into the global assembly cache (GAC) manually.

  1. Check the event logs and ULS logs on all servers to find out which assemblies of the custom claims provider are missing.

  2. Install the missing assemblies into the global assembly cache manually. For more information, see How to: Install an Assembly into the Global Assembly Cache (http://go.microsoft.com/fwlink/p/?LinkId=169102).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft