You would
find tons of blogs discussing the below first error* while installing
SharePoint 2013 pre-requisites. I also encountered the second error about .Net framework 3.5.
- Application Server Role, Web Server (IIS) Role: configuration error*
- .Net Framework 3.5 not enabled.
The first error was displayed in
both pre-requisites tool window (also known as SharePoint Server 2013
Preparation Tool) and the log file which is generated by the tool. While
the second error was found only in the log file. So make sure you read the complete log file generated by SharePoint Server 2013 Preparation tool. You should not
miss any error that might keep you troubling all the way ahead.
To resolve the first error Application
Server Role, Web Server (IIS) Role: configuration error I
executed two steps:
1.1 Add Web
Server Role and Application Server Role to your Windows Server via Server
Manager.
- Go to Server Manager > Add Roles and Features.
- Select your server in the Server Pool under Server Selection page.
- Select Web Server (IIS) Role and Application Server Role.
- Click Next until the wizard finishes.
- Run MMC
- Click File > Add/Remove Snap-in
- Select Group Policy Object Editor and Add it.
- Navigate to Administrative Templates > System
- Double click Specify Settings for optional component installation and component repair.
- Check the Enabled radio button and select “Contract Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box”.
To resolve
the second error .Net Framework 3.5 not enabled you
must add .Net Framework 3.5 feature via Server Manager > Add roles features.
- In Server Manager, click Manage and then select Add Roles and Features to start the Add Roles and Features Wizard.
- On the Select installation type screen, select Role-based or feature-based installation.
- Select the target server.
- On the Select features screen, check the box next to .Net Framework 3.5 Features.
- On the Confirm installation selections screen, a warning will be displayed asking Do you need to specify an alternate source path? If the target computer does not have access to Windows Update, click the Specify an alternate source path link to specify the path to the\sources\sxs folder on the installation media and then click OK. After you have specified the alternate source, or if the target computer has access to Windows Update, click the X next to the warning, and then click Install.
- If you are using Server Manager in Windows Server 2012 to add a role or feature to a remote server, the remote server’s computer account (DOMAIN\ComputerName$) requires access to the alternate source file path because the deployment operation runs in the SYSTEM context on the target server.
These were the
two resolutions I implemented, restarted the server and re-ran the
pre-requisites tool and got everything working fine. Hope this helps you.
