Installing MSS2010 Express on SharePoint Foundation

If you’ve gone as far as to install SharePoint Foundation and your environment can handle the additional load, why not extend the search capabilities with Microsoft Search Server Express? It’s free and will provide powerful, web-style search across your corporate intranet sites quickly, and easily. You can find additional information on it here:

I’m convinced, so I went ahead and installed it only to run into a few snags along the way. I’m running a standalone installation of Foundation with a couple of site collections. Mainly to test new functionality and upgrade my masterpages before permanently migrating my content. During the Foundation install a site collection was created on port 80 without a host header, I can’t remember if I was prompted to enter one or not. But I later added one in Central Administration and made sure in IIS that the Web Application had the correct settings. So when the MSS 2010 Express initiated the SharePoint 2010 Products Configuration Wizard I thought I was gold. Only to be prompted with the following error:

Failed to create sample data.
An exception of type System.ArgumentException was thrown. Additional exception information: The directory C:\inetpub\wwwroot\wss\VirtualDirectories\80 is already being used by another IIS Web Site. Choose a different root directory for your new Web application.


Searching online didn’t result in much information, but some people have experienced similiar errors when web applications were created without host headers. Even after ensuring that the default site had its header the Configuration Wizard would not complete. Solution – backup the Site Collection, delete the Web Application and re-run the wizard. Simple enough. Except that when deleting a Site Collection from Central Admin doesn’t immediately delete everything necessary to run the wizard and complete the configuration. After deleting it in Central Admin, and removing the IIS site manually(also removing the folder C:\inetpub\wwwroot\wss\virtualdirectories\80) I got the following error when running the wizard:

Failed to create sample data.
An exception of type System.ArgumentException was thrown. Additional exception information: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname.



In the warning dialog when deleting the site collection there is a note specifying “To perform an immediate deletion, you need to run a set of commands using, for example, Power Shell or the Object Model. Find more information, see the SharePoint Help system” which didn’t provide much help as to actual commands to delete the web application.

Fortunately, Adam Preston posted List All SharePoint 2010 PowerShell Commands that provided the necessary information to complete the deletion. Namely, run get-spwebapplication to list the web applications configured in SharePoint Foundation. Then run Remove-SPWebApplication -identity:http://webappname/ -removeContentDatabases -deleteiissite -verbose -confirm. This command will immediately delete the Web Application, delete the content database, and the IIS site. After this I was successfully able to complete the Configuration Wizard. Up popped the Search Administration page in Central Administration. Of to configuring it!

Maybe this post should be titled ‘Trials of installing MSS2010 Express on SharePoint Foundation’?


4 Responses to Installing MSS2010 Express on SharePoint Foundation

  1. Epco says:

    Thanks very much for this post.

    It was very helpful.

    After deleting the site collection I was able to restore it again and everything runs smoothly again.

    Again thank you very much.

  2. Andy says:

    Thanks for your post, it helped me!

    I ran into the same trouble, trying to install Search Server Express on Foundation that already had sites. I found that if I deleted the web application in central admin, and allowed it delete the IIS site automatically BUT NOT delete the content database, I did not have to use the PS commands. I was able to directly run the Wizard successfully. I then just removed the new blank content database the wizard created and attached my existing content database.

  3. Leon says:

    I had my default web application as http://sharepoint.domain.local and was encountering the above errors. I then renamed my default web application to http://servername as this is the only way it would let the configuration wizard complete (used to fail on creating sample data). I then changed my default web application back to it’s original address.

  4. BRG says:

    Thanks, very helpful indeed 🙂

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: