Common Issue: April 2015 fixes for SharePoint 2013 might not install on Sharepoint 2013 SP1 slipstream builds (updated May 12th)


A couple of customers already ran into this issue: if you created your farm based on the SharePoint 2013 SP1 slipstream build available on MSDN and VLSC you might not be able to install the latest patches (April CU and PU). The reason is that starting in April the RTM baseline is no longer supported by the fixes. The fixes require the SP1 baseline.

But there are two flavors of SP1: the original one with version 15.0.4569.1506 and a rereleased version with build 15.0.4571.1502. The slipstream builds never got rereleased as they were not affected by the problems that led to the rerelease of SP1.
The problem with April fixes is that they only install on the patch baseline of the rereleased SP1:

<TargetVersion Validate="true" ComparisonType="Equal" ComparisonFilter="MajorMinorUpdate">15.0.4571.1502</TargetVersion>

A workaround  right now is to install the rereleased SP1 before applying the April fixes.

Be aware that this also applies to each installed language pack.

Update April 20th, 2015: You can use the script to identify the patch baseline version info to see which components need upgrade.

[Update from May 12th, 2015]: May CU solves the problem with the different SP1 baselines introduced in April CU. May CU can be installed as well on the old and on the new SP1 baseline!

Comments (101)

  1. anonymouscommenter says:

    Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

  2. Matthew Carter says:

    Thank you! This helped me as I "swore" I had the correct SP1 but I did not! Thank you!

  3. anonymouscommenter says:

    I did SP1 slipstream for the original install, but I now have version 15.0.4701.1000 What does _that_ correspond to, and will I have issues with April CU?

  4. Hi Daniel,
    it means you have installed March CU on top of the SP1 slipstream baseline.
    Yes you will have problems.
    Cheers,
    Stefan

  5. Wes Niemi says:

    Can I reinstall the rereleased SP1 in a farm that already started with the MSDN/VLSC version [15.0.4569.1506 ] with SP1 and multiple Uber CUs afterward? or do I have to rebuild all of my SharePoint farms with a clean install and migrate the content?

  6. Wes Niemi says:

    I was able to reinstall the rereleased SP1 within my dev farm. But I still cannot install the April 2015 CU as I get the "The expected version of the product was not found on the system." message. I do not want to rebuild my SharePoint Production Farm…what
    else can I do here?

  7. I assume you some language packs which are not on the rereleased SP1 patch level.
    You also have to apply SP1 for each language pack.

  8. Wes Niemi says:

    When I installed the Language Packs, they included SP1 as well. I was not successful in reinstalling SP1 to the Farm, as the web applications are displaying errors. With VMWare, We are rolling my dev farm back to the previous state until I understand the
    best plan of action.

  9. They included the old sp1. You need to install sp1 on top.

  10. Wes Niemi says:

    Just to confirm Stefan, Yes means I have to rebuild my SharePoint Farms?

  11. Wes Niemi says:

    OK…I will try this again…first SharePoint SP1, and then the language Pack SP1 link you sent. Thank you.

  12. Wes Niemi says:

    The Language Pack SP1 when executed is displaying the message "The update is already installed on this system." The challenge here is that I built 2 SharePoint farms with the slipstream sp1, installed language packs with slipstream sp1, then multiple uber
    CUs over time (Sept 2014, Dec 2104, and Feb 2015). Just attempted reinstalling the rereleased SP1, ran products configuration. Then attempted Apr 2015 CU and it displays the message "The expected version of the product was not found on the system." I also
    attempted bringing up my web application and errors are displaying. At this point, not a happy camper.

  13. Wes Niemi says:

    Stefan: I worked with Microsoft today about the April 2015 CU and they got it going by running it through PowerShell with a switch: PACKAGE.BYPASS.DETECTION.CHECK=1 I don’t know yet what the ramifications are with doing this…but I will be doing a lot
    of testing before I touch our Production environment with the same update.

  14. Wes Niemi says:

    Last update, I promise! The April 2015 CU install still fails. I am still working the issue with Microsoft Support. I need to make sure I can install Cumulative Updates moving forward, or if April’s update is buggy and will be replaced.

  15. Hi, Stefan.
    I’m intersted with only two questions:
    1. Next CU (may,june,july,etc) won’t installing on slipstream build? that mean that now installation sequence is next: full package (doesn’t matter sleapstream or not), LP (if required), SP1 for full package, SP1 for LP (if LP applied), March PU (if full not
    slipstream), Last CU?
    2. Will be slipstream package rereleased for excluding some logical unnecessary steps?

  16. anonymouscommenter says:

    I'm confused here, I got 15.0.4701.1000 on my dev enviornment but still april CU won't install, i might have used the slipstream SP1 VLC, whats the course of action here?

  17. Hi Jasper,
    at least one component seems to be below 4701.
    Did you install language packs?
    The you also have to install the rereleased SP1 for each of the language packs.
    Cheers,
    Stefan

  18. anonymouscommenter says:

    Wes Niemi wrote:
    "Stefan: I worked with Microsoft today about the April 2015 CU and they got it going by running it through PowerShell with a switch: PACKAGE.BYPASS.DETECTION.CHECK=1 I don't know yet what the ramifications are with doing this…but I will be doing a lot of
    testing before I touch our Production environment with the same update."

    I deem the Workaround with PACKAGE.BYPASS.DETECTION.CHECK=1 for the Installation of the April CU a valid way to achive the installation, as the slipstream SP 1 is a valid baseline.

    Afterwards the Build Number should be that of the April CU and no Trouble for future Updates, or not, Stefan?

  19. anonymouscommenter says:

    Same issue as Jasper.
    My base install is with build 15.0.4569.1000 (slipstreamed SP1 from MSDN).
    Will I have to reinstall everything ? April 2015 CU keeps telling me that the expected product is not detected.
    I don't have any language packs, and now my environment is on: 15.0.4701.1000

    Thanks.

  20. anonymouscommenter says:

    No language packs are installed

    strangely enough I've started installing SP1, didnt change my build number or put servers on "upgrade required", and now the CU installs

    Can you confirm this is normal or should i raise a ticket with MSFT for this?

  21. Hi Jasper.
    I assume you have been on a higher CU level already. So SP1 installation only had to upgrade the patch baseline but not any file or db schema.
    With other words: That sounds perfectly fine.
    Cheers,
    Stefan

  22. Hi Mike,
    just install the rereleased SP1 on top and you should be able to install April CU.
    Cheers,
    Stefan

  23. Great post. Thank you.

  24. Hi Andy,
    it should be fine – but if nothing changes with future packages they will not install either as April CU does not create a different baseline.
    Cheers,
    Stefan

  25. HimuraCC says:

    Hi everyone!
    Same problem as Mike.

    I have Sharepoint Foundation 2013:
    –> version in "Program and Features" of Control Panel = 15.0.4569.1506
    –> version in "Check product and patch installation status" of Central Administration = 15.0.4571.1502

    April 2015 CU = the expected product is not detected
    Re-released SP1 = the expected product is not detected

    Language Packs = Italian at 15.0.4571.1502 (in Control Panel and in Central Administration), but I have also tried to remove it.

    Thank you very much.
    Regards.
    Alessandro

  26. Hi Alessandro,
    You are mixing patch level and patch baseline.
    The baseline on your system is 15.0.4569.1506 (old SP1).
    The patch level is 15.0.4571.1502.
    Based on the info above rereleased SP1 for you base language should install fine.
    Cheers,
    Stefan

  27. HimuraCC says:

    Thank you Stefan!

    I’ve tried several times to install Re-released SP1 (officeserversp2013-kb2880552-fullfile-x64-en-us), but it returns the message "The expected version of the product was not found on the system".

    I don’t know how I can solve this problem.

    Thank you for your support.
    Regards.
    Alessandro

  28. Hi Alessandro,
    En-us is the language you installed SharePoint with?
    In case you can’t solve it I would recommend to open a support case with Microsoft to see what is missing on your server.
    Cheers,
    Stefan

  29. Wes Niemi says:

    In working with Microsoft Support through a Support Ticket, we were able to get the appropriate SP1 version installed on my Development Farm. We created a snapshot of both of my virtual machines in case we ran into an issue and had to revert back. In our
    scenario, we did the following: 1. Uninstalled the Language packs. 2. Executed the SharePoint Products and Configuration Wizard. 3. Reapplied the correct version of SharePoint Server Service Pack 1 (rereleased version). 4. Executed the SharePoint Products
    and Configuration Wizard. 5. Applied the April 2015 CU. 6. Executed the SharePoint Products and Configuration Wizard. 7. Installed 3 language packs – the RTM version of each, not the Language Packs with SP1. 8. Executed the SharePoint Products and Configuration
    Wizard. Summary: In the end, everything seems to be working now. I have been testing and so far, no issues. Next up is to follow the same process for our Production Farm. One note: The Microsoft Support Engineer doesn’t think I need to uninstall the Language
    Packs in our Production environment…but I am going to anyhow…as this process worked for us. One final tip: I use a PowerShell Script that pauses the Search Service and shuts down IIS Processes which tremendously speeds up the installation of a Service
    Pack or a CU. I borrowed the script from here:
    http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx

  30. anonymouscommenter says:

    really dont understand why it is needed to patch the baseline, i mean couldnt this just be included in the CU ? it will double my install time (on 10 production boxes) which is already quite long (even with search paused/stopped) 🙁

  31. Hi Jasper,
    this is a concept of MSI installer.
    You always have a patch baseline for each product and a patch level.
    In general only service packs increase the patch baseline as they define whether a product is supported or not.
    So Microsoft defines the date when a service pack runs out of support and at that moment the patches no longer support the baseline for this service pack.
    It usually helps to guarantee that customers upgrade there systems to the supported level in time to ensure that they are not running unsupported systems.
    Cheers,
    Stefan

  32. anonymouscommenter says:

    how can i verify the patch baseline version number? i've tried looking at a few DLL's but these version numbers are at current patch level

  33. anonymouscommenter says:

    Are service packs going to continue to come out for sharepoint 2013?

  34. anonymouscommenter says:

    So, just to clarify. I have several SharePoint 2013 farms that were all installed using the slipstreamed ISO from MSDN. All of them have since had the November 2014 CU applied. Can I re-apply the correct SP1 even though a later CU is installed before attempting
    to install the April 2015 CU? If not, is my only option (other than reinstalling everything which I do not consider to be a real option) at this point to attempt to install the April 2015 CU with the PACKAGE.BYPASS.DETECTION.CHECK=1 switch?

  35. Hi Jonnny,
    yes just install SP1 on topm if a later CU is installed the installer will just correct the baseline but not update binaries or db schema.
    Cheers,
    Stefan

  36. Hi Jasper,
    there is a script out named roiscan.vbs (just Bing for it).
    It will give you that info.
    Cheers,
    Stefan

  37. anonymouscommenter says:

    I thought the whole purpose of releasing the slipstreamed version for a second time was to clear up errors such as this. So the fix is to go back and install another version of SP1 that has already been installed over a version that is STILL currently
    available for download on MSDN?

  38. Hi John,
    the slipstream version was not released a second time.
    Only the non-slipstream version was re-released.
    Cheers,
    Stefan

  39. anonymouscommenter says:

    Correct, so as of now you cannot install the April patches on the current version on MSDN. One farm has the baseline of 15.0.4571.1502 which allowed the patches to be installed (RTM + the good SP1) and another is 15.0.4569.1506 which is the current MSDN
    build which will not allow the patches to be installed. This makes no sense, I know it's SharePoint but this is even crazy for this product line.

  40. anonymouscommenter says:

    Hi Stefan – first i thought this is an "1st of April-joke" (after MarchPU, and the SP1-rerelease)

    But now i just came to a a Featurerequest for MSDN:
    "SharePoint 2013 with SP1 including Hotfixes"
    or should i open a case for this, so it can be routed to the Product-Group?
    (as there is now no version of SharePoint 2013 "out of the Box", patchable in a feasable ammount of time … )

    Thanks, Peter.

  41. anonymouscommenter says:

    Stefan, I have a server with the 15.0.4569.1506 build. When I run Windows Update, or MBSA, the April SharePoint security updates do not show up – the only SharePoint updates Windows Update lists are the KB2920730 and KB 2920763 non-security updates from
    February.
    On another server, build 15.0.4571.1502, the MS15-033 and MS15-036 security patches did show up in Windows Update. I'm wondering with the first server, what is preventing the April SharePoint security updates from appearing in Windows Updates?

    Thank you.

  42. Hi Erick,
    Windows Update only offers those fixes which apply to your system. My assumption is that these security fixes are not offered, as they only apply to a system which has a baseline of 15.0.4571.1502.
    Cheers,
    Stefan

  43. anonymouscommenter says:

    Thank you – so the upshot, at least for now, is that any administrator who has the SP1 slipstream build and who relies on Windows Update to see SharePoint security patches will not see the April 2015 patches? Will they become visible later? And will this
    condition hold for the succeeding months?

  44. Hi Erick,
    the issue including the questions you listed above is still in discussion.
    We hope to have an answer soon.
    Cheers,
    Stefan

  45. anonymouscommenter says:

    What's the story on installing SP1 over a later CU? Does it only change version numbers, or are there other artifacts?
    If I have SP1 slipstream with December 2014 CU and I apply SP1 Update on it, can I expect that no functionality will change, or should I fully test everything again?

    If I have two WFE servers, both with SP1 slipstream and Dec 2014 CU in one farm, can I first apply the SP1 Update (profilactically, to ease out future updates) on one of them, expect them to work together and update the other one at a later date (next weekend)?

  46. Hi Piotr,
    usually it means that only the patch baseline on the system is adjusted. No changes to files or db content.
    Cheers,
    Stefan

  47. anonymouscommenter says:

    Stefan – MS15-033 relates to the Word Automation Service, which I don't see in my service apps (https://technet.microsoft.com/en-us/library/hh487292.aspx); however, I do see "Microsoft
    Word Server" on my patch status page – is my server actually vulnerable?
    I want to eventually apply this and the MS15-036 patch, but I'm wondering if, at least with MS15-033, I can delay until it is re-released? This delay would be preferable to any potential destabilization a re-install of SP1 could cause.

  48. Hi Erick,
    sorry I don’t know all the details of the fix – so I cannot give you reliable advise here.
    Cheers,
    Stefan

  49. anonymouscommenter says:

    Stefan – thank you for all of your advice on this.

    Regards, Erick

  50. anonymouscommenter says:

    I deployed sp1 and then ran the april 2015 cu, failed sevral times, then suddenly started installing. Not sure why!
    Will let you know what happens when its on their

  51. anonymouscommenter says:

    Stefan,
    I'm in the same boat as Erick. My production SharePoint server is Window Server 2012 R2 so I had to install the slipstreamed SP1 SharePoint version, its baseline is 15.0.4569.1506. That server is not seeing MS15-033 and MS15-036 in Windows Updates. My development
    SharePoint server is Windows Server 2012 and I installed the non-slipstreamed SP1 version, its baseline is 15.0.4571.1502. That server did see MS15-033 and MS15-036 in Windows Updates and was able to install them. Reading through your blog it seems the reason
    the PUs aren't showing as needed on slipstreamed SP1 version is the same reason the CU can't be installed. I really don't want to have to go through re-installing the released SP1 in my production environment. My question is if/when SP2 comes out will that
    fix the issue of being able to install the PUs through Windows Update? And if so, do you know if there will be an SP2 or when? In the meantime if I want to install monthly PUs starting in April can I run the Windows Update patches with the baseline check 1
    option?
    Thanks.
    Cyndi

  52. Hi Cindi,
    we are working with the product group to see if we can find a solution for the issue without reinstalling SP1.
    If you need the fixes now you have to install SP1 rereleased version. If you are not in a hurry I would recommend to wait. Be aware that I cannot promise that there will be a solution – just that we are looking into it. In worst case you might have to install
    SP1 again.
    Cheers,
    Stefan

  53. anonymouscommenter says:

    Thanks Stefan. I will wait for now, and hope my server isn't compromised by my inability to install the PUs. 🙂

  54. anonymouscommenter says:

    Here is a summary of some news, Announcements and other interesting stuff. send out "randomly"

  55. anonymouscommenter says:

    Una vez más, y a la espera de que empiecen a aparecer las primeras noticias sobre SharePoint vNext, os

  56. anonymouscommenter says:

    Very informative. I hope the product team releases some fix. So in worst case if there is no fix for this and we have to install sp1 re release, will we have to install the re release service packs for language pack too?

    In my environment I have 3 Language Pack with SP1.

  57. Hi Iltaab,
    as I mentioned in the post: it applies also to all language packs.
    So you would need to install SP1 for each language pack as well.
    Cheers,
    Stefan

  58. anonymouscommenter says:

    Thanks for your reply Stefan. Any chance we can expect a fix for this to not install re release SP1 in the May CU that is due this month? Its a daunting task to install Service pack and SP for language packs as it involves lot of downtime for a production
    environment.

  59. anonymouscommenter says:

    This Month CU has been released with a full server packages, a.k.a. "Uber Packages" – so this

  60. anonymouscommenter says:

    Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

  61. anonymouscommenter says:

    Hi Stefan,

    Just found this thread… excellent information. Just wish we'd read this before completing our recent install. Our situation is below.

    We did a farm build based on the 2013 SP1 slipstream build available on MSDN. Have since installed the May 2015 CU on top of this with no errors.

    Config DB version is now showing as: 15.0.4719.1000

    Has MS fixed the issues reporting in the May CU? or will we still have issues with the SP1 that was slipstreamed into the build?

    Thanks,
    Bailes

  62. Hi Bailes,
    SP1 from the ISO never had a problem. Thats why it was not rereleased. And future CUs will also install fine on your system.
    So there is no remaining action on your side.
    Cheers,
    Stefan

  63. anonymouscommenter says:

    I have version 15.0.4701.1000 and get the error "The expected version of the product was not found on the system" when trying to run the new May 2015 CU for SP 2013. Your notes suggest I should be able to install this CU but I am not able to…do I need
    to reinstall SP1? I did not setup this server so I am not sure what patches were previously installed.

  64. anonymouscommenter says:

    I just ran a freshly downloaded SP1 again and this was the result. May 2015 CU appears to be working now, at least the files are extracting as expected.

    DisplayName : Microsoft SharePoint Server 2013
    DisplayVersion : 15.0.4571.1502

    DisplayName : Microsoft Office Professional Plus 2013
    DisplayVersion : 15.0.4569.1506

  65. anonymouscommenter says:

    We have the same issue and have a ticket opened with MS support. Our environment has both SharePoint and Project Server 2013 SP1 from volumn license installed. After installed
    https://support.microsoft.com/en-us/kb/3039780, ran PSconfig with -force command, I was not able to install April security patch (MS15-033 and MS15-036).

    I ran the ROIScan from your blog and here are the version numbers:

    In CA, servers in the farm page, Configuration DB version is 15.0.4719.1000
    The results from ROIScan shows the version is 15.0.4569.1506 (at the top of the report)

    Since I installed the SP and PS May CU, in CA, Manage Patch Status, I have Update for Microsoft Project Server 2013 (KB3039753) 64-Bit Edition installed and the version is 15.0.4719.1002

    All of the servers in the farm shows no action needed in the Serevrs in the Farm page. All databases are also No Actions Needed in the Database status page.

    So, what did I do wrongor I need to install the SP only May CU?

    Thanks.

  66. Hi Wen,
    15.0.4569.1506 baseline is the old SP1 baseline. You cannot install April CU or PU on this baseline.
    But you already have May CU installed – so instaling fixes from April does not make sense (and is not possible) as May CU include the April fixes.
    Cheers,
    Stefan

  67. anonymouscommenter says:

    Stefan,

    Thanks for your help.

    I would like to confrim two things:

    1. May CU includes MS15-033 and MS15-036 for SharePOint 2013, correct?

    2. After May CU, I should be able to install future security patches (I don't install CU unless needed) without running into this version issue?

    Thank you again and have a good weekend.

  68. Hi Wen,
    1) confirmed.
    2) correct
    Cheers,
    Stefan

  69. anonymouscommenter says:

    Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

  70. anonymouscommenter says:

    I am currently running 15.0.4569.1506. Do I still have to install 15.0.4719.1000 over top of the regressed installation or can I just install the May CU?

  71. Hi John,
    please read the bright yellow part at the bottom of my article. 😉
    Cheers,
    Stefan

  72. anonymouscommenter says:

    Thank you. I wasn't totally sure if I was reading that correctly.

    Does that statement apply to the June 2015 update as well?

    Do you also know if that applies to the most recent Office Web Apps Server updates or do I still need to apply Patched SP1 > April 2014 PU > May 2014 PU > June 2014 CU > Current Update per the following post:

    http://blogs.technet.com/b/office_web_apps_server_2013_support_blog/archive/2014/06/05/how-to-ensure-you-39-re-using-the-patched-version-of-sp1-for-office-web-apps-server-2013.aspx

  73. Hi John,
    sorry – I’m not sure about WAC. It is supported by a different team.
    Cheers,
    Stefan

  74. Hi John,
    I double checked: the patch baseline for the WAC components now also includes 15.0.4569.1506 and 15.0.4571.1502.
    Cheers,
    Stefan

  75. anonymouscommenter says:

    Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

  76. anonymouscommenter says:

    Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

  77. anonymouscommenter says:

    Hi Stefan,

    Im working on this issue for 2 days now and while googling I always end up in here, so lets ask.
    I wanted to add another server to my dev farm (using the msdn license)
    Tried a fresh install but I always get stuck at CU April (and may)
    My current farm is @ May CU.

    I read something about running the Config wizard, but that won't run when you try to add a server to the farm which is not at the same version.

    I can install -> SP2013 +SP1 (msdn) -> install SP1 download -> FEB cu, march cu and then it stops.

    Is there another way to get the server at a particular patch level to join to an existing farm?

    Thnx for the info so far!

    Kind regards,
    Lennard

  78. Hi Lennard,
    your steps look good and should work. Did you install any language packs or just the base language of the product?
    In case of language packs you also have to install SP1 for each language pack.
    Cheers,
    Stefan

  79. anonymouscommenter says:

    Hi Stefan,

    Well… I read it, checked it twice and probably fucked up somewhere on the language pack issue. Was quite sure I got the right one. But after uninstalling the language pack it lets me installing the may cu.
    So at the end, its always me who's wrong 🙂
    Afterwards will try the languagepack with SP1 again.
    Thnx for the helpful posts!

  80. Hi Lennard,
    be sure to install May CU again after installing the language pack. Otherwise the language pack will not be on the same patch level as the rest of your installation.
    Cheers,
    Stefan

  81. Ashraf says:

    Hi Stefan,
    I have the baseline 15.0.4571.1502 on my farm but still can not install the April 2015 CU KB2965266, I mean I still get the error message “The expected version of the product was not found on your system”. I have even tried to install the Language Packs SP1 but I got errors.
    Have you any idea about the issue?

    Thanks in advance
    //Ashraf

    1. Hi Ashraf,

      please run the script in this blog and post the result as comment here to allow me to see the exact baselines:
      http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx

      Thanks,
      Stefan

      1. Ashraf says:

        Hi Stefan,
        I ran your script and got the following:

        DisplayName : Microsoft SharePoint Server 2013
        DisplayVersion : 15.0.4571.1502

        DisplayName : Language Pack for SharePoint and Project Server 2013 – Danish/dansk
        DisplayVersion : 15.0.4571.1502

        DisplayName : Language Pack for SharePoint and Project Server 2013 – Finnish/suomi
        DisplayVersion : 15.0.4569.1506

        DisplayName : Language Pack for SharePoint and Project Server 2013 – Norwegian/norsk
        DisplayVersion : 15.0.4433.1507

        DisplayName : Language Pack for SharePoint and Project Server 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017

        I hope this helps.

        Regards
        //Ashraf

        1. Sure it helps!
          Only the base product and the danish language is on 15.0.4571.1502.
          Finish, Norwegian and Swedish language packs are below that patch baseline.

          Download and install the SP1 for these language packs from here and install them:
          http://www.microsoft.com/en-us/download/details.aspx?id=42543

          That will ensure that the patch baseline for all parts of the product is correct.

          Cheers,
          Stefan

          1. Ashraf says:

            Sorry, but I still get the same result after installing SP1 for the langauges above on Webapp. This is the result:

            DisplayName : Microsoft SharePoint Server 2013
            DisplayVersion : 15.0.4571.1502

            DisplayName : Language Pack for SharePoint and Project Server 2013 – Danish/dansk
            DisplayVersion : 15.0.4571.1502

            DisplayName : Language Pack for SharePoint and Project Server 2013 – Finnish/suomi
            DisplayVersion : 15.0.4569.1506

            DisplayName : Language Pack for SharePoint and Project Server 2013 – Norwegian/norsk
            DisplayVersion : 15.0.4433.1507

            DisplayName : Language Pack for SharePoint and Project Server 2013 – Swedish/svenska
            DisplayVersion : 15.0.4420.1017

            I ran the SP1 on the webserver and got the problem
            Service Pack 1 for Microsoft SharePoint Server 2013 Language Pack (KB2880554) 64-Bit Edition (15.0.4571.1502)
            Missing on ONEMLMAPP121
            when I tried to run PSConfig.

            Regards
            //Ashraf

          2. Ok, if the versions did not change, then SP1 for these language packs has not been installed.
            You need to go to the site I sent earlier, select the language of the language pack to update, wait for the redirect to happen and then download it. This has to be done for each labguage pack. In your case you need 3 downloads.
            Then you have to install these on all servers in the farm before running psconfig.

          3. Ashraf says:

            Hi Stefan,
            Thanks a lot for your time and effort, I really appreciate it 🙂
            I have downloaded and installed the 3 language packs for finish, Norwegian and Swedish all at the same time on the appserver. Did the same at the webserver and then ran PSConfig on the appserver. The result was: Finish, Norwegian and Swedish Missing on ONEMLMAPP120.
            I ran psconfig -cmd installcheck -noinstallcheck to fix this problem but got an error.
            May be I have mention that after installation of SP1 for SharePoint I have installed the follwing CU:
            – KB 2878240
            -KB 2881061
            -KB 2882989
            – then jumped over to the CU KB 2920804 and installed it.
            – then I installed KB 2956166
            – and finally I got problem when I tried to install KB2965266 April 2015. I mean the main problem “the expected version could not be found on your system”

            Do you think there is any issue to do so? I mean if it’s ok to jump to next CU when upgrading SharePoint or you have to take them one by one without missing any of them?
            I have the possibility to revert the farm to the origin state with only SP1 installed.
            If I revert it should I start with Language Packs SP1 or with CU one by one?
            Yes, I now many many questions but I really hope you have the time and desire to help me with it.

            Regards
            //Ashraf

          4. The sequence of the fixes does not matter.
            I would recommend to open a support case with Microsoft to speed up the solution for this issue.

            Cheers,
            Stefan

  82. Hi Stefan, we had the same error (The expected version of the product was not found on the system) as Wes but for the April 2016 CU coming from SP1 (re-release), with Arabic and Chinese (Simplified) language packs (also at SP1). After removing the language packs, the CU applied successfully. Just posting for others who might have this problem. Thanks both!

    1. Hi Patrick,
      that means that you did not install SP1 for for these language packs before installing April 2016 CU.
      When reinstalling the language packs you have to install April CU again – otherwise these language packs will not be updated to April CU and you have an inconsistent patch level.
      Cheers,
      Stefan

  83. Anand says:

    Hi Stefan,

    Please find the below details:

    Config DB Version:15.0.4569.1000

    Two of my servers in the farm showing “Installation Required” and one server is showing “Upgrade Blocked”

    If I click on Installation required then it showing following details:

    Microsoft Access Services Danish Language Pack 15.0.4433.1507 Installed
    Security Update for Microsoft SharePoint Enterprise Server 2013 (KB2956180) 64-Bit Edition 15.0.4701.1000 Missing/Required

    Microsoft Document Lifecycle Components Danish Language Pack 15.0.4433.1507 Installed
    Security Update for Microsoft SharePoint Enterprise Server 2013 (KB2956153) 64-Bit Edition 15.0.4701.1000 Missing/Required

    Like this it showing for difference language pack(The same error in both server- Error in one App and one Front end server) but the other server is upto date and there is not error when I checked in patch status page.

    Can you please help what has been missing from these 2 servers and what action do I need to take to make all servers in the farm same.

    Regards
    Anand

    1. Hi Anand,
      might be that the installation info in the config db is not updated correctly.
      Please try the powershell commmand “Get-SPProduct -local” on each machine where a missing fix is reported and check again.

      See here for details:
      https://blogs.technet.microsoft.com/stefan_gossner/2016/08/09/sharepoint-patching-and-get-spproduct-local/
      Cheers,
      Stefan

      1. Anand says:

        Thanks Stefan for your response.

        Before running the Get-SPLocal-Product I referred your another blog entry which helped me to get all the details about the sharepoint server and below is the output from the script

        WFE SERVER

        DisplayName : Microsoft SharePoint Server 2013
        DisplayVersion : 15.0.4569.1506
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Danish/dansk
        DisplayVersion : 15.0.4420.1017
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Finnish/suomi
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Norwegian/norsk
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017
        DisplayName : Microsoft SharePoint Designer 2013
        DisplayVersion : 15.0.4569.1506
        DisplayName : Language Pack for SharePoint Foundation 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017

        APP1 SERVER

        DisplayName : Microsoft SharePoint Server 2013
        DisplayVersion : 15.0.4569.1506
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Danish/dansk
        DisplayVersion : 15.0.4420.1017
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Finnish/suomi
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Norwegian/norsk
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017
        DisplayName : Language Pack for SharePoint Foundation 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017

        APP2 SERVER

        DisplayName : Microsoft SharePoint Server 2013
        DisplayVersion : 15.0.4569.1506
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Danish/dansk
        DisplayVersion : 15.0.4420.1017
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Finnish/suomi
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Norwegian/norsk
        DisplayVersion : 15.0.4433.1507
        DisplayName : Language Pack for SharePoint and Project Server 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017
        DisplayName : Language Pack for SharePoint Foundation 2013 – Swedish/svenska
        DisplayVersion : 15.0.4420.1017

        Do you any other suggestion or shall I go ahead and run the “Get-SPLocal-Product” script.

        Regards
        Anand

        1. Hi Anand,
          this seems to be the patch baseline – not the patch level.
          Which script did you run?
          Thanks,
          Stefan

          1. Ok, thats what I thought. This script reports the patch baseline – not the patch level.
            But the conflict you get reported is about the patch level.
            Get-SPProduct -local will ensure that the patch level info stored in the config DB is in sync with the MSI information for the server you run it on.

            Cheers,
            Stefan

  84. Chaitanya says:

    Hi Stefan,
    I’m trying to install KB3141481 on Sharepoint Server 2013 sp1 (15.0.4571.1502) is giving me error below:
    ‘The expected version of the product was not found on the system’
    What could be the correct KB to install?

    1. This is the correct KB.
      Did you install any language packs? Might be that one of the language packs is missing the service pack.
      Please run the following script to double check:
      https://blogs.technet.microsoft.com/stefan_gossner/2015/04/20/powershell-script-to-display-version-info-for-installed-sharepoint-product-and-language-packs/

Skip to main content