none
Add a New Server to a Farm with all Patches till March 2016 CU

    Question

  • Hello All,

    I have an existing farm of one server of SharePoint 2013 with Project server Patched Till March 2016 CU

    Now I have to add a new server to the farm , I have already Installed

    SharePoint 2013 RTM + SP1

    Project Server 2013 RTM + SP1

    KB3114823 which is for Project & SharePoint March 2016 CU

    When I try to add Server to the Farm using PSConfig I get the many Errors as per below based on the Existing old SErver in the Farm

    Microsoft SharePoint Foundation 2013 Core (15.0.4571.1502) 
     Missing on Old SErver
     Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit Edition (15.0.4571.1502) 
     Missing on Old SErver
     Microsoft SharePoint Foundation 2013 1033 Lang Pack
     
     Microsoft SharePoint Foundation 2013 1033 Lang Pack (15.0.4571.1502) 
     Missing on Old SErver
     Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit Edition (15.0.4571.1502)

    I tried to ran Get-SPProduct -Local on existing old Server but that didn't helped still the Same issue

    I ran the ROISCAN report in existing server it Shows the Service Pack level as SP1

    Thanks in advance, Help as this is urgent

    Tuesday, May 02, 2017 7:06 AM

Answers

  • Issue was due to SharePoint Installable file

    Gathered the correct Installable from Microsoft as the patch version was incorrect

    So marking that as an answer

    • Marked as answer by Rkakkar Saturday, July 29, 2017 1:01 PM
    Saturday, July 29, 2017 1:01 PM

All replies

  • Hi Rkakkar,

    Usually I use the script from this blog to check the patch baseline from the SharePoint servers:

    https://blogs.technet.microsoft.com/stefan_gossner/2015/04/20/powershell-script-to-display-version-info-for-installed-sharepoint-product-and-language-packs/

    I believe your problem is related to the Language pack. Check with the script above what language pack should be updated.

    I hope it helps.

    Tuesday, May 02, 2017 8:57 PM
  • Issue was due to SharePoint Installable file

    Gathered the correct Installable from Microsoft as the patch version was incorrect

    So marking that as an answer

    • Marked as answer by Rkakkar Saturday, July 29, 2017 1:01 PM
    Saturday, July 29, 2017 1:01 PM