4

Recently, I have updated April-2017 CU (KB3178730) on SharePoint Server 2013.

  • Post patching configuration DB version is: 15.0.4927.1000,
  • However when I see articles(Todd blog), should get configuration DB version: 15.0.4919.1003.

P.S. Before patching config DB version was:15.0.4841.1000 (July-2016 CU).

  • What version numbers are reported in your test environments? – Greg W Jun 3 '17 at 9:47
  • Thank you! Can you suggest me now, what I can do best way without effect share point farm? – Kishore Jun 3 '17 at 12:11
  • Post patching configuration DB version is: 15.0.4927.1000(April-2017 CU), Before patching config DB version was:15.0.4841.1000(July-2016 CU). – Kishore Jun 3 '17 at 12:17
  • Hi @Kishore sorry, I can't get it! what do you mean with the best way in "what I can do the best way without effect share point farm" ! Do you mean the best way to patching or checking the build number? anyway check my article at blog.devoworx.net/2014/11/30/… it answers all these questions, also it's mentioned in my below answer. – Mohamed El-Qassas MVP Jun 3 '17 at 12:25
  • can I uninstall the April-2017 CU now? – Kishore Jun 3 '17 at 12:31
5

Yes you are right, the build number for April 2017 CU is 15.0.4919.1003

But I advise you to don't trust the build number in Manage Servers in Farm, it often gives you a wrong indication about installed fixes.

enter image description here

Stefan Goßner discussed the reason in details at SharePoint patching demystified I quoted some

One reason might be that you looked at the KB article for SharePoint server and not the one for SharePoint Foundation. These two components might have slightly different version number – e.g. the SharePoint server package might have been created a couple of days later than the SharePoint Foundation package. As the version number on the "Manager Servers in this farm" page in the Central Admin only shows details for the SharePoint Foundation component you cannot expect to see the version number listed in the SharePoint server KB article.

But even when looking at the SharePoint Foundation KB article there are rare cases that the patch level listed in the central administration is lower than the version number in the KB article. The reason for this is that different fixes are added to the CU at different times. Some fixes modify DLLs of the components other just CSS files or JavaScript files. Most of the fixes affect the Microsoft.SharePoint.dll as this is the core component of the SharePoint Foundation component – so its version number usually has the highest version number in the package. But not always! It might be that the last fix being added to the package is a different file. If this is the case, then the version number in the KB article might reflect the version of this other file. If this file is a DLL you can verify this in explorer. But if this file is just a CSS file or a Javascript file or any other file which does not carry version information then you might not be able to identify the file which defines the version number in the KB article.

To check Get the Products and Patches build numbers that already installed on the farm.

enter image description here

Check the install status and version columns for all installed Products/Patches.

enter image description here

Also, check other alternative ways to Find Farm Patch Level/ build number

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.