February 10, 2015 update for Project Server 2013 (KB2880996)

• When you create a new task directly on the Timesheet page, regardless of the Finish Date entered for the task, the task will always be created on the correct Start Date but with a duration of one day.
  
• When you add nonstandard line classification tasks to a timesheet or manipulate tasks on an un-submitted timesheet where nonstandard lines exist, you may receive the "_error loading" error message.
  
• The permissions for all users who should have access to a project site may be synchronized incorrectly when you publish a project.
  
• Assume that you add the SQL Server Reporting web part to a Project Server 2013 page that contains other Project Server web parts. When you click the Refresh button in the SQL Server Reporting web part, the given Project Server web parts will be duplicated.
  
• Assume that you add the Project Server task list as a web part to a SharePoint page, and then you set a filter for the task list web part. When you browse to the page, the filter does not work correctly.
  
• Assume that you create a Project Web App (PWA) view for the schedule web part, and the view contains a filter that has more than 12 clauses. When you apply the view to the Schedule page while you edit a project, the view loads incorrectly. Additionally, you may receive the following error message:
  
  Project Web App hit an error processing your request and your unsaved changes were lost. Press OK to reload the session. Press CANCEL to close the session. If this happens again, contact your administrator.
• Assume that you create a site template in Project Server 2010. Then, you migrate Project Server 2010 to Project Server 2013. When you edit an Enterprise Project Type, you cannot select the given site template from the Project Site Template drop-down menu.
  
• If you cancel the selection of the Enable Project Site Sync option in the Project Permission Sync Settings page, you cannot sync the users by clicking Synchronize in the Connected SharePoint Sites page.
  
• When you click Close on the Build Team page, you may receive one of the following messages:
  
  Working on Checking In
  The project cannot be written to the server
• Consider the following scenario:
  
  • You open a project plan in Project 2013 from a Project Server 2013-based server.
  • You delete the value of a custom field that uses a lookup table on the server.
  • You publish and check in the project plan. Then, you open the project plan in Project Web App.
  In this scenario, when you click Edit on the Project Details page, you may receive an error message that resembles the following:
  This Web Part was unable to load. Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: <ID>
  For more information, contact your Project Web App administrator.
• Consider the following scenario:
  
  • You connect to a Project Web App (PWA) site by using Project Professional.
  • You create a project, and then add some resources to it.
  • You save and publish the project; in the Publish Project dialog box, you decide to provision the site as a subsite of another project.
  In this scenario, the permissions on the newly created site may be incorrect. Additionally, in the Project Server Queue Job Error Details it shows information similar to the following:
  
  GeneralQueueJobFailed (26000) - PreparePSProjectPermissionSynchronization.PreparePSProjectPermissionSynchronizationMessage. Details: id='26000' name='GeneralQueueJobFailed' GroupType='PreparePSProjectPermissionSynchronization' MessageType='PreparePSProjectPermissionSynchronizationMessage'

Windows Update

Microsoft Update Catalog

Restart information

Prerequisite