SharePoint security fixes released with October 2017 PU and offered through Microsoft Update

12 Comments

1. 

   Sajid Ali
   On 17. October 2017 Permalink

   Hi Stefan,
   After installing these SharePoint 2013 server PU, do we need to run the configuration wizard?
   Thank You
   Sajid

   Reply
   1. 

      Stefan Goßner
      On 18. October 2017 Permalink

      Hi Sajid,
      as there is not a single SharePoint fix which would not require the config wizard.
      So: yes.
      Cheers,
      Stefan

      Reply
2. 

   Michael Heuer
   On 17. October 2017 Permalink

   Hi Stefan,
   my post is 100% in the wrong category, even it’s the same product. Did you recognize any problems with SharePoint 2013 (version doesn’t matter) after that patch day?
   I got issues when I navigated in the Central Administration on “Create new SiteCollection”.
   The error I got is:
   “Sorry, something went wrong
   Common Language Runtime detected an invalid program.”
   With SharePoint 2010, this issue is not coming up, so i guess it could have something to do with .NET.
   Thanks in advance for your answer.
   Cheers,
   Michael

   Reply
   1. 

      Stefan Goßner
      On 18. October 2017 Permalink

      Hi Michael,
      haven’t seen this. The error indicates that there is a dll with corrupted content.
      Would be important to isolate which dll this is.
      Cheers,
      Stefan

      Reply
   2. 

      Ken
      On 25. October 2017 Permalink

      We are encountering the same issue after applying the security updates. The createsite.aspx page throws “Sorry Something Went Wrong” and “Common Language Runtime detected an invalid program” error. This is on a SharePoint 2013 Foundation farm that previously worked fine.

      Reply
      1. 

         Stefan Goßner
         On 25. October 2017 Permalink

         Hi Ken,
         in this case I would recommend to open a support case with Microsoft to get this analyzed.
         Cheers,
         Stefan

         Reply
         1. 

            Ken
            On 27. October 2017 Permalink

            More info:
            https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/

            Reply
   3. 

      Wei Chen
      On 8. November 2017 Permalink

      Same issue after Oct 2017 CU cannot create site collection!

      Reply
3. 

   Dominick
   On 24. October 2017 Permalink

   Hi Stefan
   Any advice on what to install to stay “supported”
   Based on this I would need to install the April 2017 PU at a minimum
   What would MS be looking for when a user calls premier support?
   Would not having the April 2017 PU keep new patches from being installed
   “https://technet.microsoft.com/library/684173bb-e90a-4eb7-b268-b8d7458bc802(v=office.16).aspx”

   Reply
   1. 

      Stefan Goßner
      On 25. October 2017 Permalink

      Hi Dominick,
      after April 2017 only security fixes will created – no regular CUs as regular CUs are only created during mainstream support.
      Newer security fixes should also install on older CUs but if you are in a need to get support from Microsoft and you are on an older CU you will have to apply one of the supported CUs first.
      Cheers,
      Stefan

      Reply
4. 

   Manoj
   On 7. December 2017 Permalink

   Hi ,
   Can someone please confirm do we need to run the ps.config after installing •KB 3213623 – Word Automation Services for SharePoint 2010
   •KB 4011194

   Reply
   1. 

      Stefan Goßner
      On 7. December 2017 Permalink

      Hi Manoj,
      there is not a single SharePoint fix which would not require psconfig.
      Cheers,
      Stefan

      Reply