The Cumulative Update package, that should have been out in February, has finally been released. This CU will act as the baseline for all future fixes meaning that you will need it in order to install e.g. the April 2013 CU.

Download the CU here: http://support.microsoft.com/kb/2768001

Issues that this hotfix package fixes

• Assume that you upgrade Microsoft SharePoint Server 2010 to SharePoint Server 2013. In this situation, when you create a discussion post in a community, the feed notification is not displayed on your My Site page.
• Assume that you remove a user profile picture from Active Directory Domain Services (AD DS). Then, you perform a user profile synchronization from AD DS to SharePoint Server 2013. In this situation, the user profile picture is not removed from SharePoint Server 2013.
• Assume that you attach a SharePoint Server 2010 content database to a SharePoint Server 2013-based server. In this situation, when you upgrade the site collection on the SharePoint Server 2013-based server, picture libraries are not updated.
• After you run a Build-To-Build in-place upgrade, accounts other than the application pool account lose the SPDataAccess and SPReadOnly roles.
• When you perform a search on a SharePoint Server 2013-based server, you experience performance problems on the server.
• When you configure Access Services to use Windows Azure SQL Database (formerly SQL Azure), database connections may time out too early.
• Consider the following scenario:
  • You open a Microsoft Word 2013 document that contains a footnote reference inside a table.
  • You click Text Direction and then click Vertical in the Page Setup section on the PAGE LAYOUT tab.
  • You scroll down to the end of the document.

  In this scenario, some pages after the table may not be displayed.

• Consider the following scenario:
  • You create a community site in SharePoint Server 2013.
  • You use the least-privileges configuration to set up the SharePoint farm.
  • You create a new discussion post on the community site.
  • You view the My Newsfeed section of the My Site page.

  In this scenario, the feed for the discussion post is not displayed in the My Newsfeed section.

• The output cache feature does not work on a page on a SharePoint Server 2013 site. This issue occurs when the page contains a Content By Search (CBS) web part.
• Assume that you use the Cross-Site Publishing feature to create a site on a SharePoint Server 2013-based server. When you perform a search on the site, the number of search results is greater than the expected number.
• Consider the following scenario:
  • You open a Word document in Word 2013.
  • The Word document contains some shapes or pictures.
  • You right-click one of the shapes or pictures in the Word document.
  • You click Edit Points for the shape. Or, you point to Wrap Text and then click Edit Wrap Points for the picture.

  In this scenario, other shapes and pictures may disappear from the Word document.

• When you run a complex query or import a large amount of data in Microsoft Access 2013, you receive the following error message:
  System Resources Exceeded

  Note This bug need registry information.

• When you try to resize an app part on a SharePoint Server 2010 webpage, you receive a JavaScript error message. This issue occurs after you set the value of the Chrome Type property for the app part to None.
• If you use the Chinese lunar calendar in Outlook 2013 or in an earlier version of Outlook, the Gregorian date is displayed as an incorrect lunar date. For example, the Gregorian date June 8, 2013, is displayed as lunar date 4/30 instead of 5/1.
• Assume that you access a SharePoint site that is not in your trusted sites list. When you try to search an item on the site, you receive the following error message:
  The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types.
• You cannot edit a Silverlight web part on a SharePoint 2010 mode site collection in SharePoint Server 2013.
• When you try to perform a search crawl on a list that contains many columns in SharePoint Server 2013, you receive the following error message:
  The filename or extension is too long
• When you create a meeting on a group calendar on a SharePoint 2010 mode site, the Attendees field is not filled by a default value.
• Assume that a SharePoint Server 2010 site contains a navigation link that points to an invalid URL. After you upgrade SharePoint Server 2010 to SharePoint Server 2013, you cannot access the site.
• When user A creates a post that refers to user B in a different SharePoint farm, user B does not receive a notification email message.
• When no workflow is published to a Microsoft Project Server 2013-based server, you cannot change the enterprise project type for a project through Project Web App.
• Consider the following scenario:
  • You create a workflow in Microsoft SharePoint Designer 2013.
  • You publish the workflow, and you set the workflow to start automatically in SharePoint Server 2013.
  • You view the workflow status page (Wrkstat.aspx).

  In this scenario, the exception messages are not completely displayed on the Wrkstat.aspx page.

• Consider the following scenario:
  • You create a site collection in Microsoft Office SharePoint Server (MOSS) 2007.
  • You create a workflow that has the Collect Data from a User task.
  • You upgrade MOSS 2007 to MOSS 2010 or MOSS 2013.
  • You receive a notification email message when the task is assigned to you.
  • You open the email message by using Microsoft Outlook and then click Open this task to open the URL of the workflow task.

  In this scenario, Internet Explorer starts. However, you receive the following error message:

  The webpage cannot be found.
• When you apply multiple filters to two columns of a custom list, only the filter that is applied to the second column applies to list items in the custom list.
• Assume that in a list on a SharePoint Server 2013 site, you reference an item from another list. When you try to view the item in the list, you receive the following error message:
  Index was outside the bounds of the array.
• Consider the following scenario:
  • You add managed metadata columns that are multivalued to the content farm and to the service farm in SharePoint Server 2010.
  • You upgrade from SharePoint Server 2010 to SharePoint Server 2013.
  • You search for a value in SharePoint Server 2013.

  In this scenario, some search results are not displayed in SharePoint Server 2013 as they would be in SharePoint Server 2010.

• When you start a workflow in SharePoint Server 2013 on folders or on large lists, you receive the following error message:
  Something went wrong. To try again, reload the page and then start the workflow.
• Assume that you create a site that contains folders and that you save the site as a template. When you try to use the template to create a new site, you receive the following error message:
  Unexpected Error happened
• SPBasePermission enumeration values are truncated from 64 bits to 32 bits for SharePoint sandboxed solutions.
• You cannot start an Agave application when you open a document in Excel Web Apps.
• Assume that you create a custom SharePoint list that contains a multivalued Person or Group field. The field does not contain any values. When you try to insert a new row into the list in Datasheet view, Internet Explorer crashes.
• Assume that you filter data in an Access form on a non-English version of SharePoint Server 2013 server. In this situation, Full-Text Search in SQL Server does not work correctly. Specifically, the filtering operations are slow or return incomplete results.
• When you perform a search in a SharePoint Server 2013 search center in backward compatibility mode, the out of box (OOB) site refiner returns incorrect results.
• When you try to import a large amount of data into an Access application on a Windows Azure SQL Database (formerly SQL Azure) database, you sometimes receive a Time-out error, and you have to cancel the import process.
• If you create an Access application that uses the Kazakh language, you cannot save the application as a package.
• Assume that a SharePoint farm receives some requests from client computers. When the farm uses a network load balancer to distribute the requests from clients, you cannot create an Access application on a SharePoint server in the farm. Additionally, you receive an error message that states that the SharePoint server IP address is invalid.
• Assume that a pinned task is split into two parts in Microsoft Project 2013. When you change the duration of the pinned task in Task Usage view, the duration of the task is calculated incorrectly.
• Assume that you create two tasks that you must manually schedule in Project 2013 and then assign the same resource to both tasks. When you assign a duration of time that includes nonworking days to the tasks, the resource-leveling feature does not work correctly.
• After you upgrade Microsoft Project Server 2010 to Project Server 2013, you cannot access document libraries and issues or risks lists in Project Server 2013.
• Assume that you use non-ASCII characters to name a task outcome field in a task in a custom workflow. Then, you change the default value in the task outcome field. In this situation, the task outcome field continues to display the default value on the workflow status page.
• Assume that you configure the app-only policy for a SharePoint workflow. Then, you publish the workflow to a website on which a SharePoint application is installed. In this situation, you cannot run an instance of the workflow on the website.
• When you use Word 2013 to save a .docx file as an OpenDocument Format (ODF) file, the paragraph alignment in the file is displayed incorrectly.
• Consider the following scenario:
  • You configure an East Asian language input method editor (IME) for Word 2013 on a Windows 8-based touch device.
  • You type some characters in a new Word document.
  • You touch the document to change the cursor location.
  • You type a new character or delete the character before the cursor.

  In this scenario, the new character is displayed in the previous location of the cursor, or the character that is before the previous location of the cursor is deleted.

• Assume that you have editor permissions on a SharePoint Server 2013-based server. When you try to create an application on the server or upload an application from the corporate catalog to the server, you receive the following error message:
  unexpected error
• Assume that you open a document that contains a text box. The text box contains a table, and the table contains some text. After you change the background color of the text box to certain colors, the text is no longer visible.