Security token service is not available- SP2010

Security token plays an important role with respect to authentication purpose, if this stops functioning then you will start getting so many tickets regarding access as well as critical tickets which are dependent on the same as few other services are also dependent on this service i.e. security token.

Here is the Microsoft link which talks about in details on security token:

http://technet.microsoft.com/en-us/library/ee806864(v=office.14).aspx

While doing the sanity check across all front ends, we have noticed the security token service exception in the event viewer logs with respect to one of the server.

Here are the details:

Error message: Security token service is not available.

Checked the IIS status and found all the application pools and websites were in stopped status.

Started all the SharePoint entities which were in stopped status.

Checked the rule again and it was not there in the HA (Health Analyzer) list anymore.

Issue resolved, we are good now. Thank you.

Few IMP points which are essential while troubleshooting this issue:

In our case, the security token service was working initially without any issues and the farm was already built properly. But in your case, if it’s a newly built farm then it might be a hotfix issue as per this Microsoft article:

http://support.microsoft.com/kb/2493524

http://technet.microsoft.com/en-us/library/hh564135(v=office.14).aspx

If you have any queries regarding the above mentioned information then please let me know, I would be more than happy to help you as well as resolves your issues.

Also-if you have a different resolution regarding the same issue then request you to share the same so that it would be useful to other as well. Thank you.

sites and site collection in SharePoint 2010

Sites, Site collections and sub-sites: Very commonly used terms in SharePoint right from the first version i.e. SharePoint 2001 till new version i.e. SharePoint 2010. Every SharePoint version has some new features, new functionalities, different GUI interface and many more.

Today we are going to concentrate on site collection features, How exactly the GUI change, where exactly we need to check, what options are available, which features are important from day to day perspective.

For site designers: a site collection's galleries and libraries provide a means for creating a unified, branded user experience across all sites in the site collection.

For site collection administrators: a site collection provides a unified mechanism and scope for administration. For example, security, policies, and features can be managed for a whole site collection; Site Collection Web Analytics Reports, audit log reports, and other data can help administrators track site collection security and performance.

For farm administrators: site collections provide scalability for growth based on how much content is stored. Because each site collection can use a unique content database, administrators can easily move them to separate servers.

For site authors: a site collection's shared site columns, content types, Web Parts, authoring resources, workflows, and other features provide a consistent authoring environment.

For site users: a site collection's unified navigation, branding, and search tools provide a unified Web site experience.

The following list includes site features that you can configure uniquely:

Templates: You can make each site have a unique template. For more information, see Site templates included in SharePoint Foundation 2010.

Language: If language packs have been installed on the Web server, you can select a language-specific site template when you create a new site. Text that appears on the site is displayed in the site template’s language. For more information, see Deploy language packs (SharePoint Foundation 2010).

Security: You can define unique user groups and permissions for each site. For more information, see SharePoint 2010 Governance Planning (white paper).

Navigation: You can fine-tune your site's navigation experience by configuring unique navigation links in each part of your site's hierarchy. Site navigation reflects the relationships among the sites in a site collection. Therefore, planning navigation and planning sites structures are closely related activities. For more information, see Site navigation overview (SharePoint Foundation 2010).

Web pages: You can make each site have a unique welcome page and other pages.

Site layouts: You can make unique layouts or master pages available in a site.

Themes: You can change colors and fonts on a site. For more information, see Plan for using themes (SharePoint Foundation 2010).

Regional settings: You can change the regional settings, such as locale, time zone, sort order, time format, and calendar type. For more information, see Regional settings (SharePoint Foundation 2010).

Search: You can make each site have unique search settings. For example, you can specify that a particular site never appears in search results.

Content types: You can make each site have unique content types and site columns. For more information, see Content type and workflow planning (SharePoint Foundation 2010).

Workflows: You can make each site have unique workflows.

I hope the above mentioned information will be helpful to you and provide some insight that you are looking for. In case of any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues J J