issue with one of web site created.
Issue: Website cannot display the page due to HTTP 500 Internal Server Error.
I tried to do open SharePoint Central Administration, to see if I get the same error message. Strangely, I was able to open Central Administration without any errors.
I opened IIS Manager to make sure SharePoint – 80 Application Pool was running, and I noticed that SecurityTokenServiceApplicationPoolapplication pool was 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.
I Check the IIS events log to check what’s the issuewith SecurityTokenServiceApplicationPool application pool.
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.
Navigated to the Identity option.
Updated the user’s credentials and clicked on OK.
I performed iisreset.
And opened IIS manager again to check if it
worked. SecurityTokenServiceApplicationPool was now started and didn’t stop anymore.
My SharePoint 2013 site was working again!
- See more at: http://expertsharepoint.blogspot.de/2014/01/http-500-internal-server-error-in.html
Note: I resolved the issue by above Method. If you find a different solution, please report it as a comment to this post. This will be useful to SharePoint Community. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.
Nenhum comentário:
Postar um comentário