.net 3.5 fails on server 2012

I'm struggling to install .net 3.5 via sever manager add roles/features

running Dism /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess gives error 0x800f081f which I believe implies it cannot see the source and yet if I enter d:\sources\sxs into File Explore it takes me into the folder so that would indicate the path is fine
andrew_2706Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

it_saigeDeveloperCommented:
Where are you running dism.exe from - i.e. C:\Windows\Syswow64 or some other location?

Are you using an Administrator command prompt?

Have you tried explicitly calling dism.exe from the System32 directory?  

%systemroot%\System32\Dism.exe /online /enable-feature /featurename:NetFx3 /All /Source:d:\sources\sxs /LimitAccess

If that does not work, try repairing the component source:

%systemroot%\System32\Dism.exe  /online /cleanup-image /scanhealth
%systemroot%\System32\Dism.exe /online /cleanup-image /restorehealth

-saige-
0
David Johnson, CD, MVPOwnerCommented:
you could use powershell
Add-WindowsFeature -Name NET-Framework-Core
0
Cliff GaliherCommented:
Welcome to a very special level of hell. The new "features on demand" functionality is very patch-level sensitive. Some patches cause the system to see source media as an older version 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
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

andrew_2706Author Commented:
The Powershell option failed

Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator> Add-WindowsFeature -Name NET-Framework-Core
Add-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more
information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. Error: 0x800f0906
At line:1 char:1
+ Add-WindowsFeature -Name NET-Framework-Core
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
    Exception
    + FullyQualifiedErrorId : DISMAPI_Error__Cbs_Download_Failure,Microsoft.Windows.ServerManager.Commands.AddWindowsF
   eatureCommand

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
False   No             Failed         {}
0
andrew_2706Author Commented:
-saige-

sadly none of your worked either :-(
0
it_saigeDeveloperCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GoodADCommented:
Uninstall this patch: http://support2.microsoft.com/kb/2966828

Run the DISM command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess

Install .Net 3.5 updates from Windows Update.

it worked for me.
0
andrew_2706Author Commented:
Many thanks for seeing the solution and coming back to me.

From http://www.askvg.com/fix-0x800f0906-and-0x800f081f-error-messages-while-installing-net-framework-3-5-in-windows-8/ the only update I had installed was KB2966827 and on removing it worked as it should of.

Cheers
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.