Project Server 2013 Cumulative Updates

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and one important Public Update (PU) for Project Server 2013.  They are listed in reverse date order – newest at the top.  The CUs are normally available in a ‘rollup’ package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) ‘Individual’ packages which just contain the Project Server fixes.  Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack).  In some months a rollup package did not get released.  Brian has also recorded the version you will see in the dbo.Versions table in the Project Server database after applying each update and running the configuration wizard.  In some months this does not get incremented if there were no database changes.

You too can enjoy seeing how your PPM Works successfully.  Start by reaching out to us – PPM Works, Inc., your trusted Microsoft Project partner.

Thank you Brian Smith at Microsoft for all the information on Project Server Cumulative Updates (CU), Service Packs (SP), and Public Update (PU)

Rollup – http://support.microsoft.com/KB/2910911

Individual – http://support.microsoft.com/KB/2910944

DB Version – 15.0.4673.1000

• Assume that you add actual work to a task in a timesheet and then save it. Later, the project manager publishes another task, and the new task appears on the same timesheet. You add actual work to the new task and you submit the timesheet for approval. In this situation, the timesheet line for approval of the new task is not displayed in the Approval center.
• Assume that you change the working time of the enterprise calendar associated with your project to a nondefault working timesuch as 9:00-17:00. Then you publish a task. You go to the Tasks page in Project Web App (PWA), then you change the finish date and the duration of the task and save the change. In this situation, both the finish hour and the task duration are incorrect.
• Assume that you create a risk or an issue for a project in PWA, then you save it. When you visit a Project Centerview that includes Active Risks and Active Issues fields, the values are always zero.
• Assume that you have a custom field that is defined to include a lookup table and the table contains many values. In this situation, you may be unable to select lookup table values from the custom field on a Project Detail Pages page that shows this field.
• Assume that you apply a filter in the Approval Center in PWA. When you refresh the page, or when you go back to the Approval Center after you visit other pages, the filter is not applied though it is already set in the ribbon.
• When you use a template to create a project in PWA, and the template contains a null task, the project cannot be displayed in Project views, and you may receive the following error message:
  View Failure The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

  Additionally, the CPU usage may reach 100 percent. Note A null task is a blank row between rows.

• Assume that you set a baseline for a project, and then you publish and check in the project in PWA. When you open the Schedule project details page, the baseline value is incorrect. For example, the baseline value should be $1.00. However, it is displayed as $100.00.
• Consider the following scenario:Consider the following scenario:
  • You visit the Project Center and you drill into a project.
  • You select the Schedule project detail page.
  • You click the Tasks tab in the ribbon.
  • You view the list of views that you have access to.

  In this scenario, some views which you have access to are missing from the drop-down list because of the way security categories are assigned to you.

• • You browse to a PWA site.
  • You click the Gear icon on the top-right-corner, then click Site contents, and then click Project Detail Pages.
  • You select an item in the library, then click the Files tab, and then click the Edit Properties button.

  In this scenario, when you click Open Web Part Page in maintenance view on the page, you may receive the following error message:

  Sorry, something went wrong An unexpected error has occurred.

  When you try to check in an item in the library, you may receive the similar error message.

November 2014

Rollup – http://support.microsoft.com/kb/2889949
Individual – http://support.microsoft.com/kb/2899547
DB Version – 15.0.4667.1000

Consider the following scenario:

• You select the check box of the Single Entry Mode option on the Timesheet Settings and Defaults page on a Project server.
• You start Project 2013 and connect to the server.
• You create many tasks that have long names.
• You link the tasks together in a finish-to-start relationship.
• You assign the tasks to a user.
• You save and publish the project.
• The user logs on to Project Web App (PWA) and opens the Timesheet. The user clicks Add Row, and then clicks the Select from Existing Assignments option.

In this scenario, you see an error message similar to the following:

• If an instance of PWA for Project Server 2013 has multiple event handlers defined for the same event, the server processes that listen to the given event may fail completely. For example, you may be unable to create new projects or submit timesheets.
• Assume that you open Manage Timesheets on the PWA Settings page. When you try to open a timesheet, the timesheet may not be loaded. Additionally, you receive the following error message:
  The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
• Assume that a team member creates a sub task under a summary task of a project in PWA. Then, the team member sends it for approval. When the project manager opens the project in Project Professional 2013, the newly created sub task is located in the wrong place, and it becomes a summary task.
• Consider the following scenario:Assume that you create a new enterprise custom text field in PWA, and you add a long description for this field. When you add the custom field into a web part of a project detail page, the word wrapping works incorrectly in the field description.
  • You create a security group in PWA and add a user to the group.
  • You set the same Resource Breakdown Structure (RBS) value for the user and a project manager.
  • You create a new category and select the The Project Owner has the same RBS value as the User check box.
  • You add the newly created security group to this category and select the View Project Site check box.
  • The project manager creates a new Enterprise project and publishes the project.

  In this scenario, the user is added into the Team Member SharePoint security group in the SharePoint site of this project, which is unexpected. This gives the user contributor rights to the content in the project site instead of reader rights.

• Consider the following scenario:Assume that you start Project 2013 and connect to Project server, then you open a project. When you try to add new dependencies for the project by clicking the Add new dependency… link in the deliverable pane, it takes longer time than expected to load and returns the following error message:
  • You create a new enterprise custom text field, and you select the Behavior controlled by workflow check box.
  • You add the custom field to the Project Information project detail page.
  • You create a new enterprise project type, and you select Project Information for the New Project Page field, and then you select Project Information for the Available Project Detail Pages field.
  • You create a new project by using the newly created enterprise project type, and you change the value of the date fields in the Project Information page, and then you save the project.

  In this scenario, when you refresh the page, the value of the date fields, such as the project start date, are not saved as expected.

• An unspecified error has occurred.Error Code:0 ErrorMessage: The argument value is not valid.

  Additionally, Project’s connection state changes to Work Offline.

• Assume that you can access a given Team Builder view by clicking Build Team button in the Projects tab in PWA. Then, your access permission to this Team Builder view is removed. However, you still have access permission to other Team Builder views. When you try to visit other Team Builder views by clicking Build Team, you receive the following error message:
  Access Denied.
• Consider the following scenario:
  • You create an Active Directory group and add a user to the group, and the user name contains semicolon.
  • You sync the Active Directory group to a security group in PWA.
  • You click Regional Settings in the Site Settings page, and then you change the Locale, for example, to Swedish.
  • You start Project Professional 2013 to create a project that contains a task, you assign the user to the task, and then you save and publish the project to Project server.
  • You create a new task for this project in PWA, and then you try to copy the user name from the original task and paste it to the Resource Name column for the newly created task.

  In this scenario, a red bullet that indicates an error appears on the left of the task.

• Consider the following scenario:Assume that you delete the default out-of-the-box Tasks Summary project view in a Project Server 2010 server, and then you upgrade from Project Server 2010 to Project Server 2013. When you log on to PWA and try to access the Project Center, you receive the following error message:
  • You start Project 2013 to create a project that has a budget cost resource assigned to a project summary task.
  • You set a value for Budget Cost in the Task Usage view or in the Resource Usage view.
  • You insert the Baseline Budget Cost column in the Gantt Chart.
  • You save a baseline for the project, and the Baseline Budget cost becomes the same value as you set for the Budget Cost.
  • You save and publish the project.
  • You query the reporting database and find the Baseline Budget Cost as expected.
  • You perform a reporting database refresh operation.

  In this scenario, when you query the Reporting Database (RDB), the Baseline Budget cost is missing.

• You do not have sufficient permissions to view the specified page. Please contact your administrator for permissions to view this page.
• Consider the following scenario:
  • You create a project and assign a resource to a task.
  • You set a baseline for a project in Project 2013, and you save it.
  • You change the units of the resource assignment, and you set a new baseline (Baseline 1) for this project.
  • You save and publish the project to the Project server.

  In this scenario, the cumulative baseline by day data is incorrect in the reporting database because it was aggregated across all baselines.

October 2014
Individual – http://support.microsoft.com/kb/2889959/
DB Version – 15.0.4659.1001

• After you install the June 2014 cumulative update for Project Server 2013, the Project Professional Versions setting does not work correctly. Therefore, you may be unable to edit a project, preview updates, or apply status updates in Project Web App.
• Assume that you enable the Only allow task updates via Tasks and Timesheets option. When you edit a project in Project Web App, and try to delete a protected task, you receive no error message. Additionally, the task disappear from the list until you refresh the page.
• Assume that you set a value for the Maximum Hours per Day setting. The setting is ignored when a user makes use of the Send a progress for… feature from the Timesheets page.
• Project Queue service might process jobs slowly when there are many pending jobs.
• You may be unable to edit a project, preview updates, or apply status updates through Project Web App. Additionally, if you apply status updates, you may see an error similar to the following in the ULS logs:
  StatusingInternalError. Details: Status approval internal error Attributes: System.TimeoutException: This request operation sent to net.pipe://localhost/pscalc_ef84be5e83f242fa81604afdf9348d52 did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout.
• Assume that you have a project that contains a resource whose display name contains a colon (:). If the project has an associated SharePoint site, you may be unable to publish the project to a Project Server 2013 server.
• When you change the view of the Project Center page and apply a different filter or grouping, the filter option and the grouping option do not change as expected. Instead, the view may still be filtered or grouped based on the previous view.
• Consider the following scenario:
  • You add a task to a project in Project 2013, and then you add to the task a note that contains a special character such as a vertical tab.
  • You publish the project to a Project Server 2013 server.
  • You log on to the project site through Project Web App, and then you browse to the Task page.

  In this scenario, the Task page is not loaded.

• Consider the following scenario:
  • You create a custom field that uses a lookup table, and you allow multiple values to be selected.
  • You insert several tasks into a project, and then you select values from the custom field for the tasks.
  • You save and publish the project.
  • You change the value of the custom field for one of the tasks, and then you save the project.
  • You change the value of the custom field on the other tasks, and then you save the project.
  • You publish the project.

  In this scenario, the value of the custom field for the tasks may be incorrect when you query the value from the reporting database tables.

• Consider the following scenarios:
  • You create a lookup table in Project Web App (PWA), and the lookup table contains multiple values. The total length of the values exceeds 255 characters.
  • You create a custom field that uses the lookup table, and you set the option that requires information in this field.
  • You create a project in PWA for the custom field, you select multiple lookup table values, and the total length exceeds 255 characters.
  • You save, check in, and then close the project.
  • You open the project in Project Professional.
  • You make a change in the project and then save it.

  In this scenario, the project cannot be saved, and you may receive the following error message:

  Project cannot save the project to Project Web App. You must first specify values for all required project fields. These fields are indicated with an asterisk in the Project Information dialog box, available from the Project tab.

  In another scenario, you add resources to tasks from PWA.

  • You have multiple resources defined in your server, and the combined length of the names exceeds 255 characters.
  • You go to the Project Center in PWA, drill into a project, select the Schedule project detail page, and then you click the Edit button.
  • You go to the Resource Names field for a task and select multiple resources. The total length of the names exceeds 255 characters.
  • You save and then close the project.
  • You open the project.

  In this scenario, some of the resources that you added to the task are not saved. For the resource names that straddle the 255 character limit, only partial resource names are displayed. To resolve these issues, you must install both the fixes in this knowledge base article, and you must also install the fix in KB 2889957.

• Consider the following scenario:Consider the following scenario:
  • You create a custom list, and you add a lookup column to the list, and then you create an item in the list.
  • You log on to the Project Web App site as Project Manager.
  • You browse to the list, and you select the item, and then you click the Create Projects button.

  In this scenario, you may receive the following error message:

  Sorry, this site hasn’t been shared with you.
• • You create a custom field, and you check the check box of the Behavior controlled by workflow option.
  • You add the custom field to the Project Details page.
  • You open and edit a project in the Project Details page.
  • You change the value of the custom field, and you change another value for the other field such as the Start Date of the project, and then you save the project.

  In this scenario, when you refresh the page, the value in the custom field is not saved, and the Start Date is reverted to the previous date.

September 2014
Rollup – http://support.microsoft.com/kb/2883072
Individual – http://support.microsoft.com/kb/2889856
DB Version – 15.0.4649.1001

• Assume that you edit the resource plan of a project in Project Web App by using Windows Internet Explorer 10 or Windows Internet Explorer 11. When you save and close the resource plan, it is still in a checked-out state.
• Assume that you enable multiple authentication providers for a Project Server 2013 server. Then, you create a user account in Project Web App. When you try to edit the user from the Edit User or Edit Resourcepage, you may receive the following error message:
  Multiple entries matched, please click to resolve.

  In addition, there is a red squiggly line in the people picker field.

• When you use a Project Server Interface (PSI) application to update a project level enterprise field that uses formulas, the values of the field may be lost.
• Assume that you set the date format to “dd/mm/yyyy” for a Project Server 2013 server. The Custom Date Range filter on the Timesheet page may change unexpectedly when you click the Apply button.
• The resource name that is written to the dbo.MSP_TimesheetResource reporting table becomes different after the approval of a timesheet or a status update. Therefore, it is difficult to do a report that is correlated by resource name.
• Assume that you create a project level custom field that uses a formula, and the formula refers to other custom fields. Then, you change the values of the other custom fields and then click the Save button in the Project Details page in Project Web App. In this situation, the project level custom field does not always calculate as expected.
• A project reporting publish job may fail. Additionally, the Reporting (Project Publish) queue job error resembles:
  The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmAssignmentBaselineByDay_ProjectUID_AssignmentUID”. The conflict occurred in database “PWA”, table “dbo.MSP_EpmAssignmentBaseline”. The statement has been terminated.
• Consider the following scenario:
  • You create an Active Directory group and add a user to the group.
  • You sync the Active Directory group to a group in Project Web App (PWA).
  • You delete the user from the Active Directory group.
  • You execute the sync operation again.

  In this scenario, the user is still active in PWA.

• Consider the following scenario:Consider the following scenario:
  • You select the Allow users to choose option in the Project Site Provisioning Settings page.
  • You create a rule that enables Automatically run this rule option, and the Automatically publish the updates option is selected in the Edit/Create Rule page.
  • You create a project, assign a task to an enterprise resource in Project 2013, and then you publish the assignment.
  • The user who owns the assignment enters progress against the task.

  In this scenario, when the user sends an update for approval by clicking the Send Status button in the Tasks page, there is an error message in the queue resembles the following:

  Queue:?GeneralQueueJobFailed (26000) – CreateWssSite.CreateWssSiteMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’c2cd523c-9ec1-e311-beee-00155d4a810b’ JobUID=’bfc3b935-9ec1-e311-beee-00155d4a810b’ ComputerName=’1c1a4290-cfc3-40a9-981b-bfe9e25c9982′ GroupType=’CreateWssSite’ MessageType=’CreateWssSiteMessage’ MessageId=’1′ Stage=” CorrelationUID=’ed3f869c-4723-1009-c998-2ee8b732a4c4′. For more details, check the ULS logs on machine 1c1a4290-cfc3-40a9-981b-bfe9e25c9982 for entries with JobUID bfc3b935-9ec1-e311-beee-00155d4a810b.

  Additionally, the job owner is listed as the user who sent the update.

• • You enable single entry mode on a Project Web App (PWA) site on a Project Server 2013 server.
  • You delete the default My Work view for the Timesheet page.
  • You create a project and assign a task to a resource.

  In this scenario, the resource cannot create a new timesheet.

August 2014
Individual – http://support.microsoft.com/kb/2883083
DB Version – 15.0.4639.1000

• Assume that you sort the items in the Approvals page by the Remaining Work field in Project Web App. When you browse to the Approvals page again, you may receive an error message that resembles the following:
  General Unhandled Exception in _Statusing.ReadStatusApprovalsForProjectForGridJson_
• If an error occurs when you approve and apply status updates to a project, the status approval may still show that it is successfully applied.
• You may be unable to open a timesheet that contains a specific field in a specific case. Additionally, you receive an error message that resembles the following:
  The View failed to Load…
• You may be unable to send status update by clicking the Send Progress for all Tasksbutton. Additionally, you may receive an error message that resembles the following:
  An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary.

  When you click OK, you receive an error message that resembles the following:

  __Error loading
• You may be unable to edit or apply status updates to a large project in Project Web App.
• When you create a resource that contains more than one rate in Project Web App, duplicate rows are displayed for the resource in the hired resources report.
• If you publish many projects to a Project server in a very short time span, the “Synchronize Project Web App Permissions to Project Site” user synchronization job may fail and you may no longer be able to access the given project site.
• You may be unable to publish a project to a Project 2013 server. Additionally, the publish error resembles:
  The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmAssignmentBaselineByDay_ProjectUID_AssignmentUID”. The conflict occurred in database “PWA”, table “dbo.MSP_EpmAssignmentBaseline”. The statement has been terminated.. Details: id=’24006′
• Assume that you approve a status update from Project Web App. When you open the project in Project Professional 2013, the actual work may not apply to the project.
• Assume that you create a project in Project Web App from a template that contains an inactive task. When you open the project and activate the inactive task in Project Professional 2013, the schedule may not change correctly based on the duration information.

July 2014
Rollup – http://support.microsoft.com/kb/2882990
Individual – http://support.microsoft.com/kb/2882995
DB Version – 15.0.4629.1000

• When you save and publish a project that has baseline data with negative cost values, the cost values in the Reporting database may be incorrect. For example, a fixed cost of negative $5 distributed over 5 days should be -$1/day. Instead, it is displayed as $0/day.
• If you publish many projects to a Project server in a very short time span, the “Synchronize Project Web App Permissions to Project Web App” user synchronization job may fail and you may no longer be able to access the given project site.

June 2014
Rollup – http://support.microsoft.com/kb/2881062
Individual – http://support.microsoft.com/kb/2880489 and http://support.microsoft.com/kb/2837680
DB Version – 15.0.4615.1000

• When you open the Server Settings > Quick Launchpage, you may find that the ribbon is disabled. Additionally, you receive an error message that resembles the following:
  It seems like the order of the items in the Quick Launch has changed unexpectedly. This could have been caused during the upgrade or as a result of modifying the Quick Launch table in the Project Database. You can use this page to update and fix the order of these items. Make sure to save your changes at the end.
• Assume that you have a loop in a workflow, and the two stages in the loop are in the same phase. The Workflow Status Web Part cannot load when you open the Workflow Stage Status page after one roundtrip in the loop.
• When you try to edit or apply status updates to a project in Project Web App that contains many complex custom formula fields, the operation fails. Additionally, you receive an error message that resembles the following:

Sorry, something went wrong. An unexpected error has occurred.

• When you approve a status update in Project Web App, the status of the associated timesheet as seen in the reporting database changes unexpectedly.

Assume that you have a local custom field that is defined to include a lookup table, and yet the table is missing. When you save the project to the Project server, the save operation fails. Additionally, you receive an error message that resembles the following:

May 2014 – (April re-release)
Individual – http://support.microsoft.com/kb/2880484
DB Version 15.0.4605.1000

• When you create deliverables directly in a SharePoint site that has the Project Web App Connectivity feature enabled, you cannot see the deliverables in Project Professional 2013.
• When you try to update project-level fields such as “owner” or “description” in Project Web App on a project that contains multiple formulas, the update times out, and you receive the following error message:
  An error has occurred when saving your project to the server. Please contact your administrator for assistance.
• Assume that you have an accepted or rejected timesheet that includes a line for a task that is reassigned, deleted, or unpublished. When you open the timesheet, it cannot be displayed. Additionally, you receive the following error message:
  The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
• When you send status updates to a task that belongs to a master project upon approving the status updates, the changes are not seen, and they are lost.
• If you do not have the Save Unprotected Baseline permission, you can still save baselines in a Project View in Project Web App Schedule Web Part unexpectedly. Additionally, when you try to save baselines in a Project view in Project Web App Schedule Web Part, you receive the following error message if you correctly have the Save Unprotected Baseline permission:
  Cannot clear or Save Baseline. You do not have the adequate permission to clear or save baselines to baselines <number>.
• When you create a project site that contains multiple issues lists in a project, you cannot publish the project. You also see an error in the queue that resembles the following:
  General•Reporting Wss list sync failed:?ReportingWssSyncListFailed (24018) – 1100. Details: id=’24018′ name=’ReportingWssSyncListFailed’ uid=’9ad16b75-059f-e311-8481-00155dec4705′ SPListType=’b20c6cbb-f59e-e311-b49a-402cf488d340′ Error=’1100′.

April 2014
Individual – http://support.microsoft.com/kb/2863881
DB Version – 15.0.4605.1000

• When you assign a resource to a task through Schedule Web Part, the resource assignment does not propagate to the reporting tables correctly in the database. For example, a resource assigned to a task is associated incorrectly with the unassigned resource.
• When you try to open a project from a project server and the project does not already exist within the Project Professional active cache, it may take longer than expected.
• You run a macro that sets the duration of a custom duration field for a task in a project in Project 2013. When you save and then reopen the project, you receive the following error message:
  Invalid Duration

  This is not a valid duration, or is outside the range for this field.

  Type a duration in the correct format: for example, 4 hours (or 4h), 12 days (or 12d), or 2ed for elapsed days.
• If there is budget resource assignment on a project summary task, you are unable to load any assignments through the client-side object model (CSOM) for the project.
• When you create a security category, category rule is ignored that results in incorrect effective permissions.
• You are unable to use a rule in the approval center to compare the Assignment Finish field with the Assignment Baseline Finish field.
• When you try to level resources in some projects that contains combinations of task constraints, Project may crash.
• After you upgrade from Project 2010 to Project 2013 and the default out of the box view is deleted, default views are unable to load for Project Center, Project Details and Resource Center. Additionally, you receive the following error message:
  The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

  If you click OK, you receive the following error message:

  You don’t have permissions to view any projects.
• When you click the New Project button in Project Center, you are unable to see the enterprise project types in the order that you have specified in their definition.
• Assume that you add some users to a project and the project is published. After the user synchronization process is complete, not all users are added to the project’s SharePoint site in the given SharePoint security group as expected.
• Assume that you have a project level enterprise custom field (ECF) that is defined as controlled by workflow. Then, you set the field to a value in Project Web App. When you view the custom field in Project Professional 2013, the ECF is displayed as zero.
• When you try to save a project without filling in values for workflow controlled required fields for the stage that the project is currently in or for globally required fields, you receive the following error message:
  Specify values for all required custom fields.
• When you view a resource plan, then enter work daily and finally set the plan to display the work on an hourly basis, the incorrect value is seen. For example, the calendar and default hours per day setting specifies 7.5 hours yet the value in the resource shows 8 hours.

April 2014 – Service Pack 1 (Re-release) Description of Project Server 2013 SP1 – http://support.microsoft.com/kb/2880553
List of fixes – http://download.microsoft.com/download/0/A/8/0A870358-D451-488E-BF54-9616292E19EC/Microsoft%20Office%20and%20SharePoint%202013%20Service%20Pack%201%20Changes.xlsx
Download –  http://www.microsoft.com/downloads/details.aspx?FamilyId=cbc2a006-638b-482b-9604-43bddda66ac0
DB Version – 15.0.4569.1000

February 2014 – skipped as Service Pack 1 was coming out.

December 2013
Individual – http://support.microsoft.com/kb/2837668
DB Version – 15.0.4525.1000 (not actually updated in Dec 2013 – same as August 2013)

• Assume that you change values for fields such as Project Owner and Name on a Project Detail Page (PDP) in Project Web App. When you save and refresh the page, the values are reverted to what they were before the change.
• You cannot enter complex link types in Schedule Web Part for a task in Project Web App. For example, you cannot enter relationship type and lag and lead time.

October 2013
Individual – http://support.microsoft.com/kb/2825659
DB Version – 15.0.4525.1000 (not actually updated in Dec 2013 – same as August 2013)

• Consider the following scenario:
  • You have a project in Project Server 2013.
  • You set a baseline for a milestone task.
  • You try to save and publish the project.
• In this scenario, you cannot publish the project successfully. Additionally, the Project Server Queue Job Error Detailscontains information that resembles the following:

ReportingProjectChangeMessageFailed (24006) – Object reference not set to an instance of an object.. Details: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’2d2c33cf-6024-e311-ab17-00155dec2002′ QueueMessageBody=’Project UID=’18cbcfc1-6024-e311-80b1-402cf488d340′. PublishType=’ProjectPublish” Error=’Object reference not set to an instance of an object.’.

• Although you can set up Active Directory group synchronization in Project Server 2013, the timer process never starts, and the security groups are never synchronized.

August 2013
Rollup – http://support.microsoft.com/kb/2817615
Individual – http://support.microsoft.com/kb/2817508
DB Version – 15.0.4525.1000

• When you change the color of a Gantt chart bar in Project Web App, the wrong color is displayed.
• When you change the pattern of a Gantt bar in Project Web App, the wrong pattern is displayed.
• You cannot change the start or end date of a fiscal period on the Fiscal Periodspage in Project Web App. Additionally, when you try to change a start or end date, you receive the following error message:
  Project Web App fiscal periods are not allowed to have duplicate names, gaps or overlaps between adjoining period start and end dates, or overlaps between adjoining fiscal years.

March Public Update – http://support.microsoft.com/kb/2768001 See the KB for all issues fixed as the package is SharePoint as well – these are the Project fixes:

• Assume that a pinned task is split into two parts in Microsoft Project 2013. When you change the duration of the pinned task in Task Usage view, the duration of the task is calculated incorrectly.
• Assume that you create two tasks that you must manually schedule in Project 2013 and then assign the same resource to both tasks. When you assign a duration of time that includes nonworking days to the tasks, the resource-leveling feature does not work correctly.
• After you upgrade Microsoft Project Server 2010 to Project Server 2013, you cannot access document libraries and issues or risks lists in Project Server 2013.

February 2013 – No server release – included in the March PU RTM DB Version – 15.0.4420.1017