Skip to main content

Legacy SharePoint troubleshooting - Web application provisioning failure

While configuring a SharePoint farm, I encountered an issue where a web application created through SharePoint Central Administration was not being provisioned in Internet Information Services (IIS) on the web front-end servers.

This was particularly confusing because the web application creation process had been initiated through Central Administration, but the expected IIS configuration was missing.

The investigation involved the SharePoint Worker Process Group Update timer job and the web application provisioning process.

Symptoms

  • A new SharePoint web application was created through Central Administration.
  • The corresponding web application was not appearing in IIS on the web front-end servers.
  • The SharePoint Worker Process Group Update job was associated with the provisioning problem.

Troubleshooting and resolution

The original troubleshooting notes below document the investigation and corrective action taken in that environment.

Applicability: This is historical guidance for older on-premises SharePoint farms. It does not apply to SharePoint Online, where Microsoft manages the underlying web servers and provisioning infrastructure.

I was implementing a new SharePoint farm and I observed that web application that I create in Central Admin site was not getting created in the IIS of WFE servers.

The sites would be created in the WFE if I restart the WSS web application service through stsadm command. But this was not an option. I ran the stsadm execadmsvcjobs and it thew this error:

The SharePoint Worker Process Group Update job failed with the following error.
This job will be skipped. Failed to connect to an IPC Port: The system cannot find the file specified.

It turned out that the service "Windows SharePoint Services Administration" was stopped on all my MOSS servers. Once I started this service the issue was resolved.
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...
10 comments
Read more

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more

Document Property disabled under Quick Parts in Word 2010

Document Property under Quick Parts sometimes appears grayed out or disabled in Word client and we can see that Compatibility mode written on the Word client on the top part. This happens because Word disables certain features to make our document compatible with previous versions of Office. To workaround we have to change the compatibility feature. To do that click File on the Word ribbon and select Info. Click on Convert button and click OK on the pop up message. This enables the disabled features and now we can access the Document Properties under Quick Part.
5 comments
Read more