Can’t install .net 3.5 on server 2012

When trying to install .net 3.5 using Roles and Features it fails with, ‘Installation of one or more role services or features failed.  The source files could not be found etc…  I have tried dism.exe /online /enable-feature /featurename:NetFX3 /Source:D:\sources\sxs /LimitAccess, this fails with Error 0x800f081f – The source files cannot be found etc. I’ve read that I should uninstall KB2966828, KB2966827 and KB2966826, but I don’t have them installed.
grsgAsked:
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.

Seth SimmonsSr. Systems AdministratorCommented:
And at last this is the solution...

the author already stated those updates are not installed
0
grsgAuthor Commented:
Hi Thommy, I've been through EE results trying the solutions, but still have the errors.  To add more info - the server can connect to MS update, I've copied the sxs folder to C:\ and have opened up permissions and have two copies of installation disks, but I always return to the same errors
0
JohnBusiness Consultant (Owner)Commented:
Try running .NET FX Verifier and see (a) if it can tell you what is installed (check all versions) and (b) if it can repair .NET.

http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog%7C_Tools/netfx%7C_setupverifier%7C_new.zip 

The .zip file that contains the tool also contains a file named history.txt that lists when the most recent version of the tool was published and what changes have been made to the tool over time.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Cliff GaliherCommented:
Even if the server can access Microsoft update, you are including the /limitaccessnflag so the server won't use it. I'd start by dropping that flag and the source flag. Let windows grab the appropriate binaries from the web. The error is *often* caused by a version mismatch between the media being used and the parched OS. While the common culprit patches have been listed, that list is by no means exhaustive. I've found others that break the ability to use RTM media as well.
0
grsgAuthor Commented:
Hi Cliff, just tried your suggestions but still get fail with error 0x800f0906 exactly as before
0
grsgAuthor Commented:
Hi John, verifier finds .net fw 4 client, 4 full, 4.5 and 4.5.1 but I need 3.5 for Sage to run
0
Seth SimmonsSr. Systems AdministratorCommented:
have you tried the all option?

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess
0
Cliff GaliherCommented:
That's usually a good sign that windows is unable to contact WU. Do you have another 2012 server with 3.5 already installed?
0
JohnBusiness Consultant (Owner)Commented:
In addition to the above, you might find .NET 3.5 in Programs and Features, Windows Features. If there, you may need to check it (enable it), close out, and possibly restart the server.
0
grsgAuthor Commented:
Seth, yes did try the All option, but no good.  Cliff, I can connect to WU from Control Panel and can see new updates waiting for MS Office and I can browse the web freely.  No, I don't have another 2012 server, I do have 2008, is that asking a bit much to think that it may be compatible?
0
Cliff GaliherCommented:
Definitely not compatible.

Well, the painful way then. I've never had this method fail.

Stand up a VM or grab an old workstation.

Install a new server from media. Since you are trying to add 3.5 to 2012, use 2012 media, NOT 2012 R2 (yes, it matters.) also match edition (standard, datacenter) and core or GUI.

Do *not* patch this new install.

Add .Net 3.5 using the media as the source. This will work as the install and media definitely match.

Meanwhile, on the existing live machine, use the windows update control panel to view installed updates. Make a list.

Once 3.5 is installed on the new machine, install each update from tour list and *only* those updates.

Restart the new server

Now you can add 3.5 to the existing server, specifying the WinSxS folder of the new server as the source. Any patches that touch the folder, causing the media mismatch, have been installed, so this makes version matching succeed.

----

Yes, it reads a bit convoluted, but in practice is easy. You can make the update list while the fresh OS is installing. The whole thing. from first click to final success, takes about an hour. Which is less time than it takes trying to uninstall various updates to find the culprit. As I said, I have a 100% success rate with this method when the rules are followed.
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
grsgAuthor Commented:
Hi Cliff, life is never easy...  I don't have another 64bit  machine to build the second server on to.  I may be able to ask some friends if I can copy from their servers the relevant files.  If I copied the WinSxS folder from another server 2012 R2 installation and used that as the source on my server, would that work?
0
Cliff GaliherCommented:
Only if it is built to a patch level similar to your live server. And copying winSxS itself is not supported and doesn't always work as expected. I'd not consider that path trustworthy.
0
grsgAuthor Commented:
I solved this in the end by removing all the updates that had been installed since we installed the server, a slow process, but easy as they were all installed over two days last week. After a reboot I was able to install 3.5.  I'm awarding Cliff the points as I could see his solution would work, but as I didn't have a spare machine to build the new server on I couldn't use his solution, but he put enough information in his explanation for me to realise my problems were being caused by the updates.  Thanks to all that contributed.
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
Windows Server 2012

From novice to tech pro — start learning today.