A List of All Changes in the October 2013 Cumulative Update


It is Cumulative Update time again and so Microsoft has once more attempted to make tracking down the specifics of what has been changed or updated to as difficult as possible. This post is just a single place that pulls together all of the changes in the October 2013 CU in one place instead of scattered across half a dozen pages with links to pages that link to other pages.

I do have to give Microsoft some credit though as this announcement is better organized than previous ones and provides a nice jump off point to find all of the changes. There is still a lot of digging but it is a good starting point.

SharePoint Foundation 2013

Sts-x-none.msp

2825674 – Updates to build: 15.0.4551.1001

  • When you use a publishing template on a SharePoint Server 2013 site, you cannot add a search box to the XsltListViewWebParts web part.
  • Assume that a blog contains more than eleven entries. When you go to the next page of the blog in the Archives view, the title of the page is displayed incorrectly. Additionally, you may receive the following error message:
      There are no posts in this month.
  • When you try to join a custom group on a SharePoint Server 2013 site, you may receive the following error message:
      Sorry something went wrong.
  • When you are a search service administrator on a SharePoint Server 2013 farm, you cannot click the Query Rules button under the Queries and Results heading in the Navigation pane to view query rules.
  • Assume that you do not install or enable the DragUpload ActiveX control in Windows Internet Explorer 8 or Internet Explorer 9. When you click the New document button on a SharePoint Server 2013 document library, Microsoft InfoPath does not start.
  • When you follow a document on a SharePoint Server 2013 site that has alternate access mappings (AAM) enabled, the link to the document points to the default zone instead of the AAM zone.
  • After you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and enable grouping on one or more fields, you cannot expand or collapse the group.
  • When you trigger an automatic approval workflow on a SharePoint Server 2013 site from a nondefault zone, the approval email message includes a URL that uses the default zone.
  • Assume that you add the Tag Cloud web part to a page on a SharePoint Server 2013 site that has the Save metadata on this list as social tags feature enabled. When you try to add a term in the Enterprise Keywords column for an item, the term is not added, and no tag is displayed on the Tag Cloud web part.
  • Consider the following scenario:
    • You create a SharePoint Server 2013 document library that has the versioning and “required check out” features enabled.
    • You upload a document to the document library.
    • You check in the document and leave a version comment.
    • You open the version history of the document.

    In this situation, the version comment that you left is blank.

  • The number of downloads is not removed from the details page of an app.
  • Assume that you enable the WOPI Binding feature for a .pdf file on a SharePoint Server 2013 server. When you click the Open button on the .pdf file callout, you receive an error message.
  • When you add a client-side connected web part that provides data to a consumer web part on a SharePoint Server 2013 site, the web part does not work in Internet Explorer 10.
  • Assume that you create a SharePoint Server 2013 site that contains a Managed Metadata Service (MMS) column. When you use the multiple file upload control to upload a document to the site, the values for calculated columns are not populated.
  • When you change the Ipersonalizable property of a web part on a SharePoint Server 2013 site, the property is not saved correctly.

Additionally, this update adds a new IT control to the SharePoint Designer client. The control helps you migrate workflows from WF3 workflows to WF4 workflows.

SharePoint Server 2013

2825647 – Updates to build: 15.0.4551.1005

  • When you assign a task to a user whose display name contains a comma on a SharePoint Server 2013 site, you receive the following error message:
      The user does not exist or is not unique.
  • After you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and enable grouping on one or more fields, you cannot expand or collapse the group.
  • The language selection drop-down list on the search page does not extended fully.
  • Consider the following scenario:
    • You create a SharePoint Server 2013 document library that has the Versioning and Required Check Out features enabled.
    • You upload a document to the document library.
    • You check in the document and then leave a version comment.
    • You check the version history of the document.

    In this situation, the version comment is blank.

  • Consider the following scenario:
    • You create a grouping view for a list that contains a managed metadata service field on a SharePoint Server 2013 site.
    • You expand all nodes for the list.
    • You apply a filter to the managed metadata service field.

    In this situation, all items are missing.

    Note This issue occurs even after you clear the filter.

  • Assume that you create a new workflow that executes many input or output (I/O) operations on a SharePoint Server site by using SharePoint Designer 2013. Then, you publish the workflow and trigger an instance. When you browse through the workflow status page, you receive the following error message:
      System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

Coreserver-x-none.msp

2825672

  • When you are a search service administrator in a SharePoint Server 2013 farm, you cannot click Query Rules under the Queries and Results heading in the navigation pane to see query rules.
  • When you follow a document on a SharePoint Server 2013 site that has alternate access mappings (AAM) enabled, the link to the document points to the default zone instead of to the AAM zone.
  • When you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and enable grouping on one or more fields, you cannot expand or collapse the group.
  • When you trigger an automatic approval workflow on a SharePoint Server 2013 site from a nondefault zone, the approval email message includes a URL that uses the default zone.
  • When you add a note board web part to a web part zone on a SharePoint Server 2013 site, web part zones on the right side of the page are unexpectedly moved down the page.
  • When you post a link for a file that contains more than 16 Unicode Transformation Format (UTF) characters on the Newsfeed page, you receive the following error message:This couldn’t be posted because we’re having some issues at the moment.
  • Assume that you add the Tag Cloud web part to a page on a SharePoint Server 2013 site that has the Save metadata on this list as social tags feature enabled. When you try to add a term in the Enterprise Keywords column for an item, the term is not added, and no tag is displayed on the Tag Cloud web part.
  • Consider the following scenario:
    • You create a SharePoint Server 2013 document library that has the versioning and “required check out” features enabled.
    • You upload a document to the document library.
    • You check in the document and leave a version comment.
    • You open the version history of the document.

    In this situation, the version comment is blank.

  • You cannot use the asset picker to add an image to a page on a Catalonian SharePoint Server 2013 site.
  • Consider the following scenario:
    • You create a Team Site web application and a My Site web application that use different host names.
    • You follow up a post on a Team Site.
    • You click the link in the Added a follow up task to your task list dialog box to view your task.

    In this situation, you are not redirected to the My Site site.

  • When you perform a crawl on a SharePoint Server 2013 site, and the site performs a redirect operation to a different page, you receive an error message that states that an object was not found.
  • Assume that you enable the Company Entity Extraction or Custom Extraction feature on a SharePoint Server 2013 site. When you perform a crawl on a list that contains some attachments, the crawl freezes and then times out.
  • When a site (site A) and your My Site site are hosted on different farms, you cannot follow people or content on the Newsfeed page on site A.
  • Consider the following scenario:
    • You create a source label and a target variation label on a SharePoint Server 2013 site.
    • You run the Variations Create Hierarchies Job Definition job to enable hierarchies.
    • You create a list under a sub-site that is under the source variation.
    • You run the Variations Propagate Sites and Lists Timer job to enable propagation.
    • You click a hyperlink in the status column on the variation settings page for the list.

    In this situation, you receive an error message that states the list does not exist.

  • When you search some words by using the Enterprise Search Center site on a SharePoint Server 2013 server on which a custom word breaker is installed, no words are highlighted.
  • 2826001
      “We’ve hit a snag” error message when a user clicks the Followed Sites or Followed Documents button in a consuming SharePoint Server 2013 farm
  • When you change the search topology and remove the replicas on a SharePoint Server 2013 server, the disk is accumulated and is eventually filled up.

Coreserver-x-none.msp; Coreservermui-<Language-Code>.msp

2825675

  • When you perform a full, incremental, or continuous crawl on a SharePoint Server 2013 site, the crawl stops, and no content is processed.
  • The language selection control on the Search Results page is not displayed as expected.

Office Web Apps Server 2013

Wacserver-x-none.msp

2825686

  • Assume that Microsoft Lync 2013 is installed on a computer that is running Windows 8.1 or that has Windows Internet Explorer 11 installed. The computer is in an environment that uses an on-premises deployment of Office Web Apps Server 2013. When you try to share or view a Microsoft PowerPoint presentation in Lync 2013, the Loading indicator is displayed for longer than expected. Or, you receive the following error message:Sorry, we ran into a problem displaying the presentation. Please try again.
Advertisements

Posted on December 4, 2013, in SharePoint and tagged , . Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s