This project has moved and is read-only. For the latest updates, please go here.

Win 2012 Server - Prerequisite installer - Known Issue occurred configuring .NET 4 / IIS.

Jun 17, 2013 at 2:52 PM
I apologize - I also posted this in the issues section.

I've been experiencing this issue noted in other threads with solution of running aspnet_regiis - but that doesn't seem to work on 2012 server.

Running AutoSPInstaller I repeatedly get this error :
  - Prerequisite Installer completed in 00:02:57.
  - SharePoint 2013 "missing hotfix" prerequisites...
   - Checking for KB2765317...Already installed.
WARNING: 2013-06-14 12:55:16 - Error when enabling ASP.NET v4.0.30319
WARNING: 2013-06-14 12:55:16 - Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
WARNING: 2013-06-14 12:55:16 - Last return code (1)
 - A known issue occurred configuring .NET 4 / IIS.
 - Setting AutoSPInstaller information in the registry...
 - Script halted!
The I read other people's solution here and tried the aspnet_regiis solution and get this error:
D:\SP\AutoSPInstaller>"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe" -i -enable
Microsoft (R) ASP.NET RegIIS version 4.0.30319.17929
Administration utility to install and uninstall ASP.NET on the local machine.
Copyright (C) Microsoft Corporation.  All rights reserved.
Start installing ASP.NET (4.0.30319.17929).
This option is not supported on this version of the operating system.  Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Windows Features On/Off" dialog,  the Server Manager management tool, or the dism.exe command line tool.  For more details please see
Finished installing ASP.NET (4.0.30319.17929).
Reading these two links:
It seems that .Net 4/4.5 can only be installed as a role/feature - Has anyone else had this issue? How have you gotten around it?
Jun 17, 2013 at 3:03 PM
Are you running AutoSPInstaller on a fresh installation of Win Server 2012 that's been fully patched via Windows Update?

Jun 17, 2013 at 3:32 PM
Also, are you able to run PreRequisiteInstaller.exe on its own with no errors? If not, then the issue is unrelated to AutoSPInstaller.

Jun 18, 2013 at 5:33 PM
So I think it turns out this was the (seemingly) dreaded .Net 3.51 feature installation issue. Is there a good article anywhere on who to resolve this in an automated unattended manner? What I did was leverage Local GroupPolicy to set the Alternate File Installation and Update path to a network source for the _\sources_ folder and I think I am now moving forward.

But to me the real question is why is the displayed error message so cryptic and unrevealing of the underlying problem?
Jun 18, 2013 at 10:38 PM
Edited Jun 18, 2013 at 10:39 PM

We just built a number of SP2013 farms on Server 2012, the only change we had to do was this: other than running Windows Update as were using SCCM.