March 8, 2016, update for Project 2016 (KB3114865)

• When you merge an Excel workbook into an existing project where there's more than one assignment on a given task, only the actual work on the first assignment is updated.
  
• When you use Microsoft Visual Basic for Applications (VBA) macros to edit project data within the  Project.BeforeSaveevent handler, the edits to the project may not be saved if the project is saved to Project Server.
  
• After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn't report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
  
• You can't remove remaining work from a manually scheduled task in Project 2016 when the task is published to Project Server. This issue occurs when the Only allow task updates via Tasks and Timesheets  task settings and display options are enabled.
  
• After you level resources by using the week-by-week or month-by-month basis in Project 2016, the resources remain overallocated.
  
• When you use Project 2016 with certain Windows region date and time formats (for example, Spanish (Mexico)), baseline bars aren't displayed in the Gantt chart.
  
• When you apply a grouping to a task type view, baseline finish type fields may not show the expected value on the grouping summary row tasks. Instead of showing the latest finish date as expected, the field shows Not Available if at least one of the grouped tasks doesn't have a baseline finish date.
  
• Consider the following scenario:
  • A user enters time phased actual work on an assignment and submits the work for approval.
  • The status manager approves the update.
  • The user changes the assignment start date and then submits the change.
  • The status manager approves the update.
  In this scenario, the time phased actual work may move to another date.
  
• When you open a project from a server, it may take a long time if the project doesn't exist in the user's local active cache.
  
• Consider the following scenario:
  • You add some Visual Basic Applications (VBA) code to a project in Project Professional 2016.
  • You save and publish the project to Project Server, and then you check in the project.
  • You edit the project on the schedule project detail page in Project Server.
  • You change and save the project.
  • You open the project again in Project Professional 2016.
  In this situation, the VBA code is missing.
  
• Assume that you have a series of related tasks (they have dependencies between them) and you now make one of the tasks inactive. In this situation, the successor tasks to the inactive task may be scheduled later than expected.
  
• Macros that exist in the local global template don't work if they are invoked from the ribbon. This issue occurs when Project 2016 is connected to Project Server.
  
• When a plan is opened for edit in Project 2016 or in Project Web App, in some cases, additional actual work may appear on an assignment.
  
• If you save an incremental baseline that rolls up baseline values from a task to summary tasks, the timephased baseline values of the summary tasks are deleted from the dbo.MSP_EpmTaskBaselineByDay table in the reporting database.
  
• If you update a sheet view to show the notes field, you may see redraw issues.
  
• If you have a project that's saved to Project Server, you can't access project level properties.
  
• When Project 2016 connects to Project Server, Project 2016 may crash if there are enterprise templates but you don't have the permission to access them.
  
• It may take a long time to open multiple projects from Project Server in Project 2016.
  
• You can't publish a project in Project Web App and receive an error message that looks something like the following:
  Cannot insert duplicate key in object 'pub.MSP_PROJECT_RESOURCES'
• It takes a long time to close and check-in a master project if Summary Resource Assignments (SRA) are loaded.
  
• When you print a timeline in Project 2016, the last letter can sometimes be wrapped to the next line.
  
• If you delete data by using the delete or backspace key in Project 2016, the BeforeTaskChange, BeforeResourceChange, and BeforeAssignmentChange events are not triggered.
  
• When you open a Project file from a SharePoint document library, the file is sometimes opened as read-only when it should be read and write. In other cases, the project is sometimes opened as read and write but you can't save changes.
  
  Note To fix this issue, you also need to install March 8, 2016, update for Office 2016 (KB3114857).
  
• After you set the Default Assignment Owner field for an enterprise resource and then create a project that uses the resource, the Default Assignment Owner field is blank.
  
• If you enable the Only allow task updates via Tasks and Timesheets option, you can't set tasks to 100% complete if the task has an assignment with zero work.
  
• When you level resources for projects in Project 2016, Project 2016 may crash.
  
• When you select to merge data from Excel and use the task name as the key in Project 2016, you receive an error message.
  

Microsoft Update

Download Center

• Download update KB3114865 for 32-bit version of Project 2016
• Download update KB3114865 for 64-bit version of Project 2016

Restart information

Prerequisite

1. Start an Office 2016 application.
2. On the File menu, select Account.
3. For Office 2016 Click-to-Run installations, an Update Options item is displayed. For MSI-based installations, the Update Options item isn't displayed.

Office 2016 Click-to-Run installation	MSI-based Office 2016