asked on

Unable to access site collections

Environment : Vsphere 5.5, VM = Server 2012 R2, Application = SharePoint 2013.

I am unable to access newly created site collections. When I attempt to access the site collection I receive the following message.

- Sorry Something went wrong.
- Correlation ID: ##########

Supporting Information:

- Under the health analyzer the following message is present: The Security Token Service is not available.

- ULS logs
- Failed to create instance of cookie value handler type .....

Event viewer
- SharePoint Foundation Event ID 8306 Claims Authentication

FarWest

try to enable NTLM authentication on the IIS

Antonio McMullen

ASKER

NTLM is selected when the site is created. This is the first site collection for the SharePoint farm. Even when the site is deleted and recreated the issue persists.

FarWest

could you please validate all SharePoint services accounts and check if any (other than SYSTEM accounts) is deleted or has expiry password

Walter Curtis

The Security Token Service is not available

In IIS go to --> applications pools --> Security Token Service

Make sure that app pool is running, or on-line. If not, start that app pool If it does not stay started, check the crdentials of the user that the app pool runs in the context of. If need be, go to advanced settings for the app pool and enter the credentials in fresh, using the correct information of course.

Hope that helps

Antonio McMullen

ASKER

The Security Token Service App pool is running. I stop and start the service and the issue continues.

Walter Curtis

You can confirm that the service is working correctly using one of the links below:

http://AppServerName:32843/securitytokenserviceapplication/securitytoken.svc

or

https://AppServerName:32844/securitytokenserviceapplication/securitytoken.svc

Antonio McMullen

ASKER

I am able to to browse the .svc file. I receive a page with SecurityTokenService Service as the header. The next line reads you have created a service. It continues on from there.

Walter Curtis

Looks like the message about the Security Token Service was not the issue. What service pack level are you at for SharePoint. Just noticed that you are using 2012 R2. SharePoint must be at least at service pack one when using 2012 R2.

ASKER CERTIFIED SOLUTION

Antonio McMullen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Walter Curtis

Glad that worked for you.

Antonio McMullen

ASKER

I found the solution on a blog and it resolved my problem