Creating new Web Application Error: This page can’t be displayed

While creating a new web application, a 404 'Page not found' error is displayed and the web application is only provisioned on the local server
After a number of web applications have been created in the SharePoint 2010 farm, further attempts to create a new web application through Central Administration result in the following:
The creation process results in a 'Page cannot be displayed' message.
The web application is only provisioned on the Central Administration server.
But if you try to create a site collection on this newly created web app, it fails. Reason is it is not completely done.
After struggling this for a while I found you can resolve by increasing the Shutdown time limit in IIS to a greater value.
Steps
Go to application pool of Central Administration.
Right click on it and go to Advanced Settings
In the Process Model section, increase the shutdown time limit to 200 for example.
It is a good idea to restart IIS now.
After searching on net for a while I found that the reason is during the web application creation process IIS is reset and by default. It allows the "Shutdown time limit" which by default is 90 seconds. Sometimes this might not be enough. And hence it forcibly shuts down in 90 seconds.

How to give the css and js file refernce in the Visual webpart from the Custom folder In SharePoint 2013

Suppose,
I want to give reference of the css and some js file in my custom web part and it is stored in my custom folder of the master page directory.
Then just need to add the links as below:


For CSS : 
<link rel="stylesheet" type="text/css" href="/_catalogs/masterpage/[foldername]/[filename]"/>



For js File:
<script type="text/javascript" src="/_catalogs/masterpage//[foldername]/[filename]"></script>

Fix: SharePoint Designer 2013: The server could not complete your request. For more specific information, click the Details below.

This happens when the current user request for some data using the SharePoint WCF Service and the server fails him due to not having the proper rights for that.

In some times,for the authenticate user as well, you will get this kind of error.

Solution : iisreset will resolve this issue.