Comments

Failed to create the configuration database. An exception of type System.Collections.Generic.KeyNotFoundException was thrown.

Installing Search Server 2010 should be as challenging as to install SharePoint itself. Although well prepared I wasn’t able to create the configuration database using the SharePoint Products Configuration wizard.

Trying several times ended in: Failed to create the configuration database.

An exception of type System.Collections.Generic.KeyNotFoundException was thrown.

Background

Search Server 2010 is an enterprise search platform by Microsoft. Companies and their requirements are different and Microsoft presents different solutions like Search Server (Express), SharePoint Server or FAST. See a list of capabilities compared of different search products.

You can e.g. index content stored in SharePoint, in databases or on file shares where Search Server exceeds the capabilities of SharePoint Foundation.

Error description

This is the exact error I got:

Failed to create the configuration database. 
An exception of type System.Collections.Generic.KeyNotFoundException was thrown.  Additional exception information: The given key was not present in the dictionary.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

The configuration of Search Server 2010 failed

Solution

Luckily your favorite search engine is your friend...

I was able to find the solution in this thread Sharepoint 2010 - Error while running Configuration wizard for SP 2010 server farm.

You have to read until the end where it is suggested to go to Active Directory and to edit the properties of the following accounts:

  • Setup administrator (account used to install SharePoint)
  • Farm account (account used in the SharePoint Products Configuration wizard)
  • Look at administrative and service accounts for a description of accounts you need to install SharePoint

In the security tab you need to give the authenticated users group read permission:

You need to edit the properties of the Authenticated Users group in Active Directory

After that the install has worked as expected.

Note: Please be aware that there might be other reasons for the same problem.