Error Installing .NET 3.5 for SQL Server


By:   |   Updated: 2020-11-02   |   Comments (1)   |   Related: More > Install and Uninstall


Problem

Sometimes we need to install an older version of the SQL Server on a server with a newer version of the Windows operating system. While SQL Server 2014 and older versions of SQL Server require .NET Framework 3.5 installed, the newer Windows operating systems do not have it installed by default. It could seem like quite a simple task.  We just needed to install .NET 3.5 and then install SQL Server. However, adding the .NET 3.5 feature on newer versions of Windows may not be as easy as expected. Particularly, when we are trying to add the .NET Framework 3.5 feature on Windows Server 2019, we receive the following error:

"The request to add or remove features on the specified server failed. Installation of one or more roles, role services or features failed. The parameter is incorrect. Error: 0x80070057"

The request to add or remove features on the specified server failed.  Installation of one or more roles, role services or features failed.  The parameter is incorrect.  Error:0x80070057

Well, it is worth mentioning beforehand that it is not possible to download and install .NET manually on this Windows Server. Additionally, quite often people do not have a Windows installation media with them in order to use it for adding this feature. Thus, it will be necessary to somehow fix the issue and add the feature from the Windows "Add Roles and Features" wizard. I believe that many database specialists have encountered this problem. If you are one of these people who faced this issue and have not found the solution yet, this article will be beneficial for you. Here, we will discuss exactly this specific case and provide a solution.

Solution

First, we are going to reproduce the problem in a detailed way and after that, provide the solution. In our test environment, we are installing SQL Server 2014 Database Engine on Windows Server 2019 (the same problem occurs while installing on Windows Server 2016 as well). So, let's begin.

We will skip all steps of the SQL Server installation, as it is out of this topic. We will just stop at the step where our problem starts. Hence, when we reach the step where the feature rules are validating, we can see that the rule fails for "Microsoft .NET Framework 3.5":

Rule Microsoft .Net Framework 3.5 Service Pack 1 is required failed.

The error message is self-explanatory (i.e. Rule "Microsoft .Net Framework 3.5 Service Pack 1 is required" failed.) and it is very easy to understand the reason. As our operating system is Windows Server 2019, we open server features on "Server Manager" where we can see that although the .NET Framework 4.7 is installed, the .NET Framework 3.5 is missing:

Server Manager with .NET Framework 4.7 and .NET Framework 3.5 is missing

We check ".NET Framework 3.5 Features" and click next trying to add this feature:

.NET Framework 3.5 Features

The warning message appears informing us that it is possible that for some features source files can be missing and cannot be obtained automatically. According to the message, for such cases, an alternative path for the source files should be provided:

.NET Framework 3.5 Features.  Do you need to specify an alternate source path?

When we click on "Specify an alternative source path", we can see that it is clearly mentioned that the source files for ".NET Framework 3.5" are not installed, but available in the side-by-side store:

Source file for .NET Framework 3.5 Features are not installed as part of a typical installation

As it is mentioned before, it is assumed that we do not have access to the Windows Features side-by-side store and Windows installation media. So, we cannot specify this option. If we leave it blank, click "OK" and then "Install", we will receive an error message (i.e. The request to add or remove features on the specified server failed. Installation of one or more roles, role services or features failed. The parameter is incorrect. Error: 0x80070057) as you might have already expected:

.NET Framework 3.5 Features.  The request to add or remove features on the specified server failed.  Installation of one or more roles, role services or features failed.  The parameter is incorrect.  Error: 0x80070057

It is also not possible to use the .NET Framework 3.5 installation file to install it on our server because this feature can be added to the Windows server only as a Windows feature. Thus, just to reformulate our problem - we need to add the .NET Framework 3.5 through the Windows features, but we cannot as the source files are missing from Windows and we do not possess these files.

Hmm… what if we have Windows download these files from the Internet? Yes, it is possible, and in order to do that, we need to edit the local computer policy. To do so, we open the command prompt and type "gpedit". The "Local Computer Policy Editor" opens where we can locate the necessary setting under the "Computer Configuration" > "Administrative Templates" > "System". On the left side, under "Settings", we can find a setting named "Specify settings for optional component installation and component repair":

Specify settings for optional component installation and component repair

This is what we are going to modify. Let's open it and check "Enabled" and then check the second option – "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)" and click "OK":

Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)

Now, if we retry adding the .NET Framework 3.5, we can see that it succeeds as the registry settings are changed and the feature is downloaded from the Internet:

retry the adding of .NET Framework 3.5, we can see that it succeeds as the registry settings are changed and the feature is downloaded

After that, if we re-run the SQL Server feature rules validation, we can see that all rules are passed, and we can successfully install SQL Server:

re-run the SQL Server feature rules validation, we can see that all rules are passed

Conclusion

All in all, installing SQL Server 2014 or older versions of SQL Server on newer Windows servers can be a bit non-standard routine. The difficulty here can be the process of adding .NET Framework 3.5 on newer Windows servers especially if you do not have a Windows installation media. Nevertheless, the problem can be fixed by editing the Windows local group policy settings.

Next Steps

For additional information, please review the links below:






get scripts

next tip button



About the author
MSSQLTips author Sergey Gigoyan Sergey Gigoyan is a database professional with more than 10 years of experience, with a focus on database design, development, performance tuning, optimization, high availability, BI and DW design.

View all my tips


Article Last Updated: 2020-11-02

Comments For This Article




Friday, April 23, 2021 - 4:16:07 PM - praveen Back To Top (88599)
Hi , Thank you so so much for this article. there were many options to install it from ISO file which is very cumbersome. I managed to install it using your solution.

Saved my day.


download














get free sql tips
agree to terms