Service Pack 1 Now Available for Microsoft Office 2013, Project 2013, and SharePoint 2013

Microsoft announced today on the Office Updates blog that Service Pack 1 (SP1) is now available for Microsoft Office 2013, Microsoft Project 2013, and Microsoft SharePoint 2013:

http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

They provide instructions and links to obtain SP1 from the Microsoft Download Center, as well as more detailed information describing the types of updates included for each product.

Here are the URLs for more information about Project SP1 and SharePoint SP1:

Project 2013 SP1: http://support.microsoft.com/kb/2817433

SharePoint 2013 SP1: http://support.microsoft.com/kb/2817429

Project Server 2013 SP1: http://support.microsoft.com/kb/2817434

 

IMPORTANT NOTE: EPMA strongly recommends that if you are considering applying SP1 or any other software updates, you should first install the updates into a non-production environment and test them thoroughly. If you do not have the system resources or personnel to do this, please seek the help of experienced experts.

 

Here is a listing of the fixes included in Project 2013 SP1 and Project Server 2013 SP1; this information is available in a downloadable Excel spreadsheet from the URLs above:

  • If the view (resource or tasks) has one column that has a dependent read-only column, the paste action will try to override the read-only column and will generate an error message.
  • Close Tasks to Updates view disappears when switching to Project Server Permissions mode.
  • When migrating projects with project-level calendars to Project 2013 from earlier versions, in some instances the default Project calendar can conflict with the calendars in the MPP file, leading to unexpected scheduling discrepancies. Additionally, when expanding a subproject inside of a master project, rollup custom fields can display the value “#ERROR” or no value at all until the subproject is opened and a recalc is forced.
  • If a view uses an interactive filter, that filter will be removed from the view definition if a user cancels setting the filter when applying the view.
  • Importing a project from Excel may fail to properly set the task progress.
  • Documents, Issues, and Risks sections on the Task Details page don’t display links.
  • Certain tasks with very high work loads cannot be viewed in the Approval Center.
  • If a project with subprojects is opened before it is completely saved on the server, it may become corrupted.
  • Deleting a project created from the Project Ideas list can fail if the Project Ideas list was deleted.
  • In some cases, time phased cost and work values entered for a baseline in Project do not properly appear in the reporting database.
  • At a high DPI setting, the view names displayed on the left side of the screen may not appear correctly.
  • Users cannot edit a task’s work or remaining work in the Schedule Web Part when Protected Actuals is enabled on the server and the task already has actual work.
  • Out-of-the-box Project web parts do not function outside of the Project Web App site collection.
  • Resource costs are not calculated correctly when using the project update PSI for assignments that contain multiple cost rate table entries.
  • When projects are created in PWA using template-based EPTs, notes that are associated with tasks are lost when the project is opened in the Project client.
  • Project shows the error “The following job failed to complete. Job Type: Save. Error ID: 9000(0x2328)” when attempting to save changes in enterprise projects with more than 5000 tasks.
  • If the user selects one (or more) cells and then right-clicks in a cell that requires the grid to scroll, the right-click selection is lost.
  • When Project CSOM is used to return the collection of projects, the collection will now include subprojects.
  • If a textbox is added to a Gantt chart with a number in front of the text, the number shows up after the text in printing/print preview.
  • The Import Timesheets feature does not work properly when the language setting is not English.
  • If the Gantt chart is split with the resource graph view, Project may crash when the bar styles for the resource graph are edited.
  • When a baseline is saved from the context of a Master Project, Project may crash unexpectedly.
  • The number of calendar exceptions allowed for a single entity in Project has been increased.
  • The main Project icons will now be displayed correctly at a high DPI setting.
  • Project may not show the baseline data correctly if time phased baseline work and/or baseline cost is edited.
  • Baseline Work calculations sometimes do not update correctly while the user is in the Resource Usage view.
  • The Previous, Next and Select Period buttons are now enabled so that the user can move to a different period where there is an active time period.
  • When leveling granularity is set to a value greater than Days (Weeks and Months, for example), leveling does not properly resolve over allocation issues.
  • Saving and publishing a project on Project Server may take a long time.
  • Publishing a project, when resources in the project have assignments in many other projects, may take a long time to complete.
  • If the Office-wide profile setting turns off saving to either XPS or PDF, then the Project Save As dialog may not work correctly.
  • Earned value calculations do not work correctly in Project when any baseline other than Baseline0 is used.
  • Time phased Actual Cost and Baseline cost may not properly appear in the reporting database if there’s no associated time phased work/baseline work with the cost.
  • On some assignments with modified contours and small assignment unit values, it’s not possible to set the % Work Complete field to 100%.
  • Tasks deleted using the Gantt view on a SharePoint list do not go to the Recycle Bin of that site.
  • CustomFieldValueListAdd method cannot write values over 127 characters long.

 

Here is a listing of the fixes included in SharePoint 2013 SP1; this information is available in a downloadable Excel spreadsheet from the URLs above:

  • Metadata is lost when documents that use a custom content type with a “Description” field are opened for editing.
  • When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.
  • An error occurs when files are moved between document libraries and the web time zone is behind that of the server.
  • Metadata filtering at list level always lists all metadata terms.
  • The hyperlink popup window drops the selected word to be linked when there is a delay of more than one second in opening the window.
  • Multiple-column, SummaryLinkWebParts with a group heading style of “Separator” are rendered incorrectly.
  • A hash tag that contains a full width space does not get created successfully.
  • Search schema compression is now enabled by default to allow larger search schemas.
  • Highlighting for FQL queries is now enabled for FQL as well as KQL.
  • Opening a custom SharePoint list in datasheet view and applying multiple custom filters, where each filter has more than one condition, can result in an incomplete set of list items.
  • When the “Export to Excel” button is clicked in a SharePoint document library that has the Content Type field displayed, the Content Type field does not appear in the Excel workbook.
  • An error occurs after changing the “Manager” property in EditProfile.aspx page when the My Sites WebApp is not in the same farm as the UPA.
  • SharePoint REST API does not return a well-defined error response for a duplicate key exception.
  • Developers are unable to specify a Content Type ID when creating Content Types in the client object model.
  • On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.
  • In some non-English languages of SharePoint, the text displayed in the callout UI for a document or list item, describing who last edited the item, may not be grammatically correct.
  • Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.
  • Pages do not render in Safari for iPad when private browsing mode is used.
  • When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.
  • An error that says “SCRIPT12004: An internal error occurred in the Microsoft Internet extensions” may occur intermittently when users visit their SkyDrive Pro or other pages on their personal site.
  • InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.
  • An InfoPath form with extended characters in its name fails to open.
  • An error that says “Security Validation for the form has timed out” may occur when an InfoPath form is digitally signed and hosted in a SharePoint site collection that uses the SharePoint version 2010 user experience.
  • “Show document icon” remains unchecked and the document icon does not show in Edit Properties for a list item.
  • A “Failed tagging this page” error occurs when the “I like it” button is clicked.
  • The wrong term is removed when manually editing a multi-valued taxonomy field.
  • When tagging list items using a language that is different from the term store default language, suggestions for labels are offered in multiple languages. The suggestions appear confusing because both language suggestions are listed without any identification of the language.
  • An error that says “There was an error processing this request” may appear when editing the user profile.
  • Times are missing from Date/Time results in certain filtered list web service calls.
  • Minimal and no metadata are now enabled as supported JSON formats.
  • Actions4 schema workflow actions can’t be deployed to SharePoint.
  • Using Client Object Model, Stream.Seek() to seek to a particular position doesn’t seek at the proper offset.
  • Refreshing a workflow status page generates the following error: “System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.”
  • Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.
  • Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.
  • Workflow task processes on wiki pages won’t start.
  • Workflows won’t wait for changes to content approval status fields.
  • E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.
  • Workflows may fail to send an e-mail or send too many e-mails.
  • Association variables do not update correctly for auto-start workflows.
  • A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.
  • Incomplete tasks are deleted when workflow task activities complete.
  • Task activity is suspended when the task is completed using app-only credentials.
  • An error that says “This task could not be updated at this time” occurs when trying to complete a workflow task using the “Open this task” button in Outlook.
  • A workflow doesn’t respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.

 

Good luck!