[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1228
  • Last Modified:

Error When Attempting to Install .NET 3.5 on Server 2012 R2

I have Windows Server Datacenter 2012 R2 (volume license version) installed on a VM server that a contractor is attempting to install the .NET 3.5 feature on, but it keeps producing the following error.

"Installation of one or more roles, role services, or features failed.
The source files could not be found. Try installing the roles, role services, or features again in a new Add Roles and Features Wizard session, and on the Confirmation page of the wizard, click "Specify an alternate source path" to specify a valid location of the source files that are required for the installation. The location must be accessible by the computer account of the destination server."

When using the following command I get the same thing plus error code 0x800f081f.

"DISM /Online /Enable-Feature /Featurename:NetFX3 /Source:G:\sources\sxs /LimitAccess"

I get these error messages if I point the installer to the source files mounted on the DVD drive as well as if I do not. The path you see in the DISM command is the correct path for the SXS folder on the Server Datacenter 2012 R2 Installer disk ISO.
0
Mdamon808
Asked:
Mdamon808
  • 2
3 Solutions
 
Cliff GaliherCommented:
Welcome to a very special level of hell. The new "features on demand" functionality is very patch-level sensitive. You install KB2919355 (the server equivalent of 8.1 update 1 that came out in May) and that DVD no longer works. Aggravating to no end.

You have three choices. First, don't specify a source and let the server use Microsoft Update. For this to work the server has to see Microsoft Update and not have policies to use WSUS. I have done this in the past..mdisable WSUS GPOs, etc. Oh, and hope that MU has the latest bits too. There have been weeks where there was ...lag.

Option 2. Grab the WIM from the DVD. Make a list of every installed patch on the existing server. And slipstream the patches into the WIM on a build machine and specify it as the source. This is good for machines that cant access MU or where disabling WSUS/SCCM breaks corporate ITIL standards. I currently use this approach. I have an MDT task sequence that builds a new WIM that I run regularly so I can grab it and use it as a source on any machine (via USB if necessary) and stay change management compliant.

The third option is to point to another server's windows directory as a source. If the other server I'd at the same patch level and has .Net 3.5, it'll simply grab those bits over the wire..this is faster than MU and easier than building a new WIM ...if you already have a server that meets the requirements. Which can be a big if.

Yeah, it is a pain. Hopefully the on-demand stuff improves in future iterations. Great idea, fairly broken current implementation.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
you can always use powershell

Install-WindowsFeature Net-Framework-Core -source D:\Sources\SxS

(change D to your drive with the mounted iso)

powershell
0
 
Mdamon808Author Commented:
I was told to drop the issue and use Server 2008R2 instead.

Thanks for your suggestions and sorry for the abandoned ticket.  :P
0
 
Mdamon808Author Commented:
Just need to close the ticket. All information above is good.
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now