SharePoint fails to create Configuration Database for a new farm

Problem Description

A new installation of SharePoint fails to provision a new farm due to a failure while creating the configuration database.


Here is the exception stack from the PSCDiagnostics log:


This issue can occur if you chose to download and install all the prerequisite software manually, namely in this case the “WCF Data Services 5.6 Tools“. If you are experiencing the error, “One or more types failed to load” , while creating a new SharePoint Farm, it’s most likely caused by the installer executable being in a “blocked” state while it was installed.


When executables are downloaded from the internet, they are put into a “blocked” state by to OS, to prevent users from running malicious code. However, in this case, if the installer was in a blocked state when the “WCF Data Services 5.6 Tools” were installed, the install will “succeed’ but will not be installed properly.


To resolve this issue:

1. Go to the properties of each prerequisite installer package that was downloaded manually and remove the block flag by selected “Unblock” and applying the changes.


Before:                                    After:


2. After the file has been unblocked, re-run the installer and choose the repair option.


3. Finally, re-run the SharePoint Configuration Wizard to successfully create a new Farm.



I wanted to update this blog with a recent discovery that will cause the same issue without the installer appearing to be”blocked”.

For example:

The following image does not show the installer package being in a “blocked” state.

How does this occur?

This condition can occur of your system is configured with the “Do not preserve zone information in file attachments” policy enabled.



What should  be done?

If you find yourself in this situation, there is a good possibility that additional pre-req software was not installed properly and will cause unexpected outcomes while working with SharePoint.

With that said, please consider the following actions.

  1. Disable the “Do not preserve zone information in file attachments” policy and reboot.
  2. Re-run each pre-req package manually and choose the repair option, if applicable.
  3. If the repair options is not offered, uninstall and re-install pre-req installer package.


If you experienced this issue,  please let me know in the comments.

Leave a Reply