The First Ever Project and Project Server 2013 July CU

Going forward we may now be releasing hotfixes (aka Cumulative Updates) in the odd numbered months as well as the even ones for Project 2013, Project Server 2013 and SharePoint 2013 – and the rest of the Office family.  July is the first of these.  I have just posted the release blog over on the Project Support blog - Microsoft Project Server 2013 July 2014 CU Announcement.

This July CU contains a number of fixes that have been eagerly anticipated:

On the client side we have the root cause fix for the Invalid Lookup Table issue that we released a server fix for last month that will avoid the Error 9000 (or at least this cause for it).

Assume that you use some local custom fields that contain some lookup tables in a project in Project 2013. Then, you save the project to Project Server. Later, you delete the project from the cache. When you open the project and save the project again, the lookup tables may be corrupted and you receive an error message that resembles the following:

The following job failed to complete
Jog Type: Save
Error ID: 9000(0x2328)

and also the fix for the wrong baselines being displayed in the client (which I know a certain Russian friend will be very pleased to see!). 

When you open a project that contains multiple baselines, the time-phased baseline cost for tasks or assignments is displayed incorrectly. For example, when you check the time-phased Baseline1 cost values, they display the values for the time-phased Baseline cost instead.

The other couple of client fixes are on the ProjectBeforeAssignmentChange VBA event and an issue with too many e-mail notifications being triggered when opening plans from SharePoint task lists.

On the server side just a couple of new fixes, a baseline issue with negative costs has been resolved and we have done some work to avoid issues when publishing many projects at once which could cause problems with "Synchronize Project Web App Permissions to Project Web App" user synchronization job failures.

Comments (0)

Skip to main content