Recently I was setting up a virtual machine environment to do some demo's. One of the virtual machines would be the home for a SQL Server database engine supporting a SharePoint 2013 farm. Since it is a back-end database, the server was not connected to the Internet. Instead, it was connected to the other servers through the Hyper-V internal network.
During the installation of SQL Server on this machine, I got the following error:
Error while enabling Windows Feature: Netfx3
A quick search on the Web taught me this is the activation of .NET 3.5. I knew this was a prerequisite for SQL Server. In the past you had to enable this before you started the SQL Server set-up, but nowadays the set-up does this for you. Aren’t we spoiled? Also keep in mind enabling .NET 4.5 isn’t enough: the 3.5 version has to be explicitly enabled.
Why did it crash now and not in all my previous installations of SQL Server? It seemed the SQL Server set-up could locate the sources to install .NET 3.5. Normally it would try to download them, but since the machine was not connected to the Internet this failed as well, resulting in the error.
Luckily it is very easy to enable .NET 3.5 using the GUI. In your Server Manager, click on Add roles and features.
Choose for Role-based or feature-based installation.
Choose the correct server, skip the Server Roles and click Next until you’re on the Features page. Select .NET Framework 3.5 Features and click Next.
On the installation page you’ll be confronted with a warning that the source files are missing. Fortunately you can specify an alternate source path at the bottom.
Click on the link and specify the path to the sourcessxs folder on your Windows Server 2012 media. In my case this was on the D: drive, which is the DVD drive.
Hit OK and on the Installation page, click Install. The .NET framework 3.5 will now be installed.
After the set-up, you can now re-launch the SQL Server set-up!
For the command line geeks amongst us, read the following blog post on how to enable .NET 3.5 using dism.
