How to Fix Error “HTTP 500 Internal Server Error in SharePoint 2013”

Once in a whereas I encounter a slip-up that doesn't give any useful data. this can be specifically what happened the opposite day I opened my SharePoint website and found out that the web site cannot show the page due to HTTP 500 Internal Server Error on my SharePoint 2013. First thing I attempted to try and do is open SharePoint Central Administration, to see if i get constant error message. Strangely, I used to be ready to open Central Administration with none errors.



Open the IIS Manager to make sure SharePoint 2013: eighty Application Pool was running, and that i noticed  that SecurityTokenServiceApplicationPool application pool was stopped.



I started SecurityTokenServiceApplicationPool application pool, refreshed my SharePoint website however that didn’t resolve the problem. I opened IIS manager and noticed  that SecurityTokenServiceApplicationPool was stopped once more.





In that case, smartest thing to try and do was to open IIS events log and check what’s occurring with SecurityTokenServiceApplicationPool application pool.
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.

To Fix this error:

1. Back to IIS manager -> SecurityTokenServiceApplicationPool application pool-> Advanced Settings.




2. Go to the Identity option.
3. Then, Update the user’s credentials and click OK button. I perform IISreset.
4. Open the IIS manager once more to examine if it worked. SecurityTokenServiceApplicationPool was now started and didn't stop any longer.




5. Finally, my SharePoint 2013 site was operating again :)

Fixed:--SharePoint Designer 2013 Crashing on Open Site

The Problem

When I installed SPD2013 on my laptop, all went well. However, every time I tried to use the Open Site dialog, it would crash. SharePoint Designer 2010 (SPD2010) was still working fine when I accessed other 2010-based installations, but not SPD2013.
I found a fix that worked for me in the Technet forums. You may or may not want to trawl through the thread, as it is quite long. Instead, here’s the Cliff Notes version of what worked for me.

You can repair your SPD 2010 to restore the regkey for SPD2010.
The issue might happen in case the ClientGUID of the Open Site dialog in SPD14 is the same as the one of the open site dialog in SPD 15 in a certain Side by Side environment.
(this repro’s only in a specific environment, but I couldn’t find the enviroment yet and when the GUIDs could be the same)
so I have couple of questions. Sorry to bother you, :(
1. Could you please check if ClientGUID value under HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site is the same as the ClientGUID value under HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site?
2. If the values are the same, could you please check if the crash still happens after removing both registry keys?
3. Have you ever installed any other version of SPD15 on your machine? (e.g. beta version) or any other version of SPD14?
4. if the issue still happens at #2, how about removing the registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDLg32\LastVisitedPidlMRU ?

Points 1 and 2 did the trick for me. Apparently both SPD2010 and SPD2013 had the same GUID for the ClientGUID value in the registry. I had not installed any betas of SPD2013 on my laptop because I was concerned about exactly this sort of incompatibility. (I’d limited my use of SPD2013 to launching it inside virtual machines.)

The Fix

If you have this problem and want to fix it, here are the steps.
Open the Registry Editor. You can do this by going to the Start menu (I’m still a Windows 7 stalwart, so I can’t vouch for how this might work on Windows 8), choosing “Run”, and typing “regedit” in the Open: box.
Look for the keys:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site
and
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Open Find\Microsoft SharePoint Designer\Settings\Open Site
In my case, they were identical, as shown below.
SharePoint Designer 2010 (14.0)

SharePoint Designer 2013 (15.0)

Delete both of the ClientGUID keys. You can do this by highlighting the key and hitting the Delete key or right clicking and choosing Delete.
Once I had deleted these two registry keys, I was able to open sites in both versions of SharePoint Designer with no problems.
Unfortunately, the two versions of SharePoint Designer seem to use the same recent sites list, so I see the same Recent Sites in both versions. This is going to make it confusing when I am trying to figure out which site to open. Now I’m a three SharePoint Designer version guy, as I’m still using SPD2007 and SPD2010 for client work in addition to SPD2013. Yeesh.

How to Resolve Error Creating Publishing Sites In SharePoint ?

I have come upon a problem in SharePoint 2013 related to the creation of publishing Sites. rather than the site being created, the user is confronted with the error below.

A list of errors logged in the ULS is at the top of this post, however the problem is because of access being denied to __DeviceChannelMappings.aspx.

To resolve the error use SharePoint Designer to assign the Restricted read access to _catalogs/masterpage and DeviceChannels.
Within SharePoint Designer, right-click on masterpage and select properties.

Now, Click on Permissions for this list

Then Assign Restricted Read permissions to the appropriate user, or group.

Next, repeat the process for the DeviceChannels folder.

List of ULS error messages:
<nativehr>0x81070211</nativehr><nativestack></nativestack>Cannot open file “_catalogs/masterpage/__DeviceChannelMappings.aspx”.
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)),
Unexpected error when trying to populate mobile mappings file ‘_catalogs/masterpage/__DeviceChannelMappings.aspx’ in web ‘/SITENAME': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
A runtime exception was detected. Details follow.  Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))  Technical Details: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))    
Watson Reporting Cancelled) System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))   
Event log message was: ‘Failed to initialize some site properties for Web
at Url: ‘http://SITENAME&#8221;. Exception was: ‘System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Publishing Feature activation failed. Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to initialize some site properties for Web
at Url: ‘SITENAME’ OriginalException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) —> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))