The tool was unable to install Application Server Role, Web Server (IIS) Role
when I install prerequisiteinstaller.exe in sharepoint 2013, got the below error:
Error when enabling ASP.NET v4.0.30319
Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
Last return code (-2146646015)
anyone can help this? thanks in advance.
October 31st, 2012 10:02am
Does the account you're logged in as belong to the "Local Administrators" group Awen?
Have you tried adding the IIS Role via "Server Manager" > "Roles"
October 31st, 2012 11:39am
yes, it is. added IIS role
October 31st, 2012 12:44pm
fixxed. just run te command:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regii -enable -i
November 2nd, 2012 5:03am
I am facing the same issue..I have tried following things,
1.Added IIS Roles
2. Run aspnet_regii -enable -i
2. Install
Windows Features for SharePoint manually using Powershell( as suggested in http://support.microsoft.com/kb/2765260)
But still it's giving the same error.
Any clues?
Rajesh
December 28th, 2012 9:50am
Create two roles one for "Application server" and "Web server (IIS)" in Server manager.
Below are the links for creation in case of windows server 2012-
http://support.simpledns.com/KB/a200/adding-application-server-server-role-net-framework.aspx
http://www.iis.net/learn/get-started/whats-new-in-iis-8/installing-iis-8-on-windows-server-2012
I faced the same issue and followed the above links for creation and later tool ran successfully.
February 26th, 2013 12:09pm
Thanks a lot, this command working.
i hope my issue has been resolved.
-
Proposed as answer by
Ben Howard [MVP]MVP
Wednesday, June 11, 2014 3:20 PM
March 13th, 2013 8:44am
Thanks a lot, this command working.
i hope my issue has been resolved.
March 13th, 2013 11:44am
Hi,
This issue has been addressed by following knowledge based article
http://support.microsoft.com/kb/2765260
There are three or four sections to this document, for me following section did the trick.
"
-
Offline method: Server is not connected to the Internet
To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used
in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.
For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the
-source parameter is as follows:
D:\sources\sxs
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
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 <var>-Source D:\Sources\sxs</var>
Your server will require a restart after you run this Windows PowerShell code. - Install the other prerequisites that are required by SharePoint 2013.
- Run the Products Preparation Tool - PrerequisiteInstaller.exe again. "
-
Edited by
Mandeep G
Friday, May 03, 2013 2:06 AM
-
Proposed as answer by
sstyhoo
Tuesday, September 24, 2013 10:42 AM
May 3rd, 2013 2:05am
Hi,
This issue has been addressed by following knowledge based article
http://support.microsoft.com/kb/2765260
There are three or four sections to this document, for me following section did the trick.
"
-
Offline method: Server is not connected to the Internet
To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used
in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.
For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the
-source parameter is as follows:
D:\sources\sxs
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
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 <var>-Source D:\Sources\sxs</var>
Your server will require a restart after you run this Windows PowerShell code. - Install the other prerequisites that are required by SharePoint 2013.
- Run the Products Preparation Tool - PrerequisiteInstaller.exe again. "
- Edited by
Mandeep G
Friday, May 03, 2013 2:06 AM
- Proposed as answer by
sstyhoo
Tuesday, September 24, 2013 10:42 AM
May 3rd, 2013 5:05am
Hi,
This issue has been addressed by following knowledge based article
http://support.microsoft.com/kb/2765260
There are three or four sections to this document, for me following section did the trick.
"
-
Offline method: Server is not connected to the Internet
To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used
in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.
For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the
-source parameter is as follows:
D:\sources\sxs
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
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 <var>-Source D:\Sources\sxs</var>
Your server will require a restart after you run this Windows PowerShell code. - Install the other prerequisites that are required by SharePoint 2013.
- Run the Products Preparation Tool - PrerequisiteInstaller.exe again. "
- Edited by
Mandeep G
Friday, May 03, 2013 2:06 AM
- Proposed as answer by
sstyhoo
Tuesday, September 24, 2013 10:42 AM
May 3rd, 2013 5:05am
Hi,
This issue has been addressed by following knowledge based article
http://support.microsoft.com/kb/2765260
There are three or four sections to this document, for me following section did the trick.
"
-
Offline method: Server is not connected to the Internet
To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used
in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.
For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the
-source parameter is as follows:
D:\sources\sxs
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
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 <var>-Source D:\Sources\sxs</var>
Your server will require a restart after you run this Windows PowerShell code. - Install the other prerequisites that are required by SharePoint 2013.
- Run the Products Preparation Tool - PrerequisiteInstaller.exe again. "
-
Edited by
Mandeep G
Friday, May 03, 2013 2:06 AM
-
Proposed as answer by
sstyhoo
Tuesday, September 24, 2013 10:42 AM
May 3rd, 2013 5:05am
Hi,
This issue has been addressed by following knowledge based article
http://support.microsoft.com/kb/2765260
There are three or four sections to this document, for me following section did the trick.
"
-
Offline method: Server is not connected to the Internet
To install the Roles and Features that are required by SharePoint 2013 on Windows Server 2012 in an offline environment, you must have access to the Windows Server 2012 installation media. You can then run the same Windows PowerShell commands that you used
in Method 2, but you must use the -source parameter to specify the location of the required files on the installation media.
For example, assume that you mounted the Windows Server 2012 installation media (ISO) to drive D of the server. Then, the path to provide for the
-source parameter is as follows:
D:\sources\sxs
Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.
Open an elevated Windows PowerShell prompt on the SharePoint server (that is, Run as Administrator), and execute the following commands:
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 <var>-Source D:\Sources\sxs</var>
Your server will require a restart after you run this Windows PowerShell code. - Install the other prerequisites that are required by SharePoint 2013.
- Run the Products Preparation Tool - PrerequisiteInstaller.exe again. "
-
Edited by
Mandeep G
Friday, May 03, 2013 2:06 AM
-
Proposed as answer by
sstyhoo
Tuesday, September 24, 2013 10:42 AM
May 3rd, 2013 5:05am
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
-
Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 3:43pm
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
- Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 6:43pm
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
- Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 6:43pm
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
-
Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 6:43pm
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
-
Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 6:43pm
After hours spent trying to figure this out, I tracked it down to the prereq installer and SharePoint not installing due to systemmangercmd.exe not being present in the system32 folder and thus not being able to run the step for the Roles.
The blog post here will show you how to get the missing files and where to upload them. You will probably need to modify the folder security on the System32 to modify and add folders.
http://danielcai.blogspot.co.nz/2012/05/install-crm-2011-on-windows-server-8.html
Once the file was in place both prereq installer and full installer worked correctly.
-
Proposed as answer by
Joachim Løe
Tuesday, December 03, 2013 7:33 PM
May 24th, 2013 6:43pm
Hi there,
In my case it had to be aspnet_regiis -enable -i
because without the s never ran.
Thanks
Big ups to you folks
-
Proposed as answer by
Tracy'S
Friday, July 11, 2014 7:29 PM
June 27th, 2013 1:09pm
Hi there,
In my case it had to be aspnet_regiis -enable -i
because without the s never ran.
Thanks
Big ups to you folks
June 27th, 2013 4:09pm
This worked in my case. Thanks :)
November 28th, 2013 4:22pm
Worked on Server 2012 R2. Yet its not supported. But to get it installed, it worked. Thanks
December 3rd, 2013 10:33pm
Thx a lot. I just copied/pasted the ServerManagementCMD.exe to the System32 forlder and the prerequisites worked great.
March 30th, 2014 1:39pm
rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe
then run
prerequisiteinstaller
March 31st, 2014 4:43am
rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe
then run
prerequisiteinstaller
-
Proposed as answer by
Retro.ru
Tuesday, May 13, 2014 5:23 PM
March 31st, 2014 8:39am
rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe
then run
prerequisiteinstaller
-
Proposed as answer by
Retro.ru
Tuesday, May 13, 2014 5:23 PM
March 31st, 2014 11:39am
rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe
then run
prerequisiteinstaller
-
Proposed as answer by
Retro.ru
Tuesday, May 13, 2014 5:23 PM
March 31st, 2014 11:39am
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
-
Proposed as answer by
JV_SubtleTech
Wednesday, April 16, 2014 6:11 AM
April 1st, 2014 7:27pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
April 1st, 2014 10:27pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
- Proposed as answer by
JV_SubtleTech
Wednesday, April 16, 2014 6:11 AM
April 1st, 2014 10:27pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
-
Proposed as answer by
JV_SubtleTech
Wednesday, April 16, 2014 6:11 AM
April 1st, 2014 10:27pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
-
Proposed as answer by
JV_SubtleTech
Wednesday, April 16, 2014 6:11 AM
April 1st, 2014 10:27pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
-
Proposed as answer by
JV_SubtleTech
Wednesday, April 16, 2014 6:11 AM
April 1st, 2014 10:27pm
Thanks , its working for me.
-
Proposed as answer by
Search
Wednesday, August 20, 2014 5:29 AM
April 11th, 2014 12:22pm
Thanks , its working for me.
April 11th, 2014 3:22pm
Thanks a lot, it worked for me.
April 15th, 2014 6:45am
The option to make a copy and then rename the file is a much better solution than simply renaming the file. This will ensure that anything else looking for the old version can find it (since it's an exe file and not a DLL).
April 16th, 2014 9:13am
To solve the issue I set the following Local Policy:
1. Windows Start
2. run MMC
3. Click File, Add/Remove Snap-in
4. Select Group Policy Object Editor and ADD it
5. Navigate to Administrative templates / System
6. Select and edit Specify Settings for optional component installation and component repair
7. Enable and select Contract Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)
http://sharelockpoint.wordpress.com/2013/09/09/sharepoint-2013-pre-requisites-install-fail-error-the-tool-was-unable-to-install-application-server-role-web-server-iis-role/
April 18th, 2014 3:58am
Yes. This works! Thanks
April 29th, 2014 10:51am
Thanks, this worked for me too
May 5th, 2014 6:16am
why did we have this problem, why does it make sense to have this type of problems in a clean installation
why are these problem legal? why can't we get our money back?
May 7th, 2014 9:15pm
Hi! This one helped, I think along with other tasks I made according to list above. I did:
1. Powershell feauture online installation,
2. Permissions set on system32 folder
3. Finally, when nothing worked, I renamed servermanager.exe to servermanagercmd.exe
After that it worked like a charm!
DON'T FORGET to rename this file back from servermanagercmd.exe to servermanager.exe! Because after restart you will see error saying that server manager link is not available, and setup of sharepoint will start again (no harm though, it will finish witn
note that nothing requires to update).
BR,
Retro
May 13th, 2014 8:22pm
Copying ServerManager.exe to ServerManagerCMD.exe on W2k12R2 for SP2013 resolved the issue.
May 15th, 2014 11:47pm
rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe
then run
prerequisiteinstaller
This worked for me.
May 19th, 2014 6:59pm
I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe
with ServerManagerCMD.exe"
This is what I did actually and it worked.
May 19th, 2014 7:00pm
am logged in as Administrator, but don't have permission to change the find name ServerManager.exe and can't even change the permission,!
May 20th, 2014 10:58pm
I was able to copy the file, paste onto my desktop, rename, and paste back into system32. It worked after that. Does anybody have advice on how to give oneself permission? I am also logged in as root system administrator and unable to
change permissions so I can actually delete/change the original file.
May 23rd, 2014 2:58pm
this worked for me to. Awesome
May 27th, 2014 5:50am
Awesome! you are a Star, thank you :)
July 19th, 2014 10:16am
Yes, make a copy. This worked for me.
August 25th, 2014 3:51pm
I am on Windows Server 2008 R2 SP1 and the command was "aspnet_regiis" instead of "aspnet_regii". THANKS!!
September 14th, 2014 7:36pm
Yeah! Year 2014 and still this bug not fixed!
September 22nd, 2014 12:13pm
WORKED!!
September 22nd, 2014 2:55pm
After following the below steps I was able to get the issue resolved.
To solve the issue I set the following Local Policy:
1. Windows Start
2. run MMC
3. Click File, Add/Remove Snap-in
4. Select Group Policy Object Editor and ADD it
5. Navigate to Administrative templates / System
6. Select and edit Specify Settings for optional component installation and component repair
7. Enable and select Contract Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)
9.- Re run the prerequisite installation
Reference: http://sharelockpoint.wordpress.com/2013/09/09/sharepoint-2013-pre-requisites-install-fail-error-the-tool-was-unable-to-install-application-server-role-web-server-iis-role/
-
Proposed as answer by
Antonio Segovia
Wednesday, October 22, 2014 12:33 AM
September 24th, 2014 3:35am
This worked for me as well - none of the other suggested solutions did.
November 7th, 2014 5:22am
If you encounter the error on server 2012 R2, the solution is simple.
1. Browse to C:\Windows\System32
2. Make a copy of the file ServerManager.exe in the same folder i.e. copy paste the file to create say
ServerManager-Copy.exe
3. rename ServerManager-Copy.exe to ServerManagerCMD.exe
Run the SP2013 pre-requisite installer again and it should now run without issues :)
December 21st, 2014 6:35pm
This works... thanks man !
December 31st, 2014 4:57am