June 14, 2016, update for SharePoint Server 2016 (KB3115181)

• The Resource Plan button is removed from the schedule Web Part and Project Center. Project Server 2016 now offers the Resource Engagements and Capacity Planning features to replace resource plans.
  
• Fixes the following issues:
  • You can't set a Resource Assignment view to be filtered by a custom field, and you receive the following error message:
    An unknown error has occurred.
  • When you try to add or delete a user from a project server security group, you experience an error if the project site is a root web and the host header configuration is enabled.
    
  • After a project manager rejects a task update, you don't receive an email notification that informs you of the task rejection.
    
  • When you're denied permissions to open a project or view a project schedule in Project Center, you receive the generic "An error occurred while opening your project" error message instead of the more specific access denied message.
    
  • Assume that you save time for a timesheet without submitting. Then, a project manager deletes it from the project of the tasks on which you saved within your timesheet. When you go to submit the timesheet or a status update for that timesheet, it fails and you receive the following error message:
    An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary.
  • If the timesheet unit settings are set to weeks, planned work isn't displayed in timesheets.
    
  • A summary task may not correctly compute the rollup value of a custom field if the field is configured with the following properties:
    • A date type
    • A minimum rollup
    • A formula where the value may be null (N/A)
  • You can't edit and save changes to enterprise resources in Project 2016.
    
  • When an administrator edits the Proposal Summary Project Detail page, the following error message appears on the page:
    Sorry, something went wrong.
  • Assume that a project server administrator creates an enterprise project template. Then, project managers create a project by using the template and specify an owner for the project. When the project is saved, Project Web App ignores the owner information.
    
  • It takes a long time for the initial project publish and user synchronization jobs to complete. The end result is that a project manager who creates a project in Project Web App waits for a long time before being able to move to other Project Web App pages.
    
  • Consider the following scenario:
    • You have a project-level enterprise field that's linked to a lookup table.
    • The custom field is exposed on a project detail page (PDP).
    • You edit a project on the PDP. 
    • You change the value of the custom field as well as other fields such as the project description field.
    • You save the project.
    In this situation, you receive the following error message:
    An error has occurred while saving your project to the server. Please contact your administrator for assistance.
    In addition, the queue job error details state GeneralItemDoesNotExist.
    
  • After you change the booking type of a resource in a project, the booking type of the resource's assignments aren't updated to reflect the new booking type.
    
  • The status update process fails to update actual work on a project when a custom field formula calculation in the project fails.
    
  • Cost values are displayed incorrectly when you edit a project in Project Web App. For example, 100$ is displayed as 10.000$.
    
  • Assume that the Project Web App project editing session of a project has timed out. After you select OK to the "Your session has timed out because of inactivity. To continue editing this project, click OK" message and save the changes, the changes aren't applied to the project.
    
  • Enterprise Flag fields don't save a No value unless you explicitly select the value. Therefore, if you're looking at this value as you move from one Project Detail Page to another, you may find that the value is displayed as blank or NULL instead of the No value that you expect.
    
  • The Approvals page doesn't roll up totals on grouping rows for the timephased data.
    

• Schema management UI doesn't list crawled or managed properties.
  
  Note Upgrade of Search Service Application and re-crawl are required for the fix to take effect.
  
• A security trimmer fails because documents miss the CrawlUrl property.
  
  Note Upgrade of Search Service Application and re-crawl are required for the fix to take effect.
  
• This update adds clear support to clean up on-premises documents in SPO search index for cloud hybrid search. A CSOM method is added to support the new clear task, and a warning ribbon contains a link to the official documentation on how to run the clear task is added in the Reset Index UI.
  
• When you add or update documents in document libraries, a memory leak occurs on web font-ends.
  
• The Search Service Application is refactored in SharePoint Server 2016 so that the original interface can't be used by ISVs for building customization. This update exposes a new public interface to re-enable the customization ability.
  
• Assume that you use a querystring URL parameter to pass values at the query time. When you select a specific taxonomy term and then use the term GUID to search, the search doesn't work.
  

Download Center

Download update KB3115181 for SharePoint Server 2016

Prerequisite

Restart information