none
Unable to install Cumulative Updates on Project Server 2013 RRS feed

  • Question

  • Hello,

    I currently have a Project Server 2013 3-tier farm which is currently on September 2014 CU with SP1 installed. For a few development reasons I was not able to patch it further, but now I have to bring it to March 2016 CU.

    For some reason the patch install fails stating "The expected version of this product was not found".

    Here's what I have tried,

    1. Tried installing previous CUs one by one and it finally accepted Feb 2015 CU.

    2. After upgrading to Feb 2015, the install failed yet again and only March 2015 CU seemed allowed.

    3. Post March 2015 CU update, its now allowing only April 2015 CU, even May 2015 CU fails giving the same error mentioned above.

    Is there any pre-requisite that I am missing here? I would like to come up to March 2016 patch version of sharepoint without having to install updates or CUs for every month one-by-one.

    Any help would be appreciated here.



    Thursday, June 16, 2016 9:15 AM

Answers

  • I was finally able to fix this by forcibly installing CU from CMD by adding bypass detection parameters on elevated access CMD

    https://social.technet.microsoft.com/Forums/en-US/5c8a870f-1e44-4a65-8175-7a97a4bc3a90/packagebypassdetectioncheck1 

    However the install took about 4 hours to complete on each server of the farm and the build version did not get updated on CA, even though PSconfig completed without errors.

    I then reinstalled the same CU exes on all the farm servers without bypassing detection check and this time they ran as expected and reflected the correct build number on central admin.

    I couldn't really figure out why this happened, but things look good now.

    Also, Sharepoint Designer connectivity failed for some users post update, which resolved after clearing contents of below folders for all user profiles on the servers.

    1. C:\Users\<username>\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache

    2. C:\Users\<username>\AppData\Local\Microsoft\WebsiteCache

    3. C:\Users\<username>\AppData\Roaming\Microsoft\Web Server Extensions\Cache

    Sunday, July 31, 2016 4:59 PM

All replies

  • Are you using Rollup patch or individual patch

    Here is the link for rollup patch which includes Project Server and SharePoint server patch)

    https://support.microsoft.com/en-us/kb/3114823



    Hrishi Deshpande, Project MVP

        

    Saturday, June 18, 2016 2:58 AM
    Moderator
  • I was finally able to fix this by forcibly installing CU from CMD by adding bypass detection parameters on elevated access CMD

    https://social.technet.microsoft.com/Forums/en-US/5c8a870f-1e44-4a65-8175-7a97a4bc3a90/packagebypassdetectioncheck1 

    However the install took about 4 hours to complete on each server of the farm and the build version did not get updated on CA, even though PSconfig completed without errors.

    I then reinstalled the same CU exes on all the farm servers without bypassing detection check and this time they ran as expected and reflected the correct build number on central admin.

    I couldn't really figure out why this happened, but things look good now.

    Also, Sharepoint Designer connectivity failed for some users post update, which resolved after clearing contents of below folders for all user profiles on the servers.

    1. C:\Users\<username>\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache

    2. C:\Users\<username>\AppData\Local\Microsoft\WebsiteCache

    3. C:\Users\<username>\AppData\Roaming\Microsoft\Web Server Extensions\Cache

    Sunday, July 31, 2016 4:59 PM
  • I was finally able to fix this by forcibly installing CU from CMD by adding bypass detection parameters on elevated access CMD

    https://social.technet.microsoft.com/Forums/en-US/5c8a870f-1e44-4a65-8175-7a97a4bc3a90/packagebypassdetectioncheck1 

    However the install took about 4 hours to complete on each server of the farm and the build version did not get updated on CA, even though PSconfig completed without errors.

    I then reinstalled the same CU exes on all the farm servers without bypassing detection check and this time they ran as expected and reflected the correct build number on central admin.

    I couldn't really figure out why this happened, but things look good now.

    Also, Sharepoint Designer connectivity failed for some users post update, which resolved after clearing contents of below folders for all user profiles on the servers.

    1. C:\Users\<username>\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache

    2. C:\Users\<username>\AppData\Local\Microsoft\WebsiteCache

    3. C:\Users\<username>\AppData\Roaming\Microsoft\Web Server Extensions\Cache

    Sunday, July 31, 2016 4:59 PM