While installing SharePoint 2013 onto Server 2012, I
came across an error as “The tool was unable to install Application
Server role. Web Server (IIS) role”. After browsing internet for resolution, I finally could resolve my issue. But while doing my investigation into
the error, I came across posts where different people have tried different
things to resolve the same error. I will try to collate those and post it in
one single post.
Option
1 :
Go to Server Manager and click on Add Roles and
Features
Select and expand Web Server (IIS) Role
Select the IIS 6 Scripting tools under Management Tools
within Web Server role
Click Next
until the wizard finishes
Rerun the Pre-requisite setup and see if you have been
able to resolve the error.
Option
2: (only for Windows 2008 R2)
Go to command prompt and run this command:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe
-i –enable
Option
3:
Run powershell with admin priviledges
Run the following commands: (I mounted my Server 2012
ISO on D drive)
Import-Module ServerManager
Add-WindowsFeature
NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45
Add-WindowsFeature
Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support,
AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer
-Source D:\Sources\sxs
1 comment:
Thanks so much for this - we've been battling with this issue for a couple of days on a customer server and have tried just about everything. Option 2 finally solved the problem for us - thanks again!
Post a Comment