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.

From February 2015 onwards all fixes are shipped in Public Updates.  From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center.

From April 2015 onwards fixes have a pre-requisite of SP1 – please ensure all components are patched to SP1, including any language packs you may have installed.

They are listed in reverse date order – newest at the top.  The PU/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.  I have 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.

June 2017

Rollup – https://support.microsoft.com/en-us/help/3203429/june-13-2017-cumulative-update-for-project-server-2013-kb3203429

Individual – https://support.microsoft.com/en-us/help/3203399/descriptionofthesecurityupdateforprojectserver2013june13,2017

Database schema updated to 15.0.4937.1000

Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issues:

  • Suppose you go to the Project Center page in the Project Web app and select many projects. When you click the Open In Microsoft Project option, nothing seems to happen, and the expected master project isn’t created in Project Professional. Now, when you’ve selected more projects than can be used to create a master project via this method, you’ll see a message similar to this:

Your selection exceeds the limit for the number of projects we can open at a time from Project Web App. We created a master project with the supported number of projects. You can then add additional projects by going through Insert Subproject.

  • Added auditing capability to determine when and who changes the “Only allow tasks updates via Tasks and Timesheets” and tracking method Task Settings and Display server settings. When changes are made on the Task Settings and Display page, details are written to the ULS logs under the Project Server Administration category and look similar to these:

PWA:http://server/PWA, ServiceApp:Project Service Application, User:i:0#.w|domain\user, PSI: WS_ADMIN setting WADMIN_PROTECT_ACTUALS changed. New Value: 0. Old Value: 1. Resource Id: xxx

PWA:http://server/PWA, ServiceApp:Project Service Application, User:i:0#.w|domain\user, PSI: WS_ADMIN setting WADMIN_DEFAULT_TRACKING_METHOD changed. New Value: 1. Old Value: 2. Resource Id: xxx

  • This update also fixes the following issues:
    • Consider the following scenario:
      • You have a series of tasks that are linked.
      • Because of the way that the tasks are scheduled, the successor tasks don’t necessarily start and finish at the day boundaries. For example, start at 8:00 AM and finish at 5:00 PM.
      • A resource is assigned to the tasks, and they are published.
      • The resource completes the work on the tasks entering all actual work on a given date and sends the status update to the project manager for approval.
      • The project manager approves the updates.

In this case, the start date of the given tasks may be different than what’s expected. For example, show an actual start time of 9:10 AM whereas in another case it may show 8:00 AM. This issue occurs because the order in which the status updates were applied was not consistent.

  • Consider the following scenario:
    • A project manager publishes a task to a team member.
    • The team member in either a timesheet or in tasks within the Project Web app reports work that’s earlier than what was scheduled. For example, 8h of work was scheduled on Wednesday but 8h of actual work was reported and submitted for Monday.
    • The status manager approves the update.
    • The team member zeros out the actual work and moves it to a later date.
    • The status manager approves the update.
    • The project is opened in Project Server.

In this situation, the task’s actual start date still reflects the earlier update instead of the new update where the actual start date is later.

  • When a Project server is processing a huge number of timesheets, the Reporting (Timesheet Save) jobs may fail. In the ULS logs, you may see an error similar to this: ReportingTimesheetSaveMessageFailed (24014) – A network-related or instance-specific error occurred while establishing a connection to SQL Server.
  • After you close a project resource plan, the resource plan isn’t check in.
  • The performance of the Approval Center PWA page is poor. This issue occurs after you install the January 12, 2016, update for Project Server 2013 (KB3114507).
  • User generated (ad hoc) custom filters that are applied to PWA views don’t display data values. For example, you open a custom filter dialog box in Project Center to add a filter on a date column. After you save, close, and then reopen the dialog box, the date you set isn’t displayed.
  • When you submit a status update, task-level baseline data disappears from the Tasks view for the given task assignments.
  • Server-side defined timesheet view grouping doesn’t work with custom fields.

To fix the following issue, install June 13, 2017, update for SharePoint Foundation 2013 (KB3203398).

When you add new tasks to a project while editing a project in PWA, formulas that use the Now() or CurrentDate() function don’t calculate the correct result.

May 2017

Rollup – https://support.microsoft.com/en-us/help/3191912/may-9-2017-cumulative-update-for-project-server-2013-kb3191912

Individual – https://support.microsoft.com/en-us/help/3191890/description-of-the-security-update-for-project-server-2013-may-9-2017

No database schema update this month – so will be set or stay at 15.0.4911.1000

This security update fixes the following nonsecurity issues:

April 2017

Rollup – https://support.microsoft.com/help/3178728/

Individual – https://support.microsoft.com/help/3191824

Database schema updated to 15.0.4919.1000

Correction – database schema NOT upgraded this month – will still be 15.0.4911.1000

This update contains the following improvements and fixes:

  • You have a required custom field with a lookup table and with a default value defined. When you create a project through a project detail page, the custom field isn’t pre-filled with the default value. Instead, you have to select a value from the dropdown manually.
  • Screen readers don’t identify that the Delegate Name and the User Name fields on the Add Delegation page are required.
  • On the Manage Queue Jobs page, the dates in the From and To in the Job History section don’t work as expected. For example, you may not be able to set a date in order to see jobs from previous days.

March 2017

Rollup –  https://support.microsoft.com/help/3172462

Individual –  https://support.microsoft.com/help/3178625

Database schema updated to 15.0.4911.1000

This update fixes the following issues:

  • The Visual Basic Applications ScreenUpdating property does not work as expected in Project 2013. Instead of freezing the screen content when the code runs, the screen continues to update. This produces screen flicker and causes the code to run slower.
  • In some cases, enterprise custom field data may be lost from a project after a status update has been applied, and the project is then opened in Project Professional 2013.
  • Assume that you open a project plan, and transfer local resource custom field lookup table values to an enterprise resource enterprise field. Then you save the project plan to a Project server. In this situation, some custom enterprise resource lookup table values may be lost.

February 2017

Just an individual package this month – https://support.microsoft.com/help/3141525

Database schema updated to 15.0.4903.1000

This update fixes the following issues:

  • After you edit a project in PWA, formulas that rely on the Now() function and the [Current Date] property aren’t calculated.
  • When multiple user and group synchronization jobs run in parallel, SQL deadlocks may occur. This issue may cause orphaned records in the MSP_WEB_SECURITY_PSMODE_PERMISSION_SYNC_STATES table that may also cause poor synchronization performance and large amounts of disk space consumed by the orphaned rows.
  • Assume that a task is locked while a status update is pending, and then the project is checked in. In this situation, the status updates history page shows the update is both applied and published. However, the published job has not occurred.
  • When you edit a project in PWA, you receive the following error message if the project summary task has a budget resource assigned:

    The view failed to load.

  • When you update a task on a timesheet, the Process Status field on other untouched tasks may be incorrectly changed to Not Submitted.

January 2017

Rollup – https://support.microsoft.com/en-us/kb/3141480

Individual – https://support.microsoft.com/en-us/kb/3141484

DB Version – No update this month, so still 15.0.4883.1000 from December.

  • On a Brazilian Portuguese Project Web App home page, the timesheet reminder uses the term Unsubmitted instead of Não enviados.
  • Fixes the following bugs:
    • Status updates aren’t applied and the Project Calculation Service (PCS) returns an internal error even though the queue job shows no error.
    • Consider the following scenario:
      • The server is set to use single entry mode.
      • You enter time on a task and save the timesheet without submitting it.
      • A project manager deletes a task that has the saved time.
      • You go to submit the timesheet or send a status update for the timesheet.

      In this scenario, you receive the following error message:

      An error occurred while communicating with the server.
    • When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
    • Assume that you apply a change to a timesheet line in which the Process Status value appears as Awaiting Approval. In some cases, the status of the timesheet line is incorrectly changed to Approved and reporting also incorrectly shows the line as Approved.
    • Consider the following two scenarios:
      • From the Project Center, you drill into a project and choose to edit it. The process fails and you have to try the process again.
      • A project is updated programmatically through some custom code and the Project Update from a PSI queue job fails at 50%.

      In both scenarios, you receive the following error message in the ULS logs:

      FilterSEH: The server encountered a very serious error but will continue to function. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION).

      You may also find that the error message is generated when a status update is applied to a project even though the status update is successfully applied during the retry operation.

December 2016

Rollup – https://support.microsoft.com/en-us/kb/3128003

This cumulative update package fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Individual – https://support.microsoft.com/en-us/kb/3128009

Fixes the following bugs:

  • Updates the translation of the check in confirm dialog box in Ukrainian when you close a changed project in PWA.
  • Fixes the following bugs:
    • If you have work in a resource plan and save or submit a timesheet which contains nonworking time and overlaps the dates of the resource plan, your work values in the resource plan may change.
    • Consider the following scenario:
      • You enter time on a task in your timesheet and then submit the timesheet.
      • You enter time on the same task in a following timesheet and then save the timesheet.
      • You go back and recall the earlier timesheet.
      • You change time on the task and then resubmit the timesheet.
      • You go to the following timesheet and then add more time to the task.
      • You submit the timesheet.

      In this scenario, the updated task isn’t submitted for approval.

    • When you publish a project, the SharePoint Visitors security group on the project site is truncated (users are deleted). This issue occurs even though the Enable Project Site Sync Project Permission sync setting is disabled.
    • When a team member views a task’s status history, the accepted date of an update is incorrectly displayed as the submitted date. Similarly, when the status manager views the Status Update History page, the approval date is incorrectly displayed as the submitted date.
    • Changes to enterprise custom files within timesheets aren’t submitted as a part of a status update. This issue occurs after you install September 13, 2016, update for Project Server 2013 (KB3118285).

November 2016

Rollup – https://support.microsoft.com/en-us/kb/3127931

This cumulative update package fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Individual – https://support.microsoft.com/en-us/kb/3127937

Fixes the following bugs:

  • Tasks, resources, or assignments, which are created, for example, with client-side object model (CSOM), and use the same UID as the Project UID, cannot be edited in Project Web App (PWA).
  • Making changes to timesheet lines may change the TASK_PUBLISHED_UID field of other timesheet lines.
  • List properties such as MSPWAPROJUID were not set as expected. Therefore, accessing these properties returns NULL.

October 2016

Rollup – https://support.microsoft.com/en-us/kb/3118365

Contains fixes from:

 

Individual – https://support.microsoft.com/en-us/kb/3118370

DB Version – 15.0.4867.1003

  • Translates a new string in multiple languages to enable third-party screen readers to recognize it on localized sites of Project Server.
  • Fixes the following issues:
    • When you use a screen reader, it doesn’t tell you whether some fields are required on a project details page. Additionally, if a custom field is associated with a lookup table, the screen reader displays no context for that, and it doesn’t tell you that there are lookup table values.
    • Windows SharePoint Services user synchronization fails.
    • When you edit a OneNote notebook, the queue job performance is affected. This update optimizes the Project Sync Jobs trigger.

September 2016

Rollup – https://support.microsoft.com/en-us/kb/3118274

Contains fixes from:

Individual – https://support.microsoft.com/en-us/kb/3118285

DB Version – 15.0.4855.1000

  • If the farm administrator upgrades a Project Server 2010 database and has non US-en settings, the process may fail with an error message that resembles the following:

    ConvertTo-SPProjectDatabase : Action 15.0.10.0 of Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence failed.

    At line:1 char:1

  • Workflow fails (internal status turns to canceled) if the status information text contains an ampersand “&”.
  • When you create a project from a SharePoint task list, queue jobs related to workflows that are associated with the list may fail. For example, the “Reporting (Enterprise Project Type and Workflow Information Sync)” jobs may display failed.
  • After you delete a value from a custom field on the My Tasks page, the change isn’t saved and the value comes back when you go to the My Tasks page again.
  • When you update a task on a timesheet, the Process Status field on other untouched tasks may be incorrectly changed to “Not Submitted”.
  • Document properties update in Project site document libraries could lead to a flood of Reporting (Project Sync) jobs in the Project Server queue if there’s also a workflow that’s applied to the document library.

August 2016

Rollup – https://support.microsoft.com/en-us/kb/3115448

DB version – 15.0.4849.1000

Contains fixes from:

KB3115456 – Project Server stand alone

KB3115454 – SharePoint Foundation

KB3115458 – SharePoint Foundation

KB3115445 – SharePoint Foundation

Individual – https://support.microsoft.com/en-us/kb/3115456

  • After you copy and paste a task from the schedule project detail page, the duration of the pasted task appears incorrect. For example, the duration of a task is 1 emon (one elapsed month). After you copy and paste the task, the duration is displayed as 1.01 emon.
  • After earned values are calculated in Project Web App (PWA) from the schedule project detail page, the values may not be saved, which means the published views of the earned value may not be accurate.
  • A server-side correlation cancelation on a save job causes deferred jobs to be canceled. For example, a team member submits time against a task and the status manager approves the update. Then, the project is checked out and the Status Update job state is listed as Skipped for Optimization. If a future save on the given project is canceled for whatever reason, the Skipped for Optimization status update job is also canceled.
  • Assume that you have created a Text type project level enterprise custom field, and it’s defined to allow multiple lines. Then, you navigate to a project detail page where the Start field and the previously mentioned field are present. When you then make a change to the Start date and save the changes, the start date isn’t saved. Likewise, changes to the custom field are also not saved.
  • When you add a task to a timesheet, the Select from Existing Assignments dialog box can’t be displayed so you can’t add the task. Instead, you receive the following error message:

Sorry, something went wrong

An unexpected error has occurred.

July 2016

Rollup – https://support.microsoft.com/en-us/kb/3115291

Individual – https://support.microsoft.com/en-us/kb/3115295

  • Translates some terms in multiple languages to make sure that the meaning is accurate.
  • Fixes the following issue:
    If you have an enterprise custom field that has a formula that references a custom field with a lookup table, the value may not be set correctly.

June 2016

Rollup – https://support.microsoft.com/en-us/kb/3115172

Individual – https://support.microsoft.com/en-us/kb/3115179

DB Version – 15.0.4833.1000

  • Improves performance of Project Server Enterprise Resources CSOM API if there’s a large number of resources.
  • Updates the translation of the project check in dialog box to make sure that the meaning is accurate.
  • On the Manage Timesheets page, a screen reader can’t determine which cell is selected and therefore it can’t read out the information in the cell to the user.
  • When you create a project in Project Web App and then you save, close and check in the project, it takes a long time before the page goes back to the Project Center. You may also see an informational dialog which states that it’s taking a long time and suggests that you check the queue. This problem may occur when the “Prepare Project Web App Permission Synchronization For Projects” queue job takes a long time. This is possible if there’re many user accounts in the server.
  • When you edit and publish a project through the Project Server Interface (PSI), the outline numbers of tasks aren’t updated to the reporting schema.
  • Assume that you make a migration from Project Server 2010 to Project Server 2013. When you edit a resource, you receive the following error message:
    The resource could not be saved due to the following reasons: A resource availability contour cannot go outside the range of the resource’s earliest and latest availability dates.
  • If project sites are created on a different site collection than Project Web App, the Web Admins group is created but never synchronized.
  • If the submitted actual work hasn’t yet been applied to a project, the related enterprise resources can be deleted.
  • Timesheet page fails to load, and 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.

    Note This issue occurs after you install February 9, 2016, update for Project Server 2013 (KB3114737).

  • Assume that you view a project on which there’s at least one task that doesn’t have a resource assigned. When you edit the project and switch from a task view to an assignment view that also has a task ID field, the view gets stuck in a loading state.
  • The Project.CreateProjectFromTemplate PSI method creates inaccessible projects because the project owner doesn’t get properly set.
  • The approval date is incorrectly displayed as the submitted date in Status Update history.
  • The Edit page function doesn’t work as expected in Project Web App. For example, the ribbon appears dimmed and the Web Part menu can’t be edited. This issue occurs after you install February 10, 2015 update for Project Server 2013 (KB2880996).
  • Assume that your Project Web App UI language is French, and exporting the Resource Assignment view to an Excel workbook fails. In this situation, if you try to open the .xlsx file, you receive the following error message:
    We found a problem with some content in ‘xxx.xlsx’. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes.

    If you click Yes, then it opens in Excel, but you see other errors pointing you to the problem.

May 2016

Rollup – https://support.microsoft.com/en-us/kb/3115024

Individual – https://support.microsoft.com/en-us/kb/3115036

DB Version – 15.0.4819.1000

  • When you try to edit the name of an enterprise resource in your project, a better translation is available for the Japanese language for the following message that appears:

    Changes to enterprise resources will be lost.You can modify an enterprise resource in a project for modeling purposes and publishing the project will include any changes. Your changes will be overwritten when the project is next opened.

  • Fixes the following issues:
    • On your timesheet, you enter an actual work value that’s after the task start date or you enter an actual start date that’s after the task’s start date. When the status update is applied to the project, the task’s actual start date isn’t updated accordingly to the assignment actual start date.
    • Assume that you press the Tab key to move the focus on a column header on the Manage Timesheets page. Then, you press the Enter key in order to sort by this field. In this situation, the focus is lost from the column header, and you have to press the Tab key many times in order to return to the column header.
    • Self-assigned timesheet lines may display an incorrect TASKUID in the OData feed.
    • The project start date on a project detail page, such as Project Details, is different from the date in the Project Information dialog box in Project Professional 2013.
    • When you try to query OData from a workflow in Project Server 2013, an access denied error message is displayed.
    • Consider the following scenario:
      • You have an enterprise project level flag field defined.
      • You have this field displayed on a Project Detail Page (PDP).
      • A user goes to the PDP page and by-default sees the value of No.
      • The user saves and moves to a different PDP page.
      • The user then goes to a different or the previous same PDP page.

      In this case, the value is empty or NULL versus the expected No value.

April 2016

Rollup – https://support.microsoft.com/en-us/kb/3114936

Individual – https://support.microsoft.com/en-us/kb/3114950

DB Version – 15.0.4815.1000

  • If dependencies between tasks in a project have unusually large lead times or lag times, saving the project in Project Web App may fail, and you receive the following error message:
    An error has occurred when saving your project to the server. Please contact your administrator for assistance.
  • After you change the start date of an assignment on the My Tasks page or the Timesheet page in Single Entry mode, actual work on the assignment is changed unexpectedly.
  • After you change project-level custom fields in a project through the Client-Server Object Model (CSOM), the project schedule may be changed unexpectedly.
  • Even though you have already installed Project 2013, you may still receive the following error message from PWA:
    Action Not Available.
    Project Professional needs to be installed to open the project. Install Project and try again.
  • Project Server doesn’t always test the checked-in status of a project correctly. Therefore, if a project is checked-out, there may not be a proper notification and a workflow running on the project may fail.
  • After you change the booking type of a resource in a project, the booking type of the resource’s assignments aren’t updated to reflect the new booking type.
  • Pending status updates may not be applied to a project upon check-in. Instead, they are applied until later check-in.
  • The User Synchronization process may incorrectly remove users from their associated SharePoint security groups. Therefore, the users may no longer have access to Project Server.

March 2016

Rollup – https://support.microsoft.com/en-us/kb/3114823

Individual – https://support.microsoft.com/en-us/kb/3114836

DB Version – 15.0.4805.1002

  • When the data is grouped, the rows under the grouping rows on the Approvals page are always collapsed. This makes it difficult to quickly and easily view the detailed records that need to be responded to. Now, the Outline Level functionality control has been added to the ribbon on the Approval page.
  • The Process Status field may show blank for a timesheet line when the status approval is pending.
  • When you switch to a different filter type on the Manage Queue Jobs page, you may receive the following error message if many jobs are present:
    Sorry, something went wrong.
  • Consider the following scenario:
    • You have a project-level enterprise field that’s linked to a lookup table.
    • The custom field is exposed on a project detail page (PDP).
    • You edit a project from the PDP.
    • You change the value of the custom field as well as another field such as the project description.
    • You save the project.

    In this situation, you receive the following error message:

    An error has occurred while saving your project to the server. Please contact your administrator for assistance.

    In addition, the queue job error details state GeneralItemDoesNotExist. This issue occurs after you install August 11, 2015, update for Project Server 2013 (KB3055018).

  • The indicator for issues and risks is still displayed for a project in the Project Center even after the issues or risks are deleted from the project.
  • When you create an enterprise project from a SharePoint task list, the project owner mapping is ignored and you become the project owner.
  • When you edit a project in a project detail page, you can remove the project name and successfully save the project without instead receiving an expected error message stating that a project must have a name.
  • On the Approvals page, when you select the units button and then select one of the work values (Minutes, Hours, Days Weeks), the grid can’t be loaded. Sometimes, when you try to expand a grouped row, the expansion fails.

February 2016

Rollup – https://support.microsoft.com/en-us/kb/3114723

Individual – https://support.microsoft.com/en-us/kb/3114737

DB Version – 15.0.4797.1000

  • Consider the following scenario:
    • You create a project in Project Professional 2013.
    • In the new project, you disable the Actual cost are always calculated by Project calculation option under Project Options in the Schedule section.
    • You create a task that has a duration value of 20d, and then you assign the task to an Enterprise resource.
    • You insert the Cost and Actual Cost columns into the view, and then you update the values for the two columns.
    • You save and publish the project to Project Server 2013.
    • You create a report that is based on an OLAP cube that is generated from the server reporting data.

    In this scenario, the task costs for this project are incorrect in the report because an additional cost for unassigned resources is added.

  • When you apply a filter on an enterprise field that has a lookup-table within the schedule web part, no tasks are displayed for the project.
  • When you save new resources to Project Server by using Project Professional, nothing happens. This issue occurs if the resources have a logon account defined. If the WindowsAccountEditable registry key is enabled, the resources can be saved successfully.
  • You receive the following error message when you view the timesheet:
    The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
  • The Approvals page doesn’t roll up totals on grouping rows for the timephased data.
  • Consider the following scenario:
    • A team member adds actual work in their timesheet.
    • The team member submits their timesheet.
    • The timesheet approver accepts the update. At this point, the team member sees the Process Status field showing the expected Awaiting Approval message for the status update.
    • The project manager opens the project but doesn’t accept the updates.
    • The project manager saves and publishes the project.
    • The team member recreates the timesheet.

    In this case, the Process Status field is empty instead of showing the expected Awaiting Approval message.

  • When you add an existing assignment to the timesheet from a project, you receive the following error message:
    error loading.

    This issue occurs if the name of the project has the “&” character.

  • Consider the following scenario:
    • A user enters time phased actual work on an assignment and submits the work for approval.
    • The status manager approves the update.
    • The user changes the assignment start date and then submits the change.
    • The status manager approves the update.

    In this scenario, the time phased actual work may move to another date.

  • A summary task may not correctly compute the rollup value of a custom field if the field is configured with the following properties:
    • A date type
    • A minimum rollup
    • A formula where the value may be null (N/A)
  • If you only change the project description on the Project Details page, the description isn’t saved. This issue occurs after you install August 11, 2015, update for Project Server 2013 (KB3055018).
  • On the Resource Availability page, you try to deselect some resources, but the resources stay selected if certain characters (for example, “<“, “>”, or “&”) are contained in the resource names.

January 2016

Rollup https://support.microsoft.com/en-us/kb/3114493

Individual https://support.microsoft.com/en-us/kb/3114507

DB Version – 15.0.4787.1000

  • After you synchronize users to a project site in Project Web App (PWA), the users who should have access to the PWA instance do not have access to it, although these same users may still have access to the specific project site. When you view the PWA root site, these users are unexpectedly missing from the Readers (Project Web App Synchronized) group. This issue occurs after you install June 9, 2015, cumulative update for Project Server 2013 (KB3054865).
  • If a self-assigned task has actual work applied and the “New assignment request” is rejected by the approver, the “Task update” record incorrectly appears in the approval center. This causes the status manager to approve work incorrectly for a task that was rejected previously. This situation may occur if the project is checked out when the “New assignment request” is rejected.
  • Assume that you edit a project in Project Web App. After you change the work on a fixed work task that has no resource assigned, the duration of the task is changed. By default, the duration should not change for a fixed work task.
  • Assume that you add the Project Details web part to a project site. When you select the resource plan button from the Project tab, you receive an error message that looks like the following:
    Application error when access /_layouts/15/PWA/RM/ResPlans.aspx
  • Consider the following scenario:
    • A project server has thousands of users defined.
    • A project manager creates a project in the project center.
    • The project manager saves, publishes, and then closes the project.

    In this scenario, the users may have to wait several minutes until the “Prepare Project Web App Permission Synchronization For Projects” queue job is completed.

  • In certain situation, status updates aren’t applied to a project through the approval process. This fix adds an auto retry mechanism to try the status approval again.
  • When you try to add or delete a user from a project server security group, you experience an error if the project site is a root web and the host header configuration is enabled.
  • It takes a long time to go to the Add or Edit Group page of a security group even though the security group doesn’t have many users.
  • After you edit a project through a project detail page, a project level custom field may become blank. This issue may occur if the project level field contains a formula that points to a task level field that also contains a formula.
  • Some Project Web App pages don’t properly set the cache-control property to no-store.

December 2015

Rollup https://support.microsoft.com/en-us/kb/3114341

Individual https://support.microsoft.com/en-us/kb/3114360

DB Version – 15.0.4779.1000

  • Some timesheet lines are displayed as not approved even though all status updates are accepted.
  • When you use the Project Server Interface (PSI) to change a master project, the project is no longer displayed as a master project in Project Web App (PWA), and the hierarchical relationship between the master project and its sub projects is lost.
  • After you apply status updates to a fixed duration task, the remaining schedule of the task changes unexpectedly.
  • When you use the UpdateResources Project Server Interface (PSI) method to change a resource, security groups that are assigned to the resource and the claims account information about the resource may be lost.
  • On the Timesheet page, if you select a task to see the assignment details, you receive a web part error message that looks like the following:
    This Web Part was unable to load.

    This error occurs when the assignment no longer exists in the project, or the assignment was un-published, or the resource commitment on the project was changed to proposed. With this update, users will no longer drill into assignments that are in these states.

  • You can’t submit a timesheet that contains locked tasks where no actual work exists.
  • In some cases, tasks on a timeline are different in Project 2013 and Project Web App.

November 2015

Rollup https://support.microsoft.com/en-us/kb/3101369

Individual – https://support.microsoft.com/en-us/kb/3101502

DB Version – no change from September – 15.0.4753.1000

  • Assume that a project manager publishes a project and grants you access through the Project Permissions feature. You’re only given sufficient permissions to edit project level fields. When you edit and save the project from a Project Detail page, you receive the following error message:
    You need to have permissions to create a new project. Please ask the Project Web App administrator for permissions.
  • When you publish a project, the publish process fails at 66%. and you receive a queue failure message that looks something like:
    GeneralQueueJobFailed (26000) – ProjectPublish.UpdateSRAMessage
  • Consider the following scenario:Assume that you change the Project Owner field from a project detail page and then save it. When you move away from the page and then go back to the page, the project owner isn’t changed.
    • As a team member, you go to your timesheet.
    • You enter actual work hours on a task.
    • You submit your timesheet.
    • You recall your timesheet.
    • You delete the actual work hours that you entered previously.
    • You resubmit your timesheet

    In this scenario, the Reporting publish job fails and the ULS log contains details similar to the following:

    System.InvalidOperationException: Reporting publish failed. The entity ‘ID‘ is too large.
  • In some instances, when you drill into a task from the Task page, you receive a message that states the web part can’t be loaded. In the ULS logs, you see an error message that resembles the following:
    Exception occured in method ‘Statusing.ReadStatusForStatusingViews’ System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.
  • After a submitted timesheet is rejected and recalled, you can’t save changes to the timesheet any longer even if you have the Adjust Timesheet permission.
  • Consider the following scenario:Consider the following scenario:
    • You add some Visual Basic Applications (VBA) code to a project in Project Professional 2013.
    • You save and publish the project to Project Server, and then you check in the project.
    • You edit the project on the schedule project detail page in Project Server.
    • You change and save the project.
    • You open the project again in Project Professional 2013.

    In this situation, the VBA code is missing.

    • You define an enterprise project level date field.
    • The date field resides on a project detail page (PDP).
    • You edit a project and change the custom date field by using the date picker control on the PDP.
    • You select the Save button.
  • In this situation, the date that you set in the field isn’t saved as expected.

October 2015

Rollup – https://support.microsoft.com/en-us/kb/3085489

Individual – https://support.microsoft.com/en-us/kb/3085586

DB Version – no change from September – 15.0.4753.1000

  • After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn’t report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
  • You can use the keyboard shortcut (Ctrl + Delete) to delete tasks from a timesheet even though the actual work is submitted or saved.
  • When you select the Publish button while editing a project in Project Web App, the project stays in a “saving” state. This issue occurs if there’re no changes to save within the project.
  • You can change your own timesheet data after you submit it if you have the Adjust Timesheet permission.
  • The queue service may consume all server memory over time and eventually crashes. This issue occurs if you have Project Server notifications and reminders enabled.
  • Assume that you create a task and then submit it for approval. However, the submission is rejected. In this situation, the task remains on the timesheet, and you can’t submit the timesheet because the rejected task is still on it.

September 2015

No rollup this month

Rollup – https://support.microsoft.com/en-us/kb/2986195

Individual – https://support.microsoft.com/en-us/kb/3085505

DB Version 15.0.4753.1000

  • Consider the following scenario: After a timesheet is submitted and approved, you can edit a task from the timesheet on the Assignment Detail page but you can’t submit the changes for approval as status updates.
    • A task is published to your timesheet.
    • You add actual work to the task and submit a status update.
    • Your status manager approves the actual work that you submitted.
    • Your status manager locks the task that you submitted work to.
    • You delete and re-create your timesheet.
    • You submit your timesheet.

    In this scenario, upon recreating the timesheet, the locked task does not reappear on the timesheet. Therefore, as soon as the timesheet is submitted, the actual work that’s previously been approved and is seen in the project isn’t on the timesheet. This means the actual work in the project and the timesheet are no longer synchronized.

  • After a timesheet is submitted and approved, you can edit a task from the timesheet on the Assignment Detail page but you can’t submit the changes for approval as status updates.
  • It may take a long time to load a resource plan if there are many resources and custom fields on the resource plans.
  • When you approve multiple status updates at one time, all remaining updates fail if a single update fails.
  • If the calendar on which a task is calculated does not have the default 8am and 5pm start times and finish times, when you edit the task’s start or finish dates on the Task Details page, the newly calculated duration is wrong.

August 2015

Rollup – https://support.microsoft.com/en-us/kb/3055005

Individual – https://support.microsoft.com/en-us/kb/3055018

DB Version 15.0.4743.1000

  • New API to bulk update project custom fields to improve performance of demand management workflows.
  • Fixes the following issues:
    • You cannot update a local custom field by using the Project Server Interface (PSI) if the field is associated with a lookup table. Additionally, you may receive a “GeneralUnhandledException” exception.
    • Consider the following scenario:After you unlink a project site from a project server, you cannot create a new project site by using a new name, and no project site update job is triggered.
      • A team member adds himself or herself to an existing task.
      • The team member adds actual work to the task.
      • The team member submits the task and actual work for approval.
      • The status manager rejects both the new task request and the actual work on the task.

      In this scenario, the rejected task still appears in the timesheet. If you try to submit the timesheet before deleting the task, you receive the following error message:

      The submitted timesheet contains lines that have been rejected. Update these lines on your timesheet and then resubmit it.
    • You cannot use the QueueUpdateProject2 method in a PSI application to update values of custom fields.
    • Approved status updates are delayed from being applied to a project schedule of a project on a Project server until they are checked out and checked in again. Usually, status updates are applied to a project as soon as they are checked in. However, in this case, it takes an additional check-out or check-in cycle before updates are applied.
    • In the Project Web App Project Center, you cannot select to open or edit a project in Project Professional when you use Chrome or Firefox.
    • When you use a PSI application to update a project-level custom field of a project, values of calculated custom fields are blank on tasks when you view them in Project Web App.

July 2015

Rollup – https://support.microsoft.com/en-us/kb/3054933

Individual – https://support.microsoft.com/en-us/kb/3054952

DB Version 15.0.4735.1000

  • Consider the following scenario: When you associate a project from one site collection to another site collection, the “Prepare Project Web App Permission Synchronization For Projects” queue fails, and the user permissions of the project are not updated.
    • As a team member from your timesheet, you assign yourself an existing task in a project.
    • You add actual work to this task.
    • You send the new task to your status manager for approval.
    • Your status manager approves the new task, but rejects the actual work that is submitted.

    When you refresh your timesheet, the Process Status field does not show that the actual work was rejected. Therefore, you assume that it is approved.

  • The assignment timephased work may be incorrect in the reporting schema EpmAssignmentByDay table.
  • When you drill into a task from the My Taskspage and the My Tasks Web Part is on a SharePoint page, you receive the following error message:
    The webpage cannot be found.
  • When you change the view for a Project Center or Project Schedule view and apply a different filter or grouping, the filter option and the grouping option do not change as expected, and the view may still be filtered or grouped based on the previous view.
  • If a task custom field has a formula and the formula references a project custom field that has a lookup table, the task custom field is not always updated as expected when changes are made to the project in Microsoft Project Web App.
  • When you try to run the Deficit and Surplus report on the Analyze Resources page in Project Web App, you experience a time-out issue.
  • When you create deliverables directly in a SharePoint site that has the Project Web App Connectivity feature enabled, you cannot see the deliverables in Microsoft Project Professional 2013.
  • After you delete a security group for a user in Project Server 2013, the user still has the permission of the security group.
  • You cannot create a project that has a task custom field with a formula that has a reference to the Status field.

June 2015

Rollup – https://support.microsoft.com/en-us/kb/3054865

Individual – https://support.microsoft.com/en-us/kb/3054869

DB Version – 15.0.4723.1000

  • You add a nonstandard line for a task in your timesheet, add actual work to it, and then save the timesheet. In this situation, the actual work for the same day is replicated onto the standard line. Therefore, the total actual work is doubled.
  • In Project Web App, when you create a project from a template in which a budget resource is assigned to the project summary task, the project cannot be published. Additionally, you receive an error message that resembles the following: 
    Your new <project_name> has been created successfully, but failed to publish and will not be listed in the Project Center.
  • Tasks and approvals are not displayed on the home page in Project Web App when the Polish language pack is applied.
  • After you use the Turn in Final Timesheet function to send a timesheet in Project Web App, the timesheet can still be edited and saved.
  • From a project detail page in Project Web App, you save a project that contains cost resource assignments. In this situation, the costs on the assignments may change unexpectedly. For example, a cost of $1.16 changes to $1.00.
  • In Project Professional, assume that a summary task is edited in such a way that its subtasks are hidden, and the plan is later published to Project Server. However, when you edit the project in the Schedule Web Part in Project Web App, the previously hidden subtasks cannot be displayed and edited.
  • When you import external data from an OData data feed to a workbook in Microsoft Excel 2013, you receive the following error message: 
    The content of the data fee is not valid for an Atom feed.

    This issue occurs if the data feed has a custom field that has a lookup table and a graphical indicator.

  • When you apply a grouping to a view, and the view contains an enterprise custom field that has a formula, the values from the custom field do not roll up into the grouping row.
  • When you create a project that’s based on a template in Project Web App, you do not become the owner of the project. This means that you cannot see it in the project center. Additionally, the user who created the template is set as the owner of the project.
  • After you rename a custom field that’s used in a timesheet, the changed field name is not displayed correctly in the dbo.MSP_TimesheetLine_UserViewCF table, and it may be associated with another field.
  • When you set a SharePoint list indicator on a timeline Web Part on a SharePoint Server 2013 site, a duplicate timeline Web Part is displayed when you refresh.
  • In single entry mode, after you submit a timesheet, the timesheet manager can adjust the time that you submitted. However, these changes are not reflected in the tasks in the project. This means that the work that was recognized in the timesheet in out of sync with the project.
  • When you save a project in Project Professional or Project Web App, custom field values are lost.Note This issue occurs after you apply March 10, 2015 update for Project Server 2013 (KB2956178).
  • In Project Web App, when you create a project that’s based on a template, the tasks do not have the TaskOutlineNumber field value that’s set in the template. This is reflected when you view the data in locations such as the dbo.MSP_EpmTask database table.
  • When you update a plan by submitting updates through a timesheet or tasks in Project Web App, auto approval rules may not apply the update. Instead, the approval appears on the status manager’s approvals page.
  • The Configure Columns settings (for example, column width, or order) on a timesheet are reset unexpectedly to the default every time that the timesheet is refreshed.
  • When you publish a project that has a task marked as a milestone in Project 2013 to a Project server, the task is not displayed as a milestone in the timeline view in Project Web App.
  • To fix the following issue for Project Server 2013, install June 9, 2015, update for SharePoint Foundation 2013 (KB3054867):

    You cannot scroll to see all the resources on the right-side grid of the build team page if hundreds of resources are added to the project team.

 May 2015

Rollup – https://support.microsoft.com/en-us/kb/3039753/

Individual – https://support.microsoft.com/en-us/kb/3054804/

DB Version – 15.0.4699.1000 (No change since March)

  • When you view a Gantt view of a task list in SharePoint, you cannot filter items if grouping is applied to the list.
  • You receive the following error message in Status Updates history:
    There was an internal error applying the update.

    This issue occurs if the decimal separator is a comma in Windows Regional settings, and an enterprise custom field that is displayed as a graphical indicator contains a decimal value.

  • If a Project Web App team member inputs actual work that is earlier than the task and project start date, when the updates are applied to the project, time-phased actual work may display an incorrect value.
  • When you go to a project detail page and then go back to another project detail page in Project Web App, the values in project-level custom fields may disappear. This issue occurs after you edit and save projects through different project detail pages.
  • When you use your keyboard and then press ENTER on the SHOW MORE link during editing or adding a task in SharePoint Server 2013, the focus is reset to the first field of the form instead of the first field of the added list of fields.
  • When you apply status updates to a project, you may receive the following message in the status field in the status updates history: 
    There was an internal error applying the update.

    This issue occurs because the Project Calculation Service failed. When you view the Unified Logging Service (ULS) logs, you see an error message that resembles the following: 

    Microsoft.Office.Project.Server (0x06A4) 0x3598 Project Server Project Calculation Service (M) adf34 Unexpected Failed to create a new desktop
  • When you publish a project to a project server that has the Project Site Sync permissions synchronization options enabled, the publish job takes a long time.
  • When you publish a project that contains thousands of tasks, it may take longer than expected. In addition, the Project Publish queue job stays at 78% for an extended time. This issue may occur when the corresponding SharePoint tasks list exists and it is synchronized.
  • Assume that you change a view of a Project Server 2013-based task list to display the item count for a column. When you filter the items in the column, the item count does not update correctly.
  • When you clear the User can be assigned as a resource check box on the Edit User page in Project Server 2013, publish errors or a loss of resource in projects may occur.

 April 2015

Rollup – https://support.microsoft.com/en-us/kb/2965263/

Individual – https://support.microsoft.com/en-us/kb/2965278/

DB Version – 15.0.4699.1000 (No change)

This update resolves vulnerabilities that could allow elevation of privilege if an attacker sends a specially crafted request to an affected Microsoft Project Server 2013. The attacker who successfully exploited these vulnerabilities could then perform cross-site scripting attacks on affected systems and run script in the security context of the current user. An attacker who successfully exploited the vulnerabilities could read content that the attacker is not authorized to read, use the victim’s identity to take actions on behalf of the victim, such as change permissions, delete content, and insert malicious content in the victim’s browser.

Improvements and fixes

This update also contains fixes for the following nonsecurity issues and improvements:

  • Translates some Russian language UI elements for Project Server 2013 to guarantee accuracy of meaning. This improvement also provides consistency with the Project Professional 2013 client.  For example, these elements translate “Рабочий” to “Трудозатраты”.
  • Disabled property and account of a user is not inactive in Project Web App. Additionally, the presence of particular accounts in Active Directory Domain Services cause partial sync errors in Project Server 2013.
  • Formula values may not be calculated for a project field on the project details page in Project Web App until you publish the project.
  • Improves security for cross-site scripting (XSS) on project detail pages.
  • Assume that you try to create a new site from the Connected SharePoint Sites page for an existing project plan. If a web application that you use has a managed path, the site is not created, and the Prepare Project Web App Permission Synchronization For Projects job is displayed as Failed But Not Blocking Correlation on the Manage Queue Jobs page.
  • When you open the Connected SharePoint Sites page in a site collection that has lots of projects, the page takes a long time to load or may time out.
  • When you try to access a view for which you have permissions, you receive an access denied error if you do not have permissions to view the default My Assignments view.

 March 2015

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

Individual – http://support.microsoft.com/kb/2956178

DB Version – 15.0.4699.1000

  • When you create a report that uses a Project OData feed, in the query string you cannot filter on nullable Boolean fields. Instead, the query fails.
  • Assume that you edit a project from the Schedule page (Schedule.aspx) in Project Web App. You set the value of the Locked field for a task or series of tasks to Yes, and then you save the project. When you return to the project later, you find that the value you set is lost and is now No. Therefore, the task is not locked and team members can still report actual work to the tasks.
  • Assume that you modify a view of a Project Server 2013 task list to display the item count for a column. When you filter the items in the column, the item count does not update correctly.
  • When you publish a project to a Project Server 2013 server, the start dates of the tasks in the published project may be calculated incorrectly.
  • When you create a security group in the Manage Groups page, the Deny permission on the View Project Site permission does not work. Therefore, users may still be able to gain access to sites.
  • Assume that you save an Enterprise project as a template where tasks on the project are associated with an Enterprise calendar. When you create a new Enterprise project by using the template in Project Web App, the Enterprise calendar is missing. Additionally, the tasks that use the missing calendar may contain incorrect values such as start dates and finish dates.
  • When you submit a status update that contains notes, the existing task note as viewed in Project Professional may be partly overwritten.
  • When you edit a project in the Schedule page (Schedule.aspx), some fields such as Task Summary Name may not be displayed.
  • Consider the following scenario:
    • You have an enterprise custom field that has a lookup table associated with it, and the field lets multiple values to be selected.
    • The regional settings locale that you select in SharePoint does not use a comma as the list separator.
    • You edit a task in Project Web App from the Tasks page, and you have more than one value selected in the custom field.

    In this scenario, when you save the task, the values may be lost. Additionally, you do not receive a warning message.

February 2015 (Now Public Updates)

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

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

DB Version – 15.0.4693.1000

  • When you create a new task directly on the Timesheet page, regardless of the Finish Date entered for the task, the task will always be created on the correct Start Date but with a duration of one day.
  • When you add nonstandard line classification tasks to a timesheet or manipulate tasks on an un-submitted timesheet where nonstandard lines exist, you may receive the “_error loading” error message.
  • The permissions for all users who should have access to a project site may be synchronized incorrectly when you publish a project.
  • Assume that you add the SQL Server Reporting web part to a Project Server 2013 page that contains other Project Server web parts. When you click the Refresh button in the SQL Server Reporting web part, the given Project Server web parts will be duplicated.
  • Assume that you add the Project Server task list as a web part to a SharePoint page, and then you set a filter for the task list web part. When you browse to the page, the filter does not work correctly.
  • Assume that you create a Project Web App (PWA) view for the schedule web part, and the view contains a filter that has more than 12 clauses. When you apply the view to the Schedule page while you edit a project, the view loads incorrectly. Additionally, you may receive the following error message:
    Project Web App hit an error processing your request and your unsaved changes were lost. Press OK to reload the session. Press CANCEL to close the session. If this happens again, contact your administrator.
  • Assume that you create a site template in Project Server 2010. Then, you migrate Project Server 2010 to Project Server 2013. When you edit an Enterprise Project Type, you cannot select the given site template from the Project Site Template drop-down menu.
  • If you cancel the selection of the Enable Project Site Sync option in the Project Permission Sync Settings page, you cannot sync the users by clicking Synchronize in the Connected SharePoint Sites page.
  • When you click Close on the Build Team page, you may receive one of the following messages:
    Working on Checking In
    The project cannot be written to the server
  • Consider the following scenario:
    • You open a project plan in Project 2013 from a Project Server 2013-based server.
    • You delete the value of a custom field that uses a lookup table on the server.
    • You publish and check in the project plan. Then, you open the project plan in Project Web App.

    In this scenario, when you click Edit on the Project Detailspage, you may receive an error message that resembles the following:

    This Web Part was unable to load. Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: <ID>
    For more information, contact your Project Web App administrator.
  • Consider the following scenario:
    • You connect to a Project Web App (PWA) site by using Project Professional.
    • You create a project, and then add some resources to it.
    • You save and publish the project; in the Publish Project dialog box, you decide to provision the site as a subsite of another project.

    In this scenario, the permissions on the newly created site may be incorrect. Additionally, in the Project Server Queue Job Error Details it shows information similar to the following:

    GeneralQueueJobFailed (26000) – PreparePSProjectPermissionSynchronization.PreparePSProjectPermissionSynchronizationMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ GroupType=’PreparePSProjectPermissionSynchronization’ MessageType=’PreparePSProjectPermissionSynchronizationMessage’

 December 2014

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:

Sorry, something went wrong
An unexpected error has occurred.
  • 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 Error

    Message: 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:

The following job failed to complete.
Job Type: Save
Error ID: 9000(0x2328)
Error Description: The project could not be saved to the server. Please retry saving the project. If the problem persists, save the project as a MPP file and contact your system administrator.

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.

June 2013

 
 
DB Version – 15.0.4510.1000
 
  • When you build an OLAP cube on a Project Web App site, you are not added to the ProjectServerViewOlapDataRole role. This issue occurs even if you have the View OLAP Cube data permissions.
  • When you try to add a task list from a root Microsoft SharePoint Server 2013 site collection to a SharePoint Server 2013 site in Project Web App, you receive the following error message:
    Failed But Not Blocking Correlation
  • It takes longer than expected to open a project that is located on a network share in Project 2013.
  • After you create a timesheet for a period of time in Project Web App, you cannot close the timesheet.

April 2013

Rollup – http://support.microsoft.com/kb/2737990

Individual – http://support.microsoft.com/kb/2760261

(Sorry, I don’t have a record of the DB version for this update)

  • Assume that you use cost resources in a project. After you set baselines in the project, the sum of individual time phased portions does not equal the baseline cost value at the task summary level.
  • Consider the following scenario:
    • You use Project Server Interface (PSI) or Project Web App to create a project plan.
    • You add some tasks whose Published fields are set to NO in the project plan.
    • You create a new project that is based on the project plan.

    In this scenario, the Published fields are set to YES in the new project.

  • When you submit a timesheet in Project Server 2013, timesheet view is not displayed. Additionally, you receive the following error message:
    The view failed to load
  • When you create a timesheet, all projects except the projects that occur during the timesheet period are added to the timesheet.
  • Actual Work values that users submit to the Approval Center are displayed only in units of hours. This issue occurs in Project Web App.
  • When you view the cost or resource analysis page in certain resolutions (such as 1600×900 or 1280×960), the pane that is typically displayed on the right side of the page is displayed at the bottom of the page.
  • After you upgrade from Project Server 2013 Release to Manufacturing (RTM) to Project Server 2013, you cannot use “O data Assignment Custom Field” views.
  • After you configure an Alternate Access Mapping for Project Web App, you cannot create a project site.
  • When you use the PSConfig or Upgrade-SPFarm command to upgrade Project Server 2013 RTM, the upgrade is unsuccessful. Additionally, all services are stopped.

 March 2013

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

 

 

 

 

Skip to main content