4

When I try to install Sharepoint 2013 on a new Windows 2012 R2 server, I encounter the following error with the Product Preparation Tool:

Unable to install Application Server Role

enter image description here

I followed a KB article of Microsoft but without any result.

Update: I manually installed all prerequisites. They are successfully installed, but the Product Preparation Tool still gives an error:

enter image description here

|improve this question
  • 1
    Do you have the disc/iso left for w2012 R2? Mount it to D, and add Net 3.5 from "Add features and roles" in Server Manager, and specify the sourcepath to " D:\sources\sxs". – Christoffer Jan 18 '16 at 9:37
  • 1
    For full support you should have installed with the SharePoint 2103 SP1 slipstreamed installation media, that is the first one officially supporting Server 2012R2 – Robert Lindgren Jan 18 '16 at 12:14
  • @RobertLindgren thanks. See my answer for the 'strange' thing I had to do to fix this. – Citizen SP Jan 18 '16 at 12:18
  • Yeah that is a known workaround, but great that you found away around it :) – Robert Lindgren Jan 18 '16 at 14:28
5

You also need .NET Framework 3.5 installed. Check under features that its available.

enter image description here

If not, follow the guide How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2

|improve this answer
  • 1
    Beat me to it. +1 :) – Christoffer Jan 18 '16 at 9:39
  • 1
    @Benny Skogberg check. Already installed. – Citizen SP Jan 18 '16 at 9:40
  • 1
    @CitizenDB You will need to restart the server. – Christoffer Jan 18 '16 at 9:43
  • 1
    @user19952 done. no result – Citizen SP Jan 18 '16 at 9:45
  • 1
    @CitizenDB Last times i had problem with R2 i had to install this update as well to be able to progress. Worth a shot. support.microsoft.com/en-us/kb/3005628 – Christoffer Jan 18 '16 at 9:52
1

The solution to this problem: In Windows Server2012 R2 ServerManagerCMD.exe does not exist, but the setup needs it. I made a copy of C:\Windows\system32\ServerManagerCmd.exe and renamed it to ServerManagerCMD.exe. After this 'fix' all prerequisites are successfully installed.

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.