cakriwut - Jan 2, 2014SharePoint 2010 | Troubleshoot Un-sync Cummulative Update http://t.co/ttCTnuUBvm
Today, we deploy December 2013 CU and PU for Project Server 2010. After completing the binary installation, our patching process can not continue because the farm shows missing KB2553430 (December 2013 PU) in one of the server. I don't see any technical reason why it happened, so I went through following work-around
Re-run the installation package using PACKAGE.BYPASS.DETECTION.CHECK=1 option (more info here). Result : unsuccessful, the impacted server is still showing that it doesn't have KB2553430 Extract the installation package and install the *.
SharePoint 2010: Troubleshoot Language Pack 14.0.6028.1000 | Ideas For Free - Jan 4, 2013[…] Subsequently apply other patches such as (install in correct order as following): - sharepointfoundation2010sp1-kb2460058-x64-fullfile-en-us.exe - officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe - serverlanguagepack2010sp1-kb2460056-x64-fullfile-en-us.exe - serverlanguagepack2010sp1-kb2460056-x64-fullfile-??-??.exe (if you have other language pack) - wacserver2010sp1-kb2460073-x64-fullfile-en-us.exe (if you have Office Web Apps) - wacserver2010sp1-kb2460073-x64-fullfile-??-??.exe (if you have other language pack for Office Web Apps)When you install those patches, make sure to use PACKAGE.BYPASS.DETECTION.CHECK=1 option, to bypass version checking.
English Its been a history, that some early release of CU contains regression bug or a slip-streamed bits contains incomplete update. Early-adopter sometimes face a dead-end situation, where the early-release patch has been deployed and unable to install the new update. The reason is because every patch/CU also contains version checking mechanism that will prevent installation/patching to wrong system. Basically, it does your homework to read the pre-requisites in the system.