SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I installed Sharepoint 2010 in farm mode on two instances. The installation was successful. I then tried to create a new web application , the web application was also created successfully. I could see the new web application on both the instances central admin. But I only see the site in on of the instances IIS , and it does not show up in other instances IIS.

Any help is appreciated.

share|improve this question
are you talking about 2 WFEs connected to the same farm here? Or 2 separate farms entirely? – pigeon Feb 8 '13 at 11:42
up vote 3 down vote accepted

Seems like your SharePoint WFE is out of synchronization as the web application is created in one server and it is not created in the other.

  • You can solve issue by deleting the web application first you just created.
  • Restart the timer services in both the WFE and try creating a web application

Or you can also try this STSADM command before performing steps above,

stsadm -o execadmsvcjobs

it will start all jobs waiting for execution by timer job.

Hope it helps.

share|improve this answer

There could be a number of things that are preventing the web application from being created on the second server. Here are a few things you can check:

Timer Service: Nearly everything that is done on multiple farm servers is done through the SharePoint timer service. Make sure that is running on all servers in your farm. If it is running, it is possible that something is hung up. Restarting the timer service on each server in the farm can sometimes help with hung timer processes.

Patch Level: I've not heard of something like this happening when farm servers are on different patch levels, but you may want to verify that SharePoint is on the same patch level for each server in the farm.

ULS Logs: Anything and everything that is done in SharePoint will show up in the ULS tracing logs. Keep in mind that there are ULS logs located on each server in the farm, so if there is something specific happening in the timer service on the server that is failing to create the web application in IIS it will show up in the ULS logs on that server. You may need to increase the tracing level as high as 'Verbose' to get a detailed picture as to what is happening. The ULS logs will most often lead you in the direction you need to go to find the source of the problem.

Windows Event Logs: If there is something happening at the OS or IIS level, it is likely that there will be an entry in the Windows Event logs that can help point you in the right direction here too.

IIS is running: I would of course assume that the World Wide Web Publishing service is up and running on the server that is failing. If IIS is in a hung state, it may be necessary to restart this service or perform an 'iisreset' on that server.

Another item to verify is that the 'Microsoft SharePoint Foundation Web Application' role is running on that server in your farm. You can check this in Central Admin. It should be in a 'Started' state.

The above items should be good starting points for you to troubleshoot as to why the web application is not being created in IIS.

share|improve this answer

Did you see any error message while you configure the web application? You should be see your site on IIS after the web application has been successfully installed.

I would recommend you to reinstall your SP site and then see the result again.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.