What to do when SharePoint prerequisite installer failed to install .Net Framework 3.5

 

We all know that there are a number of prerequisites that needs to be installed before downloading SharePoint onto our systems. Without these prerequisites, it is not possible to run the SharePoint environment successfully. Which is why, it is vital that we install the required prerequisites properly, to avoid roadblocks.

That being said, we often encounter many problems while installing these prerequisites.  In this article, I’m going to explain one such issue and give a detailed, step by step procedure of how to install it without any hassle.

Sometimes, the Products Preparation Tool might be unable to correctly configure and install the required Windows Features for SharePoint. If this happens, the tool will continuously try to configure and install the required features by default and, it restarts.

This support article has provided some work around to solve the issue. This includes:

Method 1

  • Installing Microsoft Knowledge Base (KB) article 2771431

Method 2

  • Manually install the Windows Server 2012 Roles and Features that are required by SharePoint 2013. 
  • Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
  • Import-Module ServerManager

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer

When trying, run the above command to run on windows server 2016.  We get the following error:

“The name was not found

 

 

So, here’s the work around which worked for me!

Method 3

Make sure to replace the D:\sources\sxs with the actual path of your source file. Ensure that you specify the source file of your Windows Server 2016 installation media and, have it mounted on your computer (or copied somewhere) for the prerequisite install to work properly. Everything should work properly afterwards, to run the prerequisite installer

The correct cmdlet you need to run for a Windows Server 2016 installation:

Import-Module ServerManager

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer –Source D:\sources\sxs

Related posts