Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SharePoint 2010: 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

SharePoint 2010: 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

View products that this article applies to.

Symptoms

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:
  1. The creation process results in a 'Page cannot be displayed' message.
  2. The web application is only provisioned on the Central Administration server.
Additionally, you may see Event ID 5013 in the application event logs of the SharePoint Server.

↑ Back to the top

Cause

As more and more web applications are created, the time in which it takes to create a web application increases. As part of the creation process, IIS is reset and by default, the application pool allows 90 seconds for the connections to close off before forcibly shutting down. When the number of web applications grows above 10, 90 seconds is not enough time for the provisioning to finish.

As a result, the w3wp process is killed and the provisioning process is stopped prior to the timer jobs being created.

↑ Back to the top

Resolution

The solution to this is to allow the process a longer amount of time before it is forcibly shutdown.
  • On the server(s) hosting Central Admin, open IIS manager.
  • In the tree view, expand the server name and click on Application Pools.
  • Locate the SharePoint Central Administration v4 application pool. Right click on it and choose Advanced Settings.
  • In the Process Model section, set the Shutdown Time Limit to a greater value. As an example, 300.
  • Restart IIS.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2543306
Revision : 1
Created on : 1/7/2017
Published on : 10/16/2012
Exists online : False
Views : 313