Windows Server 2012 R2 cannot install .NET Framework 3.5 solution

Windows server 2012R2 comes with .NET Framework 4.5. If you want to install SQL server2008 or SQL server2012, you need to install the .ENT Framework 3.5 or 2.0 version. It is recommended to install the .NET3.5 version. I personally tested it and it succeeded!

Analysis of unsuccessful installation error:

If you install SQL server2008 or 2012 directly, it will report: Cannot install the function .NET Framework 3.5.

If you find a .NET Framework 3.5 to install, the system will report that the installation of one or more role services or functions fails, and the original file cannot be found.

Follow the prompts from the Control Panel-Programs-Start or Shut Down Windows Features

This is different from Win7, Win10, XP operation, but the principle is the same;

 

 

 

We see that the system has installed .NET Framework 4.5 by default, so we have a vague premonition, but we still have to bite the bullet and check 3.5

It shows that you need to specify an alternate path, but I did not specify

This is a failed installation;

Solution:

 

A lot of references from the Internet: https://blog.csdn.net/sunny_lv/article/details/73603360

There are many methods mentioned in this article, you can try.

I found the C:\sources\sxs package under the installation disk path from the Internet and put it into the specified location. Entering the alternate source path didn’t work. I had to download the entire image file obediently.

(WindowsServer2012R2 image file Thunder link: ed2k://|file|cn_windows_server_2012_r2_vl_with_update_x64_dvd_4051059.iso|4683122688|BD0B95997679F83A4EE2D062865D8E64|/)

There is sxs in the downloaded image file

So insight (opportunistic), let's try this simple package, and then copy the sxs file separately to the C:/ of the server.

Fill in the alternate source path as C:/sxs

 

In fact, recall that the alternate source path only needs to point to the sxs file under the correct installation disk. The previously downloaded installation package may not be cut out from the corresponding Windows servers 2012R2 version, so students who use the method in this article must pay attention to selecting the corresponding version of the package (the simple package I used is linked in the text), and then specify the alternate source path can.


Original: https://blog.csdn.net/F12138_/article/details/80220698 
 

Guess you like

Origin blog.csdn.net/h610443955/article/details/84818059