none
SharePoint 2013 Standalone Install - "Configuration did not Complete Successfully" Error RRS feed

  • Question

  • Folks,

    I'm trying to install a standalone version of SharePoint 2013 on a single server for demo purposes on a Windows 2012 R2 server. I bring up the splash screen and the prerequisite install and reboots go as planned. However when next I bring up the splash, Install SharePoint, and standalone mode, I starts the install, then several minutes into the install I get a "Windows SharePoint Server 2013" dialog box that says, "Microsoft SharePoint Server 2013 configuration did not complete successfully. One or more required office components failed to complete successfully. For more information, consult the setup log."

    The only "error" I see in the SharePoint Server Setup Log is "Error: Command: 'C:\Program Files\Common Files\Microsoft Shared\SERVER15\Server Setup Controller\dbwrap.exe' failed with error code: -2068578304. Type: 8::CommandFailed." Not sure what that is or how to fix. Can't seem to get past this point. Even tried to run repair, but no luck. Anyone else run into this and know how to fix or what I need to do? Seems this should be pretty straight forward on a standalone install , but have it just won't install. Anybody know what I am doing wrong so I can correct? Appreciate any help. Thanks. 


    Rick Frisby

    Thursday, March 10, 2016 9:06 PM

Answers

All replies

  • Did you removed .NET 4.6 from 2012 R2 server before starting the install? 

    You need to make sure you use the .NET removal tool to remove .NET 4.6 and any other .NET updates from the server before you can start the 2013 installation.  Your SharePoint 2013 ISO must be SharePoint 2013 with SP1.

    http://geekswithblogs.net/bjackett/archive/2015/07/28/be-careful-installing-.net-4.6--visual-studio-2015-with.aspx

    https://blogs.technet.microsoft.com/stefan_gossner/2015/08/11/sharepoint-2013-and-net-framework-4-6/

    http://blogs.catapultsystems.com/eskaggs/archive/2016/03/09/bloguninstall-net-framework-4-6-to-install-sharepoint-2013/

    https://blogs.technet.microsoft.com/stefan_gossner/2015/08/11/sharepoint-2013-and-net-framework-4-6/

    Once you remove the 2 hotfixes and .NET 4.6 you will be able to install SharePoint 2013.


    Jerry Yasir - Office Server & Services MVP/MCT Hewlett Packard Enterprise - If this reply helped you resolve your issue, please propose as answer. It may help other community members. Thanks!

    Thursday, March 10, 2016 9:54 PM
  • Hmmmm... Didn't get any errors indicating needing 4.5 and didn't see 4.6 on the features page. Must be something hidden. I'll definitely go have a look and see if I can find/uninstall .net 4.6. Thanks for the pointers.

    Rick Frisby

    Friday, March 11, 2016 9:21 PM
  • Downloaded and ran the .NET removal tool to remove.NET4.6. Reran pre-requisite installer to make sure .NET4.5 was installed and everything came back ok. Went to run the SharePoint installer again which ran repair. Runs a few minutes and same "Windows SharePoint Server 2013" dialog box that says, "Microsoft SharePoint Server 2013 configuration did not complete successfully. One or more required office components failed to complete successfully. For more information, consult the setup log."

    Looking at the log, only things that look like errors near the end are highlighted:

    2016/03/14 16:35:35:410::[2264] Msi feature: SpxIntl_1033, had state -1, treating as absent
    2016/03/14 16:35:35:472::[2264] Msi feature: SpxCore, had state -1, treating as absent
    2016/03/14 16:35:35:504::[2264] Searching for patches for the current chained install in: E:\updates
    2016/03/14 16:35:35:504::[2264] Detecting Old LOBi
    2016/03/14 16:35:35:504::[2264] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.OSERVER.
    2016/03/14 16:35:35:504::[2264] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.OSERVER.
    2016/03/14 16:35:35:504::[2264] Detecting Old Outlook
    2016/03/14 16:35:35:504::[2264] Detecting Old Groove
    2016/03/14 16:35:35:504::[2264] Catalyst verified this system is not a domain controller, verify result : 1150
    2016/03/14 16:35:35:504::[2264] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.OSERVER.
    2016/03/14 16:35:35:504::[2264] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.OSERVER.
    2016/03/14 16:35:44:503::[2264] MMode choice: 'Repair' was selected.
    2016/03/14 16:35:44:503::[2264] Final Option Tree:
    2016/03/14 16:35:44:503::[2264]   Products:local
    2016/03/14 16:35:44:503::[2264] JobExecutionMode is ReinstallExecutionMode.
    2016/03/14 16:35:44:519::[3472] Kicking off chained repair...
    2016/03/14 16:35:44:519::[3472] Executing command path: 'C:\Program Files\Common Files\Microsoft Shared\SERVER15\Server Setup Controller\dbwrap.exe', args: 'timeout=2950 InstallMode=Repair'
    2016/03/14 16:35:44:519::[3472] Starting C:\Program Files\Common Files\Microsoft Shared\SERVER15\Server Setup Controller\dbwrap.exe timeout=2950 InstallMode=Repair
    2016/03/14 16:37:29:815::[3472] Error: Command: 'C:\Program Files\Common Files\Microsoft Shared\SERVER15\Server Setup Controller\dbwrap.exe' failed with error code: -2068578304. Type: 8::CommandFailed.
    2016/03/14 16:37:29:830::[2264] Showing completion dialog.
    2016/03/14 16:38:19:190::[2264] Catalyst execution finished: 03/14/2016 16:38:19.  Return code: 8.
    2016/03/14 16:38:19:190::[2264] PERF: TickCount=307394875 Name=RunSetup Description=End function

    2016/03/14 16:38:19:753::[2264] Setup temp folder set to [C:\Users\S-SPAD~1\AppData\Local\Temp\2\Setup00000c3c].

    No errors regarding.NET 4.6 (there were none the first time either). Any other ideas as to what could be causing this standalone install configuration to not complete successfully?


    Rick Frisby

    Monday, March 14, 2016 9:37 PM
  • Hi Rick,

    For resolving the dbwrap.exe failed with error code error, please try to change the following registry value:

    Open the server’s registry by typing “regedit”> navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS > find ServerRole > change its data from SINGLESERVER to APPLICATION.

    Best regards,

    Linda Zhang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, March 18, 2016 8:40 AM
    Moderator
  • Thanks for the response Linda. I tried that and the install did complete. However, at the end of the install it did not complete with the SharePoint Configuration Wizard as expected. Manually firing the wizard, it looks like it is now expecting a farm installation as it wants you to add the server information (standalone install should install/configure SQL as part of the install). Even adding the database server information (which should be the same server as standalone is a one server install), it cannot find SQL. Did you experience this to and how did you get around it?

    Rick Frisby

    Friday, March 18, 2016 2:30 PM
  • Hi Rick,

    Are there any message in the wizard or ULS logs? Please provide the logs and the screenshot of the error in the wizard for further research.

    Here are some general troubleshooting steps:

    1. Disable firewall;

    2. Verify spelling of database server;

    3. Check if all SQL server services are running;

    4. Check the user account has permissions to use SQL.

    For more troubleshooting steps, you can refer:

    http://social.technet.microsoft.com/wiki/contents/articles/24493.sharepoint-2013-cannot-connect-to-database-at-sql-server-at-the-database-might-not-exist.aspx

    Best regards,

    Linda Zhang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, March 22, 2016 12:31 PM
    Moderator
  • Hi Linda,

    Checked all that and still no go. Eventually came down to one of our IT guys having to install it with Powershell commands.


    Rick Frisby

    Wednesday, March 30, 2016 4:34 PM
  • Hi,

    I am facing same issue. Please can you help me to fix this problem?

    Can you share steps and script?

    I have SharePoint 2013 On Prem. I am not able to install patches nor repair/install sharepoint.

    Thanks

    Chirag


    • Edited by Chirag83 Sunday, July 21, 2019 7:20 AM
    Sunday, July 21, 2019 7:19 AM
  • Hi Chirag,

    Make sure you have proper permissions and share the ULS Logs while running the PSConfig.

    Thanks & Regards,


    sharath aluri


    Sunday, July 21, 2019 7:37 AM