November 1, 2016, update for Project 2016 (KB3127960)

This article describes update KB3127960 for Microsoft Project 2016, which was released on November 1, 2016. This update has a prerequisite.

Be aware that the update on the Microsoft Download Center applies to the Microsoft Installer (.msi)-based edition of Office 2016. It doesn't apply to the Office 2016 Click-to-Run editions, such as Microsoft Office 365 Home. (How to determine?)

Improvements and fixes

Fixes the following issues:

• In some cases, you can't open a saved project that you worked with previously. Instead, you may see the file open progress indicator appears as if the project is opening, but the project doesn't open.
  
  
• Assume that you start Project Professional and connect to a server, and that you have selected to load summary resource assignments. In this situation, when you go to a resource usage view, a given resource that should be shown as overallocated appears to be underallocated during a certain period, for example, daily.
  
  
• When you open certain XML files, the start date of some assignments may be ignored, which means tasks are scheduled incorrectly. You may also notice that the assignment on a task has an actual start date yet the task doesn't.
  
  
• When you level a project on a week-by-week basis, Project may freeze. After the leveling is complete, you may find that the tasks are scheduled out to the end of time, which is December 31, 2149.
  
  
• When you use the JavaScript Office API against Project 2016, querying task start dates and finish dates always returns the automatically scheduled start dates and finish dates instead of the manually scheduled start dates and finish dates.
  
  
• When you open a project from a SharePoint site and then click the Edit Project button from the banner, you may see an error message that resembles the following:
  You have made changes to '<project name>'.
  Another user has also made changes. What would you like to do?
  Click Discard to discard your changes and edit the latest version.
  Click Save as to save your changes to a different file and open the latest version.
  
  This issue occurs with projects that were stored in Project Server.
  
  
• After you save and publish a project plan, upon close and check it in, you receive the following error message:
  The following job failed to complete.
  Job Type: Checking
  Error ID: 9000(0x2328)
  Could not checkin project. Please contact your system administrator to force checkin this project.
  
  
  
• When you open an XML file, resource assignments may have trailing zero work values in a usage view. For example, the work contour may resemble the following:
  8h, 8h, 2h, 4h, 0h, 0h, 0h
  It should appear as the following:
  8h, 8h, 2h, 4h
  
  
• Consider the following scenario:
  • You have a master project.
  • You have several sub projects in the master project.
  • The sub projects are set to read-only.
  • You open the master project.
  • You select the Edit Project button from the banner.
  In this situation, the sub projects are opened with the read/write permission even though they are set to read-only.
  
  
• Assume that you change the name of an enterprise calendar. When you open projects that use that calendar, Project 2016 may crash.
  
  
• Assume that have a task that has a duration of four elapsed months or longer. When you save the task to the XML file format, Project 2016 freezes.
  
  
• When you open certain XML files, you receive the following error message:
  The actual finish date is before some of the previously entered timephased actual work values. If you continue with this operation, Project will truncate some of the previously entered timephased actual work values.
  Additionally, when you open some XML files, you may find that the Gantt bars for fixed or elapsed duration tasks show an unexpected trailing split.
  
  
• If an inserted subproject has a task that is 100% complete and has an ALAP constraint, the summary tasks within the subproject may have an incorrectly calculated start, finish, and duration.
  
  
• Assume that a project contains a local resource whose name is the same as an enterprise resource, and the local resource is assigned to an incomplete task and a task that is 100% complete. When you save the project on a server, the local resource is assigned to the completed task, and the enterprise resource is assigned to the incomplete task.