- Home
- Project
- Project Support Blog
- Project Server 2019 Public Updates
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Here are all the articles for fixes released for Project Server 2019 from its launch to date. The DB Version at release was 16.0.10337.12109. Some months there is more than 1 package for updating SharePoint Server 2019.
DB Version:16.0.10407.20000
This update fixes an issue in which access is denied on project detail pages for users and even administrators for Project Web App.
DB Version: 16.0.10406.20000
DB Version: 16.0.10403.20000
This security update also contains a fix in Project Server:
-
Fixes an issue in which you cannot update a project calendar or task calendar for a project by using the client-side object model (CSOM).
DB Version: 16.0.10402.20016
DB Version: 16.0.10401.20025
DB Version: 16.0.10399.20005
This security update also contains a fix for the following nonsecurity issue in Project Server:
-
Fixes an issue in which you cannot update the ScheduledFromStart property for a project by using the client-side object model (CSOM) code.
DB Version: 16.0.10398.20000
DB Version: 16.0.10397.20002
DB Version: 16.0.10396.20000
DB Version: 16.0.10395.20001
DB Version: 16.0.10394.20021
DB Version: 16.0.10393.20000
This security update also contains fixes for the following nonsecurity issues in Project Server:
-
Fixes an issue in which the reporting database refresh process fails when you restore metadata in Project Web App (PWA).
-
When a user publishes a project, other users might experience the following symptoms:
-
Users cannot start Project desktop and connect to the Project Server.
-
Users cannot open projects. This includes projects that they own and projects that are being opened for read-only access.
-
Users cannot open the schedule web part.
-
Team members cannot access their tasks page.
-
Administrators cannot access the Force Check-in Enterprise Objects page.
-
DB Version: 16.0.10392.20000
This security update also contains a fix in Project Server. Consider the following scenario:
-
You have the Content Editor web part placed on a Project Detail Page (PDP).
-
You edit a project in Project Web App (PWA).
-
While you are editing, the SharePoint web page security validation times out.
-
You close the project, and you try to check in the project.
In this situation, the "Processing" toast appeared but it never went away. Additionally, the project didn't get checked in. This issue is fixed so that now the following expected message appears:
The security validation for this page has timed out. Click Back in your Web browser, refresh the page, and try your operation again.
DB Version: 16.0.10391.20000
DB Version: 16.0.10390.20000
This security update also contains a fix in Project Server:
-
Fixes an issue in which you may not be able to update resources by using the client-side object model (CSOM) if a remote event handler is attached to a resource event, such as Resource Changing.
DB Version: 16.0.10389.20000
DB Version: 16.0.10388.20004
This update also contains a fix in Project Server. Consider the following scenario:
-
Users names in your Active Directory contain a comma. For example, Lastname, Firstname.
-
In Project Web App (PWA), you have enabled the Active Directory Resource Pool Synchronization connection.
-
By default, because the incoming resource names contain the comma, and the comma conflicts with the comma list separator, the server converts the comma to a semicolon.
-
You prefer that the comma is completely removed. Therefore, you set the WADMIN_AD_SYNC_REPLACE_CHAR field within the pjpub.MSP_WEB_ADMIN table to either NULL or an empty string.
-
When the synchronization occurs, you find that the comma has been replaced with a space.
After this fix is applied, you can set the WADMIN_AD_SYNC_REPLACE_CHAR field to NULL and the server correctly constructs the resource name to exclude a space. For example, Lastname Firstname.
DB Version: 16.0.10387.20008
No Project Server 2019 updates
DB Version: 16.0.10386.20015
No Project Server 2019 updates
DB Version: 16.0.10385.20001
This security update fixes the following nonsecurity issues in Project Server 2019:
-
Fixes an issue in which the language of the values in flag-type custom fields within an online analytical processing (OLAP) cube do not match the Project Server language. For example, the flag values appear as "True" or "False" in English, and they are "Vero" or "Falso" in Italian, but the values are always displayed in the English form.
-
Fixes the DatabaseUndefinedError and System.Data.SqlClient.SqlException (0x80131904): There is already an object named 'pk_lt_uids' in the database errors that occur when you query lookup tables by using the SharePoint client-side object model (CSOM).
DB Version: 16.0.10384.20000
This update also contains a fix in Project Server:
-
Fixes an issue in which percentage information is missing from the Current Progress column after you select a timesheet on the Import Timesheet page.
DB Version: 16.0.10383.20001
No Project Server 2019 updates
DB Version: 16.0.10382.20004
This security update fixes the following nonsecurity issue in Project Server 2019:
-
Fixes an issue in which you cannot filter resources by using the options under the Outline menu in the Build Team functionality.
DB Version 16.0.10381.20001
This security update also contains fixes for the following nonsecurity issues in Project Server 2019:
-
Fixes an issue in which opening the approvals page or submitting timesheets is slow.
-
Consider the following scenario:
-
On a task, you set the Status Manager.
-
You publish the project.
-
Later, while in the same editing session, you change the Status Manager to a different manager.
-
You publish the project.
In this scenario, the Status Manager property does not get updated in reporting. Instead of reflecting the new Status Manager, the old one is still observed.
-
No Project Server 2019 updates
DB Version 16.0.10379.20001
No Project Server 2019 updates
DB Version 16.0.10378.20002
No Project Server 2019 updates
DB Version 16.0.10377.20001
This security update also contains a fix for the following nonsecurity issue in Microsoft Project Server 2019:
-
Submitted status updates don't appear for approval after you submit a timesheet.
DB Version 16.0.10376.20001
No Project Server 2019 updates
DB Version 16.0.10375.20000
No Project Server 2019 updates
DB Version 16.0.10374.20000
This security update also contains a fix for the following nonsecurity issue in Microsoft Project Server 2019:
-
After you run the ExportWorkspaceItemsByDisplayName2019.sql script from the General Data Protection Regulation (GDPR) for Project Server, you can't find the OwnerUserClaimsAccount field in the query results.
DB Version 16.0.10373.20000
This security update also contains fixes for the following nonsecurity issues in Project Server 2019:
-
Deleting timesheets takes a long time.
-
Current Max. Units (%) in Microsoft Project user settings is unexpectedly reset to 100 percent after it's saved through the client-side object model (CSOM) or UI.
DB Version 16.0.10372.20060
-
The projects for which the project summary task is locked are shown in the list of projects on the Add Task page. This page is accessed from the Task and Timesheet views by using the Add Yourself to a Task option.
-
The SharePoint Products Configuration Wizard doesn't finish if the SQL Server collation is Turkish_CI_AS. Additionally, the PSCDiagnostics log shows an error message that resembles the following:
"ERR Failed to upgrade SharePoint Products.
An exception of type System.Data.SqlClient.SqlException was thrown.
Additional exception information: Must declare the scalar variable "@newViewUID".
System.Data.SqlClient.SqlException (0x80131904)"
This issue occurs after you install KB 4484472.
DB Version 16.0.10371.20043
-
Fixes accessibility issues in the Pick Resource feature (also seen in Project Web App as Choose User) dialog box because of an incorrect focus on the OK button. After you apply this update, the focus is set on the Search Text Edit field.
-
The date range of the timescale on the Project Web App (PWA) Approvals page is off by one day if the user's time zone is set to a zone east of UTC. For example, UTC+2.
-
In some situations, the Project Calculation Service (PCS) crashes while it opens a given project. The crash details that are logged in the SharePoint Unified Logging System (ULS) logs or in the Windows event logs resemble the following entry:
"The worker encountered a very serious error and will shutdown. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)." -
Ribbon buttons in the task management section (View,Edit, Delete item) in the task list are disabled for the tasks that are listed beyond the first page.
https://support.microsoft.com/en-gb/help/4493160/security-update-for-office-online-server-january-12...
https://support.microsoft.com/en-gb/help/4493162/security-update-for-sharepoint-server-2019-january-...
https://support.microsoft.com/en-gb/help/4493161/security-update-for-sharepoint-server-2019-language...
DB Version 16.0.10370.20001
- Users cannot open the Project server admin page (ServerConfig.aspx), and you receive an error message that resembles the following:
"System.ArgumentException: Culture ID 4096 (0x1000) is a neutral culture; a region cannot be created from it." - When you view a timeline in Project Web App, the day portion of a date label is repeated. For example, if the language and locale are set to Portuguese, and you have a task that is scheduled to begin on November 13, the label on the timescale shows "13 13e Novembro" instead of the expected "13 Novembro."
https://support.microsoft.com/en-nz/help/4486750/security-update-for-office-online-server-december-8...
https://support.microsoft.com/en-nz/help/4486751/security-update-for-sharepoint-server-2019-dec-8-20...
https://support.microsoft.com/en-nz/help/4486752/security-update-for-sharepoint-server-2019-language...
DB Version 16.0.10369.20000
No Project Server 2019 updates
DB Version 16.0.10368.20022
- Fixes a scheduling engine crash, and adds additional logging to help identify possible future crashes.
- Fixes an issue in which the "Reporting (Timesheet Save)" queue job runs very slowly. This job is created when timesheets are submitted. This issue creates a backup of queue jobs and causes other slow performance problems.
- Fixes an issue in which grouping in a task list that's in a project site breaks the quick edit experience.
- Fixes an issue in which a resource's availability or maximum units information is lost after the resource is updated through the Client Side Object Model (CSOM) or the Project Web App user interface (UI).
DB Version 16.0.10367.20000
- Sometimes, when you open a project, the % Complete value on a Fixed Duration task that's 100 percent complete changes to a lesser value.
- On a portfolio cost analysis, the picker control that enables you to choose "Forced-in," "Forced-out," or "Auto" is unavailable. Therefore, you can't change projects that you want to force in or out of the analysis. This occurs on Project Web App instances that have been defined as host-named site collections.
No Project Server 2019 updates
DB Version 16.0.10364.20001
- Sites that have many timesheets or timesheet views may experience a time-out when you create or modify timesheet views. This may make it impossible to create timesheets or open existing timesheets.
- When you follow a procedure to link a project task to an Issue or Risk within the Asset Picker table, items such as Issues, Documents, Tasks, and Deliverables are missing.
DB Version 16.0.10362.20025 (language dependent) 16.0.10363.12107 (language independent)
- It is now possible to update task custom field values through the REST API.
- Editing a project in Project Web App or approving status updates uses the Project Calculation Service (PCS). In some situations, PCS crashes when it closes a project. The crash details as seen when viewed in the Unified Logging Service (ULS) log (or in the Windows event logs) resembles the following:
"The worker encountered a very serious error and will shutdown. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)."
DB Version 16.0.10360.20000 (language dependent) 16.0.10361.12114 (language independent)
- In the Google Chrome and Microsoft Edge Chromium browsers, when you leave pages such as the Project and Resource Center, changes that you made (such as adjusting column widths) are not saved.
Note For this fix to work, you have to first install Chrome or Chromium browser version 81 or a later version. - The Resource Request page may unexpectedly display engagements from other resources.
- In the Google Chrome and Microsoft Edge Chromium browsers, even if you select Cancel in the Edit Resource page, the resources remain checked out.
Note For this fix to work, you have to install Chrome or Chromium browser version 81 or a later version. - Consider the following scenario:
- You create a user from Manage Users. You do not select the User can be assigned as a resource option.
- Later, you edit the user account and you enable the option.
- You go to the Resource Center and select Capacity Planning button or go to Capacity Planning page with the page URL.
In this situation, a dialog box appears and states "There is no availability data for the resources you have selected. This commonly occurs for cost and material resources without enterprise resource calendars."
DB Version 16.0.10359.20000
No Project Server 2019 updates
https://support.microsoft.com/en-us/help/4484292/security-update-for-sharepoint-server-2019-april-14
DB Version 16.0.10358.20000
- Querying for a task dependency through the client-side object model (CSOM) returns a non-elapsed LinkLagDuration string for elapsed values. For example, you have a dependency that says 2FS+1ed. Instead of returning the expected 1ed, it returns 3d.
- When accessing certain projects through the client-side object model (CSOM) or REST, the process fails because of overflow in the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) fields.
- Consider the following scenario:
- You have server event code on the publishing event that extracts data from a project through the client-side object model (CSOM).
- You open a project by using Project or Project Web App.
- You make changes in the project.
- You publish the project.
In this scenario, the publishing event code that reads the project data runs for more than a minute and then times out. Therefore, the event unexpectedly cancels the publishing job.
- If you apply a filter to a Tasks list, you don't see the expected result for those items (which are on the second and subsequent pages).
https://support.microsoft.com/en-us/help/4484271/security-update-for-sharepoint-server-2019-march-10
DB Version 16.0.10357.20002
- After you edit a project in Project Web App, it may take a long time to save the project. This is especially true if there are many custom field values. This causes slower publishing, check-in jobs, and other related actions.
- Editing a project in Project Web App or approving status updates uses the Project Calculation Service (PCS). In some situations, PCS crashes while it closes the given project. The crash detail is logged in the Unified Logging System (ULS) logs, and it resembles the following:
"The worker encountered a very serious error and will shut down. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)." - Consider the following scenario:
- You have an enterprise resource custom field.
- You edit a resource and assign a value to the field.
- You delete the enterprise resource field.
- You edit the resource, and save your changes.
In this scenario, the process fails, and you receive the following error message:
"Unknown error has occurred"
DB Version 16.0.10355.20000
Adds support for the SameSite cookie attribute to remain compatible with changes in how web browsers such as Chrome handle cookies.
- Loading a timesheet takes a long time and may time out.
- Resource calendars aren't updated correctly when a base calendar changes. This may cause the timephased actual work reported by a team member to appear on different days from where it was entered.
- You are unable to set the assignment Actual Cost field either as a timephased or scalar value through the client-side object model (CSOM).
December 2019
DB Version 16.0.10353.20001
- When a SharePoint update is applied and the SharePoint Products configuration wizard is run, the reporting association views are dropped but not re-created.
- After you upgrade from Project Server 2010 to 2019, if you edit a project in PWA and delete an inactive task, after you save the project, you may be unable to reopen it.
- You are unable to update and clear local Duration and Outline Code field lookup values through the client-side object model (CSOM).
- Consider the following scenario:
- You create a project with a single task and large number of resources.
- You add all resources to the task.
- You save and publish the project.
- You edit the project in PWA.
- You click the drop down for the Resource Names column.
In this case, you will see that some resources are no longer assigned to the task.
DB Version 16.0.10352.20000
- When the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) earned value becomes very large, an overflow condition occurs. This causes the client-side object model (CSOM) or REST calls that are made while accessing the project to fail. The SVP and CVP values now have a lower limit of -100% and upper limit of 100%.
- After this update is installed, you can receive information about any type kind of completed queue jobs for a project when you use the new GetAll() method from a REST call.
- Consider the following scenario:
- You create a new project in Project Web App.
- When the schedule project detail page appears, the Project Summary Task is visible.
In this situation, you cannot type in the Task Name field to create a new task.
- Consider the following scenario:
- As a timesheet user, you open your timesheet.
- On an assignment that has no actual work, you enter actual work on a given date.
- You save the timesheet.
- You change your mind, and you remove the actual work that you previously entered.
- You send the timesheet or status update for approval.
- The status manager approves the update.
In this scenario, when the assignment is viewed in Project Professional, it has an actual start date set even though you removed the actual work in the timesheet, and this also removed the actual start date. This fix correctly removes the assignment's actual start date in this situation.
DB Version - 16.0.10351.20000
- When you select View Installed Updates in the Windows Control Panel, you see the most recently installed SharePoint Server 2019 Public Updates listed. However, the version number of these updates isn't displayed in the Version column. After you install this update, the version number of these updates will be displayed.
- Makes changes to display the new Japanese era name for date format samples in Date Format in Project Web App (PWA) sites.
- You can now update a task dependency lead and lag time by using the LinkLagDuration property through the client-side object model (CSOM). Similar to other duration properties (such as the Task.Duration property in the Task Object), it excepts either a string or an integer value. For example, either 1d or 480 is acceptable to indicate one day of work.
- The CalendarException.RecurrenceWeek property returns wrong values for calendar exceptions through the client-side object model (CSOM).
- When the Schedule Variance Percentage (SVP) earned value becomes very large, an overflow condition occurs. This may cause either abnormal SVP values within Project Web App (PWA) project views or the view may fail to load. The SVP value now has a lower limit of "-100%" and upper limit of "100%".
DB Version 16.0.10350.20000
-
Through the client-side object model (CSOM), the TaskLink ProjUid property for an external task returns the ID of its own project instead of the ID of the project that the task refers to. This update adds the ExternalProjectUid and ExternalTaskUid properties to the Task class to fix this issue.
-
Loading a timesheet is very slow and may take one minute or more.
-
Project Server Interface (PSI) API calls that require the permission of a farm administrator fail for users who are farm administrators but not server administrators.
https://support.microsoft.com/en-us/help/4475555/security-update-for-sharepoint-server-2019
DB Version 16.0.10349.20000
-
Fix: When the Schedule Variance Percentage (SVP) earned value field becomes very large, an overflow condition occurs and prevents PWA project views from loading.
-
Fix: When you click the Export to Excel button to export data on pages such as from the Project Center, you receive the following error message:
Sorry, something went wrong. An unexpected error has occurred.
DB Version 16.0.10348.12104
-
Adds the ProjectIdMinDigit, ProjectIdSeed, ProjectIdPostfix and ProjectIdPrefix properties in the EnterpriseProjectTypeCreationInformation class. You can now use these properties to update the Project Identifier information of an enterprise project type (EPT) through the client-side object model (CSOM).
-
Adds the ProjectQueuePublishSummary method for the ProjectCollection class in the client-side object model (CSOM) so that project-level fields on a project can be published independently from the entire project. For example, if you use a workflow in your project creation process, you can use this new method to publish the stage summaries.
- Updating a fixed duration task assignment from a timesheet may unexpectedly change the assignment’s finish date to an earlier date.
DB Version ?
Contains fixes for the following nonsecurity issues:
-
In some circumstances, if you delete a few views that are associated with custom fields that support multi-value selection from a lookup table in the database, and then you run the Repair-SPProjectWebInstance cmdlet, you find that the first view isn’t generated in the database.
DB Version - 16.0.10345.12101
Contains the following improvements:
- Adds support for the new Japanese era in the timeline portion of the Project Summary web part in Project 2019.
- Adds the GraphicalIndicator property to the CustomField class in the Client-Side Object Model (CSOM). You can now set and get a Graphical Indicator for a custom field.
For the complete list of SharePoint fixes see the article above
DB Version - 16.0.10343.20000
- In an environment that uses the Japanese new era calendar, date formats that contain year aren't applied on the Timeline view for dates that occur after May 1, 2019.
For full details of the SharePoint Server 2019 fixes see the articles above.
DB Version - 16.0.10342.12113
Contains the following improvement and fixes:
- Adds support for the new Japan era in SharePoint Server 2019.
-
Editing a project-level custom field while on a project detail page (PDP) cuases lost task-level calculated custom field values if the field formula includes the task's Unique ID.
- When you upload content to a document library, selecting a destination folder doesn't work. This issue occurs when you open the SharePoint site by using the Microsoft Edge browser.
DB Version - 16.0.10341.20000
-
his update adds the ability to change a task's duration type through the client-side object model (CSOM) after the task is created.
-
You can't set the description of a lookup table value to blank through the client-side object model (CSOM).
-
You can't get all the details of a dependency link, such as the lag duration and project UID properties, through the client-side object model (CSOM).
For full details of the SharePoint Server 2019 fixes see the articles above.
DB Version - 16.0.10340.12101
-
When the Missing server side dependencies health analyzer rule runs on a server that's not running the SPWebService service, an error message that states that some web parts are missing in the system is displayed in the health analysis report.
Note To fix the issue, you need to install both fixes together with this update.
For full details of the SharePoint Server 2019 fixes see the articles above.
DB Version - 16.0.10339.12102
For full details of the SharePoint Server 2019 fixes see the articles above.
DB Version - 16.0.10338.12107
Note To apply this security update, you must have the release version of Microsoft SharePoint Server 2019 installed on the computer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.