Project Server 2010 Cumulative Updates


This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and infrastructure update for Project Server 2010. 

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

They are listed in reverse date order - newest at the top.  The CUs are normally available in a 'rollup' package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) 'Individual' packages which just contain the Project Server fixes.  Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack).  In some months a rollup package did not get released.  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.

December 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for December 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application.

Project Server roll-up package

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

No database change - so 14.0.7156.5000

November 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for November 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application.

Project Server roll-up package

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

No database change - so 14.0.7156.5000

October 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for October 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application.

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

No database change - so 14.0.7156.5000

September 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

August 2016

There are no updates for Project 2010 for August 2016.

July 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

June 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

May 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

April 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

March 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

February 2016

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

January 2016

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

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

No database change - so 14.0.7156.5000

December 2015

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

November 2015

No individual Project Server 2010 package this month

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

October 2015

No individual Project Server 2010 package this month

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package).  This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch.

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

No database change - so 14.0.7156.5000

September 2015


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

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

Database Version - 14.0.7156.5000

  • When you approve multiple status updates at one time, all remaining updates fail if a single update fails.
  • When you open a resource plan that contains many resources and customer fields in Project 2010, it takes a long time to load up the resource plan.

August 2015

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

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

Database Version - 14.0.7151.5000 (Not updated this month)

  • When you use a Project Server Interface (PSI) application to update a project-level custom field of a project, values of calculated custom fields are blank on tasks when viewed in Project Web App.

July 2015

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

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

Database Version - 14.0.7151.5000 (Not updated this month)

  • 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.
  • When you try to run the Deficit and Surplus report on the Analyze Resources page in Microsoft 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 2010.

June 2015

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

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

Database Version - 14.0.7151.5000

  • When you try to edit a resource in Project Web App, you receive an unknown error that resembles the following in the ULS logs:
Exception occurred in method Microsoft.Office.Project.Server.BusinessLayer.Project.ProjectQueueUpdatePDPProjectCF System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'MSP_ReadLocalAndEnterpriseLookupTableInfoByUIDs', database 'ProjectServer_Published_PWA', schema 'dbo'.

For more information, see Project Server 2010: After applying the March CU resources can't be saved in PWA.

May 2015

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

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

Database Version - 14.0.7145.5000 (not updated)

  • When you try to insert a task for a project in the Schedule Web Part in Project Web App, you receive the following error message:
    This edit is unsupported in Project Web App.

    This issue occurs if the project has a particular structure of outline levels or task indentations and if you are using Internet Explorer 11.

  • When you export or print a resource plan for a project in Project Web App, the work or full-time equivalent is incorrect. For example, suppose that you enter the values 1d, 2d, and 3d. The print may show the values as 0.63d, 1.75d, and 2.63d.
  • When you publish a project in Project Web App in which tasks contain formulas that use the ProjDateDiff function, incorrect calculations may be made. This issue occurs if your project calendar does not use the default calendar configuration (08:00-12:00 and 13:00-17:00).

 

April 2015

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

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

Database Version - 14.0.7145.5000 (not updated)

No Project Server feature fixes this month, but a security patch:

This update resolves vulnerabilities that could allow elevation of privilege if an attacker sends a specially crafted request to an affected Microsoft Project Server 2010. 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.

March 2015

Rollup - http://support.microsoft.com/KB/2956198

Individual - http://support.microsoft.com/kb/2553480

Database Version - 14.0.7145.5000

  • You cannot update a local custom field by using Project Server Interface (PSI) if the field is associated with a lookup table. Additionally, you may receive a "GeneralUnhandledException" exception.
  • Assume that you change the working time of the enterprise calendar associated with your project to a nondefault working time such as 9:00-17:00. Then you publish a task and open 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.

 

February 2015

Rollup - http://support.microsoft.com/KB/2899557

Individual - http://support.microsoft.com/KB/2881024

Database Version - 14.0.7137.5000 (Not updated - so same as November 2014)

  • Assume that you browse to a Project Web App (PWA) site on a computer where the time zone setting differs from the server that hosts the PWA site. When you browse to the Tasks page, the active time period may be incorrect.
  • Assume that you create a new Enterprise custom field, and then you enter a formula that refers to the Task Calendar field. When you save the Enterprise custom field, you receive the following error message:
    The custom field could not be saved due to the following reason(s):
    This formula contains references to one or more fields that do not exist in the system. Correct the formula and try again.
  • Consider the following scenario:
    • You link two tasks by using a Start-to-Start (SS) dependency. In this case, the predecessor is a summary task and the successor is an ordinary task.
    • You make some changes to the project plan by using a Project Server Interface (PSI) application.
    • You publish the project plan to a Project server.

    In this scenario, the start date of the successor tasks may be earlier than expected.

 

December 2014

Rollup - http://support.microsoft.com/KB/2910889 

Individual - http://support.microsoft.com/KB/2899587

Database Version - 14.0.7137.5000 (Not updated - so same as November 2014)

  • 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, and the view may still be filtered or grouped based on the previous view.
  • Assume that you have a resource whose Latest Available date is set, and the resource’s calendar has exceptions. When you call the Resource.UpdateResources method, you may receive the "CalendarUnusedCalendarException" error message.

November 2014

Rollup - http://support.microsoft.com/kb/2899479

Individual - http://support.microsoft.com/kb/2899537 and http://support.microsoft.com/kb/2899549

Database Version - 14.0.7137.5000

Consider the following scenario:

  • You create a project in Project Professional 2010.
  • 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 2010.
  • 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.

Consider the following scenario:

  • In Project Server 2010, you create a custom field that uses a lookup table, and then you enable 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 for 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.

  • It takes longer than expected to publish a project to a server that is running Project Server 2010 when there are many projects on the server.

October 2014

No rollup this month

Individual - http://support.microsoft.com/kb/2899485/ and http://support.microsoft.com/kb/2880539/

Database Version - 14.0.7134.5000

  • Assume that you log on to your Project Server 2010, open a timesheet, and then select the Add Yourself to a Task option from the Insert Row button. The Add Tasks page is refreshed every 10 seconds, and this behavior makes it very difficult to enter information on the page.
  • Assume that there are tens of thousands of projects on your Project Server 2010 server. It may take a long time for you to open or save a project on the server.

September 2014

Rollup - http://support.microsoft.com/kb/2883006

Individual - http://support.microsoft.com/kb/2880531

Database Version - 14.0.7132.5000

  • Assume that you log on to Project Web App by using Windows Internet Explorer 10 or a later version. When you try to export the resource availability information by using the Export to Excel function on the Resource Availability page, the function does not work.
  • Assume that you edit a project on the Project Details page. When you change a property such as the name, the value of the Cost field of material resources may be changed to $0.00.

August 2014 - No Project Server 2010 Cumulative Update released

July 2014 - No Project Server 2010 Cumulative Update released

June 2014

Rollup - http://support.microsoft.com/kb/2880974

Individual - No individual package released.

Database Version - 14.0.7121.5000 (Not updated - same as for April 2014)

  • Timephased values shown in Project don't appear correctly in the PWA availability page

April 2014

Rollup - No rollup package released

Individual - http://support.microsoft.com/kb/2878259 and http://support.microsoft.com/kb/2878266

14.0.7121.5000

  • The decimal value in the Standard Rate field does not always round correctly after you edit any resources in Project Web App (PWA).
    For example, assume that you enter a resource’s standard rate as $733/d. On an hourly basis this is equal to $91.625 and is stored in the Project Server database as $91.625 though it appears in the interface in Project Professional and PWA as $91.63. However, if you edit the resource in PWA, the value that is stored internally changes to $91.63. Therefore, costs dependent on rate may change because of the rounding problem.
  • The Assignment Baseline Finish field and the Task Baseline Finish field are missing from the Published Field list when you create an approval rule in the Approval Center.
  • Assume that you have a timesheet and that since its creation one or more custom fields that were available when the timesheet was created are deleted (from the Enterprise Custom Fields and Lookup Tables page).
    When you open the Timesheetview, you receive the error message that resembles the following:

    The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
  • Assume that you create a project by using a project template where, for example, the Hours per day option is set to 9 hours. In this situation, the project may schedule incorrectly in Project Web App. Additionally, you receive the error message that resembles the following:
    An error occurred scheduling the project. Try to schedule the project again in a moment.
  • When in a project detail page in Project Web App you save a project that contains cost resource assignments. In this case, the costs on the assignments may change unexpectedly. For example, a cost of $1.16 changes to $1.00.
  • When resources in a project have many assignments in other projects in Project Server 2010, it takes longer than expected to publish the project.
    Note The time that is required to publish the project may increase if many projects that use the same resource are published at the same time as can occur if you enable the Automatically publish the updates option.
  • Because of SQL Server deadlock errors, data is not always transferred to the Reporting database when you save a timesheet.

February 2014

Rollup - http://support.microsoft.com/kb/2863917

Individual - http://support.microsoft.com/kb/2863927 and http://support.microsoft.com/kb/2863934

Database Version 14.0.7115.5000

  • When users are marked as inactive, the User can be assigned as a resource option on the Server Settings Edit Users page can still be changed. Deselecting this option can lead to project publishing errors and the loss of resources on projects.
  • If dependencies between tasks in the project have unusually large lead times or lag times, saving a project in Project Web App may fail. Additionally, you receive the following error message: 
    An error has occurred when saving your project to the server. Please contact your administrator for assistance.
  • Automatic approval rules may not get executed as expected. Additionally, you can find a job in the queue with a state of Failed But Not Blocking Correlation. When you click View Error Details, you may see details about the error that resembles the following:

A GeneralQueueJobFailed (26000) error occurs

  • When Project Server is using Claims Based Authentication, the Enterprise Resource Pool and Security Group Active Directory synchronization jobs may fail and in the ULS logs you may see errors similar to:

A resource could not be updated during Project Server Active Directory Synchronization because a duplicate windows account name conflict occurred that could not be resolved

December 2013

Rollup - http://support.microsoft.com/kb/2849972

Individual - http://support.microsoft.com/kb/2849978 and http://support.microsoft.com/kb/2849988

Database Version - 14.0.7113.5000

  • Consider the following scenario:When you add yourself to a task in Project Web App, the Timesheet page buttons in the Submit and Tasks sections are greyed out. Therefore, you cannot save or send the timesheet.
    • A resource is assigned to a 2 day fixed duration task.
    • The resource only works the first day of the task, and then you set the task’s % Complete option to 100%.
    • You open, calculate, and save the project in Project Web App.
    • You open the project in Project Professional 2010 again.

    In this scenario, the task’s % Complete option is set to 50%.

  • After you approve some status updates in the Approval Center, the updates are not applied to schedules. Additionally, when you click the Error link on the Manage Queuepage, you see an error message that resembles the following:

General
Status approval internal error:
StatusingInternalError (3116). Details: id='3116' name='StatusingInternalError' uid='5cb8a27d-71db-491a-9c0a-782950a2d6ce'.
Queue:
GeneralQueueJobFailed (26000) - StatusApproval.StatusApprovalMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='16a0be21-3b4d-44a2-98e0-d6452342bf7a' JobUID='43b6dac0-53c9-4fbe-ad3c-1731608c4cbc' ComputerName='ComputerName' GroupType='StatusApproval' MessageType='StatusApprovalMessage' MessageId='3' Stage=''. For more details, check the ULS logs on machine ComputerName for entries with JobUID 43b6dac0-53c9-4fbe-ad3c-1731608c4cbc.

  • When you publish a project on a Project Server 2010 server, there is a publish failure message in the queue, and deadlock errors are logged in the ULS logs.

October 2013

Rollup - http://support.microsoft.com/kb/2825793

Individual - http://support.microsoft.com/kb/2825803

Database Version - 14.0.7110.5001

  • Assume that you accept some updates for a project on the Approval Center page in Project Web App. When you open the Status updates history page, you receive the following error message:

    There was an internal error applying the update.

    Additionally, when you open the project in Project 2010, the update is not applied.

  • After you accept updates for a project in Project Web App, the work and duration information for some tasks and assignments is set to zero.

August 2013

Rollup - http://support.microsoft.com/kb/2817573

Individual - http://support.microsoft.com/kb/2817587

Database Version 14.0.7104.5000

  • Assume that you belong to many security groups that have many security categories applied, and the security categories have many of the dynamic RBS permissions applied. When you move from one Project Detail Page (PDP) to another, it may take longer than expected.

June 2013 (Actually re-released in July)

Rollup - http://support.microsoft.com/kb/2817530

Individual - http://support.microsoft.com/kb/2817538

Database Version 14.0.7102.5000

  • When you edit a project that contains cross-project links and enterprise custom fields in Project Web App, task durations are changed unexpectedly.
  • When you edit a custom field from the Assignment Details page in Project Web App, you cannot input more than 50 characters.
  • Consider the following scenario:
    • You enable the Protected Actuals feature and then create a task.
    • A team member reports an actual work, and the actual work is approved.
    • You edit a work or remaining work of the task in a Project view in Project Web App.

    In this situation, you receive the following error message:

    Your last edit changes actual work on the project. Currently Project Web App is set up to protect actuals on tasks.
  • Consider the following scenario:When you use Project Server Interface (PSI) to update a project that contains multiple cost rate table entries in Project Server 2010, resource costs are calculated incorrectly.
    • You create a task that has predecessor relationship, multiple assignments and at least one assignment that has actual work applied.
    • You report and approve actual work for one of the other assignments.
    • The work is reported earlier than scheduled and earlier than when the actual work that is already reported on the other assignments.

    In this situation, the actual work on the assignment is scheduled incorrectly. Therefore, the start date and duration of the task is calculated incorrectly.

  • Unnecessary user account synchronization occurs and you experience performance issues in Project Web App. For example, you cannot log on the server.
  • When you use a template that contains a null task to create a project in Project Web App, the project cannot be displayed in Project views.
    Note A null task is a blank row between rows.
  • Totals for grouping rows on the Approvals page in Project Web App are not rolled up.

Service Pack 2 (SP2)

Download - http://www.microsoft.com/downloads/details.aspx?FamilyId=387a7889-8266-429a-bfd3-b6bb2f9cbe63

List of fixes - http://download.microsoft.com/download/9/5/9/959F3A24-80B3-4930-8FF8-D3C631BB878F/Microsoft%20Office%20and%20SharePoint%202010%20Service%20Pack%202%20Changes.xlsx

Database Version - 14.0.7015.1000

April 2013

Rollup - http://support.microsoft.com/kb/2775426

Individual - http://support.microsoft.com/kb/2791064

Database Version 14.0.6136.5000

  • Consider the following scenario:
    • You create a proposal on the Project Center page in Project Server 2010.
    • You do not enter data into all the required fields.
    • You submit the proposal, and it is displayed unexpectedly as "checked in".
    • You edit the proposal. However, you do not enter data into all the required fields.
    • You submit the proposal again.

    In this situation, the proposal is displayed unexpectedly as "checked out".

  • Assume that you set some values for the date range, filter, and group fields on the Approval Center page in Project Server 2010. When you move away from the Approval Center page and then move back to the Approval Center page, you experience the following issues:When resources in a project have many assignments in other projects in Project Server 2010, it takes longer than expected to publish the project.
    • The value is not retained in the date range field.
    • The filter and group fields are set. However, the filter and group settings are not applied to the data.
  • Note The time that is required to publish the project increases if many projects that use the same resource are published at the same time. This can occur after you enable the Automatically publish the updates option.

February 2013

Rollup - http://support.microsoft.com/kb/2767794

Individual - http://support.microsoft.com/kb/2760772

Database Version - 14.0.6131.5000 (Not updated - same as December 2012)

  • Consider the following scenario:Assume that you try to create a new project that is based on a template in Project Web Application. However, the Queue service job never finishes, and the Queue service restarts continuously. Additionally, Project Server 2010 crashes.
    • You create a new task in Project Web Application.
    • You associate the new task with an existing summary task in the project.
    • You open the project in Project Professional 2010.
    • You search for the new task.

    In this scenario, the new task is not associated with the correct summary task.

  • Assume that you add users to custom SharePoint groups in a Project Web Application site collection. However, when the server performs a user synchronization Queue Service job, these users lose their permissions to access resources.
  • After you update the "% Work Complete" value in a sub-task when you edit a project in a Project Web App schedule view, the "% Work Complete" value in the parent task is incorrect.

December 2012

Rollup - http://support.microsoft.com/kb/2596956

Individual - http://support.microsoft.com/kb/2553504 and http://support.microsoft.com/kb/2553268

Database Version 14.0.6131.5000

  • Assume that you install update 2730388 on a computer that has Microsoft Project Server 2010 installed. In this situation, the updated actual work value is not displayed in the project plan after you accept updates that include actual work in Project Professional 2010. 
  • In the Project Web App (PWA) approval center, the actual work values that are submitted for approval on a timesheet will be displayed in hours when the submitted values are in days.
  • Consider the following scenario:
    • You enable single entry mode in Project Server 2010.
    • You insert a personal task on a timesheet.
    • You edit the start date or another non-timephased field for the task, and then try to save the timesheet.

    In this situation, you receive an error message, and the timesheet cannot be saved.

  • Consider the following scenario:Assume that you set up a multiple forest environment. When you perform an Active Directory resource pool or an Active Directory security group synchronization over an external trust to another forest, the process fails.
    • User A and user B are status managers in Project Server 2010.
    • User A creates a task and assigns it to a Work Resource in Project Web App (PWA).
    • User A saves the project plan.
    • User B opens the project and removes the Work Resource on the task.
    • User B saves the project plan.

    In this scenario, the status manager for the task automatically switches from user A to user B.

    Note
     If the resource is a Work Resource or a Generic Resource, the status manager does not change in the Project Professional 2010. Additionally, if the resource is the Generic Resource, the status manager does not change in the PWA for the user who removes the Work Resource.

  • Assume that you publish a project with actual costs outside the task span in Project Server 2010. In this situation, the timephased and baseline actual cost do not appear correctly in the reporting database. This occurs when there is no timephased or baseline work span associated with the actual cost.
  • Assume that you set up a delegation in Project Server 2010.  Then you assign yourself as a delegate and create new timesheets. In this situation, the newly created timesheets are missing administrative lines. Additionally, you receive the following error message: 
    The timesheet creation failed, because of problems with the project server or with data validations, such as resources not being valid work resources or users. Check your environment, and then try again.
  • When you submit timesheets in Project Server 2010, a deadlock situation occurs, and the timesheet page is not updated correctly. 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.
     

October 2012


Rollup - http://support.microsoft.com/kb/2687565

Individual - http://support.microsoft.com/kb/2687615

Database Version - 14.0.6129.5002

  • Assume that you configure Project Server 2010 in two or more zones that are accessed by using different URLs. Additionally, assume that you create Project sites that contain a Project web part. In this situation, when you try to connect to the Project site from a zone that differs from the zone in which the Project site is created, you receive the following error message from the web part:
    Cannot communicate with the server. Verify your connection and try again.
  • Consider the following scenario:Assume that a resource has the Max Units field set to a value that is not 100 percent. Additionally, assume that the default task type for a project is "Fixed Duration." The resource creates a new task in Project Web App and adds the task to the project. In this situation, the task is displayed in the project with a high amount of work. Additionally, the task does not appear in the Approval Center and causes an error on the approval page.
    • You have an enterprise resource that is assigned to a task in a plan.
    • The resource enters actual work in a timesheet and saves (but does not submit) the timesheet in Project Web App.
    • You set the Publish field in the task to No," and then you publish the plan.
    • You set the Publish field in the task to Yes," and then you publish the plan.
    • The resource submits the timesheet update for approval.

    In this scenario, the actual work is not submitted in Approval Center.

  • Assume that a delegate user makes corrections to a timesheet that was previously rejected in Project Web App and then sends the timesheet for approval. In this situation, time that is added to the lines that already contain approved status updates cannot be resubmitted and approved.
  • Assume that you try to edit an existing project in Project Web App while you are using Internet Explorer 10. However, occasionally you cannot edit the project.
  • When you create and load a timesheet in Project Web App, the process takes longer than expected.
  • When you create a project plan from a template in Project Web App, the value of the Publish field is not copied from the template.
  • Assume that you create an enterprise project template in Microsoft Office Project Professional 2010 in which you configure the default start time and the default finish time at the project level. Then, you create a new project plan that is based on the template. In this situation, the default start time and the default finish time are those from the enterprise global template instead of the template from which thenew project was created.
  • Assume that you set the WADMIN_USER_SYNC_SETTING setting to a value greater than one in the published database of Project Server 2010. When you try to add a user to a project by using the project permissions feature, the user is not added to the project site.
  • Assume that you enter the actual work for a task by using Project Web App. However, when you click Status Updates to view task update history, the actual work column is blank.
  • When all task updates are submitted to Project Server 2010, the OnStatusSubmitted event returns a NULL value instead of an array of GUIDs that match the submitted updates.

August 2012 (Actually released in September)

Rollup - http://support.microsoft.com/kb/2687354

Individual - http://support.microsoft.com/kb/2687390 and http://support.microsoft.com/kb/2687385

Database Version - 14.0.6126.5001

  • When enterprise flag fields are defined in a project, and you publish the project, the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW table in the published database contains two times as many records as the original table.Note To resolve this issue, apply update 2687386 on the Project client application. For more information about the update, click the following article number:

    2687386

    Description of the Project 2010 hotfix package (Project-x-none.msp): August 28, 2012

  • Assume that you set a baseline cost value for a task that contains negative cost values. When you publish the task while it is synchronizing with the Reporting database, the negative cost values are converted to 0 in the MSP_EpmAssignmentByDay and MSP_EpmAssignmentBaselineByDay tables.
  • On the History page for certain projects in Project Server 2010, error messages are displayed in the status updates field. These error messages are displayed even though you already applied the updates to resolve the issues that caused the error messages.
  • Assume that you assign a resource to a task, and the resource's calendar contains nonworking time. Additionally, assume that you enter actual work for the task. When you open the task, the actual work is displayed in the wrong time period.
  • Assume that you submit actual work for a resource that has a nonzero cost rate on the My Tasks page. When you publish the project that contains the resource, the actual costs that are calculated through the actual work are not updated in the reporting database.
  • When you configure a Project Server 2010 server to run in single entry mode, and then you open a project, tasks that are manually scheduled in the project are not displayedin the Add an Existing Task dialog box. Therefore, you cannot enter time for these tasks.
  • When you start a delegation session as a delegate in Project Server 2010, auto-approval rules for task updates do not work as expected.
  • Assume that you assign some material resources to some summary tasks in a project. When you edit and publish the project through Project Web App, the number of material resources in the published project is much greater than the number of material resources in the original project.
  • Assume that you set the replacement character for Active Directory synchronization to a null value on a Project 2010 server. After you synchronize the server, resource names are displayed with two additional spaces on the server. For example, "LastName, FirstName" is displayed as "LastName  FirstName."
  • Assume that many projects contain local custom fields in Project Server 2010, and the local custom fields contain custom field formulas. When you open a project in the publishing database, the project contains formulas that are from other projects.

June 2012

Rollup - http://support.microsoft.com/kb/2598355

Individual - http://support.microsoft.com/kb/2598375 and http://support.microsoft.com/kb/2598376

Database Version - 14.0.6122.5000

  • Consider the following scenario:
    • You create a user account in Project Web Access (PWA), and you enable Exchange Synchronization for the user account.
    • You create a new plan that contains many tasks in Project 2010.
    • You assign the user account to all the tasks.
    • You save and then publish the plan in Project Server 2010.
    • You log on to the mailbox of the user account that you created to see whether the task list is synchronized.


In this scenario, duplicate tasks are created in the task list in Microsoft Outlook.

  • You cannot edit security categories that contain more than 1000 projects when one or more projects in the security categories are archived and then renamed.
  • You cannot submit a project to the next stage of a demand management workflow in Project Server 2010.
  • When a team resource tries to self-assign a task, the task is still displayed in the task list and is not assigned correctly to the team resource.
  • When you change a project summary task in Project Server 2010, the timephased budget cost information for cost resources is lost.
  • When Active Directory Domain Services (AD DS) contains an inactive user, the Project Server security group synchronization process fails.
  • Timephased remaining costs and actual costs are calculated incorrectly in the report database in Project Server 2010.
  • When you set a custom date field to NA in Project Server 2010, the date 1/3/84 is displayed unexpectedly in the field.
  • Values in a custom field are not displayed in Project Professional 2010 or in Project Web App (PWA). This issue occurs when the custom field can contain multiple values. However, the values are displayed in Project Professional 2010 or in PWA after you clear the local project cache.
  • After you save a value in the cost formula field on a Project Detail Page (PDP), an incorrect value is displayed. This issue also occurs in the percentage formula field.
  • After you accept status updates for a project in Project Server 2010, the project displays actual work that is submitted through PWA as an incorrect decimal value. For example, a project displays .48h as the actual work even though you submitted .5h as the actual work.
  • Assume that you self-assign a task in Project Server 2010, and then you open a new timesheet that contains an assignment without any planned work. In this situation, the task enterprise custom field does not populate values as expected.
  • Assume that you edit a task by using the Schedule Web Part in the Project Center. When you try to close and update the task, you receive the following message:
    This project is currently checked out. No edits can be made to it while it is checked out.
  • When you update the status of certain projects, the status update job fails. Additionally, you receive the following error message:
    Status approval internal error: StatusingInternalError (3116)
  • When you publish a Project Detail Page (PDP) in Project Server 2010, the values in an enterprise custom field are lost. This issue occurs even when you do not change the project schedule in the PDP.
  • Buttons on the ribbon are disabled for certain tasks in the Approval Center. This issue is caused by a script error that occurs on the Approval Center page.

April 2012

Rollup - http://support.microsoft.com/kb/2598152

Individual - http://support.microsoft.com/kb/2598272

Database Version 14.0.6119.5000

  • When a project manager approves status updates, and then publishes a project plan from Project Web App (PWA), the field that is calculated based on a cost rate table contains an incorrect value.
  • Assume that you configure an auto-publish rule for projects in Project Server 2010. When a project is checked out, the auto-publish rule does not publish the project as expected. Additionally, all successive auto-publish jobs are skipped, and other projects that meet the auto-publish rule are not published.
  • You cannot change the user logon account information to an account that does not exist in the Manage Users page. Additionally, you receive the following error message:
    The NT account specified is invalid. Check the spelling of the user name, verify that a valid domain name was included, and check that a duplicate domain was not used.

    Note If the user account is inactive, the user account validation should not occur, and you should not receive the error message.

  • It takes a long time to create a portfolio analysis in Project Server 2010 when the Analyze time-phased project resource requirements against organizational resource capacity check box is selected.It takes a long time to display the Resource Availability page when you click the Resource Availability button on the Resource Center view.
  • When you try to access a Project Center view that has a filter which filters by a value field of a custom lookup table, you receive the following error message:

    Unknown Error

    When you visit a project detail page in PWA, you see duplicate values in fields that are associated with a lookup table.

  • Assume that you back up a project that contains a resource plan. After you restore the project, the resource plan disappears.
  • Project Server 2010 deletes resources and assignments from projects unexpectedly.

February 2012


Rollup - http://support.microsoft.com/kb/2597152

Individual - http://support.microsoft.com/kb/2597138

Database Version - 14.0.

  • Consider the following scenario:
    When you use the Project Server Interface (PSI) to update an enterprise custom field on a local resource, the values in the enterprise custom field that are associated with the local resource are lost.

    • You set the system time zone to a setting between UTC and UTC +12:00 on a Project Server 2010 server.
    • You set a date period for a project in the Date Range dialog box by using Project Web App (PWA). For example, you set the Date Range when you edit a resource plan.
    • You view the date value on the Date Range group on the ribbon.

    In this scenario, the date value that is displayed does not match the date value that you set. Additionally, the date period is one day earlier than the date period that you set.

  • Assume that you create a timesheet that contains a task. The task has a Flag enterprise custom field that is set to Roll down. In this situation, the timesheet is not created successfully. Additionally, you receive the following error message:
    The Timesheet creation failed, because of problems with the project server or with data validations, such as resources not being valid work resources or users. Check your environment, and then try again.

    Then, you delete the timesheet. In this situation, you receive error 24011 for the Reporting (Timesheet Delete) queue job.

  • When you add a task to a timesheet in a project whose name contains an ampersand (&), you receive the following error message:
    An unknown error has occurred.
  • Assume that a status manager rejects some updates to a user's timesheet and publishes the project plan. Then, the user resubmits the rejected values. In this situation, the timesheet is displayed as approved. However, the re-submitted updates do not appear in the approval center or in the project plan.
  • When a resource pool is resynchronized with Active Directory, the Exchange Server Synchronize Tasks property flag for users is reset. Therefore, users are not synchronized with the Exchange Server until the Synchronize Tasks settings are re-enabled.
  • When you try to set actual work for a manually scheduled task on a nonworking day, the actual work values that are displayed in PWA, such as in My Tasks, may not appear. For example, five hours of actual work entered on Sunday may be displayed as zero hours in My Tasks.
  • The Task Hierarchy field in a timesheet view is not populated until the timesheet is saved. This issue occurs when one of the following conditions is true:
    Assume that you have a fixed duration task that has more than one enterprise resource assigned. Then, a user updates the actual work of a resource in the task by using Project Web Access (PWA). In this case, the task-level % Complete and Actual Duration values are not updated correctly when you view the task in Project Professional.

    • An existing task that is assigned to a resource has no planned or actual work during the period of a newly created timesheet.
    • A new task is assigned to a resource, and a user opens an existing timesheet period that contains the new assignment.
  • When you publish projects, you receive the following error message in the queue:

    Queue Error:

    General

    Microsoft.Office.Project.Server.BusinessLayer.Queue.Message:

    ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='<uid>' projectuid='<projectuid>' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.UpdateSRAMessage: projectUid = <projectuid>' messageID='179' stage='' blocking='Block'.

    Queue:

    GeneralQueueJobFailed (26000) - ProjectPublish.UpdateSRAMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='<uid>' JobUID='<jobuid>' ComputerName='<computername>' GroupType='ProjectPublish' MessageType='UpdateSRAMessage' MessageId='179' Stage=''. For more details, check the ULS logs on machine <computername> for entries with JobUID <jobuid>.

  • Assume that you have a multiple-value custom field that is referred from a formula in an enterprise project custom field. In this situation, when the formula is recalculated on the server, you do not receive a list of all selected values. Instead, you receive only the last value. For example, a multiple-value custom field displays the values A1, A1.1, C, C1.1, and C1.2. However, the formula on the server returns the value C1.2 only.

December 2011

Rollup - http://support.microsoft.com/kb/2597015

Individual - http://support.microsoft.com/kb/2596997

Database Version - 14.0.6114.5000

  • Consider the following scenario:
    Assume a PWA site administrator disables the Allow future time reporting setting on a Project Server 2010 server that has single entry mode enabled. In this situation, when you submit a timesheet, an error occurs.

    • You create a Project Web App (PWA) site on a Project Server 2010 server that has single entry mode enabled.
    • You recall a timesheet through the PWA site.
    • You review the timesheet on the PWA site.

    In this scenario, the actual work values in the timesheet are updated unexpectedly.

  • When you create a project template that contains a custom calendar, you cannot use Project Server Interface (PSI) to create a project from the project template.
  • When a timesheet approval job fails, the timesheet appears in the approval list. Then, when you approve the timesheet for the second time, a TimesheetIncorrectMode error occurs. Additionally, you receive the following detailed information about the error:
    There has been an error processing a timesheet for which you are/were responsible. Check your approvals list to locate the offending timesheet if one exists. The error condition may be related to the fact that Timesheets are a state driven feature; therefore, the allowable values for processing are dependent upon the existing value which for this transaction was 3.
  • Consider the following scenario:

    • You apply Service Pack 1 for a non-English language pack on a Project Server 2010 server.
    • You create a PWA site that uses the same non-English language.
    • You apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2536600.
    • You log on to the PWA site.

    In this scenario, the column headers on the Project Center page, My Tasks page and Resource Center page are displayed in English instead of the non-English language that you used to create the site.

  • Consider the following scenario:
    Assume that you specify a minimum version level required by Project clients to connect to a Project server in Project Server 2010. When you use a Project client that does not meet the minimum version level required to connect to the Project server, the client connects to the server successfully. However, the client should be unable to connect to the server.

    • You add an enterprise custom field that includes a formula to a project.
    • The formula references a baseline field that is set to NA.
    • You save the project from a Project Detail page.
    • You review the project through PWA.

    In this scenario, the data in the enterprise custom field is lost.

  • When you try to save a project to a Project Server 2010 server, you receive the following error message:
    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.
  • Assume that you set the Publish field to No for a task that is already published in a project. After you publish the project to a Project Server 2010 server, all the pending status approval items are rejected on the Approval Center page.Note This hotfix package does not change the rejection behavior for reassigned, self-assigned, or newly created tasks. In these cases, if you set the Publish field to No, all the pending approval items are still rejected on the Approval Center page.
  • Assume that a workflow for a project is successfully completed. When you try to open the project by using PWA after 60 days, you receive the following error message:
Unable to open the project. The workflow associated with the project has been terminated unexpectedly.
 
Database Version - 14.0.6112.5000
  • When you use the TimesheetCreated event to customize a timesheet in Project Server 2010, the timesheet does not display the correct data.
  • When you accept updates for a task in Project Web App (PWA), the duration and actual work values for certain tasks are lost.
  • Consider the following scenario:

    • You add an enterprise custom field which is based on a lookup table to a timesheet in Project Server 2010.
    • You update the timesheet.
    • You submit the timesheet.
    • You view the Approval Center.

    In this scenario, the Approval Center displays two items that have to be approved. However, the Approval Center should only display one item.

  • Consider the following scenario:
    Assume that you close a task to prevent that task from being updated in a timesheet in Project Server 2010. When you recall a timesheet to which the task was previously added, the task disappears from the timesheet.

    • You set yourself as the assignment owner of a material resource in the Assignment Owner field in Project Server 2010.
    • You assign the material resource to a new task in a project.
    • You save and publish the project.
    • You view the new task on the My Tasks page in PWA.

    In this scenario, the My Tasks page does not display the new task. Additionally, the reminder does not display the correct number of new tasks.

  • When you group by projects in the Timesheet view in PWA, PWA displays duplicate project names.
  • Consider the following scenario:
    Consider the following scenario. You add a Task Hierarchy field to the Timesheet view in PWA. Then, you add a new assignment to the timesheet. In this situation, the Task Hierarchy field does not display the task hierarchy details. However, the Task Hierarchy field displays the task hierarchy details after you save the timesheet.

    • You create custom fields that are associated with tasks in PWA.
    • You update a task together with the custom field information on the My Timesheets page.
    • You import the results into the My Tasks page.

    In this scenario, the Timesheet view does not display the custom field value. Additionally, the Timesheet view does not display the custom field value when you create additional timesheets.

  • Consider the following scenario. You log on to PWA as a project manager. You approve a task and enter many characters into the comments text box in the Approval Center. In this scenario, you receive the following error message:

    An Error occurred while processing one or more items. This was caused by one of the following:

    A timesheet job is failed and blocking correlation in the queue.
    The approval item no longer exists or has already been approved.
    The host server is unreachable.

  • This hotfix configures the Approval Center to highlight task updates when a task is updated in Project Server 2010.

August 2011

Rollup - http://support.microsoft.com/kb/2553049

Individual - http://support.microsoft.com/kb/2553047

Database Version - 14.0.6105.5000 (Not updated - so same as June)

  • When you apply updates on a completed task that does not have an actual start date, task scheduling fails in Project Server 2010.
  • Assume that you first set a large value for the actual work on a material assignment in Project Server 2010. Then, youreduce the value. In this case, the actual work is saved incorrectly for the material resource.
  • Assume that you click Send to submit a timesheet in Project Server 2010. You click Send again when the timesheet is being processed in the queue. In this case, a TimesheetIncorrectMode error occurs.
  • Task scheduling fails in Project Server 2010 if a project contains links to tasks that do not exist.
  • Consider the following scenario:
    The scheduling feature changes a task’s start date to an earlier date under certain conditions. This issue may cause task scheduling to fail in Project Server 2010.

    • You have a project that has a material resource.
    • The material resource is assigned to a task.
    • The material resource has no cost.
    • The cost accrual is set to the start of the assignment.

    In this scenario, task scheduling fails in Project Server 2010.

  • Assume that you open a timesheet for a future period of time. Then, you click Save. In this case, additional lines are added into the timesheet.
  • You may experience one or more of the following issues in Project Server 2010:
    When a project manager makes a change to an assignment in Project Server 2010, resources receive an email message notification even if the assignment is completed.

    • When you update a timesheet line, you may receive the following error message:
      An unhandled exception occurred in Microsoft.Office.Project.Server.BusinessLayer.Statuing.StatusingSendGridUpdatesForNodeConsistency.
    • When you save a timesheet, the queue job fails. Additionally, the following message is logged in the Unified Logging Service (ULS) log:
      assert - resume_computation error.
  • The reporting database update job fails in Project Server 2010. Therefore, other jobs that are marked with "waiting to be processed" that follow the update job in the queue are auto canceled. 
  • When you click the This is an Enterprise Project. Click this icon to open the Project for editing in Project Professional icon to open a project in read/write mode in the Project Center, the project opens in read-only mode.
  • You cannot use the QueueUpdateProject project server interface (PSI) to change a project owner if you do not have Save permission in Project Server 2010.

 June 2011

Rollup - http://support.microsoft.com/kb/2536600

Individual - http://support.microsoft.com/kb/2536586

Database Version - 14.0.6105.5000

  • Assume that you edit a project plan through a Project Web App (PWA) site that is hosted in Microsoft Project Server 2010. When you try to calculate the project plan, you receive the following error message:
    An error occurred while scheduling the project. Try to schedule the project again in a moment. If the problem persists, contact your administrator.
  • No cancellation feedback message displays when you perform a cancel operation in a PWA site that is hosted on Project Server 2010.
  • Assume that you perform a cancel operation for the Project Publishing event, the Project Summary Publishing event, or the Project Updating Scheduling Project event in a project detail page (PDP) in Project Server 2010. In this situation, no cancellation notification message is displayed.
  • An exception occurs when you synchronize users from a domain that does not contain a Project Server 2010 server.
  • You cannot create timesheets when you migrate databases from Office Project Server 2007 to Project Server 2010.Note This issue occurs because the Project Name field is removed from the My Timesheet view when an Office Project Server 2007 instance is configured.
  • When you enable Single Entry Mode on a Project Server 2010 server, resources can remove themselves from a task through PWA even though they have added actual work to the task. Therefore, the approved actual work is deleted from the Project server.
  • You edit a project plan that contains a custom field in a project detail page in Project Server 2010. Additionally, the custom field includes a formula. You save and check in the project plan, and then you visit another page before the save and check in request is completed. In this situation, the project plan may remain in a checked-out state.
  • Assume that you try to approve a task that has a summary task as its predecessor or successor in Project Server 2010. When you preview the task’s status update in the Status Update Preview page, 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.
  • You cannot open multiple projects from the PWA that is hosted on a Project Server 2010 server when the list separator is not a comma.
  • The PSI returns incorrect results when lots of Project Server Interface (PSI) calls are sent to the ASMX interface in Project Server 2010.
  • Consider the following scenario:
    You cannot sort your assignments on the My Timesheet page in Project Server 2010.

    • You log on to the My Timesheets page through PWA.
    • You open an already approved timesheet in the My Timesheets page.
    • You recall your timesheet.
    • You change actual work on a task in the timesheet.
    • You add actual work to a nonworking administrative time category.
    • You save the timesheet, and then you submit it.
    • You open the project plan in a Project 2010 client after actual work is synchronized with the project plan.

    In this scenario, the actual work contour is incorrect. For example, a value that displayed as 0.5d before, now displays as 0.51d.

  • When you log on to a project site through PWA, and then you try to view an issue that links to a deleted project task, you receive one of the following error messages:
    An error has occurred in the script on this page.

    Or

    An unexpected error has occurred.
  • When you enable the Use this field for matching generic resources option in PWA, the Roll down, unless manually specified optionin the Calculation for Assignment rows section is disabled unexpectedly.
  • Assume that you delete values in the Enterprise Custom Field (ECF) of a task through PWA. In this situation, any following update for the task cannot be saved. Additionally, there is no message that indicates the save operation failed.
  • The OnUpdatingScheduledProject event handler method that cancels updates for a project does not work in Project Server 2010.
  • Assume that you try to manage users on the Manage Users page in Project Server 2010. When you try to deactivate a user who is not listed on the first page, you receive an error message.
  • The NullRefrenceException exception may occur when you create a project by using the PSI in Project Server 2010.
  • Consider the following scenario:
    Assume that you perform a cube building operation on a PWA site that uses Claims based authentication. In this situation, Windows NT accounts are not automatically added to the Online Analytical Processing (OLAP) cube role.

    • A project manager accesses the Approval Center page by using PWA.
    • The project manager accepts task status updates from a team member.
    • The project manager verifies that the status update queue job is finished successfully.
    • The project manager opens the project plan, and then views the updated task status.

    In this scenario, the task status updates are not applied to the project plan.

  • The user delegation feature does not work for pages that directly call Windows Communication Foundation (WCF) in a Claims based authentication PWA site.
  • When a status manager accepts updates for tasks in Project Server 2010, the status of the update job is listed as processing on the Manage Queue page and never finishes.
  • Consider the following scenario:

    • You enableSingle Entry Mode in a PWA site.
    • You create a delegation for a user.
    • You start a delegation session as the user’s delegation.
    • You create a timesheet, and then you save it.

    In this scenario, the user or you as the delegation cannot open the timesheet. Additionally, you receive the following error message:

    Timesheet has already been created by either the timesheet owner or a delegate. Refresh this page to get an up-to-date list of timesheets.
  • Consider the following scenario:

    • You create a user account in a PWA site.
    • You add the user account to a group that only has the permission to see a project's details, but not to open the project.
    • You use the account to log on to the PWA site to see the project’s details.

    In this scenario, you cannot see the projects details. Additionally, you receive the following error message:

    Error: Access Denied.
  • Consider the following scenario. You edit a project through PWA. The edit operation starts a server-side scheduling process. In this scenario, you cannot save the project successfully. Additionally, you receive the following error message in the Unified Logging Service (ULS) log:
GeneralProject:ProjectSchedulingEngineException (9133). Details: id='9133' name='ProjectSchedulingEngineException' uid='a610edbc-b5ad-448b-8b35-3895e09441b8' exception='Microsoft.Office.Project.Scheduling.EventHorizonFinishException: Error in the application.
 
 
 
Due to some known issues found at release it was also recommended to update to June 2011 CU

Download - http://www.microsoft.com/downloads/details.aspx?FamilyId=B9FCDC42-EEA4-4C08-9169-A9A73E55B8D4

List of fixes - http://download.microsoft.com/download/B/0/D/B0D1540B-6CF6-4674-9C8E-7A45FD91C163/Microsoft%20SharePoint%202010%20and%20Office%20servers%20Service%20Pack%201%20Changes.xlsx

Database Version 14.0.6027.1000

April 2011

Rollup - http://support.microsoft.com/kb/2512801

Individual - http://support.microsoft.com/kb/2516483

Database Version - 14.0.5137.5000

  • Assume that a master project has a subproject that contains more than 100 tasks in Microsoft Project Server 2010. You try to view the master project tasks from Project Detail Pages. In this situation, not all the tasks are visible. Additionally, the subproject tasks collapse unexpectedly.
  • Consider the following scenario:
    You try to select certain time periods on the My Tasks page through Project Web App (PWA). You click the Next button multiple times on the My Tasks page. In this situation, a time period start date is a day earlier than what it should be.

    • You have a single entry mode in Project Server 2010.
    • You update the timesheet line for a task assignment.
    • You submit the task status and the timesheet.
    • You try to delete the project that contains the task after the timesheet is approved.

    In this scenario, the project cannot be deleted. Additionally, you receive an error message.

February 2011

Rollup - http://support.microsoft.com/kb/2475879

Individual - http://support.microsoft.com/kb/2479792

Database Version - 14.0.5130.5000 (Not updated - same as December)

  • You enable Single Entry Mode on a Microsoft Project Server 2010 server, and then you send a timesheet. In this situation, the task status manager does not receive an email message notification for status updates.
  • Consider the following scenario:
    When many users try to create timesheets on a Project Server 2010 server at the same time, the user who first submits a timesheet creation request receives an error message. In this situation, the rest of users can create timesheets successfully. However, the timesheets that are created do not contain administrative line items.

    • You create a custom field in a Project Web App site.
    • The site is hosted on a Project Server 2010 server and has a non-English locale.
    • The custom field contains a graphical indicator that is based on formulas.
    • You save the custom field, and then you open it again.

    In this scenario, the formulas displays in English instead of non-English. Additionally, you cannot save the custom field again.

  • You assign a resource to an existing project plan in Project Server 2010. Then, the resource inserts a row in a timesheet. In this situation, there is no top-level summary task that is listed for the plan in the menu of the row.
  • When lots of users try to create timesheets at the same time on a Project Server 2010 server, the following issues occur:
    Assume that you edit a project in a project detail page (PDP) in Project Server 2010. When you select to save and check in the project, then you visit another page before the save and check in request is completed. In this situation, the project may be left in a checked out state.
  • Certain users cannot create timesheets successfully. Additionally they receive an error message.
  • The timesheets that are created do not contain administrative lines. In this situation, users cannot add time to the timesheets.
  • When you try to save a project in Project Server 2010, you receive the following error message:
Cannot insert duplicate key row in object 'dbo.MSP_ASSN_CUSTOM_FIELD_VALUES_SHADOW' with unique index 'UQ_MSP_ASSN_CUSTOM_FIELD_VALUES_SHADOW'
 
 
 

Individual - http://support.microsoft.com/kb/2459112 and http://support.microsoft.com/kb/2459113

Database Version - 14.0.5130.5000

  • In Project Web App (PWA), you cannot change the value in the Actual Start field on the My Work Tasks page.
  • Consider the following scenario:In Project Professional 2010 you save the baselines for a project. Then, you use the Update Tasks command to update the tasks in the project. In this situation, the baseline values that you previously saved are lost.
    • You are a team member of a project in Project Server 2010.
    • You only have permissions to view projects in PWA.
    • You drill into the project.

    In this scenario, you receive the following error message:

    An unexpected error has occurred.
  • In Project Server 2010, you try to change the owner for a project in the Project Information Project Detail Page (PDP). However, you cannot change the project owner in the Owner field when the new owner does not have the Save permission on the project.
  • In Project Server 2010, you cannot create a PWA site that uses a host header name. Instead, the site can only use the server name.
  • Consider the following scenario. In Project Server 2010 you create a site by using the Microsoft Project Site template. Then, you try to access the Cost column in the Risks page of the new project site. In this scenario, you receive the following error message:
    An unexpected error has occurred.

October 2010

Rollup - http://support.microsoft.com/kb/2394322

Individual - http://support.microsoft.com/kb/2413667

Database Version - 14.0.5114.5000 (Not updated - unchanged from June 2010)

  • Assume that you create a custom field together with a formula that uses the semicolon separator. When you create another custom field together with a formula that refers to the first custom field, you receive the following error message:
Unknown Error.

August 2010


Rollup - http://support.microsoft.com/kb/2352345

Individual - http://support.microsoft.com/kb/2276341 (There was also a reliance on the SharePoint Foundation patch for a jsgrid fix - http://support.microsoft.com/kb/2266423

Database Version - 14.0.5114.5000 (Not updated - unchanged from June 2010)

  • The New-SPProjectWebInstance cmdlet does not work together with the host header when a site collection already exists.
  • Project Server administrators now can resolve user names by using email addresses. For example, depending on how the claims providers are configured, the user logon account can be entered and validated as an email address such as username@live.com

    on the Edit User page.

  • After you provision a Project Web Access (PWA) site, the queue service process restarts unexpectedly. This causes the interruption of the queue on other PWA sites.
  • The queue service may consume large amounts of memory, such as several gigabytes (GB), when there are hundreds of PWA sites in a farm.
  • If users cannot be resolved in Active Directory because of intermittent connectivity issues, the users are deactivated.
  • Consider the following scenario. You apply the hotfix package that is described in Microsoft Knowledge Base article 2075990. You connect the Project client to Project Server 2010 and use manually scheduled tasks. Then, you update the % complete column on a manually scheduled task in the project. In this scenario, the baseline work value is cleared from other manually scheduled tasks unexpectedly.

June 2010


No Rollup

Individual - http://support.microsoft.com/kb/2075990

Database Version - 14.0.5114.5000

  • The tracking GUID that is specified in the Project Server Interface (PSI) headers is not honored as the Job Group ID of the resulting queue jobs.
  • If the project uses a Force-in alias or a Force-out alias, you cannot switch a project to automatic scheduling. Additionally, recalculation fails, and you receive the following error message:
    An unknown error has occurred.
  • You set a baseline to the NA status for any project task. However, this baseline is not updated when you publish the project from the client.
  • You cannot create enterprise projects or templates on the server from certain Microsoft Office Project 2007 templates.
  • If the value of the ChangeXML parameter is a large number, the UpdateStatus PSI method requires a long time to update many tasks that apply to different users. This behavior blocks the Team Foundation Server (TFS).
  • When you attach some databases and then provision a site, the upgrade fails if you load a language pack that is not supported by Project Server 2010.

RTM Initial Release

Database Version 14.0.4750.1000

 

Skip to main content