Lydia Bronze

How to resolve HTTP 500 Internal Server Error in SharePoint 2013 site

January 12th, 2013 | Author: | Filed under: CloudShare, SharePoint | Tags: , , , , , , ,


Once in a while I encounter an error that doesn’t provide any helpful information. This is exactly what happened the other day I opened my SharePoint site and found out that the website cannot display the page due to HTTP 500 Internal Server Error.

First thing I tried to do is open SharePoint Central Administration, to see if I get the same error message. Strangely, I was able to open Central Administration without any errors.

01 - SharePoint 2013 the website cannot display the page HTTP 500

 

I opened IIS Manager to make sure SharePoint – 80 Application Pool was running, and I noticed that SecurityTokenServiceApplicationPool application pool was stopped.

02 - SecurityTokenServiceApplicationPool Application pool is stopped

I started SecurityTokenServiceApplicationPool application pool, refreshed my SharePoint site but that didn’t resolve the issue. I opened IIS manager and noticed that SecurityTokenServiceApplicationPool was stopped again.

In that case, best thing to do was to open IIS events log and check what’s going on with SecurityTokenServiceApplicationPool application pool

03 - IIS events log

 

The IIS event log showed the warning ID 5021:

The identity of application pool SecurityTokenServiceApplicationPool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.  If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

In order to resolve this problem I navigated back to IIS manager -> SecurityTokenServiceApplicationPool application pool-> Advanced Settings.

04 - SecurityTokenServiceApplicationPool advanced settings

Navigated to the Identity option.

05 - SecurityTokenServiceApplicationPool advanced Identity settings

Updated the user’s credentials and clicked on OK.

06 - SecurityTokenServiceApplicationPool reset Identity credentials

07 - SecurityTokenServiceApplicationPool reset Identity credentials

I performed iisreset.

08 - IIS reset

And opened IIS manager again to check if it worked. SecurityTokenServiceApplicationPool was now started and didn’t stop anymore.

09 - SecurityTokenServiceApplicationPool is started

 

My SharePoint 2013 site was working again!

10 - SharePoint 2013 team site

 

About the author:
Lydia Bronze ( @LydiBee ) , Cloud Content Architect at CloudShare, is an experienced technologist with a diverse and deep background in infrastructure technologies, information security and technical training. Lydia's proven ability to architect, implement and provide solutions for advanced infrastructures using Microsoft and Open Source technologies makes her an invaluable asset to the team. She brings technical experience from a variety of industries, including the Defense and Finance sectors. In addition, Lydia has extensive SharePoint experience and has implemented corporate environments as well as custom SharePoint solutions for organizations of all sizes. Lydia is continuously seeking new challenges that will allow her to utilize her technical abilities.

  • Marius Constantinescu

    Hi Lydia,
    Would you happen to know why that happen in the 1st place (source of the problem)?
    Thank you for the tip otherwise,
    C:>Marius

    • Lydia Bronze

      Hi Marius,

      Apparently the password was changed. Unfortunately this is not automatically updated in the web application and needs to be updated manually. This can also happen when the user has insufficient permissions.

      • Marius Constantinescu

        Hi again Lydia,
        I thought so, ok, it does make sense if someone simply changed it! I was expecting somewhat more stranger behaviour.
        Thank you for clearing that up,
        C:>Marius

  • devang zala

    Hi Lydia,

    Thanks a lot for the tip.

    it has saved my day.

    worked like a charm.

    in my case i have changed SPFarm Password and that has changed site behavior.

    Thanks……………….

    • http://blog.cloudshare.com/ Lydia Bronze

      Great, I’m really glad you found this helpful!

  • Ritu Ranjan

    Its Working
    Thanks
    Ritu Ranjan

  • Pingback: Summarizing the year 2012 | Beetalks

  • Janaiah

    Thanks a lot for the help.

  • Sathishkumar s

    Hi Sir

    my sharepoint2010 site is does not open because it is produce http 500 internal server error

  • Pingback: Cannot log in to SharePoint 2013 with AD account / Local Trust SSL Cert Changed | The-IT-Blog

  • http://sharepointclo.blogspot.com/ Pablo Guerra

    Good article, but i have a little doubt, ¿is it possible to get this error due to security issues in custom webparts or features?

    Thanks!

  • Pingback: SharePoint 2010: Como resolver el error HTTP 500 Internal Server Error al acceder a un sitio! - Blog de Juan Carlos González en Geeks.MS

  • Mahesh

    Thanks to the post,i got resolved by restarting the token service thank alot

  • kiran

    Thanks to post this. its really help me a lot. thank you

  • patompon

    Thank You it Solve my porblem

  • Sista Sue

    Great blog on how to fix this issue

  • obviously

    I can confirm this strategy works for the July 8, 2014 SharePoint 2013 updates that are part of the July 2014 Windows Update “patch Tuesday” set of patches.

    I had to reapply SharePoint 2013 Service Pack 1 (the good version, not the original bad version), run psconfigui.exe, reboot, run Windows Update (which applies the 4 SharePoint 2013 July 8, 2014 updates), run psconfigui.exe, and then run through the process shown above (re-entering the credentials). At that point, the HTTP 500 errors go away (for me).

  • Vicky

    Hi Lydia. I keep getting the same error 500 and all my application pools are running. I’ve impersonated the account and yet, no solution. What can I possibly do to resolve this issue?

  • LJS

    it works! thanks a lot!