Unable to create any Webapp & Site Collection on SharePoint 2013 due to error 404

-
404 page not found Error while creating webapp & new site collection on it​.

After a number of web applications have been created in the SharePoint 2013 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 taken to resolve issue :

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.

Comments

Post a Comment

Popular posts from this blog

How to Improve Workflow Performance in SharePoint Server 2010

-
Image
How to Improve Workflow Performance in SharePoint Server 2010 SharePoint workflows are getting  slow for several reasons. in my environment I'm having a problem with following performance issues, therefore in my environment i got following problems. When a item added to the library it takes some times to initiate the workflow. Workflow mail generating is not very fast sometimes. Workflows takes more time to process “Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time” is coming sometimes. I had a custom workflow approval web part and it is taking more than 30 seconds to proceed. Work Done I had a custom workflow approval web part and it is taking more than 30 seconds to proceed. here in my custom web part there is the function which is programmatically updating the workflow. SPWorkflowTask.AlterTask(item, data, false) the last parameter mentioning whether it is synchronous asynchronous. if  is it ...
Read more

PowerShell Script to Check and Generate Report on Access Rights for a Specific User:

-
Requirement: To ensure security, generate permissions report on all locations like (sites, lists, etc.) where a specific user has permissions. When people moving from one role to another, Its necessary to audit their permissions on sites and lists where user has access rights. But unfortunately, There is no out of the box ways to find all sites and lists where a particular user has been granted access in SharePoint with out using third party tools. Luckily, We've PowerShell! Lets find all SharePoint sites and lists where a particular user has access rights. PowerShell Script to Check and Generate Report on Access Rights for a Specific User: With this script, you can analyze and track the security effectively check what permissions on an account has been granted on each all places in SharePoint. This PowerShell script scans these areas to to retrieve a specific user's access rights: •Farm Administrator's Group •Central Administration Web Application Polici...
Read more

Disable Loopbackcheck using PowerShell

-
Disable Loopback Check Powershell To disable Loopback check run the following cmd on the (each) SharePoint server from a SharePoint PowerShell prompt (run as administrator): New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -value "1" -PropertyType dword
Read more