none
Can't Add WFE to SharePoint2013-ProjectServer 2013 Farm RRS feed

  • Question

  • I need to add a WFE to an EXISTING farm (one WFE, one APP, separate SQL Server--all machines running Windows Server 2012) that is running SharePoint 2013-Project Server 2013 farm version 15.0.4535.1000 (August CU).

    However, I can't get the March PU to install.

    Here are the steps I am taking:

    1. Install SharePoint 2013 RTM (after running Pre-installer successfully)

    2. Install Project Server 2013 RTM

    At this point Programs and Features reveals that SharePoint Server 2013 15.0.4420.1017 and Project Server 2013 15.0.4420.1017 are installed

    3. Install March 2013 PU which contains updates for both SharePoint 2013 and Project Server 2013 - kb2768001.

    However, when I run the March 2013 PU (ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe) it runs for a couple of minutes and then says "The installation of this package has failed" and the log gave the common Error 1603 error. I rebooted the server, thinking that some file could be open and now when I try to run the March PU update I immediately receive the error "An error occurred when running detection".

    Does anybody have any idea what is going on? Am I following the correct steps to add a WFE to an existing SP2013-ProjectServer2013 farm?


    Kathryn Birstein, Senior SharePoint Architect

    Monday, December 30, 2013 4:18 AM

All replies

  • I need to add a WFE to an EXISTING farm (one WFE, one APP, separate SQL Server--all machines running Windows Server 2012) that is running SharePoint 2013-Project Server 2013 farm version 15.0.4535.1000 (August CU).

    However, I can't get the March PU to install.

    Here are the steps I am taking:

    1. Install SharePoint 2013 RTM (after running Pre-installer successfully)

    2. Install Project Server 2013 RTM

    At this point Programs and Features reveals that SharePoint Server 2013 15.0.4420.1017 and Project Server 2013 15.0.4420.1017 are installed

    3. Install March 2013 PU which contains updates for both SharePoint 2013 and Project Server 2013 - kb2768001.

    However, when I run the March 2013 PU (ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe) it runs for a couple of minutes and then says "The installation of this package has failed" and the log gave the common Error 1603 error. I rebooted the server, thinking that some file could be open and now when I try to run the March PU update I immediately receive the error "An error occurred when running detection".

    Does anybody have any idea what is going on? Am I following the correct steps to add a WFE to an existing SP2013-ProjectServer2013 farm?


    Kathryn Birstein, Senior SharePoint Architect

    Monday, December 30, 2013 4:20 AM
  • Hi there,

    Issue is not due to any open file. Do you have any office component installed on this server?, if yes most of the time issue due to msi cache corruption of installed office products, since SharePoint and Project is part of office family this affects the installation. If this is a new server I would recommend to re-image the server to get you back on the track  quickly, since troubleshooting might take some time.


    Hrishi Deshpande Senior Consultant

    Monday, December 30, 2013 4:27 AM
    Moderator
  • Hi, 

    I would suggest you first after SharePoint and project server installation run configuration wizard and add new WFE server into the farm, Then check windows for updates, update your server with new windows patches then install march roll up  CU + Aug CU for project server 2013 and try to run it .

    If possible i would suggest you to reinstall everything as server it new.

    Also go with link which is telling about some issues of March CU.

    http://blogs.technet.com/b/projectsupport/archive/2013/04/11/project-server-2013-march-public-update-problems-running-the-sharepoint-configuration-wizard.aspx

    http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=209


    kirtesh



    • Edited by Kirteshtiw Monday, December 30, 2013 5:16 AM
    Monday, December 30, 2013 5:10 AM
  • Hi, 

    I would suggest you first after SharePoint and project server installation run configuration wizard and add new WFE server into the farm, Then check windows for updates, update your server with new windows patches then install march roll up  CU for project server 2013 and try to run it .

    If possible i would suggest you to reinstall everything as server it new.

    Also go with link which is telling about some issues of March CU.

    http://blogs.technet.com/b/projectsupport/archive/2013/04/11/project-server-2013-march-public-update-problems-running-the-sharepoint-configuration-wizard.aspx

    http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=209


    kirtesh

    Monday, December 30, 2013 5:13 AM
  • Hi Hrishi,

    Actually, we have reimaged it once to no avail and there are no Office products installed.

    Kathryn


    Kathryn Birstein, Senior SharePoint Architect

    Tuesday, December 31, 2013 3:37 PM
  • Kathryn Did you try installing the update using elevated privileges? (Run as administrator). Also try downloading the update once again.


    Hrishi Deshpande Senior Consultant

    Tuesday, December 31, 2013 4:18 PM
    Moderator
  • Hi Hrishi,

    I figured out what was wrong! It's kind of a strange situation. The server only had 32 gigs of SYSTEM hard drive space although the other WFE had 80 gigs of SYSTEM hard drive space.

    There was only 4 gigs of SYSTEM space free after I installed the SharePoint 2013 RTM and Project Server 2013. So there was not enough SYSTEM drive space for the March PU to expand.

    When I noticed the low drive space condition, I had it increased to 80 gigs but I still got an error when trying to install the March PU.

    Then I had a brainstorm and I uninstalled the Project Server 2013 RTM and the SharePoint Server 2013 and rebooted the server.

    Then I reinstalled the SharePoint Server 2013 and the Project Server 2013 RTM and FINALLY, the March PU installed!

    So apparently the low system drive condition affected the install of the RTM softwares . . .

    Thanks for your suggestions!

    Kathryn


    Kathryn Birstein, Senior SharePoint Architect

    Wednesday, January 1, 2014 2:07 AM
  • Thanks for updating us, glad to hear that your issue has been resolved.


    Hrishi Deshpande Senior Consultant

    Thursday, January 9, 2014 3:48 AM
    Moderator