Project Server 2010 Cumulative Updates from August 2012 to date.

This post has been republished via RSS; it originally appeared at: Project Support Blog articles.

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and infrastructure update for Project Server 2010 from August 2012 to date.  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.

March 2019

No specific Project Server 2010 updates - but the roll up for SharePoint - https://support.microsoft.com/en-us/help/4462227/march-12-2019-cumulative-update-for-project-server-2010-kb4462227

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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.