SharePoint 2013 Installation and Configuration Issues


# Issue 1:

During Installing SharePoint 2013 Prerequisites there was an error in installing Application Server Role , Web Server (IIS) Role : Configuration error

 

Steps to fix (Installing .Net Framework 3.5):

  1. Insert the Windows Server 2012 installation image or DVD
  2. Open a command prompt window (run as Administrator) and run the following:
  3. Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:\sources\SxS /LimitAccess

Note: D:\ is a Label for CD Drive in my case where Windows Server 2012 ISO image.

 

# Issue 2:

During running Configuration Wizard I got the following error in step 3:

Failed to create the configuration database.

Steps to fix (Change setting in SQL Server Instance - this option was optional in SharePoint 2010 but in SharePoint 2013 it's mandatory):

  1. Open Microsoft SQL Server Management Studio
  2. Login with sysadmin user 
  3. Right Click on instance name and select properties >> Advanced
  4. Change Max Degree of Parallelism to 1
  5. Restart the SQL Service

For more details: http://sps2013.blogspot.com/2013/01/this-sqlserver-instance-does-not-have.htm 

 

# Issue 3:

During running Configuration Wizard I got the following error in step 3:

Failed to secure the SharePoint resources.

 

Steps to fix (Change Folder Owner):

  1. Go to C:\Windows\Tasks
  2. Right Click on Tasks Folder and select Properties
  3. Go to Security Tab
  4. Click Advanced button
  5. Click Change link in owner filed
  6. Enter local Administrators group (Where SharePoint account which perform the installation belong to this group)

 

# Issue 4:

During installing April 2013 Cumulative update http://support.microsoft.com/kb/2726992 I got the following error:
 

 

Steps to fix:

Make sure when you downloaded the package to keep the cap file with the exe file during the installation and the reason CU has two files when its size more than 2 GB.
 

 

For more details http://blogs.technet.com/b/praveenh/archive/2013/06/18/the-installation-of-this-package-failed-error-while-installing-april-2013-cu-kb-2726992-for-sharepoint-2013.aspx

 

 # Issue 5:

After installing SP 1 and then try to run Configuration Wizard I got the following error in log file

Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.

Steps to fix:

check this link

http://blogs.msdn.com/b/opal/archive/2010/04/18/track-sharepoint-2010-installations-by-service-connection-point-ad-marker.aspx

 

 

 

 

 

Comments (29)

  1. sunitha_km says:

    Nice article

  2. Naseer says:

    No Success even after doing all of these steps. Still prerequisites is failing.

  3. fabdulwahab@outlook.com says:

    Check if SharePoint servers have internet access and you are local admin or try to configure the prerequisites using offline and manual way.

  4. Shehzad says:

    i did every thing but still same error IIS configuration

  5. fabdulwahab@outlook.com says:

    Try to configure IIS configuration manually :

    1- open Server Manager

    2-click on Add roles and features

    3-click next

    4- click next

    5-click next

    6-from roles : select Application Server and Web Server

    7-select .Net Framework

    8-click next

    9-click next

    10-click next

    11-from role services :keep the default settings and select windows authentication

    12-click next

    13-specify the alternate source path for sxs folder and then click ok and install

  6. sachin sisodiya says:

    Issue 1 was resolved successfully.

    Thanks,

  7. Amit says:

    Hi

    Issue 3  not working.. still giving the same error..

    Can you guide me ??

    Thanks

  8. Joe C says:

    Perfect Thank you!

  9. Nabeel says:

    rename the file C:windowsSystem32ServerManager.exe with ServerManagerCMD.exe

    then run prerequisiteinstaller

  10. Endrik says:

    Perfect..

  11. Thai says:

    Nabeel…thanks a lot.  That worked!

  12. G.R. says:

    did the :-

    rename the file C:windowsSystem32ServerManager.exe with ServerManagerCMD.exe

    and low and behold – it now works  ( I just copied ServerManager.exe to ServerManagerCMD.exe )

    I am running Server 2012 R2

    thanks

  13. Nick White says:

    I thought copying C:windowsSystem32ServerManager.exe to ServerManagerCMD.exe was ridiculous.  But I did it, and it worked! Same as above Server 2012 R2.

  14. odee says:

    Worked a treat…  Good work on that MS.  Obviously been through a rigorous testing regime

  15. IDG says:

    C:windowsSystem32ServerManager.exe to ServerManagerCMD.exe   it work for me in windows server 2012 R2 !!!

  16. Roy says:

    ServerManager.exe rename worked!

    I copied ServerManager.exe to desktop, renamed to ServerManagerCMD.exe back to C:windowssystem32

  17. Richard says:

    Worked, thanks Nabeel!  

    Just to clarify, you can't rename the original file.  You need to create a copy and rename the copy to "ServerManagerCMD.exe" and just leave them both in that directory.  

  18. MrVinni says:

    "" I thought copying C:windowsSystem32ServerManager.exe to ServerManagerCMD.exe was ridiculous.  But I did it, and it worked! Same as above Server 2012 R2. ""

    After many other tries and workarounds… this worked for me too!

    #ridiculous

  19. Doug Mooney says:

    Its .net 3.5. Install this and it will work.

  20. autechre12 says:

    ServerManagerCMD thing worked for me as well.  Lamest issue ever, thanks so much for the fix.

  21. Neil says:

    Hi guys,

    will it work in 2008r2 also. Please let me know. i have a important delivery tomr. i need to fix it

  22. Errant13 says:

    Nabeel's solution works

    Thanks Nabeel

  23. Michael says:

    Also did the rename – also worked C:windowsSystem32ServerManager.exe with ServerManagerCMD.exe

  24. Zulqarnain Ul Hassan says:

    Renaming to ServerMangerCMD worked perfectly. Thanks a million,

  25. Zulqarnain Ul Hassan says:

    Renaming to ServerMangerCMD worked perfectly. Thanks a million,

  26. Ditto Devassy- EVENTTRACKER says:

    install SP2013 without SP1 on windows 2012 and with SP1 on windows 2012 r2

  27. stewart says:

    copied servermanager to another folder renamed with CMD copied back and YIP it works on 2012R2

  28. Oscar Perez says:

    Thank you, just copy the ServerManager.exe to ServerManagerCMD.exe and works!!

    How do you found this is the problem?

Skip to main content