Skip to main content

SharePoint 2013 - Setup is unable to proceed due to the following error(s): This product requires Microsoft .Net Framework 4.5

Synopsis

I recently ran into this issue while deploying SharePoint Server 2013.  Everything seemed to go according to plan, before SharePoint Gods decided to throw yet another lightning bolt my way.

Shortly after getting the software prerequisites successfully installed (accompanied by a couple of reboots of course), it was time to install the SharePoint Server software bits.  About a minute after executing the bootstrap (setup.exe) this error message comes up:

"Setup is unable to proceed due to the following error(s): This product requires Microsoft .Net Framework 4.5"

Here is an exact screenshot:


Unless I was loosing my mind, I was pretty confident the software prerequisites installation completed successfully, which performs all the necessary checks and balances on the system, including the installation of .Net Framework 4.5.

The Problem

After running around and attempting to re-install .Net Framework 4.5, which by the way didn't resolve the issue, I proceeded to check the current version of .Net Framework inside the registry.  This can easily be done via Windows PowerShell by executing the following cmdlet at the prompt:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client'

This quickly revealed that the current version of .Net Framework was 4.6.x and not 4.5.x.  This presents a bit of a challenge since SharePoint Server 2013 software is strictly checking against 4.5 and not higher.

Further research uncovered an actual KB article released by Microsoft regarding this exact issue.  You can read about it here: https://support.microsoft.com/en-us/kb/3087184

It appears that a recently released patch upgraded the .Net Framework from 4.5.x to version 4.6.x, leaving no trace for the bootstrap program to verify any existence of the previous version.  What now!  Keep reading.

The Solution

The trick is finding the specific KB update which applied the version upgrade and uninstalling it.  In my case this was KB3102467.

Following steps should get you to the promise land:
  1. Uninstall KB3102467
  2. Reboot the machine
  3. Run Setup.exe to install SharePoint Server 2013 software - success!
  4. Run Windows Update to re-install KB3102467
Perform the steps above on each of the server instances.

Comments

Post a Comment

Popular posts from this blog

SharePoint Server Search - Error Starting

Problem I recently ran into this snag at a client site while setting up the Search Service Application.  I was able to create the service application without a problem however when I attempted to start the SharePoint Server Search service (Manage services on server page) I kept getting Error Starting . After taking a peak at the logs I found the following: An attempt to start/stop instance of service SharePoint Server Search on server did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) I double/triple checked the permissions and made sure that my Farm Administrator account was a member of WSS_WPG and WSS_ADMIN_WPG groups, and that those groups had full control permissions to the C:\Windows\Tasks and C:\Windows\Temp folders. Resolution I nearly lost hope when I remembered my old lost friend called STSADM.EXE. Just like in the old da...
Post a Comment
Read more

SharePoint 2013 - Creating and Applying Composed Looks (PowerShell)

If you are a SharePoint administrator looking to quickly apply some basic branding to a site-collection in your SharePoint 2013 environment then you've come to the right spot. Before we begin I assume you have a basic understanding of what Composed Looks are, and perhaps you spent some time playing around with this concept in SharePoint 2013. If not, then don't worry.  Here is a basic primer: Composed Look is basically a package which contains elements used for controlling the overall look and feel of a SharePoint site.  This includes but not limited to Colors, Fonts, Background Image, CSS files, and Master Page files. Once created, Composed Look can be packaged by using the Design Manager feature, or we can use PowerShell to apply it across one or multiple site collections. NOTE: In this post we will be focusing on creating a composed look from an .spcolor file then using PowerShell to apply the design to a site-site collection of our choice.  We wil...
2 comments
Read more

SharePoint 2013 - Can't access the site externally in Internet Explorer ("Page cannot be displayed")

Synopsis Before we start talking about the problem let's understand the setup here.  We have a SharePoint 2013 intranet site that is also configured for access outside of the corporate network.  Employees use the same URL to visit the site both internally and externally via standard ports (80 and 443). Internal URL: http://sharepoint.domain.com Public URL: https://sharepoint.domain.com The site URL has been added to the Local Intranet zone in Internet Explorer for passing domain credentials. Alternate Access Mappings have been configured in such a way that if a user requests the site over HTTP they are automatically re-directed to HTTPS. Internal URL Zone Public URL for Zone https://sharepoint.domain.com Default https://sharepoint.domain.com http://sharepoint.domain.com Default https://sharepoint.domain.com Web application has been configured to use Kerberos protocol for authenticating incom...
7 comments
Read more