October 2017 CU for SharePoint 2013 product family is available for download

26 Comments

1. 

   Brad
   On 17. October 2017 Permalink

   Hi Stefan,
   I’m working through applying the October Cumulative updates for SharePoint and in both my SharePoint Farms I am seeing bizarre issues. On one I am consistently receiving the error below, I’ve tried a bunch of the suggestion on the web with no luck. Any thoughts on this, I’ve never had an issue like this applying updates.
   An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
   Upgrade [SPContentDatabase Name=SP2013DEV_CONTENT] failed. (EventID:ajxnm)
   Exception: Object reference not set to an instance of an object. (EventID:ajxnm)
   (EventID:ajxnm)
   (EventID:ajxnm)
   Upgrade Timer job is exiting due to exception: System.NullReferenceException: Object reference not set to an instance of an object.
   … (EventID:aj0ur)

   Reply
   1. 

      Stefan Goßner
      On 18. October 2017 Permalink

      Hi Brad,
      if you need assistance to analyze the issue ensure to open a ticket with Microsoft Support.
      Cheers,
      Stefan

      Reply
2. 

   Andreas
   On 20. October 2017 Permalink

   Hi Brad,
   starting the following services at “configurationtask 8” of “SharePoint Products Configuration Wizard” solved the problem for me.
   $foo = get-service “SPTimerV4”
   $foo.start()
   $bar = get-service “IISSVCS”
   $bar.start()

   Reply
   1. 

      Brad
      On 23. October 2017 Permalink

      Hi Andreas,
      Yep that’s what did it for me after many hours of reading. Thanks for the tip.

      Reply
3. 

   iamgeorgem
   On 21. October 2017 Permalink

   Hi Stefan, which Sharepoint 2013 CU will support SP4 for SQL 2012?

   Reply
   1. 

      Stefan Goßner
      On 23. October 2017 Permalink

      There is no specific CU required.

      Reply
4. 

   Jatin
   On 26. October 2017 Permalink

   Hi Stefan,
   After installing this CU we are unable to create any sites. This issue is also mentioned at http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346 that multiple people have had this issue.
   The error is
   Application error when access /_layouts/15/newsbweb.aspx, Error=Common Language Runtime detected an invalid program.
   at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
   at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) e041269e-de3e-802d-746e-7d3742eb2725
   System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
   at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) e041269e-de3e-802d-746e-7d3742eb2725
   Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.InvalidProgramException: Common Language Runtime detected an invalid program.
   at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
   at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.HandleError(Exception e)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) e041269e-de3e-802d-746e-7d3742eb2725
   Cheers
   Jatin

   Reply
   1. 

      Jatin
      On 26. October 2017 Permalink

      Link is http://www.toddklindt.com/blog/Regressions/sp2013Oct2017.aspx

      Reply
      1. 

         Stefan Goßner
         On 26. October 2017 Permalink

         Hi Jatin,
         please ensure to open a support ticket for this to request a fix.
         Cheers,
         Stefan

         Reply
   2. 

      Tim B
      On 27. October 2017 Permalink

      Sounds like this is an issue with just Foundation: https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/
      Standard, Enterprise, and Project builds aren’t experiencing the problems.

      Reply
   3. 

      Prasad
      On 29. October 2017 Permalink

      I’m seeing this issue as well – cannot create sites anymore. More reports of this issue:
      https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/

      Reply
5. 

   John
   On 27. October 2017 Permalink

   Hi Stefan,
   I couldn’t help but notice that with this CU the size of ubersrv_2.cab suddenly dropped to 277.9 MB, after staying in a range of 335 to 340 MB for the previous year of updates. That was a real red flag for me! Where these are cumulative, I always assumed the CAB files would stay around the same size or grow in size from month to month.

   Reply
   1. 

      Stefan Goßner
      On 27. October 2017 Permalink

      Hi John,
      everything is fine here!
      The packaging team identified some packages being included in our previous CUs which contained fixes which were released between RTM and SP1. As our patches can only be installed on SP1 the packaging team decided to remove the additional unnecessary packages.
      Cheers,
      Stefan

      Reply
6. 

   Pradeep
   On 30. October 2017 Permalink

   Hello Stefan,
   We have installed October 2017 Cu on our Farm, The DB configuration Version is Showing as 1001 instead of 1002 .
   Is this an issue ?
   Thanks,
   Pradeep

   Reply
   1. 

      Stefan Goßner
      On 30. October 2017 Permalink

      Hi Pradeep,
      the database schema version is not always identical with the build number the most recent SharePoint component in a fix.
      These are different things and you should not use the DB Config version to verify patch installations.
      See here for details:
      https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
      Cheers,
      Stefan

      Reply
7. 

   SNJ
   On 8. November 2017 Permalink

   Hi Stefan,
   We have Sharepoint Server 2013 with SP1 installed (version 15.0.4571.1502).
   If I now want to reach the latest version (this from October 2017), can I just install the latest Full Server Packages for Sharepoint Server 2013?
   The link in your text, [Download SharePoint Server 2013 October 2017 CU], says CU but isn’t it a Server/Uber Packages?
   Because if I have understood it correct; a Server/Uber Packages not only include patches for the components updated in the current CU but also all patches released for other components of the product.
   CU, on the other hand, only contain cumulative update for the components in that specific CU.
   Should I go for latest patch, 2017-Oct, or should I step through all patches from May 2015?
   Best Regards
   Stefan

   Reply
   1. 

      Stefan Goßner
      On 8. November 2017 Permalink

      Hi Stefan,
      if not stated otherwise the links in my SharePoint 2013 blog posts always point to the full server packages of the current CU.
      You can see that also from the following sentence in the blog post: “The Full Server Packages for October 2017 CU are available through the following links:”
      Cheers,
      Stefan

      Reply
      1. 

         SNJ
         On 8. November 2017 Permalink

         Thank you for your answer. I read the blog post to fast so I missed that sentence ;-).
         From your experience, should I go for this Full Server Update from 2017-October or should I take step by step from May-2014 (as I said earlier we only have version 15.0.4571.1502)?
         /Stefan

         Reply
         1. 

            Stefan Goßner
            On 8. November 2017 Permalink

            Hi Stefan,
            installing all the fixes in between is just wasting time. The full server packages is all you need.
            Cheers,
            Stefan

            Reply
8. 

   S. M. Rabiul Islam
   On 14. November 2017 Permalink

   Hi Stefan,
   After updating October 2017, CU. We are having issue like deployment getting stuck.
   When we did run configuration wizard, it run fine in app-server. In web-server configuration wizard failed at step9 with error
   “Failed to add the service connection point for this farm”
   The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=robi,DC=com,DC=bd doesn’t exist in the directory.
   However, we run configuration wizard in web-server using command psconfig -cmd upgrade -inplace b2b -wait -force
   It was successful then. But since patch applied wsp-deployment hangs on.
   This is a major issue for client, please advice.

   Reply
   1. 

      Stefan Goßner
      On 14. November 2017 Permalink

      Hi,
      this is not an issue I have seen so far. My suggestion would be to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply
   2. 

      RN
      On 29. November 2017 Permalink

      Hello Rabiul,
      First run the below command on your SharePoint server and check if you see any timer service instance disable.
      $farm = Get-SPFarm
      $farm.TimerService.Instances | where {$_.Status -ne “Online”}
      IF you find it disable, then you need to start it using below command.
      $farm = Get-SPFarm
      $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne “Online”}
      if ($disabledTimers -ne $null)
      {
      foreach ($timer in $disabledTimers)
      {
      Write-Host “Timer service instance on server ” $timer.Server.Name ” is not Online. Current status:” $timer.Status
      Write-Host “Attempting to set the status of the service instance to online”
      $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online
      $timer.Update()
      }
      }
      else
      {
      Write-Host “All Timer Service Instances in the farm are online! No problems found”
      }

      Reply
9. 

   Wesley Chak (HK)
   On 24. January 2018 Permalink

   Dear Stefan
   I would like to consult that we encounter issue on Word Web App after applying the patches in order, kb3178725, kb3213562 and kb4011247, it prompts error “Sorry, we ran into a problem”, but Excel webapp and powerpoint webapp are working fine. The office web app server is connected with our SharePoint 2013 server. I follow the Microsoft guide to apply the software update for Office web app server https://technet.microsoft.com/en-us/library/jj966220.aspx
   I have checked the event viewer for the Office Web apps monitoring with errors as well.
   AgentManagerWatchdog reported status for AgentManagerWatchdog in category ‘Recent Watchdog Reports’. Reported status: Machine health is Unhealthy
   I would appreciate if you could advise how to resolve it ?
   Thanks,
   Wesley

   Reply
   1. 

      Stefan Goßner
      On 24. January 2018 Permalink

      Hi Wesley,
      if you need assistance to get this investigated I would recommend to open a ticket with Microsoft support.
      Cheers,
      Stefan

      Reply
10. 

    Wikus
    On 14. February 2018 Permalink

    Hi Stefan, which UP/SP is the latest one for SP Server 2013? I am on Service pack 1 Mark 2?

    Reply
    1. 

       Stefan Goßner
       On 14. February 2018 Permalink

       Hi Wikus,
       the latest Uber package (in case UP means that) is from February 2018.
       the latest service pack is SP1 mark 2 and there will not be another service pack.
       If you are on SP1 mark 2 you will be unsupported after April 10th as outlined in the new servicing policy:
       https://blogs.technet.microsoft.com/stefan_gossner/2017/12/13/updated-product-servicing-policy-for-sharepoint-2013/
       Cheers,
       Stefan

       Reply