November 1, 2016, update for Project 2013 (KB3127959)

Improvements and fixes

Fixes the following issues:

• When you open certain XML files, you may receive the following invalid 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.
  To continue, click OK.
  To remove the actual finish date, click Cancel.

  Additionally, when you open some XML files, the Gantt bars for fixed or an elapsed duration task show an unexpected trailing split.
  

• If you have a task that has a duration of four elapsed months or longer, Project 2013 freezes when you save the project as an XML file.
  

• Assume that you start Project Professional and connect it to a server, and then you select the load summary resource assignments check box. When you go to a resource usage view, a given resource may be displayed to be underallocated during a certain period (for example, daily) even though it should be displayed as overallocated.
  

• When you level a project on a week-by-week basis, Project may freeze. Additionally, when the leveling finally finishes, tasks are scheduled out to the end of time which is December 31, 2149.
  

• If an inserted subproject has a task that's 100% complete and has an ALAP constraint, the summary tasks within the subprojectmay have an incorrectly calculated start, finish, and duration.
  

• Assume that you start Project Professional and connect it to a server, and then you select the load summary resource assignments (SRA) check box. When you go to a resource usage view, a given resource may displayed to be overallocated during a certain period (for example, daily) even though it should not displayed as overallocated. This can occur if the actual work value from the SRA for the given period isn’t handled correctly.
  

• 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 problem can occur with projects that were stored in Project Server.
  

If you want to fix the following issue in Project 2013, please install November 1, 2016, update for Office 2016 (KB3118340).

When you use the Send as Attachment email function to share a project, Project 2013 may crash if you have Outlook 2016 installed.

How to download and install the update

Update information

Prerequisites To apply this update, you must have Microsoft Project 2013 Service Pack 1 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 Project 2013.

2. On the File menu, select Account.

3. For Office 2013 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 terminology that Microsoft uses to describe 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.