Solution for the list view issue with MS16-004 (January 2016 PU) for SharePoint 2013


Several people ran into the issue that list views stop working after installing MS16-004.

The security fix contains a code change which requires as well an update to the not localized and to the localized files of the SharePoint foundation component. Localized and not localized file are installed through two different msp files and the security fix package does not include the localized msp file.

If you are looking for a minimal change to resolve the issue it you can just install the following fix which contains the missing msp file containing the localized files:

KB 3114508 – Download location: https://www.microsoft.com/en-us/download/details.aspx?id=50667

Alternatively you can install the full server package of January 2016 CU for SharePoint 2013 which also includes the required msp file.

[Update – January 25th, 2016] A couple of customers reported that the fix from 3114508 does not install or that the issue still occurs after installing it for some languages. Our analysis shows that in each of these cases SP1 was missing – either for the core product or for one of the language packs. You can use the following script to verify the patch baseline (means the installed service pack level): http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx


Comments (72)

  1. Tim B says:

    Good Afternoon,

    I was wondering if anything has been said about providing a version of this security patch that contains all the needed msp’s so that list view functionality isn’t lost after applying this patch?

    Thanks!

    1. Hi Tim,
      I don’t have information on that.
      Cheers,
      Stefan

  2. Hi Stefan,

    Thank you Sir!. This post saves us from a ton of work and end-user outages. Thanks once again!

    Cheers,
    AG

  3. Gregg says:

    Howdy!
    This has my SharePoint service back up and running normally again.
    Thank you very much for the information.

  4. Eystein says:

    Too bad this fix only works on English language sharepoint installations

    1. Hi Eystein,
      I tested with english (1033), german (1031), portuguese (2070) and french (1036) and it worked on all of them.
      Should be as the fix contains the msps for all language packs.
      Cheers,
      Stefan

      1. Eystein says:

        Does this work on the Server also, or just on the Foundation version? My install is the Server version i Norwegian language.

        1. Hi Eystein,
          this solution works on foundation and on server.
          Cheers,
          Stefan

  5. itsas says:

    Hi,

    I tried to install it too. But I have the following error : “the expected version of the product was not found on the system”
    My server is a Windows server 2012 FR and SharePoint foundation 2013 English version with french language pack.

    If you have an idea

    Thanks

    1. Hi Itsas,
      sounds as if SP1 for the language pack is not installed.
      Please double check.
      Cheers,
      Stefan

      1. itsas says:

        You speak about KB2880555 ?

        If it is, it doesn’t installed,

        Thanks for your answer

        1. You have SharePoint foundation? Not SharePoint server?
          Then yes. For SharePoint server you need this:
          http://www.microsoft.com/en-us/download/details.aspx?id=42543

  6. Ron says:

    Hi,

    After install of Jan 2016 CU the error is still there. We use the Dutch language pack, what can we do?

    Cheers,
    Ron

    1. Ron says:

      When I create a site in English it works, so it the fix is not solved for the Dutch language pack.

      1. Hi Ron,
        I would recommend to open a support case to get your specific issue analyzed.
        Cheers,
        Stefan

        1. Ron says:

          Hi Stefan,

          Thanks for the answer. I see that you did tests on english (1033), german (1031), portuguese (2070) and french (1036). Can you also try this on Dutch (1043)?

          Thanks,
          Ron

          1. Hi Ron,
            sorry I’m out of office this week and cannot do these tests.
            Cheers,
            Stefan

        2. Ron says:

          Our language pack was not on 2013 SP1 yet so maybe this is the problem? What is the best way to update the language pack?

          Thanks,
          Ron

          1. Hi Ron,
            Yes, that would explain it.
            Without SP1 the system is in an unsupported state and current fixes will not install correctly.
            Cheers,
            Stefan

  7. Jason Soh says:

    Hi Stefan,

    Any idea when will Microsoft be releasing the revised patch for MS16-004?

    Regards,
    Jason

    1. Hi Jason,
      from what I know there is no plan to release a revised version.
      Cheers,
      Stefan

  8. Thank you Stefan for this, it was extremely helpful. Thank you for your effort and work in providing this blog and for explaining the updates with SharePoint. I enjoy reading it and the information is extremely valuable and helpful as a SharePoint Administrator! Thank you for your effort and work in making this a powerful and informative blog!

  9. Danny Garland says:

    This is great, it fixed the issue. HOWEVER, it did have another undesirable effect. It changed all my lists across my sites wherever I had a view with just “linked to Item” rather than a “link to item with edit menu” it changed it so that all my views everywhere are “link to item with edit menu”!!!! I now have to go through them all and fix views where I didn’t want the edit menu……

    Anyone else experience this?

  10. TD says:

    Can you install both, 3114503 and 3114508, before running psconfig?

  11. Ben says:

    Hi Stefan,

    After installing 3114508 it fixed the view issue and I’m able to see the existing data. The remaining issue when I try to create new item in a SharePoint Link list, after I filled the new form and try to save it, it display the message that there is a mandatory field must be filled? is there another patch to fix this problem? Note this problem do not exist in my QA farm it is only on my production farm

    Thanks!

    1. Hi Ben,
      I haven’t heard about this issue. I would recommend to open a support case with Microsoft to get this analyzed.
      Cheers,
      Stefan

  12. Adrian says:

    After installing January 2016 CU for SharePoint 2013, I noticed that the Follow site functionality stopped working. I wonder if there are other users experienced it after the install. Im getting the below error message:

    Something went wrong

    Sorry, we couldn’t follow the site.

    Technical Details

    InternalError : Could not find item http://

    1. Hi Adrian,
      is this a multi-farm environment or follow site within a single farm?
      Cheers,
      Stefan

      1. Adrian says:

        Yes, it is a multi farm environment. We have a separate farm for Service Apps. Same with the content farm, the Service apps farm is also in Jan CU.

        1. Ok, thanks. That is an issue which was introduced with September CU – not with January 2016 CU.
          The fix is currently planned to be included in February 2016 CU.

          1. Adrian says:

            Thank you so much for the response, Stefan. I have been looking the whole weekend on what could be the issue in all of our farms on why it is not running. I will just wait for Feb CU.

          2. Hi Adrian,
            I would recommend to open a support case with Microsoft to ensure that you get the latest updates about the scheduling of the fix.
            Cheers,
            Stefan

          3. Adrian says:

            Thanks again, Stefan. I will do your recommendation, will open a support case with Microsoft.
            On the other hand, below is the exact error that I am getting:

            Line 470: 01/25/2016 06:25:48.93 w3wp.exe (0x27284) 0x26460 SharePoint Foundation CSOM agmjp High Original error: Microsoft.Office.Server.UserProfiles.FollowedContentException: InternalError : Could not find item http://mylocalsite.home at Microsoft.Office.Server.UserProfiles.FollowedContent.RefreshFollowedItem(FollowedItem item, SPS2SAppExecutionPolicy policy) at Microsoft.Office.Server.UserProfiles.FollowedContent.Follow(Uri url, FollowedItemData data) at Microsoft.Office.Server.UserProfiles.FollowedContentServerStub.InvokeMethod(Object target, String methodName, XmlNodeList xmlargs, ProxyContext proxyContext, Boolean& isVoid) at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, XmlNodeList args, ProxyContext proxyContext, Boolean& isVoid) c2ae589d-c43d-70bb-ccee-37b903b14b84

  13. DeWi11 says:

    It is necessary to run psconfig after the installation of this fix?

    1. You should run the SharePoint Configuration Wizard (psconfigui.exe or psconfig.exe with the correct parameters) after all SharePoint fixes.
      See here for details:
      https://blogs.technet.microsoft.com/stefan_gossner/2015/09/09/why-we-recommend-require-to-run-the-configuration-wizard-also-for-security-fixes/

  14. Annoyed IT GUY says:

    Why are you deploying security updates through WSUS if they are not tested? First the security updates brake search crawl, then I run command Psconfig -cmd secureresources to fix the issue and in microsoft support article it does not say it will also upgrade databases and take whole sharepoint site down while doing it. Then this list issue and now I HAVE to upgrade to January 2016 CU to fix the issue and no way can test it before deploying it cause already have the security updates in that come automatically from WSUS. If you push deploy stuff from wsus make sure it works just by pushing update now from wsus, cause no where I can go read all the articles from wsus that if there are some extra commands to be run.

      1. Hi Jussi,
        you can easily avoid this by switching from Microsoft Update to Windows Update.
        If you have chosen Microsoft update then you asked to get security fixes also for other products but Windows.
        And you cannot expect Microsoft to no longer ship security fixes for SharePoint.
        Cheers,
        Stefan

  15. Romain says:

    Hello Stefan,

    I have a question about issues with another update, this time client-side :
    Please, would you have any informations about client Office 2010 KB3101521 (and following on MSO.DLL) that breaks SharePoint Workspace 2010 sync ?
    This problem affects us since some weeks, and the ticket opened to our workstation support team hasn’t give any solutions until now (except uninstalling the KB)

    More information about this problem here :
    http://answers.microsoft.com/en-us/office/forum/office_2010-office_install/november-2015-critical-security-office-update/3f88c1a4-235a-4691-8b23-7b572e28d012/?rtAction=1450340419509

    Thank you if you have some information, and sorry for the quite off-topic question if not 😉

    1. Hi Romain,
      sorry – office client products are supported by a different team and I don’t have the relevant information available.
      Cheers,
      Stefan

  16. Matt says:

    Experiencing a different issue after patching. I am getting a 40 forbidden when loading /_layouts/15/sp.js.

    This occurs sporadically, and will sometimes work on IE and not Chrome and vice versa.

  17. Edson Catugy says:

    Worked perfectly for me, thanks Stefan Goßner!

  18. HI,
    We have SharePoint 2013 SP1 + April 2014 CU (15.0.4617.1000) and we have to plan configure January 2016 CU. Please let me know if we Patch directly form April 2014 CU to January 2016 CU

    1. Yes you can directly go to Jan 2016 CU.

  19. john says:

    my farm build number was 15.0.4763.1000 with SP1, and we start facing this problem after our system admin install the MS16-004 on SharePoint server. so i download and install the KB 3114508 . and the list views worked well. then to make sure that the KB 3114508 is intalled successfully , i run the product configuration wizard, which failed on step 8 of 9 .. so i restarted the server, but now when i try accessing the site collections i am getting blank pages , and if i try to check the site collection from my central administration, i found that the site collections info such as site collection administrator,url , etc are not showing … can anyone adivce on this?

    1. Did you run PSCONFIG again after restarting the server? You stated that the last 2 steps (8 and 9) have not been completed. So your system is in a limbo state till PSCONFIG is completely done.

      1. john says:

        yes i tried running it again ,, but it failed at the same stage..

        1. Then I would recommend to open a support case with Microsoft.

          1. john says:

            i wrote a question on MSDN regarding this ? but meanwhile do u recommend if i try installing the latest CU for SharePoint which is January 2013 from https://support.microsoft.com/en-us/kb/3114497 ??? as in my case i only install the hotfix KB 3114508 and i was on October CU 2015 ??

          2. Hi John,

            I don’t understand your question. If you were on October CU then there was no need for 3114508. Or did you install some security fixes after October CU?
            Then you can either install just 3114508 or the complete January 2016 CU. Whatever you prefer.

            Cheers,
            Stefan

          3. john says:

            no the KB-3114508 is a January update as mentioned in this link:- https://support.microsoft.com/en-us/kb/3114508 … so i am not sure i understand your point of saying “If you were on October CU then there was no need for 3114508”?? now we have installed some security updates last week , where MS16-004 was part of them,, and caused the list views to stop working.. so i installed the https://support.microsoft.com/en-us/kb/3114508 ?? could the problem is that i have SharePoint server while the update is for SharePoint foundation ?.

          4. Ok, so you were not on October CU but on October CU + some post October CU security fixes. Got it.
            As outlined before you can either install 3114508 or the complete January 2016 CU to fix the list view issue.
            Whatever you prefer.
            You can always install foundation fixes on SharePoint server as SharePoint foundation is part of SharePoint server – so that will not cause any issues.
            For your PSCONFIG issues I would recommend to open a support case with Microsoft.

          5. john says:

            @Stefan
            yes i installed the 3114508 , and after that the list views start working well. but to make sure that the 3114508 is installed correctly , i run the product configuration wizard , which failed on task 8 of 9 … but the problem now is that when i try accessing my sites i will get blank pages,, and when i try to check my site collections from “Central administration >> view all site collections”.. i can see the site collection, but the section which should list the site collection info such as site collection admin, url, content database is not showing .. here is the problem i wrote on msdn https://social.technet.microsoft.com/Forums/office/en-US/56d2596b-7454-4dc6-86d2-9e4d798de5a7/sharepoint-server-2013s-site-collections-are-showing-blank-web-pages-after-i-appl-y-a-hot-fix-kb?forum=sharepointadmin#56d2596b-7454-4dc6-86d2-9e4d798de5a7 ..thanks

          6. Again: open a support case.

  20. Kris says:

    Hi Stefan,

    We have one of those environments you wrote about in your update. After installing the fix from 3114508, we still had the list view problem. So yes, after checking we noticed we were on the old SP1 baseline. I’ve (re-)installed SP1 and we are now on the new SP1 baseline but unfortunately the problem is still occurring and now I cannot uninstall and/or reinstall the 3114508 fix (uninstalling is not possible and re-installing does not work since it is already installed).
    Is there any way out of this, or is my only option installing the Feb 2016 CU (and will that give a solution)?

    Regards,
    Kris

    1. Hi Kris,
      for 3114508 it does not matter if the old or the new SP1 has been installed – both would be fine.
      Only if your language pack is on a patch baseline older than SP1 (e.g. RTM or March 2013 PU) 3114508 would not fix the issue.
      So if you still have the issue you should open a support case with Microsoft to get this issue analyzed.
      Cheers,
      Stefan

      1. Kris says:

        Ok, I will do so.
        Thanks for the swift reply.

        Regards,
        Kris

  21. Bernhard says:

    For me the following worked (SharePoint 2013 Foundation, german language pack)

    -> making sure, SP1 was there kb2880551
    -> KB2880555 (!!)
    -> KB3114508

    1. 2880555 should only be used for SharePoint foundation.
      2880552 is the package for SharePoint server.

  22. Tim B2 says:

    Dear Stephan,

    KB3114508 & 3114503 gave some issues with the list view, this had been solved with the February 2016CU.

    we see another strange issue, when opening a SharePoint file in Word/Excel 2013 you can’t scroll in de document library when saving.
    Others are saying the same.
    http://www.networksteve.com/exchange/topic.php/Microsoft_Office_(Word/Excel)_Save/Open_Window_not_showing_Scrol/?TopicId=65154&Posts=1

    we’ll try in the next couple of days to see if March 2016 CU is better.

    we’re running SP2013 Foundation.

    regards
    Tim

    1. Hi Tim,
      ensure to open a support case if you need this issue investigated.
      Cheers,
      Stefan

      1. Tim B2 says:

        Hi,

        march Cu didn’t solved the issue.
        fromout of Word/excel/… save as has no scroll bar when accessing SharePoint through the URL.
        if we use WebDAV, it works correctly.

        I support Microsoft is aware of the issue, because we’re not the only one with the problem.
        https://social.technet.microsoft.com/Forums/sharepoint/en-US/d0c3de61-46fb-42b4-a46a-93a0cff2c00d/microsoft-office-wordexcel-saveopen-window-not-showing-scrollbar-for-sharepoint-sites?forum=sharepointgeneral

        hopefully this will be solved in a next CU.

        regards,
        Tim

        1. Hi Tim,
          this issue was reported to the product group on March 30th (several weeks after March CU was released) and is currently under investigation.
          We don’t have a timeline for a fix right now. It is always recommended to open a support ticket if you run into a problem as reporting something in a forum will not trigger hotfix request creation.
          Cheers,
          Stefan

  23. Kannan says:

    How microsoft missed this msp file? It seems to be a simple use case for testing.

  24. Ritu says:

    Hi Steve,
    We are currently on SharePoint 2013 on-prem integrated environment with Enterprise license. Currently, we are on May 2015 CU(15.0.4719.1002). Can we apply May 2016 CU (15.0.4823.1003) without installing other CU’s? Would we need both Foundation and Server package or need only Server package?
    Also, would that include all the security updates till date?
    Thanks so much

    1. Yes, you can directly apply May 2016 CU. Of Course this includes all Security fixes up to May 2016.
      Server packages include foundation packages. No need to apply both.

  25. Chuck Atkinson says:

    We are working on a new install of 2013 and are having a list view issue. Search points to this fix, but we have applied monthly CU’s February, March, April. Wouldn’t the fix have been in one of those updates?
    Thanks

    1. Hi Chuck,
      thats correct. Sounds to me as if you ran into a different issue.
      Cheers,
      Stefan

      1. Chris Cundy says:

        Hi Stefan,
        I have the problem with list views on SharePoint Server 2013 15.0.4571.1502
        I also have KB3114938 (April 2016)

        What update do you suggest using that would resolve this issue? As the previous fixes applied to using a January update however that cannot be done when the issue is present with the April 2016 update.

        Thanks.

  26. Chris Cundy says:

    Hi Stefan,
    I have the problem with list views on SharePoint Server 2013 15.0.4571.1502
    I also have KB3114938 (April 2016)

    What update do you suggest using that would resolve this issue? As the previous fixes applied to using a January update however that cannot be done when the issue is present with the April 2016 update.

    Thanks.

Skip to main content