Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

If there are GPO in place, you should make sure service accounts have Log on as a Batch Job permissions

Because of this STS Token service - SecurityTokenServiceApplicationPool will not run or keeps stopping.
Central Admin site application pool keeps stopping

You will see the following error in the event log -

Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

Internet Explorer cannot display this feed - REST api not working in IE

If IE is responding correctly to REST api calls and you get a message like

Internet Explorer cannot display this feed

To fix the problem we need to disable feeds in IE. Go to the browser settings and select the Content tab, and click on the Feeds Settings button:


Then uncheck the "Turn on feed reading view" (it defaults to on, naturally).

This is for IE10. Other versions might look slightly different.

Cannot access Host Named Site Collection on a local server ( BackConnectionHostNames / DisableLoopbackCheck )

Method 1 (recommended): Create the Local Security Authority host names that can be referenced in an NTLM authentication request

To do this, follow these steps for all the nodes on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
3. Right-click MSV1_0, point to New, and then click Multi-String Value.
4. In the Name column, type BackConnectionHostNames, and then press ENTER.
5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
   
   Note Type each host name on a separate line.
   
   Note If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
7. Exit Registry Editor, and then restart the computer.

Method 2: Disable the authentication loopback check

Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry

subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

Using PowerShell:

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword

Unexpected response from server. The status code of response is 500. The status text of response is system.servicemodel.serviceactivationexception - When accessing TERM-Driven-page link on Term Store Management

If you encounter this weird error message while accessing TERM-Driven-page link on Term Store Management, don't get panic.. the solution is very simple :-)

'iisreset /noforce' 

Happy Sharepointing!