SharePoint Server 2016 Project Server Public Update Issue

Starting with the December 2019 Public Update for SharePoint Server 2016, if your content database has Project Server tables (i.e. you’ve enabled Project Server on your farm), you may run into an error upgrading one or more content databases due to a Deny ACL on Project Server tables to the PSDataAccess role. This issue only occurs when you have provisioned your content database via PowerShell under an account other than the farm admin service account (the account running owstimer.exe). If you have provisioned your content databases through Central Administration or PowerShell under the context of the farm admin service account, you should not see this issue during execution of the Config Wizard.

When running the Config Wizard or psconfig, the ULS and Upgrade logs will reflect an error similar to the below.

The SELECT permission was denied on the object 'MSP_PROJECTS', database 'ContentDatabaseName', schema 'pjpub'.

To resolve this, in the database users, verify the user mapped to the dbo user is the farm admin service account, similar to the below screenshot. This may also impact content databases that were upgraded from previous farms if the previous farm used a different service account for the farm admin service account.

dbo-farm-admin-mapping

Once you have remapped dbo to the farm admin service account, re-run the Config Wizard to complete the upgrade.

This also impacts the January 2020 Public Update if you skipped the December 2019 Public Update.

There is an TechNet thread if you would like to follow along for a potential product-based resolution.

Trevor Seward is a Microsoft Office Apps and Services MVP who specializes in SharePoint Server administration, hybrid scenarios, and SharePoint Online. He has been working with SharePoint for 16 years from SharePoint 2003 on up, managing environments with terabytes of content for 150,000+ user organizations. Trevor is an author of Deploying SharePoint 2016 and Deploying SharePoint 2019. You can find him on Twitter and in /r/sharepoint.