November 10, 2015, update for Project Server 2013 (KB3101502)

• Assume that a project manager publishes a project and grants you access through the Project Permissions feature. You're only given sufficient permissions to edit project level fields. When you edit and save the project from a Project Detail page, you receive the following error message:
  You need to have permissions to create a new project. Please ask the Project Web App administrator for permissions.
• When you publish a project, the publish process fails at 66%. and you receive a queue failure message that looks something like: 
  GeneralQueueJobFailed (26000) - ProjectPublish.UpdateSRAMessage
• Consider the following scenario:
  • As a team member, you go to your timesheet.
  • You enter actual work hours on a task.
  • You submit your timesheet.
  • You recall your timesheet.
  • You delete the actual work hours that you entered previously.
  • You resubmit your timesheet
  In this scenario, the Reporting publish job fails and the ULS log contains details similar to the following:
  System.InvalidOperationException: Reporting publish failed. The entity 'ID' is too large. 
• Assume that you change the Project Owner field from a project detail page and then save it. When you move away from the page and then go back to the page, the project owner isn't changed.
  
• In some instances, when you drill into a task from the Task page, you receive a message that states the web part can't be loaded. In the ULS logs, you see an error message that resembles the following:
  Exception occured in method 'Statusing.ReadStatusForStatusingViews' System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.
• After a submitted timesheet is rejected and recalled, you can't save changes to the timesheet any longer even if you have the Adjust Timesheet permission.
  
• Consider the following scenario:
  • You add some Visual Basic Applications (VBA) code to a project in Project Professional 2013.
  • You save and publish the project to Project Server, and then you check in the project.
  • You edit the project on the schedule project detail page in Project Server.
  • You change and save the project.
  • You open the project again in Project Professional 2013.
  In this situation, the VBA code is missing.
  
• Consider the following scenario:
  • You define an enterprise project level date field.
  • The date field resides on a project detail page (PDP).
  • You edit a project and change the custom date field by using the date picker control on the PDP.
  • You select the Save button.
  In this situation, the date that you set in the field isn't saved as expected.
  

Restart information

Prerequisite