2

Opening a newly created site collection on SharePoint 2013 throws '500 INTERNAL SERVER ERROR'

  • Are you able to access other site collection under that web application where you created your new site collection? Can you access you central administration site? youSiteURL/SecurityTokenServiceApplication/securitytoken.svc check this URL by simply replacing the youSiteURL with your site URL and let me know. – Zakir HC Apr 16 '15 at 5:38
  • 1
    Also check your ULS logs if possible. – Zakir HC Apr 16 '15 at 5:44
  • Thank you for the response.I am unable to acces any site collection and I also tried the above solution.Nothing positive. – user41444 Apr 18 '15 at 11:36
  • did you try to iisreset? or reboot the application server? sometimes it helps – Nk SP Apr 18 '15 at 14:59
  • Check also the Windows Event log if possible – Nk SP Apr 18 '15 at 15:04
3

Resolving 500 Internal Server Error [ Source ]

  1. Go to Central Administration and see if you access.

  2. Go to IIS Manager and check you application pools are all running. If not, start your application pools. To see if they are running click on Application Pool folder and you should see the list on the right-side under state should be "running" or "stopped".

enter image description here

  1. Go to your site and see if its working now.

  2. If not, go back to IIS and check to see what application pool is turned off again. Make sure SecurityTokenServiceApplicationPool is running. If not follow this:

    • SecurityTokenServiceApplicationPool Application Pool -> Advanced Settings.

enter image description here

  • Navigated to the Identity option.

enter image description here

  • Updated the User’s Credentials and clicked on OK.

enter image description here

  1. Do an IIS Reset.

  2. Go to the site and see if its working, these steps can be repeated for any app pool that keeps going off.

[ Source ]

1

In my case when i went to View Site Collection in CA the details were blank so i knew it was the database.

Luckily we use a standard naming convention so i knew the DBs name.

Went to the SQL server and checked the SQL logs, the DB had recovered from a corruption but when i compared the Site Collection db's permissions to another working one the permissions for two values were missing:

select permission for spdataaccess and spreadonly

Added the values back and the site came up.

0

If you are getting this error for SharePoint , you can also check about the IIS feature delegation to the Central Admin.

In the site hosting server,--> start-->run-->inetmgr-->click on server-->features view--> Management pane-->double click on Feature Delegation-->Handler mapping--> change it to Read/Write.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.