June 7, 2016, update for Project 2016 (KB3115149)

Improvements and fixes

• Updates the translation in the project check in dialog box for French to make sure that the meaning is accurate.
  

• Fixes the following issues:

  • When you try to unlink a subproject from a master project that has a custom field with a lookup table defined, Project 2016 crashes if the subproject doesn't have the same lookup table definition as in the master project yet the custom field has values.
    

  • When you try to open a large project in Project 2016, you receive the following error message:

    This operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

    This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.
    

  • Project 2016 may freeze when you print or preview certain projects.
    

  • Consider this scenario:

    • You have an enterprise resource custom field.

    • The field has a lookup table applied to it, and multiple values can be selected.

    • You have a resource that has a value in the field that's longer than 255 characters.

    • You open a project in Project Professional that uses this resource.

    In this situation, you receive the following error message:

    The value you entered does not exist in the lookup table of this code. All values must be predefined in the code lookup table. Contact your server administrator to get new values added.

    You also find that the list of values in the field is truncated or has disappeared completely.
    

  • When you try to print a specified number of pages and select to have the timescale fit to the end of the page, the timescale doesn't horizontally fill the entire page.
    

  • Assume that you change a date by using the date picker, and the date is not in the current year. In this situation, the day and month are changed but the year isn't changed. This issue occurs when the date format is set to 4/W04.
    

  • When you save subprojects in the context of a master project, Project 2016 may crash. This issue may occur if the subprojects have Visual Basic Applications code in them.
    

  • When you set a finish date for a fixed duration task in which assignments on the task have actual work entered on non-working times, the finish date is changed to a different date from what you entered, and the assignment finish date is changed to the task finish date even though the assignment doesn't share the task's finish date.
    

  • When you open a project that has many cross project links in Project 2016, Project 2016 may freeze and eventually crashes when the computer runs out of memory.
    

  • Assume that you open a master project that has many subprojects in Project 2016. When you press ESC to cancel the loading, Project 2016 may crash.
    

  • Consider the following scenario:

    • You have a task in your project.

    • You have two resources that are assigned to the task.

    • On one of the assignments, delay has been added.

    • You publish the project to a server where protected actual work is enabled.

    • The resource who owns the assignment where delay doesn't exist reports work and the status update is applied to the task. The other assignment still has no actual work.

    • As the project manager, you set the work value to zero on the assignment that has no actual work.

    In this situation, the actual start and actual finish dates are set on the assignment even though these dates weren't reported by the team member. Later, when the project manager adds work back to the assignment and tries to reschedule it, the operation fails because Project tells that the change would change work entered by a team member.
    

  • Project 2016 may freeze when you create a recurring task.
    

  • If you try to reset the work breakdown structure (WBS) for a selection of tasks, the entire project is updated instead.
    

  • When you scale a printout to fit to one page in Project 2016, the printed output is unreadable.
    

  • When you submit a Physical % Complete value for a task that is synchronized to a SharePoint task list in Project 2016, an incorrect value is displayed. For example, the value of 100% appears as 1000%.
    

  • When you open projects, Project 2016 may crash. This issue occurs for some projects in which certain calendars in that project were duplicated.
    

  • Consider this scenario:

    • A task has an eight-hour assignment and it has been published to a team member.

    • The team member opens their timesheet and enters multiple time-phased actual work values. For example, 8h on one day and 3h on a second day.

    • The team member changes their mind and zeros out the last time-phased value. In this case, the 3h turns to 0h.

    • The team member submits their timesheet and the status manager approves the update which is then applied to the project.

    When the task and assignment are viewed in Project Professional, the task ends on the second day and the assignment ends on the first day. The expectation is that the task ends at the same time as the assignment.
    

  • The Office.ProjectProjectFields.ProjectServerUrl property that is used in Office Application solutions returns an integer instead of a URL string.
    

  • When you use the Project Import Wizard, you receive an incorrect merge result if the merge key is set to a custom field.
    

  • When you set the % Work Complete value for summary tasks in Project 2016, Project 2016 may crash. This issue occurs if Project is connected to a Project server where the Only allow task updates via Tasks and Timesheets setting is enabled.
    

  • When you synchronize a project in Microsoft Project 2016 to a SharePoint task list, some assignment data is lost if there are more than 50 rows.
    
    Note To fix this issue, you need to install June 7, 2016, update for Office 2016 (KB3114709).
    

How to download and install the update

Update information

PrerequisiteTo apply this update, you must have Microsoft Project 2016 installed.

Restart informationYou may have to restart the computer after you install this update.

More Information

To determine whether your Office installation is Click-to-Run or MSI-based, follow these steps:

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.

References

Learn about the standard terminology that's used to describe Microsoft software updates. The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office.

File Information

The global version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.