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:

Uninstall KB3102467
Reboot the machine
Run Setup.exe to install SharePoint Server 2013 software - success!
Run Windows Update to re-install KB3102467

Perform the steps above on each of the server instances.

Comments

SharePoint 2013 - Simple Glossary using "HTML Form Web Part"

Introduction At some point you probably thought about incorporating glossary functionality as a part of a larger solution, or perhaps you were simply looking for providing a more intuitive way of filtering hundreds of items within a List or Library. Now there are countless web parts out there that you can either purchase or download from the SharePoint Store free of charge, and they all come with their own set of bells and whistles. However, if you are looking at building one yourself, well look no further. To accomplish this we will need three major ingredients: SharePoint Page (either Wiki or Publishing will work) SharePoint List/Library with some content (Files/Items) HTML Form Web Part Let's Implement In this post I’m using a simple Wiki page, but you can also use a Publishing page as well. We just need a canvas to display our glossary. I presume you already have a list or library that contains some content which is applicable to this concept. I’m

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 incoming c

Remove Orphaned Web Parts - MissingWebPart

At some point you may have encountered an error like this while browsing through the SharePoint Health Analyzer or if you are attempting to test your content database (i.e., Test-SPContentDatabase) prior to mounting it. Message reads something like this: One caveat is that the log message never reveals the Location of the culprit web part. Luckily we can utilize T-SQL to query the content database and reveal the location of the web part in question. Query the Content Database To do this fire up the SQL Server Management Studio either locally from your machine or while logged on to the SQL Server back-end of your SharePoint farm, open up the new Query window and enter the following statement: USE < Content_Database_Name > SELECT AllDocs.SiteId,WebId, Webs.Title as 'Web Title', ListId, DirName,LeafName FROM AllDocs inner join AllWebParts on Alldocs.Id = AllWebParts.tp_PageUrlID inner join Webs on Alldocs.WebId = webs.Id WHERE AllWebParts.tp

SharePoint Musings

Search This Blog