Skip to content

Configuration Wizard hanging? Don’t forget NIC cards!


I was recently on a team installing SharePoint 2010 for a client.  The client had created the service accounts and set up the hardware based on the MS whitepapers we recommended.  Once on site we ran the PrerequisiteInstaller and installed the SharePoint binaries without issue.  Then we kicked off the Configuration Wizard.  Step one, no problem.  Step two, no issue.  Step three… hello?  Step three was hanging.

First we checked the obvious stuff:  Event logs (no errors), SharePoint logs (no errors), SQL permissions and configuration all looked fine.

One of the first things that often occurs to me in slowness/hanging situations are the NIC cards.  This is because I once had a major performance issue in a MOSS environment caused by improperly configured NIC card settings.  So we asked the Systems Team to take a look and they said we were set for a Gig/full.  Fine.

 Searching this issue on the internet turned up a few results.  The most promising was concerning the disabling of IPV6.  After consulting one of our contacts at MS, we disabled IPV6.  Still hanging at step 3. 

We tried using the Psconfig command-line tool instead of the GUI .  Same story.

 We tried uninstalling and re-installing the binaries (even with a different install source in case the original was corrupted).  Still hanging.

 Since we weren’t getting any errors we thought we’d just let it run overnight and see what happens.  The next morning, sure enough, the wizard was no long stuck on step three…it was now on step 5.

 So it appeared that the configuration wizard was running successfully.  It was just running very, very slowly.  This led us back to connectivity/NIC cards again.  After asking the Systems Team to take one more look at the NIC card configuration, they realized that they had only checked the SQL server, which was set to Gig/Full.  But the SharePoint servers were only set to 100MB/half.  Bingo!  Once they opened those suckers up, the Configuration Wizard ran within a couple of minutes.

 So what are the lessons learned here?

  1. Don’t forget about the NIC cards as a major performance factor – EVEN DURING CONFIGURATION!
  2. Don’t take anyone’s word for it!  Here’s how to check that you actually have the connectivity you need.  Details may vary depending on what type of adapter you’re using and which OS, etc.  But basically, you want to look at the properties of the NIC card.  It should look something like this.


One interesting thing to note is that in the MOSS requirements document the Network connectivity requirements are called out explicitly

But in the 2010 document , there is no mention of Network requirements.  So while we know that we need the cards opened up, pointing a client to this document will not educate them to set this up properly.  (The requirement is mentioned in the Capacity Planning document).

Hope this might save you time if you run into the same issue!

  1. dpalfery01 permalink

    This blog post was the answer for a one weekend problem. Thank you so much for taking the time to post your solution!

  2. You’re welcome – glad it helped!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: